This wiki has undergone a migration to Confluence found Here
Difference between revisions of "ActReference"
Jump to navigation
Jump to search
(→Issue) |
|||
Line 13: | Line 13: | ||
**How do I distinguish different versions of the same object? | **How do I distinguish different versions of the same object? | ||
**How do I handle "snapshot" references? | **How do I handle "snapshot" references? | ||
+ | |||
+ | Note that Datatypes R2 will add use to II. One of the use codes is | ||
+ | Reference - so you could use this to make the Act as a reference. | ||
+ | But I believe that this is wrong - it's the Act that is the reference, | ||
+ | not the ID in the act. --[[User:GrahameGrieve|GrahameGrieve]] 11:56, 3 May 2007 (CDT) | ||
+ | |||
==Discussion== | ==Discussion== | ||
==Guidance== | ==Guidance== |
Revision as of 16:56, 3 May 2007
What is an Act Reference
Act References have been defined by committees per MnM guidance like the following:
Issue
There are a number of issues:
- The only thing that really identifies this as an ActReference is the clone class name, violating the rule that Clone Class names don't add semantics.
- It could be argued the fact that since there is no other information in the class, aside from classCode, moodCode, or ID, it must be a reference.
- This doesn't satisfy all reference requirements.
- How do I know how much of the Act and its descendent's are intended to be referenced?
- How do I distinguish different versions of the same object?
- How do I handle "snapshot" references?
Note that Datatypes R2 will add use to II. One of the use codes is Reference - so you could use this to make the Act as a reference. But I believe that this is wrong - it's the Act that is the reference, not the ID in the act. --GrahameGrieve 11:56, 3 May 2007 (CDT)