Difference between revisions of "Concept Domain Naming Conventions"
| Line 17: | Line 17: | ||
| − | + | === Example - Domains That Specialize a Root Concept Domain === | |
Where the ['''concept domain'''] is ''ActMood'', and the specialized print name qualifier is ''Proposal'' the specialized concept domain is ''ProposalActMood'' | Where the ['''concept domain'''] is ''ActMood'', and the specialized print name qualifier is ''Proposal'' the specialized concept domain is ''ProposalActMood'' | ||
Revision as of 19:16, 9 June 2009
Contents
Overview
Naming Conventions
Root concept domains are assigned to a specific RIM class attribute or HL7 Abstract Datatype property. The naming standard for all Root concept domains is as follows:
- [RIM Class Name] + [attribute name] or
- [Abstract Datatype Name] + [property name]
For all concept domains that specialize a root concept domain, they're names shall begin with a print name qualifier followed by the root concept domain name.
Example - RIM Class
Where [RIM Class Name] = Act and [attribute name] = Mood, the concept domain is ActMood
Example - Domains That Specialize a Root Concept Domain
Where the [concept domain] is ActMood, and the specialized print name qualifier is Proposal the specialized concept domain is ProposalActMood
Backwards Compatibility
At this time there will be no effort to modify existing concept domains to adhere to the naming conventions specified here. While changing the name of a domain is easy, any modification of an existing domain name will necessitate an update to all models making use of that domain. For the time being, this effort is considered unreasonable and focus will be directed at ensuring new domains are named in accordance with the recommended naming conventions.
