<xsd:complexType name="CandidateType">
<xsd:annotation>
<xsd:documentation source="http://www.hr-xml.org" xml:lang="en">
<ccts:DictionaryEntryName xmlns:ccts="urn:un:unece:uncefact:documentation:1.1">Candidate. Detail</ccts:DictionaryEntryName>
<ccts:DefinitionText xmlns:ccts="urn:un:unece:uncefact:documentation:1.1">A collection of data about an applicant or prospective employee or resource. Like a resume, a Candidate document contains details about a person's professional, education, and professional experience. However, Candidate may include data that is not typically included on a Resume, such as remuneration requirements and various position preferences. </ccts:DefinitionText>
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:group ref="DocumentIDGroup" minOccurs="0" />
<xsd:element ref="DocumentSequence" minOccurs="0" />
<xsd:element ref="ProcessingInformation" minOccurs="0" />
<xsd:element ref="DataCapture" minOccurs="0" />
<xsd:element ref="CandidateSupplier" minOccurs="0" maxOccurs="unbounded" />
<xsd:element ref="RecruitmentStatusCode" minOccurs="0">
<xsd:annotation>
<xsd:documentation> Use cases:
Interchange between ATS and VMS?
Interchange between two ATSs?
Job board sends candidates pre-qualified
as a result of passing an assessment.
Multi-business unit collaborations / tracking
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element ref="PositionSeekingStatusCode" minOccurs="0">
<xsd:annotation>
<xsd:documentation>A code classifying the candidate's job search posture or disposition. In other words, whether the candidate is actively engaged in a job search, is passively considering opportunities, or is not considering job opportunities at all. This is an HR-XML open list.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element ref="DistributionGuidelines" minOccurs="0" />
<xsd:element ref="CandidatePerson" minOccurs="0" />
<xsd:element ref="CandidateProfile" minOccurs="0" maxOccurs="unbounded" />
<xsd:element ref="UserArea" minOccurs="0" />
</xsd:sequence>
<xsd:attribute name="languageCode" type="LanguageCodeContentType" use="optional" />
<xsd:attributeGroup ref="EffectiveDateAttributeGroup" />
</xsd:complexType>
|