Tim Farlow, CPO Work Group Leader New CPO Standards January 2003 Tim Farlow, CPO Work Group Leader Welcome, introductions.

New CPO Standards Employment History Military History ISO Utilities Identifier Types Organization Taxonomy Types WorkSite

Employment History and Military History Provide a method to exchange employment history between trading partners Intended for use within other HR-XML schemas Originally developed in Resume 2.0, and used in BackgroundCheck 1.0 A more flexible schema was needed for BackgroundCheck 2.0 EH Example MH Example

ISO Utilities Many HR-XML specifications use a set of agreed-upon XML schema types to represent ISO codes for currency, country, gender, and names of languages This recommendation documents the use of these types and formalizes their adoption as Cross-Process Objects

Gender Code ISO 5218 GenderCodeType allows only these values 0 – Not known, 1 – Male, 2 – Female, 9 – not specified GenderCodeType allows only these values <Applicant> <Name>Juan Estevez</Name> <Gender>1</Gender> …

Currency Code ISO 4217 CurrencyCodeType Three letter, uppercase currency code CurrencyCodeType Enforces 3 letter, uppercase. Does not validate that the code is an actual ISO 4217 code. <DeductionAmount currency=“USD”> 50.34</DeductionAmount> …

Country Code ISO 3166-1 CountryCodeType <Applicant> Two letter, uppercase country code CountryCodeType Enforces 2 letter, uppercase. Does not validate that the code is an actual ISO 3166-1 code <Applicant> <Nationality>CH</Nationality> …

Language Codes LanguageCodeType LanguageDependentTextType ISO 639-1 is a two letter, lowercase language code The Type enforces 2 letter, lowercase Does not validate that the code is an actual ISO 639-1 code Used to specify as a language when language is the data <ApplicantSpeaks>ja</ApplicationSpeaks> LanguageDependentTextType Used when you need to specify the language of the body of the element <SignOffMessage xml:lang=“fr”>Adieu</SignOffMessage>

Identifier Types A home for common identifiers for use in HR-XML specifications InternetDomainNameType defines Internet domains EntityReferenceType defines a name and id of an entity DunsNumberType defines the pattern of Dunn & Bradstreet identifiers EntityIdType is an existing standard that has a new home in this new Identifier Types document

InternetDomainType Specifies an internet domain Does NOT specify a URL (we have that already) Typical use – match an email address domain with a company Examples: hr-xml.org ibm.com needham.k12.ma.us

EntityReferenceType Many transactions need to identify an entity, but don’t need a full entity schema – Example: a screening transaction may need to exchange the name and Id of an organization but does not need the entire Organization schema <Vendor> <Id idOwner=“USHiFi”><IdValue name=“vin”>4035</IdValue></Id> <Name>CD Covers of America</Name> </Vendor>

DunsNumberType Used to exchange Dun & Bradstreet identifiers Simple pattern of digits <Vendor> <DunsNumber>45-563-3452</DunsNumber> …

EntityIdType No changes to this existing standard Now bundled into the IdentifierTypes standard <WorkerId idOwner="Cogs, Inc."> <IdValue name="Employee ID">113355</IdValue> <IdValue name="Division">Corporate</IdValue> </PersonId> <PersonId idOwner=“TempStaffInc"> <IdValue>MA237</IdValue> </WorkerId>

Organization Many HR-XML standards transmit data about organizations and their components OrganizationType defines companies, subsidiaries, governments, etc. OrganizationalUnitType defines departments, business units, project teams, etc. OrganizationType, OrganizationalUnitType Organization Example

Taxonomy Types A taxonomy is a structure for classifying or categorizing information into a hierarchy This specification is a home for types taxonomies of codes that are common within the context of Recruiting, Staffing and Hiring processes The first of these is Industry Coding taxonomies such as SIC, NAICS, and UNSPSC. Later we may include Occupational Coding and Competency Coding into this document Structure only, no code sets

WorkSite Updates the WorkSite and WorkSiteEnvironment schemas to use existing CPOs, converts to global complex types, removes locally scoped prefixes, and combines the two schemas The functionality of the schemas does not change, but the schemas are not backwards compatible with previous work site versions WorkSite Example

Data Dictionary: Wednesdays, 10:00 Eastern Time www.hr-xml.org Questions? cpo@lists.hr-xml.org Schema: Thursdays, 11:00 Eastern Time Data Dictionary: Wednesdays, 10:00 Eastern Time