This wiki has undergone a migration to Confluence found Here

Difference between revisions of "TemplateId"

From HL7Wiki
Jump to navigation Jump to search
Line 1: Line 1:
A globally unique, non-semantic, identifier for the Template. This is the primary identifier for all [[Template]]s. A globally unique reference that can be used by look-up services and registries in an international distributed computing environment, and can be stored within each instance as a permanent record of the knowledge artefact to which it conforms.
+
A globally unique, non-semantic, identifier for the Template. This is the primary identifier for all [[Template]]s.  
  
Note [[Constraints on infrastructureRoot attributes]]
+
TemplateId is a globally unique reference that can be used by look-up services and registries in an international distributed computing environment, and can be stored within each instance as a permanent record of the knowledge artefact to which it conforms.
 +
 
 +
Notes:
 +
*The constraint applies from the "point of occurrence" (of the templateId attribute) in the model. A sender can assert any templateID anywhere they like. It can be ignored by receivers.
 +
*There's no reason to prohibit the declaration of any templates at all, because the declaration of non-recognized templates has no impact on the receiver. Prohibiting custom templates would be similar to prohibiting local extensions, which you're also not allowed to do.
 +
*If an application rejects a message because that message contains a template the application doesn't recognize, that application would be considered non-conformant.
 +
*(discussion)The use of specific templateId may be constrained, see [[Constraints on infrastructureRoot attributes]]

Revision as of 08:19, 8 September 2006

A globally unique, non-semantic, identifier for the Template. This is the primary identifier for all Templates.

TemplateId is a globally unique reference that can be used by look-up services and registries in an international distributed computing environment, and can be stored within each instance as a permanent record of the knowledge artefact to which it conforms.

Notes:

  • The constraint applies from the "point of occurrence" (of the templateId attribute) in the model. A sender can assert any templateID anywhere they like. It can be ignored by receivers.
  • There's no reason to prohibit the declaration of any templates at all, because the declaration of non-recognized templates has no impact on the receiver. Prohibiting custom templates would be similar to prohibiting local extensions, which you're also not allowed to do.
  • If an application rejects a message because that message contains a template the application doesn't recognize, that application would be considered non-conformant.
  • (discussion)The use of specific templateId may be constrained, see Constraints on infrastructureRoot attributes