This wiki has undergone a migration to Confluence found Here
Difference between revisions of "Types of Identifiers"
Jump to navigation
Jump to search
Charliemccay (talk | contribs) |
Charliemccay (talk | contribs) |
||
| Line 1: | Line 1: | ||
Historically, it has not been possible to differentiate between identifiers in the II datatype. However, an MnM resolution at the May, 2006 WGM recommending the introduction of an II.useCode property should differentiate this (see the [[Datatypes R2 Issue 57]] proposal). | Historically, it has not been possible to differentiate between identifiers in the II datatype. However, an MnM resolution at the May, 2006 WGM recommending the introduction of an II.useCode property should differentiate this (see the [[Datatypes R2 Issue 57]] proposal). | ||
| + | Note that the proposal includes a list of types that are not mutualy exclusive, and so various combinations are permitted. | ||
*''Business Identifier'': This is a commonly used identifier associated with a particular object. It is often a publicly exposed identifier which is known to providers and may be printed on reports or forms. It remains consistent as a class undergoes state transitions, including suspend, resume, revise, abort and complete. It is the truest identifier of the "object", given the MnM paradigm that an object persists across state transitions. | *''Business Identifier'': This is a commonly used identifier associated with a particular object. It is often a publicly exposed identifier which is known to providers and may be printed on reports or forms. It remains consistent as a class undergoes state transitions, including suspend, resume, revise, abort and complete. It is the truest identifier of the "object", given the MnM paradigm that an object persists across state transitions. | ||
| Line 5: | Line 6: | ||
*''Version Identifier'': This is a type of identifier introduced in some jurisdictions to allow referencing a particular business object as it existed at a given point in time. They can be considered identifiers of a static snapshot of the object. This type of identifier changes with each state transition on the object. I.e. The version identifier of an object prior to a 'suspend' state transition is distinct from the identifier of the object after the state transition. Each version identifier can be tied to exactly one ControlAct event which brought that version into being. | *''Version Identifier'': This is a type of identifier introduced in some jurisdictions to allow referencing a particular business object as it existed at a given point in time. They can be considered identifiers of a static snapshot of the object. This type of identifier changes with each state transition on the object. I.e. The version identifier of an object prior to a 'suspend' state transition is distinct from the identifier of the object after the state transition. Each version identifier can be tied to exactly one ControlAct event which brought that version into being. | ||
| − | *''Information Instance Identifier'': This is an identifier for the exact information items that are included within a static model instance. This identifies a view of the business object at a particular point in time, and as such identifies a set of data items that can be digitally signed and/or attested. This is in contrast to the ''Version Identifier'' which identifies the object at a specific time, but not the amount of information being asserted about the object. | + | *''Information Instance Identifier'': This is an identifier for the exact information items that are included within a static model instance. This identifies a view of the business object at a particular point in time, and as such identifies a set of data items that can be digitally signed and/or attested. This is in contrast to the ''Version Identifier'' which identifies the object at a specific time, but not the amount of information being asserted about the object. This identifier would be changed when a transformation of the information is performed (eg to add code translations, to provide a simplified textual rendering, or to provide additional information about the object as it existed at the specific point in time). Note that the ''Information Instance Identifier'' may be conveyed with all its information items "byValue" or with none or some "byReference". These additional use codes allow Information Instance Identifiers to be use d when only enough information for populating a picklist is needed, with the full inforomation instance being retreived if needed. |
| + | |||
| + | *''byValue'' and ''byReference'' | ||
| + | These make sense in the context of Information Instance Identifiers only, and are discussed in that section of this page. | ||
See [[Types of Updates]] for a discussion of the link between [[Types of Identifier]] and updates of objects. | See [[Types of Updates]] for a discussion of the link between [[Types of Identifier]] and updates of objects. | ||
Revision as of 09:52, 15 August 2006
Historically, it has not been possible to differentiate between identifiers in the II datatype. However, an MnM resolution at the May, 2006 WGM recommending the introduction of an II.useCode property should differentiate this (see the Datatypes R2 Issue 57 proposal). Note that the proposal includes a list of types that are not mutualy exclusive, and so various combinations are permitted.
- Business Identifier: This is a commonly used identifier associated with a particular object. It is often a publicly exposed identifier which is known to providers and may be printed on reports or forms. It remains consistent as a class undergoes state transitions, including suspend, resume, revise, abort and complete. It is the truest identifier of the "object", given the MnM paradigm that an object persists across state transitions.
- Version Identifier: This is a type of identifier introduced in some jurisdictions to allow referencing a particular business object as it existed at a given point in time. They can be considered identifiers of a static snapshot of the object. This type of identifier changes with each state transition on the object. I.e. The version identifier of an object prior to a 'suspend' state transition is distinct from the identifier of the object after the state transition. Each version identifier can be tied to exactly one ControlAct event which brought that version into being.
- Information Instance Identifier: This is an identifier for the exact information items that are included within a static model instance. This identifies a view of the business object at a particular point in time, and as such identifies a set of data items that can be digitally signed and/or attested. This is in contrast to the Version Identifier which identifies the object at a specific time, but not the amount of information being asserted about the object. This identifier would be changed when a transformation of the information is performed (eg to add code translations, to provide a simplified textual rendering, or to provide additional information about the object as it existed at the specific point in time). Note that the Information Instance Identifier may be conveyed with all its information items "byValue" or with none or some "byReference". These additional use codes allow Information Instance Identifiers to be use d when only enough information for populating a picklist is needed, with the full inforomation instance being retreived if needed.
- byValue and byReference
These make sense in the context of Information Instance Identifiers only, and are discussed in that section of this page.
See Types of Updates for a discussion of the link between Types of Identifier and updates of objects.
