ERRATA: An error existed in the version of Candidate.xsd originally included in the 2_5 release. RelatedPositionPostings is an optional element. By error it was required in the version released on 2007-04-15. This has been corrected within the 2_5 release package. RelatedPositionPostings is optional as it was in prior releases. An instance valid against the uncorrected version will still be valid against the corrected version.

1 Overview

The landscape that defines the Recruiting and Staffing world today is vastly more fragmented and complex than the landscape of even five years ago. Every part of the hiring process has been broken apart, enhanced and web-enabled to allow greater efficiencies to be realized. It also allows the possibility that a wide variety of technology and service providers can be involved in a single hire. Job boards, staffing company systems, applicant tracking systems, resume parsers, assessment systems, employment screening – and of course the hiring company’s ERP, HRIS or Procurement systems---all are potential points of data exchange in the hiring process. Since every one of these systems is configured somewhat differently, the need for standards in the data exchanged is clear.

1.1 Objective

The Staffing Exchange Protocol (SEP) is a set of XML specifications that support many types of recruiting and staffing related transactions. Transactions supported by the Staffing Exchange Protocol include the posting of job or position opportunities to job boards and the exchange of a candidate resume and/or profile data independent of or related to those postings to other recruiting and sourcing venues.

SEP 2.0 was designed with multi-national input from a variety of stakeholder groups including hiring organizations, staffing companies, job boards/career portal sites, applicant tracking systems and service providers, assessment providers and HRIS vendors.

Staffing Exchange Protocol consists of the following document types and outlines the transactions they facilitate:

· Resume

· Candidate

· Position Opening

1.2 New In This Version

To enable the end-to-end tracking of search metadata throughout the recruiting process and to support compliance with U.S. Office of Contract Compliance Programs (OFCCP) recruiting record keeping requirements optional elements have been added to the PositionOpening and Candidate schemas.

SearchCriteria has been added as an optional element within the PositionDetail node:

PositionOpening/PositionProfile/PositionDetail/SearchCriteria

Optional SearchCriteria and SearchResult elements also have been added to the optional and repeatable PositionPosting node:

Candidate/RelatedPositionPostings/PositionPosting/SearchCriteria
Candidate/RelatedPositionPostings/PositionPosting/SearchResult

These changes are fully described in the separate Search Types specification. See Appendix B – Related Documents.

1.3 Specification Enhancements and Corrections

As this specification was implemented with various trading partners, the implementers identified possible errors and enhancements. The Recruiting workgroup collected and reviewed these issues, resulting in a list of changes. Some of the issues require modeling, detailed analysis, and non-backwards compatible changes. Those issues will be resolved in a future version of Staffing Exchange Protocol. This current version will only include minor, backwards compatible changes.

SharedStaffingModules, Organization, and EducationHistory are Cross-Process Objects residing in the CPO folder. Details on Organization and EducationHistory changes are covered in their respective documents. All other details will be handled in this document. Note that changes were also made to Resume, which are defined in the Resume document. See Appendix A - Document Version History for changes.

1.4 Terminology

1.4.1 Resume vs. Candidate Profile

A Candidate Profile may be described as a set of data pertaining to a job seeker that has been compiled and structured in a way to optimize automated matching of supply and demand for talent. Candidate profiles are created to capture overall work related preferences, skills and historical information that are not specific to a particular position. A resume, however, is frequently customized to particular positions, so that the most relevant information is emphasized. There is usually a core intersection of common data between a Resume and a Candidate Profile. However, a resume can include some data not included in a corresponding Candidate Profile and vice versa. For instance, a resume may include “avocational” information (hobbies, and personal interests) and histories of publications, patents, presentations, awards, or similar information not generally used for matching against position requirements. A resume on the other hand, would not typically include details on the job seeker’s work preferences and salary requirements. While a Candidate profile may exclude some of the information included in a corresponding Resume or CV, it might support the ability to link to or retrieve the full Resume/CV.

Another way that Resumes and Candidate Profiles differ is that Resumes more commonly are a “formatted” representation of job seeker qualifications. One of the goals of a job seeker in creating a Resume is to have a formatted document (paper, HTML, Flash™, Portable Document Format (HTML), or other means of online presentation). Data within a Candidate Profile may be flexibly formatted (even formatted as a “Resume”). However, formatting and display are typically not the primary reason for creating Candidate Profiles.

Resumes and Candidate Profiles also differ in the way they are created and maintained. Resumes commonly are created within word processing software or desktop office software and stored locally. In a Profile-based system, candidates are provided the ability to create and maintain a personal profile on a career website or company’s employment portal. The Candidate Profile is stored in a database, accessible through the career web site or portal by the job seeker using a password. The job seeker can login to modify and update the information on file.

A Resume can serve as a source for some of the data necessary to build a Candidate Profile, although it often has to be “manually integrated” from the Resume into the Profile. For instance, the job seeker or a recruiter keys the data from the Resume into a Web-based form. In other cases, a resume extraction tool (a piece of software that lexically parses and interprets a resume file) takes information from the Resume and populates appropriate fields within a Candidate Profile. It may not be possible to complete the Candidate Profile from the Resume. A recruiter may follow up with the job seeker in an initial screening interview or the job seeker might be asked to provide the additional information through a web-based interface. Information in a Resume or a Candidate Profile is commonly verified through assessments and other screening processes.

1.4.2 Shared Modules

Many of the modules used in the SEP may also be useful in other schemas. These reusable schemas are part of the SharedStaffingModules file stored in the CPO library and may be included in other HR-XML schemas. Examples include Distribution Guidelines, Associations, Supporting Materials, etc.

1.4.3 Matching Modules

There is a collection of elements that share the same structure when describing the attributes of a position. From the candidate side, they describe the type of position a candidate requires or desires. On the hiring company side, they describe specifics that a position offers or requires. Examples of this include shift and schedule information, remuneration packages and travel considerations. These shared structures are a key component in SEP that facilitates the ultimate goal of all staffing transactions - better matching between a candidate and an open position.

1.5 Design Requirements

This specification was developed to enable global use and therefore, contains (optional) information that is acceptable to collect in one location and unlawful to collect in another location. It is the responsibility of the implementers to understand and comply with the appropriate regulatory requirements for each transaction.

1.5.1 Items Within the Design Scope

Enables data interchange among:

Hiring Organizations
Staffing Companies
Candidates
Recruitment Systems Vendors
Recruitment Service Vendors
Assessment Service Vendors
Screening Service Vendors

1.5.2 Items Outside of Design Scope

Feedback – Although work was not done regarding feedback of the candidate information during this project, the original JobPositionFeedback may be used with the existing schemas.

2 Business Use Cases

The Staffing Exchange Protocol can be used within a variety of contexts. The current Internet recruiting and staffing environment involves a diverse range of end-users and intermediaries, which can vary significantly and may be subject to change as new staffing and business models emerge.

Two of the most common models used today are:

The Standard Funnel – This process begins with an open position based on a specific need, and many candidates are sourced then filtered or screened out to find the best fit for that position. It is generally demand driven and buyer-centric. This approach is most common in a down economic cycle, where supply is greater than demand.

The Reverse Funnel – This process begins with a candidate who is profiled based on their experience and interests, and many positions are sourced then filtered or screened out to find the best fit for that candidate. It is generally supply driven and seller-centric. This approach is most common in a high growth economic cycle, where demand is greater than the supply of available labor.

2.1 Use Case 1 – “The Standard Funnel”

This methodology is requirements-based and begins when a manager or Human Resource representative identifies and internally communicates a need for additional resource. The employer creates an open position (requisition) usually based on a pre-existing job description or profile. Once the deployment related details are added, the position is usually submitted for authorization. When approved, it is entered into a commercial or proprietary HRIS-type system, a public system or both, for distribution to a third party, publication and/or other sourcing venue.

Next, as candidates apply, recruiters begin to use the position-specific characteristics and requirements to reduce the number of people who will progress through the evaluation process. Various filtering and screening and interviewing procedures may be implemented, until a final candidate is chosen. The position may be considered filled either after an offer has been made and accepted or possibly when the person actually begins the job.

Sample process flow for the standard funnel model

2.2 Use Case 2 – “The Reverse Funnel”

In this candidate oriented model, staffing professionals proactively recruit candidates with a variety of in-demand skills-sets that can either be pooled in reserve for anticipated need, marketed to potential employers, matched to general occupations or matched to specific current positions. The candidate’s experience, qualifications, career interests and availabilities are profiled. Based on the initial profile they are interviewed (generally with a structured format or general behavioral model), and their skills are assessed.

At this point depending on the business processes being employed, the candidate’s employment history and eligibility to work may be verified. Finally, a list of job titles that the person is interested and qualified for is produced. If they are interested in finding immediate work, they are matched to open positions. If they are interested in career development, a skills gap analysis may be done and a training curriculum devised to help the candidate reach their employment goals.

Sample process flow for the reverse funnel model

3 Candidate Schema Design

3.1 Candidate

Candidate is a comprehensive and flexible set of modules designed to include detailed information about a person within the context of the hiring process. While some information may also be useful once a person has begun their employment engagement, its primary purpose is to capture the nature and level of detail appropriate to support recruiting and staffing activities.

The specification was structured so that information relating to the nature of the transaction is at the higher levels of the schema. Examples of transactional information include: references to job/position postings that the Candidate document may be a response to, references to an agent in the event the candidate is being represented, and distribution guidelines that allow specific entities to be named if there are restrictions on where the candidate document should or should not be sent. Detailed, structured information about the candidate (person) is captured at the lower levels in the CandidateProfile and PreferredPosition modules, however, Resume is also included as an option, so that implementers can send the most appropriate set of information to meet the needs of their systems and processes.

3.1.1 Diagram

3.1.2 Definitions

Elements and Attributes [Global types listed alphabetically in following table.]	ContentModel* Data type Occurrence: Sequence \| Choice \| All (minOccurs/maxOccurs) Attributes	Definition
/ Candidate	- CandidateType - (1/1) xml:lang - - CandidateRecordInfo - RecordInfoType - S (0/1) RelatedPositionPostings - PositionPostingsType - S (0/1) CandidateSupplier - SupplierType - S (0/) DistributionGuidelines - DistributionGuidelinesType - S (0/) CandidateProfile - CandidateProfileType - S (0/*) Resume - [see include/import] - S (0/1) UserArea - [see include/import] - S (0/1)	A person who is actively pursuing or passively interested in a work engagement.
/ Candidate/ CandidateRecordInfo	- RecordInfoType - S (0/1)	Container for overall information about the candidate document.
/ [CandidateType]/ RelatedPositionPostings	PositionPosting - PositionPostingSearchInfoType - S (0/*)	Contains information about one or more specific job posting(s) in which the candidate has expressed interest.
/ Candidate/ CandidateSupplier	- SupplierType - S (0/*)	Reference information about the person or entity that is acting on behalf of a candidate.
/ Candidate/ DistributionGuidelines	- DistributionGuidelinesType - S (0/*)	Allows guidelines to be specified for distributing the resume or profile information.
/ Candidate/ CandidateProfile	- CandidateProfileType - S (0/*)	Contains (a unique version of) structured information about a candidate.

Global types (alphabetically listed)		ContentModel* Data type Occurrence: Sequence \| Choice \| All (minOccurs/maxOccurs) Attributes		Definition
/ [RecordInfoType]		Id - EntityIdType - S (0/*) Status - ExtendedBasicStatusType - S (0/1)		Globally scoped data type. See element or attribute declaration for definition.
/ [RecordInfoType]/ Id		- EntityIdType - S (0/*)		A unique identifier used to reference the entity. The Id is associated with the higher level element.
/ [RecordInfoType]/ Status		xsd:extension base: ExtendedBasicStatusType validFrom - AnyDateTimeNkNaType - validTo - AnyDateTimeNkNaType -		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.
/ [RecordInfoType]/ Status/ validFrom		- AnyDateTimeNkNaType -		The date the event begins, is active or valid.
/ [RecordInfoType]/ Status/ validTo		- AnyDateTimeNkNaType -		The date through which the event is active or valid.
/ [BasicStatusType]		xsd:restriction base: xsd:string [Enumerations]: Active, Inactive, Pending		Globally scoped data type. See element or attribute declaration for definition.
/ [ExtendedBasicStatusType]		- [Union]: BasicStatusType,xStringPatternExtensionType		Globally scoped data type. See element or attribute declaration for definition.
/ [PositionPostingsType]		PositionPosting - [complexType] - S (0/*)		Globally scoped data type. See element or attribute declaration for definition.
/ [PositionPostingSearchInfoType]		xsd:extension base: PositionPostingType SearchCriteria - [see include/import] - S (0/1) SearchResult - [see include/import] - S (0/1)		Globally scoped data type. See element or attribute declaration for definition.
/ [PositionPostingsType]/ PositionPosting		Id - EntityIdType - S (0/1) Title - xsd:string - S (0/1) Link - InternetWebAddressType - S (0/1)		Reference information about a specific job posting that an organization has generated or candidate has expressed interest in.
/ [PositionPostingsType]/ PositionPosting/ Id		- EntityIdType - S (0/1)		A unique identifier used to reference the entity. The Id is associated with the higher level element.
/ [PositionPostingsType]/ PositionPosting/ Title		- xsd:string - S (0/1)		The name or title within a given context. [Synonym(s): JobTitle, PositionTitle ]
/ [PositionPostingsType]/ PositionPosting/ Link		- InternetWebAddressType - S (0/1)		Contains a URL or link to the job ad or posting.
/ [SearchCriteriaType]		SearchCriteriaId - EntityIdType - S (0/1) SearchTarget - xsd:string - S (0/) UserId - EntityIdType - S (0/1) SearchTimeStamp - xsd:dateTime - S (0/1) SearchString - xsd:anyURI - S (0/1) OtherSearchCriteria - OtherSearchCriteriaType - S (0/) UserArea - [see include/import] - S (0/1)		Globally scoped data type. See element or attribute declaration for definition.
/ [SearchResultType]		SearchResultId - EntityIdType - S (0/1) SearchTarget - xsd:string - S (0/*) UserId - EntityIdType - S (0/1) SearchTimeStamp - xsd:dateTime - S (0/1) MatchedObjectId - EntityIdType - S (0/1) SearchRelevanceScore - xsd:string - S (0/1) SearchRelevanceRank - xsd:int - S (0/1) SearchResultCount - xsd:int - S (0/1) RankedSearchResults - RankedSearchResultsType - S (0/1) UserArea - [see include/import] - S (0/1)		Globally scoped data type. See element or attribute declaration for definition.
/ [SourceTypeType]	StandardValue - SourceEnumType - C (1/1) NonStandardValue - xsd:string - C (1/1)		Globally scoped data type. See element or attribute declaration for definition.
[SourceTypeType]/ SourceType/ StandardValue	- SourceEnumType - C (1/1)		A list of standard values.
/ [SourceTypeType]/ SourceType/ NonStandardValue	- xsd:string - C (1/1)		A string used to extend a list of non-standard values.
/ [SourceEnumType]	xsd:restriction base: xsd:string [Enumerations]: JobBoard, PrintedMedia, StaffingAgency, PublicEmploymentService, Referrer, Self		Job Board - An Internet site offering a service of job search, resume management and more. Printed Media - A printed publication offering a service of job advertising. Staffing Agency - An organization whose mission is to provide permanent, part time or temporary candidates to an organization in exchange of a fee. Public Employment Service - A public organization whose mission is to help unemployed individuals finding a job. Referrer - An individual who referred the candidate for the position. Self - The candidate.
/ [SupplierType]	relationship - RelationshipsType - optional SupplierId - EntityIdType - S (0/1) EntityName - xsd:string - S (0/1) ContactName - PersonNameType - S (0/1) ContactMethod - ContactMethodType - S (0/*) SourceType - SourceTypeType - S (0/1)		Globally scoped data type. See element or attribute declaration for definition.
/ [SupplierType] / relationship	- RelationshipsType -		Deprecated for use in CandidateSupplier. Use CandidateSupplier/SourceType.
/ [SupplierType]/ SupplierId	- EntityIdType - S (0/1)		A unique identifier for the entity that acts on behalf of a candidate
/ [SupplierType]/ EntityName	- xsd:string - S (0/1)		Name of entity that is contacted. This would typically be the organization.
/ [SupplierType]/ ContactMethod	- ContactMethodType - S (0/*)		Defines the methods of contacting a person or organizations.
[SupplierType]/ ContactName	- PersonNameType - S (0/1)		The name of the person to contact.
[SupplierType]/ SourceType	- SourceTypeType - S (0/1)		Indicates the type of organization from which the candidate was sourced.
/ [RelationshipsType]	- [Union]: RelationshipType,xStringPatternExtensionType		Globally scoped data type. See element or attribute declaration for definition.
/ [RelationshipType]	xsd:restriction base: xsd:string [Enumerations]: agent, broker, self, referer		Deprecated for use in CandidateSupplier. Use CandidateSupplier/SourceType.

3.2 Candidate Profile

The Candidate Profile module contains both personal and professional information about the candidate. An unlimited number of profiles can be created, identified and exchanged within a single candidate document. The reasons for multiple profiles are many and varied, such as: candidates wanting different profiles for different skill-sets they want to emphasize, or different audiences or, because each profile has a language attribute, they may want profiles in multiple languages. CandidateProfile’s components are flexible enough to accommodate most scenarios.

The key components in CandidateProfile are as follows:

ProfileName and ID – Allows each profile to be uniquely identified

AvailabilityInfo – Captures one or more dates or date ranges as well as the length of notice that must be worked before the candidate can begin a new work engagement. This element is at the profile level, because the candidate may want to alter the information to match the opportunity they are pursuing.

PersonalData – This element identifies the person whose information is being exchanged, captures contact information, and contains a module called PersonDescriptors designed to capture a wide range of personal demographics and other characteristics. This module deals with information that can be extremely sensitive and requires discretion on the part of the implementers. It is also a module that may be reused in other HR related schemas. Because of these factors, a separate document was created so that the issues can be discussed in greater detail.

Distribution Guidelines – See 7.1 DistributionGuidelines.

Employment History – See 7.6 EmploymentHistory.

Education History – See 7.7 EducationHistory.

Military History – See 7.8 MilitaryHistory.

Associations – See 7.3 Associations.

Supporting Materials – See 7.4 SupportingMaterials.

3.2.1 Diagram

3.2.2 Definitions

Elements and Attributes [Global types listed alphabetically in following table.]	ContentModel* Data type Occurrence: Sequence \| Choice \| All (minOccurs/maxOccurs) Attributes	Definition
/ Candidate/ CandidateProfile	CandidateProfileType - S (0/) xml:lang - - ProfileId - EntityIdType - S (0/1) ProfileName - xsd:string - S (0/1) AvailabilityInfo - [complexType] - S (0/1) DistributionGuidelines - DistributionGuidelinesType - S (0/) PersonalData - CandidatePersonalDataType - S (0/1) PreferredPosition - PositionMatchingType - S (0/1) EmploymentHistory - [see include/import] - S (0/1) EducationHistory - [see include/import] - S (0/1) MilitaryHistory - [see include/import] - S (0/1) Associations - [see include/import] - S (0/) SupportingMaterials - [see include/import] - S (0/) UserArea - [see include/import] - S (0/1)	Contains (a unique version of) structured information about a candidate.
/ Candidate/ CandidateProfile/ ProfileId	- EntityIdType - S (0/1)	Unique identifier for a particular instance of a Candidate or Position Opening Profile.
/ Candidate/ CandidateProfile/ ProfileName	- xsd:string - S (0/1)	Name for a particular Candidate or Position Opening Profile.
/ Candidate/ CandidateProfile/ AvailabilityInfo	AvailabilityDates - [complexType] - S (0/*) TermOfNotice - [complexType] - S (0/1)	Container for information about a candidate's availability for work.
/ Candidate/ CandidateProfile/ AvailabilityInfo/ AvailabilityDates	StartDate - LocalDateNkNaType - S (0/1) EndDate - LocalDateNkNaType - S (0/1)	The specific (inclusive) dates that a candidate is available for work.
/ Candidate/ CandidateProfile/ AvailabilityInfo/ AvailabilityDates/ StartDate	- LocalDateNkNaType - S (0/1)	Contains the (inclusive) date, period, or interval the event becomes active or begins.
/ Candidate/ CandidateProfile/ AvailabilityInfo/ AvailabilityDates/ EndDate	- LocalDateNkNaType - S (0/1)	Contains the (inclusive) date, period, or interval the event becomes inactive or ends.
/ Candidate/ CandidateProfile/ AvailabilityInfo/ TermOfNotice	Value - xsd:integer - S (1/1) Interval - NoticeFrequencyType - S (1/1)	The length of time that a candidate must serve in their current position before becoming eligible to begin a new work engagement.
/ Candidate/ CandidateProfile/ AvailabilityInfo/ TermOfNotice/ Value	- xsd:integer - S (1/1)	A numerical quantity that is assigned or determined by calculation or measurement.
/ Candidate/ CandidateProfile/ AvailabilityInfo/ TermOfNotice/ Interval	- NoticeFrequencyType - S (1/1)	A defined period of time between associated events.
/ Candidate/ CandidateProfile/ DistributionGuidelines	- DistributionGuidelinesType - S (0/*)	Allows guidelines to be specified for distributing the resume or profile information.
/ Candidate/ CandidateProfile/ PersonalData	CandidatePersonalDataType - S (0/1) PersonId - EntityIdType - S (0/1) PersonName - PersonNameType - S (0/1) ContactMethod - ContactMethodType - S (0/*) PersonDescriptors - PersonDescriptorsType - S (0/1) UserArea - [see include/import] - S (0/1)	A collection of information containing descriptive elements, demographic and contact information about the person.
/ Candidate/ CandidateProfile/ PersonalData/ PersonId	- EntityIdType - S (0/1)	A unique identifier for a person.
/ Candidate/ CandidateProfile/ PersonalData/ PersonName	- PersonNameType - S (0/1)	The name of a person.
/ Candidate/ CandidateProfile/ PersonalData/ ContactMethod	- ContactMethodType - S (0/*)	Defines the methods of contacting a person or organizations.
/ Candidate/ CandidateProfile/ PersonalData/ PersonDescriptors	- PersonDescriptorsType - S (0/1)	Contains legal, biological, and demographic descriptors for a person.
/ Candidate/ CandidateProfile/ PreferredPosition	xsd:extension base: PositionMatchingType Commute - CommuteType - S (0/1)	A collection of information about the candidate's job interests and preferences.
/ [BasicNoticeFrequencyType]	xsd:restriction base: xsd:string [Enumerations]: Hour, Day, Week, Month	Globally scoped data type. See element or attribute declaration for definition.
/ [NoticeFrequencyType]	[Union]: BasicNoticeFrequencyType, xStringPatternExtensionType	Globally scoped data type. See element or attribute declaration for definition.

3.3 Preferred Position

This module captures detailed information about the candidate’s interests and preferences as well as specific deployment related information and is one of the key differentiators that separate commonly used resume data from profile data. The PreferredPosition structure is designed primarily to facilitate electronic matching of a candidate to an open position. One of the key ways this is accomplished is that almost every element in this module has an identical counterpart element within PositionOpening. When the information is in Candidate, it represents what a person requires or desires – when it is in PositionOpening, it represents what an open position requires or offers. This is the type of information that can facilitate the gap between candidates that are “qualified” or have the right background and skill sets for an open position and candidates that are the best overall “fit” for the open position.

3.3.1 Diagram

3.3.2 Definitions

PreferredPosition uses the PositionMatchingType with an extension for the commute information. The following table only shows the extension. For information and descriptions for PositionMatchingType, see 6.1 Position Matching Type.

Elements and Attributes [Global types listed alphabetically in following table.]	ContentModel* Data type Occurrence: Sequence \| Choice \| All (minOccurs/maxOccurs) Attributes	Definition
/ PreferredPosition	xsd:extension base: PositionMatchingType Commute - CommuteType - S (0/1)	A collection of information about the candidate's job interests and preferences.
/ PreferredPosition/ Commute	- CommuteType - S (0/1) TimeMax - xsd:decimal - S (0/1) DistanceMax - xsd:decimal - S (0/1) Comments - xsd:string - S (0/1)	Container describing the person's commute preferences.
/ [CommuteType]/ TimeMax	xsd:extension base: xsd:decimal unitOfMeasure - xsd:string - optional	Maximum amount of time the person is willing to commute.
/ [CommuteType]/ TimeMax/ unitOfMeasure	- xsd:string -	Unit in which the quantity is measured.
/ [CommuteType]/ DistanceMax	xsd:extension base: xsd:decimal unitOfMeasure - xsd:string - optional	Maximum amount of distance the person is willing to commute.
/ [CommuteType]/ DistanceMax/ unitOfMeasure	- xsd:string -	Unit in which the quantity is measured.
/ [CommuteType]/ Comments	- xsd:string - S (0/1)	Describes the contextual information relating to a group of elements.

4 Position Opening Schema Design

4.1 PositionOpening

The PositionOpening module is structured similarly to the Candidate module, in that the highest level contains transaction oriented information. In this usage, “transactional” does not refer to the date/time/sender information typically contained in the message envelope, but rather refers to the business process that gives the schema its context.

Examples of transactional information in PositionOpening include: references to job/position postings that the PositionOpening document may provide the content for, references to the entity that is responsible for filling the position if it is other than the hiring company, and distribution guidelines that allow specific entities to be named if there are restrictions on where the PositionOpening document should or should not be sent. Detailed, structured information about the open position is captured at the lower levels in the PositionProfile and PositionDetail modules.

When PositionOpening is used in transactions with job boards or other types of career sites where publication of position information is the objective, the PositionRecordInfo structure can be used to specify the dates of active publication. It contains a repeatable ID as well as a Status element with accompanying date range attributes.

4.1.1 Diagram

4.1.2 Definitions

Elements and Attributes [Global types listed alphabetically in following table.]	ContentModel* Data type Occurrence: Sequence \| Choice \| All (minOccurs/maxOccurs) Attributes	Definition
/ PositionOpening	PositionOpeningType - (1/1) xml:lang - - PositionRecordInfo - RecordInfoType - S (0/1) PositionPostings - PositionPostingsType - S (0/1) PositionSupplier - PositionSupplierType - S (0/) PositionProfile - PositionProfileType - S (0/) NumberToFill - xsd:integer - S (0/1) UserArea - [see include/import] - S (0/1)	A single or specific instance of a job to be filled.
/ PositionOpening/ PositionRecordInfo	- RecordInfoType - S (0/1)	Container for overall information about the position document.
/ PositionOpening/ PositionPostings	- PositionPostingsType - S (0/1)	Information referencing one or more job advertisements or postings.
/ [PositionOpeningType]/ PositionSupplier	- PositionSupplierType - S (0/*)	The entity advertising or responsible for filling an open position.
/ PositionOpening/ PositionProfile	- PositionProfileType - S (0/*)	Contains (a unique version of) structured information about a position.
/ [PositionOpeningType]/ NumberToFill	- xsd:integer - S (0/1)	Allows a posting to be used for multiple positions. [BusinessRule(s): Rather than requiring 10 different posting records for the same position, a single one can suffice with a NumberToFill equal to 10. ] [Example(s): 10 (for the same position); 1 for each position needed ]

Global types (alphabetically listed)	ContentModel* Data type Occurrence: Sequence \| Choice \| All (minOccurs/maxOccurs) Attributes	Definition
/ [RecordInfoType]	Id - EntityIdType - S (0/*) Status - ExtendedBasicStatusType - S (0/1)	Globally scoped data type. See element or attribute declaration for definition.
/ [RecordInfoType]/ Id	- EntityIdType - S (0/*)	A unique identifier used to reference the entity. The Id is associated with the higher level element.
/ [RecordInfoType]/ Status	xsd:extension base: ExtendedBasicStatusType validFrom - AnyDateTimeNkNaType - validTo - AnyDateTimeNkNaType -	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.
/ [RecordInfoType]/ Status/ validFrom	- AnyDateTimeNkNaType -	The date the event begins, is active or valid.
/ [RecordInfoType]/ Status/ validTo	- AnyDateTimeNkNaType -	The date through which the event is active or valid.
/ [BasicStatusType]	xsd:restriction base: xsd:string [Enumerations]: Active, Inactive, Pending	Globally scoped data type. See element or attribute declaration for definition.
/ [ExtendedBasicStatusType]	- [Union]: BasicStatusType,xStringPatternExtensionType	Globally scoped data type. See element or attribute declaration for definition.
/ [PositionPostingsType]	PositionPosting - [complexType] - S (0/*)	Globally scoped data type. See element or attribute declaration for definition.
/ [PositionPostingsType]/ PositionPosting	Id - EntityIdType - S (0/1) Title - xsd:string - S (0/1) Link - InternetWebAddressType - S (0/1)	Reference information about a specific job posting that an organization has generated or candidate has expressed interest in.
/ [PositionPostingsType]/ PositionPosting/ Id	- EntityIdType - S (0/1)	A unique identifier used to reference the entity. The Id is associated with the higher level element.
/ [PositionPostingsType]/ PositionPosting/ Title	- xsd:string - S (0/1)	The name or title within a given context. [Synonym(s): JobTitle, PositionTitle ]
/ [PositionPostingsType]/ PositionPosting/ Link	- InternetWebAddressType - S (0/1)	Contains a URL or link to an e-mail or to an identifier. [Synonym(s): InternetWebAddress, InternetEMailAddress ]
/ [PositionSupplierType]	relationship - RelationshipsType - optional SupplierId - EntityIdType - S (0/1) EntityName - xsd:string - S (0/1) ContactName - PersonNameType - S (0/1) ContactMethod - ContactMethodType - S (0/*) SourceType - SourceTypeType - S (0/1)	Globally scoped data type. See element or attribute declaration for definition.
/ [PositionSupplierType] / relationship	- RelationshipsType –	Describes the nature of the relationship or connection between two elements or entities.
/ [PositionSupplierType]/ SupplierId	- EntityIdType - S (0/1)	A unique identifier for the entity that acts on behalf of a candidate
/ [PositionSupplierType]/ EntityName	- xsd:string - S (0/1)	The name of the supplier.
[PositionSupplierType]/ ContactName	- PersonNameType - S (0/1)	The name of the person to contact.
/ [PositionSupplierType]/ ContactMethod	- ContactMethodType - S (0/*)	Defines the methods of contacting a person or organizations.
[PositionSupplierType]/ SourceType	- SourceTypeType - S (0/1)	Identifies the type of organization from which the candidate was sourced.
/ [RelationshipsType]	- [Union]: RelationshipType,xStringPatternExtensionType	Globally scoped data type. See element or attribute declaration for definition.
/ [RelationshipType]	xsd:restriction base: xsd:string [Enumerations]: agent, broker, self, referer	Globally scoped data type.

4.2 Position Profile

The PositionProfile module contains high-level information about the open position. An unlimited number of profiles can be created, identified and exchanged within a single PositionOpening document. The reasons for multiple profiles are many and varied, such as: a company wanting different content for different audiences (e.g. internal posting, commercial or niche job board, staffing company order, etc.) or, because each profile has a language attribute, they may want profiles in multiple languages. PositionProfile’s components are flexible enough to accommodate most scenarios.

The key components in PositionProfile are as follows:

ProfileName and ID – Allows each profile to be uniquely identified.

PositionDateInfo – Captures any combination of a series of dates that may be appropriate for that specific PositionProfile.

Organization – Uses the CPO Organization structure to provide detailed information about the company who generated the open position, and in most (but not all) cases, controls the day to day activities that govern the work to be done. It can contain details about the company’s organizational structure, departments/business units, work sites, work environments and even staff as they relate to the open position. This is not used to describe an agent organization in the event that responsibility for filling the position has been granted to a third party.

FormattedPositionDescription – This element consists of name/value pairs used to carry verbatim descriptions of a position, primarily for the purpose of a job posting or other advertising-related purpose. It was created as a way of parsing unstructured text and was designed to carry the information in ‘named’ sections (for example: summary description, qualifications, application procedure, etc) so that the data can be directed into the appropriate places based on business partner agreement.

HowToApply – Provides details about how the applicant should apply for the opening. For example, if the person should apply by e-mail and/or post, the e-mail and postal address will be supplied. Available methods are by telephone, fax, e-mail, website, post mail, and in person.

Distribution Guidelines – See 7.1 DistributionGuidelines.

SupportingMaterials – See 7.4 SupportingMaterials.

4.2.1 Diagram

4.2.2 Definitions

Elements and Attributes [Global types listed alphabetically in following table.]	ContentModel* Data type Occurrence: Sequence \| Choice \| All (minOccurs/maxOccurs) Attributes	Definition
/ PositionProfile	PositionProfileType - S (0/) xml:lang - - ProfileId - EntityIdType - S (0/1) ProfileName - xsd:string - S (0/1) PositionDateInfo - PositionDateInfoType - S (1/1) Organization - OrganizationType - S (0/) PositionDetail - PositionMatchingType - S (0/1) PositionClassification - LocalizedPositionClassificationType - S (0/1) FormattedPositionDescription - xsd:string - S (0/) HowToApply - [complexType] - S (0/) DistributionGuidelines - DistributionGuidelinesType - S (0/) SupportingMaterials - StaffingSupportingMaterialsType - S (0/) UserArea - [see include/import] - S (0/1)	Contains (a unique version of) structured information about a position.
/ PositionProfile/ ProfileId	- EntityIdType - S (0/1)	Unique identifier for a particular instance of a Candidate or Position Opening Profile.
/ PositionProfile/ ProfileName	- xsd:string - S (0/1)	Name for a particular Candidate or Position Opening Profile.
/ PositionProfile/ PositionDateInfo	StartAsSoonAsPossible - xsd:boolean - S (0/1) StartDate - AnyDateTimeType - S (0/1) ExpectedEndDate - AnyDateTimeNkNaType - S (0/1) MaximumStartDate - AnyDateTimeNkNaType - S (0/1) MaximumEndDate - AnyDateTimeNkNaType - S (0/1)	Container for period of time over which the position is expected to or does exist. This allows for actual and estimated dates.
/ PositionProfile/ PositionDateInfo/ StartAsSoonAsPossible	- xsd:boolean - S (0/1)	Indicates an immediate need to have a position filled.
/ PositionProfile/ PositionDateInfo/ StartDate	- AnyDateTimeType - S (0/1)	Contains the (inclusive) date, period, or interval the event becomes active or begins.
/ PositionProfile/ PositionDateInfo/ ExpectedEndDate	- AnyDateTimeNkNaType - S (0/1)	The date the position, assignment, or contract is expected to end.
/ PositionProfile/ PositionDateInfo/ MaximumStartDate	- AnyDateTimeNkNaType - S (0/1)	The maximum acceptable date for an event to begin.
/ PositionProfile/ PositionDateInfo/ MaximumEndDate	- AnyDateTimeNkNaType - S (0/1)	The maximum acceptable date for an event to end.
/ PositionProfile/ Organization	- OrganizationType - S (0/*)	Contains information about the organization.
/ PositionProfile/ PositionDetail	xsd:extension base: PositionMatchingType JobLevelInfo - JobLevelInfoType - S (0/*)	Granular information about the characteristics of a position.
/ PositionProfile/ PositionClassification	- LocalizedPositionClassificationType - S (0/1)	Information that is required principally for compliance with governmental labor laws.
/ PositionProfile/ FormattedPositionDescription	Name - xsd:string - S (1/1) Value - xsd:string - S (1/1)	Specific verbiage used to describe a position, generally in the context of a job advertisement.
/ PositionProfile/ FormattedPositionDescription/ Name	xsd:extension base: xsd:string xml:lang - -	A descriptive identifier within the given context.
/ PositionProfile/ FormattedPositionDescription/ Value	xsd:extension base: xsd:string xml:lang - -	Verbatim text used for reproduction or publication. For example, advertising a job posting. This element, in this context, is designed for verbiage, so if graphics or formatting information also need to be exchanged, it is recommended that the “SupportingMaterials” structure be used.
/ PositionProfile/ HowToApply	PersonName - [see include/import] - S (0/1) ApplicationMethod - ApplicationMethodType - S (0/1) UserArea - [see include/import] - S (0/1)	Provides the details on how to apply for a job or position.
/ PositionProfile/ HowToApply/ ApplicationMethod	- ApplicationMethodType - S (0/1) Telephone - [see include/import] - S (0/1) Fax - [see include/import] - S (0/1) InternetEmailAddress - [see include/import] - S (0/1) InternetWebAddress - [see include/import] - S (0/1) PostalAddress - [see include/import] - S (0/1) InPerson - [complexType] - S (0/1)	Contains the phone number, address, e-mail or other pertinent contact information needed to apply for a job or position.
/ PositionProfile/ HowToApply/ ApplicationMethod/ InPerson	TravelDirections - xsd:string - S (0/1) MapLink - InternetWebAddress - S (0/1) AdditionalInstructions - xsd:string - S (0/1)	Identifies information used to apply for job or position in person.
/ PositionProfile/ HowToApply/ ApplicationMethod/ InPerson/ TravelDirections	- xsd:string - S (0/1)	Provides directions to the site. These could include directions by bus, air, car, walking, etc.
/ PositionProfile/ HowToApply/ ApplicationMethod/ InPerson/ MapLink	- InternetWebAddressType - S (0/1)	An URL to a map or other travel directions.
/ PositionProfile/ HowToApply/ ApplicationMethod/ InPerson/ AdditionalInstructions	- xsd:string - S (0/1)	Provides further instructions about applying for a position in person.
/ PositionProfile/ DistributionGuidelines	- DistributionGuidelinesType - S (0/*)	Allows guidelines to be specified for distributing the resume or profile information.
/ PositionProfile/ SupportingMaterials	- StaffingSupportingMaterialsType - S (0/*)	Allows the exchange of supporting information. [BusinessRule(s): Supporting materials may also include visual/audio media and binary data. ] [Example(s): A picture associated with a resume, a copy of a driver's license sent as part of a background check, proof of good health sent with a life insurance enrollment, a copy of diploma or license, or a copy of a pay stub. ]

4.3 Position Detail

PositionDetail is the equivalent of PreferredPosition on the Candidate side. This module captures detailed information about the open position’s attributes and requirements as well as specific deployment related information. The PositionDetail structure is designed primarily to facilitate electronic matching between a candidate and an open position. One of the key ways this is accomplished is that almost every element in this module has an identically structured counterpart element within Candidate. This allows for true “apples to apples” comparisons, resulting in a cleaner and more equitable basis for candidate filtering.

4.3.1 Diagram

4.3.2 Definitions

PositionDetail uses the PositionMatchingType with an extension for the job level information. The following table only shows the extension. For information and descriptions of PositionMatchingType, see 6.1 Position Matching Type.

Although Job Level Information is part of PositionDetail, it is also shared by other staffing schemas. Therefore, JobLevelInfoType resides in the SharedStaffingModules schema.

Elements and Attributes [Global types listed alphabetically in following table.]	ContentModel* Data type Occurrence: Sequence \| Choice \| All (minOccurs/maxOccurs) Attributes	Definition
/ PositionDetail	- PositionMatchingExtendedType - S (0/1) xsd:extension base: PositionMatchingType JobLevelInfo - JobLevelInfoType - S (0/) SearchCriteria - [see include/import] - S (0/)	Granular information about the characteristics of a position.
/ PositionDetail/ JobLevelInfo	- JobLevelInfoType - S (0/*) JobPlan - xsd:string - S (0/1) JobGrade - xsd:string - S (0/1) JobStep - xsd:string - S (0/1) Comments - xsd:string - S (0/1)	Contains information about the relative echelon a position has within a salary structure or program.
/ [JobLevelInfoType]/ JobPlan	- xsd:string - S (0/1)	Identifies a specific salary structure or program used either throughout, or in specific segments of an enterprise.
/ [JobLevelInfoType]/ JobGrade	- xsd:string - S (0/1)	Defines the salary range or band that a job falls within, based on the formal structure.
/ [JobLevelInfoType]/ JobStep	- xsd:string - S (0/1)	Pinpoints a specific level or point within a range or band.
/ [JobLevelInfoType]/ Comments	- xsd:string - S (0/1)	Describes the contextual information relating to a group of elements.
/ [SearchCriteriaType]	SearchCriteriaId - EntityIdType - S (0/1) SearchTarget - xsd:string - S (0/) UserId - EntityIdType - S (0/1) SearchTimeStamp - xsd:dateTime - S (0/1) SearchString - xsd:anyURI - S (0/1) OtherSearchCriteria - OtherSearchCriteriaType - S (0/) UserArea - [see include/import] - S (0/1)	Globally scoped data type. See element or attribute declaration for definition.

5 Resume

This module captures a summary of a candidate’s skills, experience, and education. It may include information on academic and research experience, publications, inventions (patents), presentations, awards, honors, affiliations, and other details. Full details can be found by following the link in Appendix B.

6 Matching Modules

6.1 Position Matching Type

PositionMatchingType forms the structure for Candidate’s PreferredPosition and Position Opening’s PositionDetail. It is composed of commonly used ‘points of comparison’ that are gathered throughout the course of the candidate selection process. The type and level of detail in this module is more than is commonly found in a job posting alone. Other factors are included that traditionally are captured elsewhere in the hiring process, such as a pre-screening process, an interview or an application. This is one of the primary reasons that the term “Position Opening” was used in SEP 2.0, rather than the previous “JobPositionPosting”.

The definitions section adequately describes most of the less complex elements in this structure, but in the interest of clarity, some of the larger modules in PositionMatchingType are called out and defined in more detail in sections 6.2 through 6.4.

The following scenario illustrates an example of how the data captured in PositionMatchingType could be useful to an implementer who, in this case, is using the Standard Funnel approach described in Section 2.1.)

Scenario:

Company A is a large Auto Manufacturing firm who has a need for a Mechanical Engineer with 10+ years of experience. They post the position on a national site and (times being what they are) they receive 1000 candidates that have 10+ years of experience as a Mechanical Engineer. All 1000 candidates are obviously not going to be right for that position at that company. The data in the PositionMatchingType structure may help Company A determine which ones will be a better fit.

For example, 300 candidates indicated their desire to work in the Automotive Industry (Industry). The position is located in Detroit, Michigan, and Company A will consider relocating their new engineer, so candidates who are not in the Detroit area (PhysicalLocation) and are not willing to relocate (Relocation) are separated out, leaving 75 candidates. The position requires working on alternate weekends and evening hours (Shift). Candidates that have not indicated a willingness or desire for that type of a schedule are also separated out bringing the “best fit” number down to 16. The position offers a reasonable salary, but does not offer the dental or vision insurance coverage, which was important for half of the remaining candidates (RemunerationPackage), so the “best fit” candidate count is down to 8 – a reasonable number to send through to the next round of reference checking, assessments and/or interviewing.

All 1000 of the original candidates were technically qualified to do the work the position required, but through the use of the data in PreferredPosition/PositionDetail, Company A was able to save substantial time and money narrowing the list down to a manageable number of appropriate candidates and increasing the likelihood of finding the right person for that job.

6.1.1 Diagram

6.1.2 Definitions

Elements and Attributes [Global types listed alphabetically in following table.]	ContentModel* Data type Occurrence: Sequence \| Choice \| All (minOccurs/maxOccurs) Attributes	Definition
/ PositionMatching	- PositionMatchingType - (1/1) Company - EntityReferenceType - S (0/) CompanyScale - ScaleType - S (0/) IndustryCode - IndustryCodeType - S (0/) PhysicalLocation - SEPPhysicalLocationType - S (0/) JobCategory - OccupationalCategoryType - S (0/) PositionTitle - xsd:string - S (0/) PositionClassification - StaffingPositionClassificationType - S (0/) PositionSchedule - PositionScheduleType - S (0/) Shift - WorkShiftScheduleType - S (0/) Competency - [see include/import] - S (0/) RemunerationPackage - PrehireRemunerationPackageType - S (0/1) WorkStyle - WorkStyleType - S (0/) DressCode - DressCodeType - S (0/) Travel - StaffingTravelType - S (0/1) Relocation - StaffingRelocationType - S (0/1) PreferredLanguage - LanguageCodeType - S (0/1) UserArea - UserAreaType - S (0/1)	This element only exists for display purposes. The complex type is used within the PositionOpening and Candidate records.
/ PositionMatching/ Company	- EntityReferenceType – S (0/*)	Contains identifying information about a company.
/ PositionMatching/ CompanyScale	- ScaleType – S (0/*)	Defines the relative size of an organization. This is more generic than Headcount.
/ PositionMatching/ IndustryCode	- IndustryCodeType – S (0/*)	A code that specifies the type of industry to which the entity belongs.
/ PositionMatching/ PhysicalLocation	- SEPPhysicalLocationType – S (0/*)	Container to describe a physical place.
/ PositionMatching/ JobCategory	- OccupationalCategoryType – S (0/*)	A grouping of jobs under one or more classification schemes that is meaningful to an organization.
/ PositionMatching/ PositionTitle	- xsd:string – S (0/*)	A short phrase describing the position the way it would be listed on a business card or in a company directory.
/ PositionMatching/ PositionClassification	- StaffingPositionClassificationType – S (0/*)	Describes the category or nature of the position.
/ [PositionMatchingType]/ PositionSchedule	xsd:extension base: PositionScheduleType percentage - xsd:float -	Describes the nature of the schedule associated with the position.
/ [PositionMatchingType]/ PositionSchedule/ percentage	- xsd:float -	A percentage. [Example(s): 3.5, 10 ]
/ PositionMatching/ Shift	- WorkShiftScheduleType – S (0/*)	Work shift as it pertains to a particular assignment being reported on.
/ PositionMatching/ Shift/ Id	- EntityIdType – S (0/1)	A unique identifier used to reference the entity. The Id is associated with the higher level element.
/ PositionMatching/ Shift/ Name	- xsd:string – S (0/1)	A descriptive identifier within the given context.
/ PositionMatching/ Shift/ Hours	- xsd:decimal – S (0/1)	The number of hours specified for an event or work period.
/ PositionMatching/ Shift/ StartTime	- LocalTimeNkNaType – S (0/1)	The time the interval or event started.
/ PositionMatching/ Shift/ EndTime	- LocalTimeNkNaType – S (0/1)	The time the interval or event ended.
/ PositionMatching/ Shift/ PayTypeHours	- PayTypeHoursType – S (0/1)	Specific type of work hours.
/ PositionMatching/ Shift/ Comments	- xsd:string – S (0/1)	Describes the contextual information relating to a group of elements.
/ PositionMatching/ RemunerationPackage	- PrehireRemunerationPackageType – S (0/1)	A group of components that relate to pay or other compensatory benefits information associated with a particular job or position.
/ PositionMatching/ WorkStyle	- WorkStyleType – S (0/*)	Defines the general work style preferred by a candidate or required by the hiring organization.
/ PositionMatching/ DressCode	- DressCodeType – S (0/*)	Defines any dress code requirements for the environment.
/ PositionMatching/ Travel	- StaffingTravelType – S (0/1) Applicable - xsd:boolean - C (0/1) TravelFrequency - xsd:string - S (0/1) TravelConsiderations - xsd:string - S (0/1)	Information regarding if the person is willing to travel or the position requires travel.
/ PositionMatching/ Travel/ Applicable	- xsd:boolean - C (0/1)	Indicates if the associated element applies to this transaction. This specifies if travel is applicable to the job or position.
/ PositionMatching/ Travel/ TravelFrequency	- xsd:string – S (0/1)	Percentage of time the person is willing to travel or the position requires.
/ PositionMatching/ Travel/ TravelConsiderations	- xsd:string – S (0/1)	Describes any special travel considerations.
/ PositionMatching/ Relocation	- StaffingRelocationType – S (0/1) relocationConsidered - xsd:boolean - required Comments - xsd:string - S (0/1)	Contains Information on whether relocation is an option for the candidate or considered by the hiring company.
/ [StaffingRelocationType] / relocationConsidered	- xsd:boolean -	True/False. Indicates whether relocation is an option for the candidate or considered by the hiring company.
/ PositionMatching/ Relocation/ Comments	- xsd:string – S (0/1)	Describes the contextual information relating to a group of elements.
/ PositionMatching/ PreferredLanguage	- LanguageCodeType – S (0/1)	Specifies the language that is the most desirable or commonly used by a person or in a particular work environment.

Global types (alphabetically listed)	ContentModel* Data type Occurrence: Sequence \| Choice \| All (minOccurs/maxOccurs) Attributes	Definition
/ [BasicScaleTypes]	xsd:restriction base: xsd:string [Enumerations]: Global, National, Regional, Local	Globally scoped data type. See element or attribute declaration for definition.
/ [BasicScheduleTypes]	xsd:restriction base: xsd:string [Enumerations]: Full Time, Part Time, Flex Time, Seasonal, Any	Globally scoped data type. See element or attribute declaration for definition.
/ [BasicWorkStyleTypes]	xsd:restriction base: xsd:string [Enumerations]: Independent, Team	Globally scoped data type. See element or attribute declaration for definition.
[PositionScheduleType]	- [Union]: BasicScheduleTypes,xStringPatternExtensionType	Globally scoped data type. See element or attribute declaration for definition.
/ [ScaleType]	- [Union]: BasicScaleTypes, xStringPatternExtensionType	Globally scoped data type. See element or attribute declaration for definition.
/ [StaffingPosition ClassificationType]	- [Union]: BasicPositionClassification, xStringPatternExtensionType	Globally scoped data type. See element or attribute declaration for definition.
/ [BasicPosition Classification]	xsd:restriction base: xsd:string [Enumerations]: Direct Hire, Temp to Hire, Contract to Hire, Contract, Temporary, Volunteer, Internship, Apprenticeship, On Call, Remote, Any	Globally scoped data type. See element or attribute declaration for definition.
/ [WorkStyleType]	- [Union]: BasicWorkStyleTypes, xStringPatternExtensionType	Globally scoped data type. See element or attribute declaration for definition.

6.2 Physical Location

The SEPPhysicalLocation module contains information about the actual location of a particular position, which may be different than the employer's location. In the PositionOpening schema, it specifies where the position is located. In the Candidate schema, it specifies where the candidate would prefer to work. This is key information that is used to assist in the process of matching candidates to open positions.

The structure is both simple and comprehensive. It can be as precise as Latitude/Longitude coordinates, which are useful in pinpointing field locations for Geo coding purposes. Yet it also offers a repeatable, recursive Area structure that will allow for much broader company-specific location groupings to be specified. This is commonly used in Job Boards or Career Websites to facilitate flexible search functionality.

In addition, it still allows for traditional PostalAddress information capture, rounding out the options for implementers to track this type of location information. It is important to remember, that while PhysicalLocation is flexible enough to be used in many contexts, this version is designed to facilitate staffing oriented search and match processes. More details about a position's worksite and employer information are contained in the "Organization" include in PositionProfile (See section 4.2 Position Profile).

6.2.1 Diagram

6.2.2 Definitions

Elements and Attributes [Global types listed alphabetically in following table.]	ContentModel* Data type Occurrence: Sequence \| Choice \| All (minOccurs/maxOccurs) Attributes	Definition
/ SEPPhysicalLocation	- SEPPhysicalLocationType - (1/1) Id - EntityIdType - S (0/1) Name - xsd:string - S (0/1) SpatialLocation - SpatialLocationType - S (0/1) TravelDirections - xsd:string - S (0/) Area - AreaType - S (0/) PostalAddress - [see include/import] - S (0/1) Comments - xsd:string - S (0/1)	The complex type is used within the PositionOpening and Candidate records.
/ SEPPhysicalLocation/ Id	- EntityIdType - S (0/1)	A unique identifier used to reference the entity. The Id is associated with the higher level element.
/ SEPPhysicalLocation/ Name	- xsd:string - S (0/1)	A descriptive identifier within the given context.
/ SEPPhysicalLocation/ SpatialLocation	- SpatialLocationType - S (0/1) Latitude - LatitudeType - S (1/1) Longitude - LongitudeType - S (1/1) Altitude - xsd:decimal - C (0/1) AltitudeMeanSeaLevel - xsd:decimal - C (0/1) HorizontalAccuracy - NonNegativeDecimal - S (0/1) VerticalAccuracy - NonNegativeDecimal - S (0/1)	The location relating to a specific point on the earth. This is determined by a coordinate system.
/ SEPPhysicalLocation/ SpatialLocation/ Latitude	- LatitudeType - S (1/1)	The angular distance of a place north or south of the earth’s equator. It is expressed in degrees, minutes and seconds, with a range of 0-90 degrees, where 0 is at the equator and 90 is at the poles.
/ SEPPhysicalLocation/ SpatialLocation/ Longitude	- LongitudeType - S (1/1)	The angular distance of a place east or west of the prime meridian at Greenwich, England. It is generally expressed in degrees, minutes and seconds, with a range of 0-180 degrees.
/ SEPPhysicalLocation/ SpatialLocation/ Altitude	- xsd:decimal - C (0/1)	The height of an object or point in relation to the earth's surface. This value is expressed in meters.
/ SEPPhysicalLocation/ SpatialLocation/ AltitudeMeanSeaLevel	- xsd:decimal - C (0/1)	The height of an object or point in relation to sea level or above the mean sea level. This value is expressed in meters.
/ SEPPhysicalLocation/ SpatialLocation/ HorizontalAccuracy	- NonNegativeDecimal - S (0/1)	The margin of error for longitude and latitude coordinates.
/ SEPPhysicalLocation/ SpatialLocation/ VerticalAccuracy	- NonNegativeDecimal - S (0/1)	The margin of error for the altitude coordinate.
/ SEPPhysicalLocation/ TravelDirections	- xsd:string - S (0/*)	Provides directions to the site. These could include directions by bus, air, car, walking, etc.
/ SEPPhysicalLocation/ Area	- AreaType - S (0/) Type - [Union]: AreaTypeType,xStringPatternExtensionType - - Value - xsd:string - S (1/1) Area - AreaType - S (0/)	The amount of surface included within a closed figure; a particular piece of ground often set aside for special use.
/ [AreaType] / type	- [Union]: AreaTypeType,xStringPatternExtensionType	Further defines the associated element in the context provided.
/ SEPPhysicalLocation/ Area/ Value	- xsd:string - S (1/1)	A known description of a physical area, e.g. a name of a municipality, a postcode or a country code.
/ SEPPhysicalLocation/ Comments	- xsd:string - S (0/1)	Describes the contextual information relating to a group of elements.

Global types (alphabetically listed)	ContentModel* Data type Occurrence: Sequence \| Choice \| All (minOccurs/maxOccurs) Attributes	Definition
/ [LatitudeType]	xsd:restriction base: xsd:string	Globally scoped data type. See element or attribute declaration for definition.
/ [LongitudeType]	xsd:restriction base: xsd:string	Globally scoped data type. See element or attribute declaration for definition.
/ [NonNegativeDecimal]	xsd:restriction base: xsd:decimal	Globally scoped data type. See element or attribute declaration for definition.

6.3 Remuneration Package

RemunerationPackage is both comprehensive and flexible, yet limited in the depth of information it is intended to exchange. The two primary types of data it can convey are “pay” and “benefits”. It is important to note that level of detail was kept consistent with the context of pre-hire recruiting and staffing activities. It is not designed to address jurisdiction-specific payroll or other forms of compensation management.

6.3.1 Diagram

6.3.2 Definitions

Elements and Attributes [Global types listed alphabetically in following table.]	ContentModel* Data type Occurrence: Sequence \| Choice \| All (minOccurs/maxOccurs) Attributes	Definition
/ [PrehireRemunerationPackageType]	BasePay - BasePayType - S (0/) OtherPay - OtherPayType - S (0/) Benefits - BenefitsType - S (0/*) UserArea - [see include/import] - S (0/1)	Globally scoped data type. See element or attribute declaration for definition.
/ [PrehireRemunerationPackageType]/ BasePay	- BasePayType - S (0/*) currencyCode - CurrencyCodeType - baseInterval - FrequencyType - BasePayAmountMin - xsd:decimal - S (0/1) BasePayAmountMax - xsd:decimal - S (0/1)	Describes the monetary pay structure considered standard for a particular job or position.
/ [BasePayType] / currencyCode	- CurrencyCodeType -	A three-letter code identifying the currency of a monetary amount.
/ [BasePayType] / baseInterval	- FrequencyType -	The interval or increment in which the BasePay is expected to be issued.
/ [PrehireRemunerationPackageType]/ BasePay/ BasePayAmountMin	- xsd:decimal - S (0/1)	The lowest amount of a range of BasePay amounts.
/ [PrehireRemunerationPackageType]/ BasePay/ BasePayAmountMax	- xsd:decimal - S (0/1)	The highest amount of a range of BasePay amounts.
/ [PrehireRemunerationPackageType]/ OtherPay	- OtherPayType - S (0/*) currencyCode - CurrencyCodeType - otherInterval - OtherIntervalType - otherPayType - OtherPayTypeTypes - OtherPayAmountMin - xsd:decimal - S (0/1) OtherPayAmountMax - xsd:decimal - S (0/1) OtherPayCalculation - xsd:string - S (0/1) Comments - xsd:string - S (0/1)	Describes the pay structure considered additional, flexible or atypical for a particular job or position.
/ [OtherPayType] / currencyCode	- CurrencyCodeType -	A three-letter code identifying the currency of a monetary amount.
/ [OtherPayType] / otherInterval	- OtherIntervalType -	The interval or increment other than the standard or base interval.
/ [OtherPayType] / otherPayType	- OtherPayTypeTypes -	Types of remuneration that are flexible or atypical.
/ [PrehireRemunerationPackageType]/ OtherPay/ OtherPayAmountMin	- xsd:decimal - S (0/1)	The lowest amount of a range of OtherPay amounts.
/ [PrehireRemunerationPackageType]/ OtherPay/ OtherPayAmountMax	- xsd:decimal - S (0/1)	The highest amount of a range of OtherPay amounts.
/ [PrehireRemunerationPackageType]/ OtherPay/ OtherPayCalculation	- xsd:string - S (0/1)	Allows expression and/or calculation of variables that determine OtherPay.
/ [PrehireRemunerationPackageType]/ OtherPay/ Comments	- xsd:string - S (0/1)	Describes the contextual information relating to a group of elements.
/ [PrehireRemunerationPackageType]/ Benefits	- BenefitsType - S (0/) Insurance - xsd:boolean - S (0/) RetirementOrSavingsPlan - xsd:boolean - S (0/1) CompanyVehicle - [complexType] - S (0/) RelocationAssistance - [complexType] - S (0/) VisaSponsorship - xsd:boolean - S (0/1) TimeOffAllowance - TimeOffAllowanceType - S (0/) ExpatriateBenefits - ExpatriateBenefitsType - S (0/1) OtherBenefits - xsd:string - S (0/) Comments - xsd:string - S (0/1)	Describes other forms of compensation or remuneration a person might receive in the context of a work engagement.
/ [PrehireRemunerationPackageType]/ Benefits/ Insurance	xsd:extension base: xsd:boolean type - InsuranceTypes -	Indicates whether various insurances are provided by the organization or desired by the candidate.
/ [PrehireRemunerationPackageType]/ Benefits/ Insurance/ type	- InsuranceTypes -	Further defines the associated element in the context provided.
/ [PrehireRemunerationPackageType]/ Benefits/ RetirementOrSavingsPlan	- xsd:boolean - S (0/1)	Indicates whether a retirement or savings plan is desired by candidate or offered by the hiring company.
/ [PrehireRemunerationPackageType]/ Benefits/ CompanyVehicle	companyOffered - xsd:boolean - Description - xsd:string - S (0/1)	Indicates whether use of a company vehicle is desired by candidate or offered by the hiring company.
/ [PrehireRemunerationPackageType]/ Benefits/ CompanyVehicle/ companyOffered	- xsd:boolean -	True/False. Specifies if the associated item is offered by the company.
/ [PrehireRemunerationPackageType]/ Benefits/ CompanyVehicle/ Description	- xsd:string - S (0/1)	Describes the contextual information relating to a specific element.
/ [PrehireRemunerationPackageType]/ Benefits/ RelocationAssistance	companyOffered - xsd:boolean - Description - xsd:string - S (0/1)	Contains information about relocation assistance desired by the candidate or provided by the employer.
/ [PrehireRemunerationPackageType]/ Benefits/ RelocationAssistance/ companyOffered	- xsd:boolean -	True/False. Specifies if the associated item is offered by the company.
/ [PrehireRemunerationPackageType]/ Benefits/ RelocationAssistance/ Description	- xsd:string - S (0/1)	Describes the contextual information relating to a specific element.
/ [PrehireRemunerationPackageType]/ Benefits/ VisaSponsorship	- xsd:boolean - S (0/1)	Indicates whether visa sponsorship is desired by candidate or offered by the hiring company.
/ [PrehireRemunerationPackageType]/ Benefits/ TimeOffAllowance	- TimeOffAllowanceType - S (0/*) timeOffType - TimeOffTypes - Description - xsd:string - S (0/1)	Contains information about time off allowed by the hiring company or desired by the candidate.
/ [TimeOffAllowanceType] / timeOffType	- TimeOffTypes -	A list of the types of allowed time off desired by candidate or offered by the hiring company.
/ [PrehireRemunerationPackageType]/ Benefits/ TimeOffAllowance/ Description	- xsd:string - S (0/1)	Provides further information about the time off.
/ [PrehireRemunerationPackageType]/ Benefits/ ExpatriateBenefits	- ExpatriateBenefitsType - S (0/1) ExpatriateBenefitsOffered - xsd:boolean - C (0/) ExpatriateBenefitList - ExpatriateBenefitTypeTypes - C (0/)	Contains information about expatriate benefits.
/ [PrehireRemunerationPackageType]/ Benefits/ ExpatriateBenefits/ ExpatriateBenefitsOffered	- xsd:boolean - C (0/*)	True/False. Defines if expatriate benefits are offered as part of employment.
/ [PrehireRemunerationPackageType]/ Benefits/ ExpatriateBenefits/ ExpatriateBenefitList	- ExpatriateBenefitTypeTypes - C (0/*)	Describes the type of benefits that might exist in an expatriate compensation package.
/ [PrehireRemunerationPackageType]/ Benefits/ OtherBenefits	xsd:extension base: xsd:string type - xsd:string -	Describes benefits not explicitly defined.
/ [PrehireRemunerationPackageType]/ Benefits/ OtherBenefits/ type	- xsd:string -	Further defines the associated element in the context provided.
/ [PrehireRemunerationPackageType]/ Benefits/ Comments	- xsd:string - S (0/1)	Describes the contextual information relating to a group of elements.

Global types (alphabetically listed)	ContentModel* Data type Occurrence: Sequence \| Choice \| All (minOccurs/maxOccurs) Attributes	Definition
/ [BasicExpatriateBenefitTypeTypes]	xsd:restriction base: xsd:string [Enumerations]: Relocation Package, School Fees, Vehicle, Professional Service Fees, Language Instruction, Club Membership	Globally scoped data type. See element or attribute declaration for definition.
/ [BasicInsuranceTypes]	xsd:restriction base: xsd:string [Enumerations]: Medical, Dental, Vision, Life	Globally scoped data type. See element or attribute declaration for definition.
/ [BasicOtherPayTypeTypes]	xsd:restriction base: xsd:string [Enumerations]: Bonus, Commission, Incentive, Sliding Commission	Globally scoped data type. See element or attribute declaration for definition.
/ [BasicTimeOffTypes]	xsd:restriction base: xsd:string [Enumerations]: PaidHoliday, UnpaidHoliday, PaidVacation, PaidLeave, UnpaidLeave, PersonalDays, HealthDays	Globally scoped data type. See element or attribute declaration for definition.
/ [ExpatriateBenefitTypeTypes]	- [Union]: BasicExpatriateBenefitTypeTypes, xStringPatternExtensionType	Globally scoped data type. See element or attribute declaration for definition.
/ [InsuranceTypes]	- [Union]: BasicInsuranceTypes, xStringPatternExtensionType	Globally scoped data type. See element or attribute declaration for definition.
/ [OtherIntervalType]	- [Union]: BasicFrequencyType,SignOnType, xStringPatternExtensionType	Globally scoped data type. See element or attribute declaration for definition.
/ [OtherPayTypeTypes]	- [Union]: BasicOtherPayTypeTypes, xStringPatternExtensionType	Globally scoped data type. See element or attribute declaration for definition.
/ [SignOnType]	xsd:restriction base: xsd:string [Enumerations]: Sign-on	Globally scoped data type. See element or attribute declaration for definition.
/ [TimeOffTypes]	- [Union]: BasicTimeOffTypes, xStringPatternExtensionType	Globally scoped data type. See element or attribute declaration for definition.

6.4 Shift

The Shift module contains detailed information about the days (or other increments) and hours associated with a particular position, or that a candidate is willing/able to work. ShiftPeriod is one of the key defining components that sets the interval or time period to which the rest of the elements apply. It can be as specific as a day of the week or as unspecific as “varies”, but if any of the elements do not apply to the entire ShiftPeriod, it is recommended you send as many instances/versions of Shift as necessary to communicate all the variables.

For example, say there is an open position that requires a person to work Monday and Wednesday from 0800 to 1300, and Tuesday, Thursday and Friday from 1200 to 1700. You could send two instances of Shift, one to cover the Monday/Wednesday hours and one to cover the Thursday/Friday hours.

<Name>Morning Shift</Name>