How are components named?
To find a component (type or element), it is helpful to understand how they are named and be aware of the challenges for searching introduced by the inheritance relationships in GJXDM and NIEM.
One design criteria for GJXDM and NIEM is to provide a set of data element names that are relatively complete, semantically precise, and globally understood. The meaning of any given tagname should be determinable within a variety of circumstances, ranging from well-structured documents with rich context to transaction- or message-oriented formats that may be weak in context. To accomplish this goal, GJXDM and NIEM prohibit synonyms and use ISO/IEC Standard 11179 (Specification and Standardization of Data Elements) syntax for naming elements consistently and precisely.
As a result, GJXDM and NIEM have wide applicability and a larger scope, but also longer tagnames. However, it is not difficult to codify the tagnames for transmission efficiency or to apply compression techniques. The Federal XML Developer's Guide requires that XML data element names (tagnames) be specified using the syntax rules of ISO/IEC Standard 11179 (Specification and Standardization of Data Elements). Therefore, all XML data element names contain three basic parts: object class term, property term, and a representation term. Each of these terms may be further supplemented with optional qualifier terms (essentially adjectives), as required to clarify or focus semantic meaning.