Job Listing Brainstorming
Ideas for a possible job-listing microformat.
Fields from examples
(see the job-listing-examples)
|property||xhtml-element||description||major/minor (+/-) priority|
|title||h#||title of the job, e.g. 'Project-Manager for Customer-Service-Project'||+|
|start & end date||dtstart & dtend||:or should we use dstart for the date the ad is posted,
and dtend for the closing date for aplications?
temp to hire|seasonal|internship)
|salary base||class (see currency)||+|
|salary max||class (see currency)||+|
|wage/hour||class (see currency)||+|
|skill||class||management can fall under skill|
|holiday allowance||expressed in days or weeks?|
|time posted||date-time||(is this dtstart? See above)|
|job function||class||(if absent, fall back to title?)|
|industry||tag on company?|
|language of job-listing|
|job-language||class||mainlanguage spoken with colleagues|
|applicationmaterial||class||e.g. cv, worksamples, licenses, greencard|
|organisationalid||class||number or phrase - large enterprises have an unique id for a specific job offer|
|applicationurl||class||Some companies require applicants to fill out application forms online|
- Maybe there's no need to have a dedicated microformat for jobs and we could somehow extend the hListing proposal, by adding the following optional fields under description:
I concur with Filip C.T.E.. A vacant or new position at a company can be represented in its basic form by the hListing proposal. hMeasure and hCurrency could handle the salary as it would the monetary value of any basic listing. Describing optional and required skill set items needs more discussion.
"job-listing" is clunky, would "vacancy" be a better name?
- I second the change of name to "Vacancy". - ntoll
- I disagree, "vacancy" has no context. It could refer to anything - eg "hotel vacancy". - Quint
What about "job-offer"? Reason: People with low english-skills often know "offer" but not "vacancy". On the other hand: Why not easily "job"? With an attribute you can specify if it is a "job-offer" or a "job-application". So human beeings/job-platforms can easily compare "offers" and "applications". Manually (humans) or automatic (machines) -- Christian 05:48, 28 Apr 2007 (PDT)
Keep in mind the internationally recognized term in the ATS industry is "requisition". This is also defined in the HRXML specification.
While I believe other non-standard options should be considered, it does not appear as though the hResume specification gave any consideration to HRXML, which does have a large adoption for backend transations regarding HR data (including resumes and requisitions).
- While this makes perfect sense from a specialist's back-end view, I'm not sure that I would ever look for a requisition (actually positive that I wouldn't) Robert Cooksey
- Joined Up Jobs (job syndication initiative in UK local government)
- currency - proposed microformat for marking-up amounts of money (for salary, wage, payment, earnings)
(hello everyone, my first post, I'll get to creating my user page Robert Cooksey )
- The idea of extending the hListing proposal sounds like a good one.
- This simplifies the models to more generic containers with detail coming from attribute values
- It also utilizes the time tested models of information organization on sites such as craigslist and paper models such as classifieds while adding the semantic specificity that allows the data to be utilized by systems in widely divergent varieties by agents--human and digital
- Questions concerning this:
- Is there another word than job or requisition that captures all of each and is used in common parlance?
- Would "offer" be the best action for this? Maybe "opportunity" or something of which I'm not thinking?
- A general enough heading for this action in hListing would allow for a breakdown in terms of type of different forms
- The suggestion of type could accept values such as:
- contract, submission (for calls for conferences, publications, etc.), full-time, part-time, etc.
- This would allow for an opportunity (job/employment, call for papers, etc.) that could be differentiated by attributes of type and availability status (open, closed, conditional, etc.)
- Also, the word "available" seems more flexible should one want to allow for just an expression that expresses openness without too much specificity, but the expiration date might catch-that. What if open-until-filled?
- One last suggestion is to add "experience" to the list Filip posted above
- While many job listers search for skills and education level, number of years experience are also used at least as often
Agree the hlisting format looks like it could easily be extended to meet the initial needs of a job posting, assuming we look at a job posting as a classified ad not from the view point of a recruiter. One of the issues that limited the take up of HRXML in the early days was it's complexity, experienced gained here in Australia trying to get vendors to support the format. The list of elements above seems to describe a job from an HR/recruitment point of view not a classifieds point of view.
I see the biggest issue with the hlisting format being how to handle: salary, skills, type, industry and application process.
For tech jobs at least, it'd be nice to have /graded/ requirements for skills, whether measured in years experience, general goodness, or how important to the position (1-5 say; 5 absolutely required, 1 lightly used, only nice-to-have). Also, Visa requirements (H1B, citizen, green card ...), security clearance, whether remote work is ok. And actually, all of these are applicable to general jobs as well. -- Jeff Donner