Docs for schema item EffectiveDateAttributeGroup in HR-XML

HR-XML's 3.0 architecture makes a distinction between effective-date meta data and effective dating that is an integral part of the data model for the particular component. For example, a License typically has as an integral part of its data model, a start date and end date during which it is effective. This might be expressed using StartDate and EndDate components. Where there is the need to provide “effective dating” metadata for a component the standard approach to be used across the 3.0 library will be use EffectiveDateAttributeGroup. For example, a PersonName does not include effective dating as an integral part of its data model, but effective date meta date may be necessary for accurate processing or handling of a PersonName. Note also in some cases, a component that has effective dating as part of its data model may also have effective datng meta data. For example, EmploymentHistory includes dating relevant to the tenure of a person at an employer and within a position. Effective dating meta data (using the EffectiveDateAttributeGroup) also could be valuable on EmploymentHistory to distinquish among different versions of the same persons history.

<xsd:attributeGroup name="EffectiveDateAttributeGroup"> <xsd:annotation> <xsd:documentation>HR-XML's 3.0 architecture makes a distinction between effective-date meta data and effective dating that is an integral part of the data model for the particular component. For example, a License typically has as an integral part of its data model, a start date and end date during which it is effective. This might be expressed using StartDate and EndDate components. Where there is the need to provide “effective dating” metadata for a component the standard approach to be used across the 3.0 library will be use EffectiveDateAttributeGroup. For example, a PersonName does not include effective dating as an integral part of its data model, but effective date meta date may be necessary for accurate processing or handling of a PersonName. Note also in some cases, a component that has effective dating as part of its data model may also have effective datng meta data. For example, EmploymentHistory includes dating relevant to the tenure of a person at an employer and within a position. Effective dating meta data (using the EffectiveDateAttributeGroup) also could be valuable on EmploymentHistory to distinquish among different versions of the same persons history.</xsd:documentation> </xsd:annotation> <xsd:attribute name="validFrom" type="FormattedDateTimeType" use="optional" /> <xsd:attribute name="validTo" type="FormattedDateTimeType" use="optional" /> </xsd:attributeGroup>

Definition Type:	AttributeGroup
Name:	EffectiveDateAttributeGroup
Namespace:	http://www.hr-xml.org/3
Containing Schema:	Fields.xsd
Documentation:	HR-XML's 3.0 architecture makes a distinction between effective-date meta data and effective dating that is an integral part of the data model for the particular component. For example, a License typically has as an integral part of its data model, a start date and end date during which it is effective. This might be expressed using StartDate and EndDate components. Where there is the need to provide “effective dating” metadata for a component the standard approach to be used across the 3.0 library will be use EffectiveDateAttributeGroup. For example, a PersonName does not include effective dating as an integral part of its data model, but effective date meta date may be necessary for accurate processing or handling of a PersonName. Note also in some cases, a component that has effective dating as part of its data model may also have effective datng meta data. For example, EmploymentHistory includes dating relevant to the tenure of a person at an employer and within a position. Effective dating meta data (using the EffectiveDateAttributeGroup) also could be valuable on EmploymentHistory to distinquish among different versions of the same persons history.