 AccessPoint | A set of information about the location of a screening report and information to access it.The access point could be the location for a report or it could be a location where the candidate or recruiter is instructed to enter additional information. The typeCode could be used to distinquish the purpose. |
| AssessmentDetailedResult | |
| AssessmentOverallResult | A high-level or summary result for an assessment or appraisal. Can indicate whether or not there was a satisfactory result (PassedIndicator) as well as include some type of overall socre or a "rolled up" average or weighted average of component scores. |
| AssessmentProfileID | Uniquely distinquishes the normative group associate with the score(s). In the case of pre-hire and promotional assessments, this might be a Position ID or other identifier that could be used as a key in identifying the group of candidates in the normative group. |
| AssessmentStatus | |
| Attachment | |
| ID | |
| Name | Identifies the Name of the object in which associated. |
| PackageID | The "package" concept is used within both the employment screening and assessment domains. A package is a screening or a collection of screenings (or assessment or a collection of assessments) that are referenced when ordering services. The package concept greatly simplifies the ordering process. A PackageID is a unique identifier for the package. PackageIDs are developed and assigned by the service provider. Packages can be customized per client or standardized for offerings for multiple clients. |
| TestInstance | |
| 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.
|
| 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. |
| 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. |