Docs for schema item JobType in HR-XML

Job. Details Contains a collection of information relating to a job. A job can be thought of as a template for a position. A position is an instance of a job. Jobs describe the nature of the work, whereas related positions represent the time, place, and organizational structure in which a person or persons actually perform the work. Positions usually have a specific budget associated with them. Employer practices vary significantly with respect to the management of jobs. Some organizations have formal and rigorously developed job structures (See JobEvaluation). Other employers may not really manage jobs at all, but rather manage resources and resource requirements only using "Position" concepts. Consider that processes such as recruitment can be either Job or Position-based. For example, an employer might have a continuing need for resources to fill the Job of "Accountant I" and "Accountant II" (what it defines as entry level Accountants). The employer might regularly advertise and recruit for these Jobs. Once candidates are identified, qualified ones might be associated and considered with respect to specific positions (For example, an Account I position specializing in Banking at the London office). Broadly speaking, the HR-XML library is designed to flexibly accomodate Job and Position-based processes. Both JobDetails and Position components (or qualified versions of these components) usually are presented as options within the same context. Where used, both are optional so implementers can choose to use or not use one or both of these components as their situation dictates.

<xsd:complexType name="JobType"> <xsd:annotation> <xsd:documentation source="http://www.hr-xml.org" xml:lang="en"> <ccts:DictionaryEntryName xmlns:ccts="urn:un:unece:uncefact:documentation:1.1">Job. Details</ccts:DictionaryEntryName> <ccts:DefinitionText xmlns:ccts="urn:un:unece:uncefact:documentation:1.1">Contains a collection of information relating to a job. A job can be thought of as a template for a position. A position is an instance of a job. Jobs describe the nature of the work, whereas related positions represent the time, place, and organizational structure in which a person or persons actually perform the work. Positions usually have a specific budget associated with them. </ccts:DefinitionText> <ccts:UsageRule xmlns:ccts="urn:un:unece:uncefact:documentation:1.1">Employer practices vary significantly with respect to the management of jobs. Some organizations have formal and rigorously developed job structures (See JobEvaluation). Other employers may not really manage jobs at all, but rather manage resources and resource requirements only using "Position" concepts. Consider that processes such as recruitment can be either Job or Position-based. For example, an employer might have a continuing need for resources to fill the Job of "Accountant I" and "Accountant II" (what it defines as entry level Accountants). The employer might regularly advertise and recruit for these Jobs. Once candidates are identified, qualified ones might be associated and considered with respect to specific positions (For example, an Account I position specializing in Banking at the London office). Broadly speaking, the HR-XML library is designed to flexibly accomodate Job and Position-based processes. Both JobDetails and Position components (or qualified versions of these components) usually are presented as options within the same context. Where used, both are optional so implementers can choose to use or not use one or both of these components as their situation dictates. </ccts:UsageRule> </xsd:documentation> </xsd:annotation> <xsd:sequence> <xsd:element ref="JobID" minOccurs="0" maxOccurs="unbounded" /> <xsd:element ref="oa:JobTitle" minOccurs="0" /> <xsd:element ref="JobCategoryCode" minOccurs="0" maxOccurs="unbounded" /> <xsd:element ref="JobEvaluation" minOccurs="0" /> <xsd:element ref="JobDescription" minOccurs="0" maxOccurs="unbounded" /> <xsd:element ref="UserArea" minOccurs="0" /> </xsd:sequence> <xsd:attributeGroup ref="EffectiveDateAttributeGroup" /> </xsd:complexType>

Definition Type:	ComplexType
Name:	JobType
Namespace:	http://www.hr-xml.org/3
Containing Schema:	Components.xsd
Abstract
Documentation:	Job. Details Contains a collection of information relating to a job. A job can be thought of as a template for a position. A position is an instance of a job. Jobs describe the nature of the work, whereas related positions represent the time, place, and organizational structure in which a person or persons actually perform the work. Positions usually have a specific budget associated with them. Employer practices vary significantly with respect to the management of jobs. Some organizations have formal and rigorously developed job structures (See JobEvaluation). Other employers may not really manage jobs at all, but rather manage resources and resource requirements only using "Position" concepts. Consider that processes such as recruitment can be either Job or Position-based. For example, an employer might have a continuing need for resources to fill the Job of "Accountant I" and "Accountant II" (what it defines as entry level Accountants). The employer might regularly advertise and recruit for these Jobs. Once candidates are identified, qualified ones might be associated and considered with respect to specific positions (For example, an Account I position specializing in Banking at the London office). Broadly speaking, the HR-XML library is designed to flexibly accomodate Job and Position-based processes. Both JobDetails and Position components (or qualified versions of these components) usually are presented as options within the same context. Where used, both are optional so implementers can choose to use or not use one or both of these components as their situation dictates.

Derivation Tree:
	*JobType* nsA:Job

References:
	nsA:Job