job-listing-brainstorming

Job Listing Brainstorming

Ideas for a possible job-listing microformat.

Fields from examples

(see the job-listing-examples)

• title - h#
• description - class
• company - hcard
  • company size - class
• location - adr
• 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?

• type (employee|contract) - class
• classification (full time|part time|temporary|temp to hire|seasonal|internship) - class
• hours/week - class
• salary base - class (see currency)
• salary max - class (see currency)
• wage/hour - class (see currency)
• education - class
• certification - class (security clearance can fall under certification)
  • years - class
  • required - class
• skill - class (management can fall under skill)
  • years - class
  • required - class
• benefit - class
• Holiday allowance - expressed in days or weeks?
• contact - hcard
• time posted - date-time (is this dtstart? See above)
• relocation covered - class
• job function - class (if absent, fall back to title?)
• travel required - class
• industry - tag on company?

Andy Mabbett

"job-listing" is clunky, would "vacancy" be a better name?

I second the change of name to "Vacancy". - ntoll

What about "job-offer"? Reason: People with low english-skills often now "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)

See also

• Joined Up Jobs (job syndication initiative in UK local government)
• currency - proposed microformat for marking-up amounts of money (for salary, wage, payment, earnings)