Assessment Catalog

Recommendation, 2007 April 15

Editor:

Kim Bartkus, HR-XML Consortium

Authors:

Romuald Restout

Contributors:

Drew Cox, ePredix; Michelle Winston, Gallup; Jason Guarracino, Caliper; Roger St-Amand, Taleo ; Iain Clarke, SHL Group; Reid Klion, PAN Testing ; Jack Ramirez, PSI online; Andrew Fladmark, HireDesk;; David Hetzer, InScope and other members of the Assessment project.

Abstract

This document describes assessment catalog query schema, which allows customers to query an assessment catalog. An assessment catalog provides a description of a test publisher's available "assessment packages" and provides the assessment package identifier necessary to order a particular assessment package.

Table of Contents

1 Overview.. 4

1.1 Objective. 4

1.1.1 Domain Issues. 4

1.1.2 Business Reasons. 4

1.1.3 Terminology. 4

1.2 Design Requirements. 5

1.2.1 Consistency with other HR-XML Assessment specification. 5

1.2.2 Consistency with HR-XML standards and guidelines. 5

1.3 Scope. 5

1.3.1 Items within the Design Scope. 5

1.3.2 Items outside the Design Scope. 5

2 Supported Business Processes. 6

2.1 Actors. 6

2.2 Recruiting Process. 6

2.3 Use Cases. 7

2.3.1 Use Case – Query Assessment Catalog. 8

2.3.2 Use Case – Query Assessment Catalog. 9

3 Schema Design. 11

3.1 AssessmentCatalog. 11

3.1.1 Schema diagram.. 11

3.1.2 Element Definitions. 12

3.2 AssessmentCatalogQuery. 17

3.2.1 Schema diagram.. 17

3.2.2 Element Definitions. 17

4 Implementation Considerations. 19

4.1 General Query. 19

4.2 Data Privacy. 19

5 Appendix A - Document Version History. 19

6 Appendix B – Related Documents. 20

7 Appendix D – Reference Examples. 20

7.1 Assessment Catalog. 20

7.1.1 Example 1. 20

7.1.2 Example 2. 23

7.1.3 Example 3. 23

7.2 Assessment Catalog Query. 23

7.2.1 Example 1. 23

7.2.2 Example 2. 24

1 Overview

The Assessment Catalog specification and schemas support query requests to providers of assessment and testing services. The specification also is designed to support the return of the query results, i.e. the assessment catalog. This specification includes the following schemas:

AssessmentCatalogQuery
AssessmentCatalog

1.1 Objective

1.1.1 Domain Issues

Assessments have always been part of the HR function. At selection or evaluation time, managers have always tried to evaluate the skills of candidates/employees.

Until recently HR systems, customer systems, and the assessment vendor systems are unable to universally exchange information. HR-XML Assessments specification solved this problem.

However, in order to request an assessment (AssessmentOrderRequest message), the customer needs to know the reference of the assessment (packageID) for the provider.

In many cases, the end-user, e.g. a line manager, is not knowledgeable of the packages that have been negotiated and defined by the HR department.

1.1.2 Business Reasons

Assessment providers are continuously enriching their services, and employers are increasingly interested in using these new services. Due to increasing number of assessment providers and increasing number of assessment users, it can be difficult and expensive to maintain an accurate and up-to-date list of available assessments.

Integration is very important since: (1) employers want to keep up on the available services in order to use them, and (2) providers want to distribute the information, so employers can order them thus providing additional revenues.

1.1.3 Terminology

The term “package” describes a collection of elements that define and specify what can be ordered for a Subject from an Assessment Vendor

The term “catalog” describes a compilation of records describing the contents of a particular collection or group of collections. An assessment catalog contains records of assessment packages.

1.2 Design Requirements

1.2.1 Consistency with other HR-XML Assessment specification

The Assessment Catalog specification is part of a set of specifications targeting the Assessment industry that are developed by HR-XML’s Assessment workgroup.

Especially, the workgroup has issued an “Assessments” specification aimed at ordering an Assessment and receiving its results. During the elaboration of this specification, some decisions have been taken in terms of supported business processes and rules, and technical representations.

The Assessment Catalog specification goes along with the Assessments specification and therefore must follow the business and technical decisions that have been made.

1.2.2 Consistency with HR-XML standards and guidelines

The Assessment Catalog specification must follow standards and guidelines as defined by the HR-XML consortium, especially, but not limited to, the ones defined by the Technical Steering Committee.

This includes the existing mechanisms for extending enumerations.

Also, the specification must reuse existing information structures whenever possible, thus ensuring a greater consistency, both at the technical and semantic level, with the rest of HR-XML specifications.

1.3 Scope

1.3.1 Items within the Design Scope

The HR-XML Assessment Catalogue specification provides support for describing and negotiating the content of an Assessment package between two trading partners.

1.3.2 Items outside the Design Scope

General Query.
The HR-XML Assessment Catalogue specification does not provides support for describing and negotiating the content of an Assessment package between two parties that are not trading partners. Still some mechanisms can be used (see Implementation Considerations)
Data Synchronization.
The HR-XML Assessment Catalogue specification does not support the synchronization of data between the assessment provider and consumer.
Reports.
Assessment catalog deals with assessment package that defines the base of what can be ordered to a provider.
Reports may be included within an assessment package, but do not have a separate description from the package.

2 Supported Business Processes

The Assessment Catalog specification is sufficiently generalized to be used in a wide variety of scenarios: employment screening, performance evaluation, training, etc. Its main focus though is on the recruiting process.

2.1 Actors

The transactions supported by this specification are typically between an employer and an assessment service provider. However, assessment transactions also are likely to take place between an assessment service provider and the agent of an employer, such as an Applicant Tracking System or a Staffing company.

2.2 Recruiting Process

The diagram depicted below (Figure 1) illustrates a supported assessment catalog query in the context of recruiting.

Figure 1: Assessment Process (Recruiting Context)

2.3 Use Cases

Figure 2 – Assessment Use Cases

The above diagram identifies all use cases of the Assessment specification, and where the Query Catalog use case fits among all other use cases.

2.3.1 Use Case – Query Assessment Catalog

Figure 3 – Assess a Subject

The above diagram depicts the “Assess a subject” use case that was supported in Assessments 1.0, and illustrates where the “Query Catalog” use case fits in.

Primary Actors: Employer, Assessment Provider, and Candidate

Stakeholders and Interests: Employer/Recruiter - wants to assess candidates.

Precondition:
1. Employer/Recruiter has a business relationship with the assessment vendor.

Minimal Guarantee: A group order request will have a response from the vendor.

Success Guarantee: The assessment provider supplies to the employer/recruiter the assessment results of the subject.

Main Success Scenario

1. The recruiter (or manager) wants a subject to be assessed.

2. The recruiter queries the assessment catalog and selects a package to evaluate against, based on a Trading Partner Agreement (TPA) that was defined when the customer and assessment provider decided to work together.

3. The recruiter requests an assessment.

4. The recruiter can then invite the subject to be assessed using the most appropriate way to communicate this: email with facility address for a proctored assessment, URL for a direct web assessment, etc.
Alternately, subject’s invitation can be done directly by the assessment provider.

5. At some point in time, the subject takes the assessment.

6. Then, the assessment provider processes the subject’s answers, the outcome being the subject’s results. Results can contain an overall score as well as detailed scores.
The assessment provider then passes the assessment results to the recruiter who includes them into the selection decision.

Extensions

3a. Employer directs applicant to web site and provides the applicant with the access code(s) returned by the vendor.

2.3.2 Use Case – Query Assessment Catalog

Primary Actors: Assessment Orderer, Assessment Provider, Client

Stakeholders and Interests:

Assessment Orderer - wants to obtain list of assessment packages to enable subsequent construction an AssessmentOrderRequest.

Preconditions:

Client and Assessment Vendor have a business relationship defining the assessment packages available for that client and the billing arrangements.
The Assessment Vendor and Assessment Orderer have a business and technical relationship enabling them to exchange HR-XML documents.

Minimal Guarantee: All delivered catalog queries will receive an acknowledgement.

Success Guarantee: On receipt of a valid query, the Assessment Provider will supply the Assessment Orderer with a list of assessment packages available for a particular Client.

Main Success Scenario:

1. Assessment Orderer requires an updated list of assessment packages available from an Assessment Provider for a particular Client.

2. Assessment Orderer sends an Assessment Catalog Request to the Assessment Provider, including the target Client ID.

3. Assessment Provider validates the request, constructs an Assessment Catalog Response and sends it back to the Assessment Orderer. The response would include assessment package ids and suitable descriptive information.

4. Assessment Orderer uses information in Assessment Catalog Response to select an assessment package id when constructing an AssessmentOrderRequest.

Failure Scenario:

If the Assessment Provider determines the Assessment Catalog Request contains invalid information (e.g. an unknown Client ID) they will return an error indicator in the Assessment Catalog Response.

Alternate Scenario:

The diagram depicted in Figure 4 illustrates an alternate supported scenario for querying a provider’s catalog.

In this scenario, Assessment provider is queried first in order to get a “short list” of assessments that meet the criteria. The set of information that is provided at this time is somewhat limited. Then the customer requests details on a specific package. In this case the set of information provided is much more extensive.

Figure 4: Alternate Query Process

3 Schema Design

3.1 AssessmentCatalog

3.1.1 Schema diagram

3.1.2 Element Definitions

Elements and Attributes [Global types listed alphabetically in following table.]	ContentModel* Data type Occurrence: Sequence \| Choice \| All (minOccurs/maxOccurs) Attributes	Definition
/ AssessmentCatalog	- AssessmentCatalogType - (1/1)	Contains information to describe the vendor's assessment package catalog.
/ AssessmentCatalog/ ClientId	- EntityIdType - S (0/1)	A value that uniquely identifies a client for the 3rd party vendor (assessor). It is up to the vendor to provide the client its identifier. [BusinessRule(s): The client id is mandatory for all messages going from a customer to an assessment vendor. ]
/ AssessmentCatalog/ ProviderId	- EntityIdType - S (0/1)	A unique identifier for the provider. Context definition: A value that uniquely identifies an assessment provider for the customer. The client specifies this to the provider. [BusinessRule(s): Assessment: The provider id should be filled for all messages going from a customer to an assessment vendor ]
/ AssessmentCatalog/ CatalogQueryStatus	Status - xsd:string - S (1/1) Details - xsd:string - S (0/1)
/ AssessmentCatalog/ CatalogQueryStatus/ Status	xsd:restriction base: xsd:string [Enumerations]: Match Found, No Match Found, Error	The status of the associated item. If the status isn't specified, the implementer may place the record in whatever status seems appropriate given the context of the data.
/ AssessmentCatalog/ CatalogQueryStatus/ Details	- xsd:string - S (0/1)	Describes any information not previously defined.
/ AssessmentCatalog/ AssessmentPackage	- AssessmentPackageType - S (1/*)	Contains characteristics of an assessment product available for ordering from an assessment vendor.
/ AssessmentCatalog/ AssessmentPackage/ PackageId	- EntityIdType - S (1/1)	A unique identifier for a Background Search or Assessment Package. Context definition: Identifies the package of assessments being ordered for the Subject. Package Ids are supplied by the Assessment Vendor to the Client in a Trading Partner Agreement.
/ AssessmentCatalog/ AssessmentPackage/ PackageGroupId	- EntityIdType - S (0/*)	A unique identifier for the group to which the package belongs. [BusinessRule(s): Groups of packages and any dependencies or relationships between them would be established by the assessment provider ]
/ AssessmentCatalog/ AssessmentPackage/ Name	- xsd:string - S (1/1)	A descriptive identifier within the given context. Context definition: The name or title of the assessment package, possibly for User Interface display to assist in selection.
/ AssessmentCatalog/ AssessmentPackage/ Description	- xsd:string - S (0/1)	Describes the contextual information relating to a specific element. Context definition: A longer description of the assessment package, possibly for User Interface display to assist in selection.
/ AssessmentCatalog/ AssessmentPackage/ PricingInfo	- xsd:string - S (0/1)	Contains information about the cost or estimated cost of a product or service levied by the vendor. [BusinessRule(s): String type for unit flexibility and to discourage use in monetary calculations. ]
/ AssessmentCatalog/ AssessmentPackage/ AdministrationInfo	AdministrationNotes - xsd:string - S (0/1) IsProctored - xsd:boolean - S (0/1) IsTimeEnforced - xsd:boolean - S (0/1) EstimatedTime - xsd:string - S (0/1) AssessmentDelivery - AssessmentDeliveryTypes - S (0/*)	Context definition: Contains information about how the assessment is administered to a subject.
/ AssessmentCatalog/ AssessmentPackage/ AdministrationInfo/ AdministrationNotes	- xsd:string - S (0/1)	Context definition: Notes concerning the administration of this assessment package.
/ AssessmentCatalog/ AssessmentPackage/ AdministrationInfo/ IsProctored	- xsd:boolean - S (0/1)	Indicates if the assessment package should be administered in a proctored environment.
/ AssessmentCatalog/ AssessmentPackage/ AdministrationInfo/ IsTimeEnforced	xsd:extension base: xsd:boolean maxTimeAllowed - xsd:duration - optional	Indicates whether there is a time limit for performing a time sensitive action.
/ AssessmentCatalog/ AssessmentPackage/ AdministrationInfo/ IsTimeEnforced/ maxTimeAllowed	- xsd:duration -	If a time sensitive action is required, this element indicates the maximum time allowed to complete the action. [Example(s): Allow 30 minutes to complete an assessment test; This form must be returned within three days. ]
/ AssessmentCatalog/ AssessmentPackage/ AdministrationInfo/ EstimatedTime	- xsd:string - S (0/1)	Context definition: Estimated time to complete the assessment package, possibly for User Interface display to the subject.
/ AssessmentCatalog/ AssessmentPackage/ AdministrationInfo/ AssessmentDelivery	xsd:extension base: AssessmentDeliveryTypes schedulingRequired - xsd:boolean -	Identifies or describes how the assessment is delivered.
/ AssessmentCatalog/ AssessmentPackage/ AdministrationInfo/ AssessmentDelivery/ schedulingRequired	- xsd:boolean -	Context definition: Defines if the assessment delivery type requires scheduling before the actual delivery.
/ AssessmentCatalog/ AssessmentPackage/ ResultInfo	ResultProfile - xsd:string - S (0/1) Description - xsd:string - S (0/1) ResultLanguage - xsd:language - S (0/1)	Information on the results report.
/ AssessmentCatalog/ AssessmentPackage/ ResultInfo/ ResultProfile	- xsd:string - S (0/1)	Context definition: Lists the AssessmentResult scoring profiles generated for this assessment package.
/ AssessmentCatalog/ AssessmentPackage/ ResultInfo/ Description	- xsd:string - S (0/1)	Describes the contextual information relating to a specific element. Context definition: A longer description of the assessment package, possibly for User Interface display to assist in selection.
/ AssessmentCatalog/ AssessmentPackage/ ResultInfo/ ResultLanguage	- xsd:language - S (0/1)	The language in which results are available.
/ AssessmentCatalog/ AssessmentPackage/ Applicability	CompetencyAssessed - AssessmentCompetencyReferenceType - S (0/) AssessmentLanguage - xsd:language - S (0/) ApplicableRegion - xsd:string - S (0/) AssessmentTarget - xsd:string - S (0/) AssessmentJobCategory - xsd:string - S (0/) AssessmentJobLevel - xsd:string - S (0/)	Elements which are relevant to a particular context. [Example(s): May include elements relevant to an assessment package or position requirement. ]
/ AssessmentCatalog/ AssessmentPackage/ Applicability/ CompetencyAssessed	- AssessmentCompetencyReferenceType - S (0/*)	References the competencies the assessment is intended to evaluate. [BusinessRule(s): This approach provides complete decoupling from the Compentencies working group in the Assessments Core Schemas. The extension mechanism is used to hold the compentencies associated with the Assessment Package. ]
/ AssessmentCatalog/ AssessmentPackage/ Applicability/ AssessmentLanguage	- LanguageCodeType - S (0/*)	The language in which the assessment is available or was taken. [BusinessRule(s): Available languages might be obtained from AssessmentLanguage within AssessmentCatalog.]
/ AssessmentCatalog/ AssessmentPackage/ Applicability/ ApplicableRegion	- xsd:string - S (0/*)	Context definition: The geographic region for which an assessment is suitable for use. This is used to distinguish assessments that may be designed for use in specific localities due to factors such as norming and legal issues.
/ AssessmentCatalog/ AssessmentPackage/ Applicability/ AssessmentTarget	- xsd:string - S (0/*)	Identifies or describes what the assessment is intended to target. [Example(s): A high-level description might include knowledge, skills, psychometrics, etc. Specific competencies could be specified within CompetencyAssessed. ]
/ AssessmentCatalog/ AssessmentPackage/ Applicability/ AssessmentJobCategory	- xsd:string - S (0/*)	A grouping of jobs under one or more classification schemes that is meaningful to an organization.
/ AssessmentCatalog/ AssessmentPackage/ Applicability/ AssessmentJobLevel	- xsd:string - S (0/*)	A grouping of similar jobs in terms of function, job duties, tasks, responsibilities, job evaluation method, or similarity in pay philosophy. [Example(s): S1 job step within "Web Site Developer" job type in the "Developer" job family ]

Global types (alphabetically listed)	ContentModel* Data type Occurrence: Sequence \| Choice \| All (minOccurs/maxOccurs) Attributes	Definition
/ [AssessmentCatalogType]	xml:lang - - ClientId - EntityIdType - S (0/1) ProviderId - EntityIdType - S (0/1) CatalogQueryStatus - xsd:string - S (1/1) AssessmentPackage - AssessmentPackageType - S (0/*) UserArea - [see include/import] - S (0/1)	Globally scoped data type. See element or attribute declaration for definition.
/ [AssessmentDeliveryTypes]	xsd:restriction base: xsd:string [Enumerations]: online, telephone, mail, fax	Globally scoped data type. See element or attribute declaration for definition.
/ [AssessmentPackageType]	validFrom - AnyDateTimeNkNaType - optional validTo - AnyDateTimeNkNaType - optional PackageId - EntityIdType - S (1/1) PackageGroupId - EntityIdType - S (0/) Name - xsd:string - S (1/1) Description - xsd:string - S (0/1) PricingInfo - xsd:string - S (0/1) AdministrationInfo - xsd:boolean - S (0/1) ResultInfo - [complexType] - S (0/) Applicability - [complexType] - S (1/1) UserArea - [see include/import] - S (0/1)	Globally scoped data type. See element or attribute declaration for definition.
/ [AssessmentPackageType] / validFrom	- AnyDateTimeNkNaType -	The date the event begins, is active or valid. [BusinessRule(s): This date is inclusive. Dates are represented in accordance with ISO 8601. ]
/ [AssessmentPackageType] / validTo	- AnyDateTimeNkNaType -	The date through which the event is active or valid, or the date the event ends. [BusinessRule(s): This date is inclusive. Dates are represented in accordance with ISO 8601. ]
/ [SpecifiedCompetency ReferenceType]	CompetencyId - EntityIdType - S (1/1) ProficencyLevel - xsd:string - S (0/1)	Globally scoped data type. See element or attribute declaration for definition.
/ [SpecifiedCompetency ReferenceType]/ CompetencyId	- EntityIdType - S (1/1)	An identification code assigned to identify or classify the Competency. [BusinessRule(s): A taxonomy might include an indentification code for each Competency or identification codes might be agreed upon by trading partners. ]
/ [SpecifiedCompetency ReferenceType]/ ProficencyLevel	- xsd:string - S (0/1)	Indicates the level of proficiency. [BusinessRule(s): The scale and meaning of the proficiency level value is determined within the context of the particular competency taxonomy referenced.]

3.2 AssessmentCatalogQuery

3.2.1 Schema diagram

3.2.2 Element Definitions

Elements and Attributes [Global types listed alphabetically in following table.]	ContentModel* Data type Occurrence: Sequence \| Choice \| All (minOccurs/maxOccurs) Attributes	Definition
/ AssessmentCatalogQuery	- AssessmentCatalogQueryType - (1/1)	Container for the request of a vendor's catalog of assessment packages.
/ AssessmentCatalogQuery/ ClientId	- EntityIdType - S (0/1)	A value that uniquely identifies a client for the 3rd party vendor (assessor). It is up to the vendor to provide the client its identifier. [BusinessRule(s): The client id is mandatory for all messages going from a customer to an assessment vendor. ]
/ AssessmentCatalogQuery/ Filter	- FilterType - S (1/1)	Used to restrict the result set of the query.
/ AssessmentCatalogQuery/ Filter/ FilterString	xsd:extension base: xsd:string type - [Union]: FilterStringTypeType, xStringPatternExtensionType - - required	A complete query string, in any query language.
/ AssessmentCatalogQuery/ Filter/ FilterString/ type	- [Union]: FilterStringTypeType, xStringPatternExtensionType	Further defines the associated element in the context provided.
/ AssessmentCatalogQuery/ Filter/ SimpleExpression	- SimpleExpressionType - C (1/*)	A structured query, as opposed to the query string.
/ AssessmentCatalogQuery/ Filter/ SimpleExpression/ ElementName	- xsd:string - S (1/1)	Context definition: The name of the element, upon which the assessment consumer wants to query.
/ AssessmentCatalogQuery/ Filter/ SimpleExpression/ Operator	- [Union]: SimpleExpressionOperatorType, xStringPatternExtensionType	Allows for determining how database information is compared to a query criterion.
/ AssessmentCatalogQuery/ Filter/ SimpleExpression/ ElementValue	- xsd:string - S (1/1)	Context definition: The value of the element, upon which the assessment consumer wants to query.
/ AssessmentCatalogQuery/ Filter/ Unfiltered	xsd:restriction base: xsd:string	Context definition: The assessment consumer requests no filter be applied to the catalog. [BusinessRule(s): The result from this request is a complete, unfiltered, catalog. ]
/ AssessmentCatalogQuery/ ProviderId	- EntityIdType - S (0/1)	A unique identifier for the provider. [BusinessRule(s): The provider id should be filled for all messages going from a customer to an assessment vendor ]

Global types (alphabetically listed)	ContentModel* Data type Occurrence: Sequence \| Choice \| All (minOccurs/maxOccurs) Attributes	Definition
/ [AssessmentCatalogQueryType]	ClientId - EntityIdType - S (0/1) Filter - FilterType - S (1/1) ProviderId - EntityIdType - S (0/1) UserArea - [see include/import] - S (0/1)	Globally scoped data type. See element or attribute declaration for definition.
/ [FilterStringTypeType]	xsd:restriction base: xsd:string [Enumerations]: xpath, xquery, sql	Globally scoped data type. See element or attribute declaration for definition.
/ [FilterType]	FilterString - xsd:string - C (1/1) SimpleExpression - SimpleExpressionType - C (1/*) Unfiltered - xsd:string - C (1/1)	Globally scoped data type. See element or attribute declaration for definition.
/ [SimpleExpressionOperatorType]	xsd:restriction base: xsd:string [Enumerations]: equals, not equals, greater than, less than, like	Globally scoped data type. See element or attribute declaration for definition.
/ [SimpleExpressionType]	ElementName - xsd:string - S (1/1) Operator - [complexType] - S (1/1) ElementValue - xsd:string - S (1/1)	Globally scoped data type. See element or attribute declaration for definition.

4 Implementation Considerations

4.1 General Query

As explained in the design scope section, the specification is not aimed at querying the catalog of an assessment provider when no business relationships exist.

However, this case may be partially supported when omitting the clientId element in the catalog query.

4.2 Data Privacy

Human resources data, by its very nature, is personal data. The laws of many jurisdictions as well as codes of fair information practice require organizations to handle personal data in a way that protects individuals from loss of privacy.

The data exchange specifications developed by the HR-XML Consortium are designed to be useful across many jurisdictions and within a variety of business contexts. It is not feasible for the HR-XML Consortium to develop specific privacy guidance for every jurisdiction or business context in which the Consortium's specifications might be implemented. When implementing data exchanges using the HR-XML Consortium's data definitions (or, for that matter, using any other type of data exchange mechanism), organizations are advised to examine the privacy protections that may be required under applicable law and codes of fair information practice.

For information on protecting personal data, general references include: European Union Data Protection Directive (95/46/EC); the Association Computing Machinery Code of Ethics (1992); Canadian Standards Association Model Code for the Protection of Personal Information (1995 – PIPEDA); and U.S.-EU Safe Harbor Principles and FAQs (2000).

5 Appendix A - Document Version History

Date	Description
2004-Dec-14	Draft
2005-Apr-25	Updated diagrams, tables, examples based on workgroup schema changes.
2005-May-02	Updated tables, added example text.
2006-Feb-28	Approved by Consortium
2007-April-15	Updated for 2_5 Release, Approved

6 Appendix B – Related Documents

Reference	Link
Assessment Catalog Schema	http://ns.hr-xml.org/2_5/HR-XML-2_5/Assessment/AssessmentCatalog.xsd
Assessment Catalog Query Schema	http://ns.hr-xml.org/2_5/HR-XML-2_5/Assessment/AssessmentCatalogQuery.xsd
Assessments Document	http://ns.hr-xml.org/2_5/HR-XML-2_5/Assessment/Assessments.html
Assessment Catalog Examples	http://ns.hr-xml.org/2_5/HR-XML-2_5/Assessment/AssessmentCatalog.xml http://ns.hr-xml.org/2_5/HR-XML-2_5/Assessment/AssessmentCatalog2.xml http://ns.hr-xml.org/2_5/HR-XML-2_5/Assessment/AssessmentCatalog3.xml
Assessment Catalog Query Examples	http://ns.hr-xml.org/2_5/HR-XML-2_5/Assessment/AssessmentCatalogQuery.xml http://ns.hr-xml.org/2_5/HR-XML-2_5/Assessment/AssessmentCatalogQuery2.xml

7 Appendix D – Reference Examples

7.1 Assessment Catalog

7.1.1 Example 1

This example returns an AssessmentCatalog with 3 matching assessment packages. Each assessment package demonstrates the different range of results that may be returned with a successful query. This document would be returned when the search criteria is matched against 3 existing assessment packages in the vendor system.

<IdValue>PSI_Example_Only</IdValue>

</ProviderId>

<Status>Match Found</Status>

<Details>3 matching assessment packges found.</Details>