An object may be labeled for human identification where the Name may indicate a well-known identifier. While there is no restriction on usage of such identifier, it is recommended the Name is unique within it's containing scope. Further guidance on usage is provided at specific entities; for example, for spaces, the Name may reflect a room number. An object may have a description provided via the Description attribute that provides further context in identifying or locating the object.
Specific subtypes introduce additional attributes for the Object User Identity template.
Spatial objects may be further identified via the LongName attribute. This value should generally correspond to building signage describing floor levels or rooms. While the Name attribute generally provides a coded or abbreviated identifier, the LongName provides a functional name for the location such as "Reception Area". See concept template Spatial Element Occurrence Attributes
Physical elements may be further identified via the Tag attribute. This is a human readable identifier such as an element or item number While there is no restriction on usage of such tags, it is recommended the Tag is unique within it's containing scope. See concept template Element Occurrence Attributes
The following diagram shows the generic classes and relationships used when applying this concept.
In addition, concepts may have particular importance to common or standardised industry practices and scenarios. For these specific usage scenarios, the table below shows a recommended list of general usage patterns that users may adopt.