AlternateDocumentID
DocumentID| Type : IndicativeDataType |
| Elements | |||
| AlternateDocumentID | The DocumentID serves as an identifier of an entity corresponding to the noun instance (i.e., the entity being managed in an interaction). In many cases, trading partner requirements may make it necessary to associate multiple indentifiers for an entity. Only a single DocumentID is permitted within any noun instance, but multiple AlternateDocumentIDs are permitted. | ||
| DocumentID | |||
| DocumentSequence | Intended as an identifier on different instances of a noun in a BOD message instance. It is possible to have a single BOD message instance with both multiple nouns instances and multiple ActionExpressions. In support of this need, every noun is defined with DocumentID and DocumentSequence property elements. The DocumentID serves as an identifier of an entity corresponding to the noun. The DocumentSequence serves as an identifier on the different instances of a noun in a message instance; the sequence numbers are specific to the message instance (i.e. in the case of a message instance with two noun instances, the first noun instance may have a DocumentSequence of "1" and the second noun instance would have a DocumentSequence of "2". | ||
| EmployerIdentifiers | |||
| IndicativePersonDossier | |||
| UserArea | Allows the implementer to extend the base HR-XML specification. This is done by defining the additional information in XML Schema and referencing the new schema in the xml instance document throught the use of namespaces. Once this is done the additional information defined there can be carried in the BOD XML instance document. Allows the implementer to extend the base HR-XML specification. This is done by defining the additional information in XML Schema and referencing the new schema in the xml instance document throught the use of namespaces. Once this is done the additional information defined there can be carried in the BOD XML instance document. | ||
| Attributes | |||
| languageCode | This list is based on Internet Engineering Task Force (IETF) RFCs 4646 and RFC 4647 for language tags. This tag system is extensible to region, dialect, and private designations. The IANA Language Subtag Registry is a source of the tag values. See http://www.iana.org/assignments/language-subtag-registry This is implemented as an HR-XML Open List. Additional values are permitted. | ||
| Attribute Group : EffectiveDateAttributeGroup | |||
| validFrom | This is formatted representation of a date, which may be specified as a date, date/time, year, or year/month. | ||
| validTo | This is formatted representation of a date, which may be specified as a date, date/time, year, or year/month. | ||
| Attribute Group : VersionIDAttributeGroup | |||
| majorVersionID | |||
| minorVersionID | |||