ActReference

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)

The above act, whatever its scope in terms of attributes, represents the same act as all other acts that have one and the same Act.id. It is the equivalent of all other acts that have one and the same id. Designating (in one way or another) that an Act instance is a "minimalistic version of a more fuilly detailed act elsewhere" (which to me is the real underlying use-case) may be a worthy use-case, but any receiver may have a business rule to go look for a more detailed act upon the receipt of an act that doesn't carry enough detail. What's the difference between 4 act instances that all have one and the same ID, but one has only the id attribut, the scond has id,code,status, the third that has id,code,status,value and a fourth that has all possible OBS attributes and associations? Which instances are references to "richer" versions? What is a "reference" for one application is the amount of detail required by another application.. Rene spronk 00:57, 4 May 2007 (CDT)