- From: Jarno van Driel <jarnovandriel@gmail.com>
- Date: Tue, 16 Sep 2014 22:04:42 +0200
- To: W3C Web Schemas Task Force <public-vocabs@w3.org>
- Message-ID: <CADK2AU0bKOSzGxTZYQdP8TQ9ufq2-pt2v3unKENnJCMYT+_eaA@mail.gmail.com>
During Vicki Tardif Holland's post about Financial information for Person and Organization ( http://lists.w3.org/Archives/Public/public-vocabs/2014Sep/0115.html) once again the subject of adding a Job and/or Profession type to schema.org has come to the table. Maybe therefore it's time to start thinking about this out loud. A Job type would probably have a lot of properties in common with the already existing JobPosting, but which ones exactly will still have to be figured out. There are a couple of things I know people are looking for the Person type, which sort of overlap with this. For Person some would like to have: skill > Skill (eg. a list of Skills) qualification > Qualification (eg. a list of Qualification) as opposed to JobPosting's 'skills' and 'qualifications', which are plural forms with Text as their expected value. So the question here also is, should Person be expanded with: baseSalary, salaryCurrency, skill > Skill or just skills qualifications > Qualification or just qualifications and any other property that seems to be fitting, looking at JobPosting. Or should we only focus on schema.org/Job/Profession for now and continue the discussion about Person after that? Anyways, any thoughts are appreciated, (I'm just trying to get the subject raised here).
Received on Tuesday, 16 September 2014 20:05:09 UTC