- From: Nate Harris <nate.sirrah@gmail.com>
- Date: Mon, 10 Jun 2019 10:21:07 -0700
- To: "public-talent-signal@w3.org" <public-talent-signal@w3.org>, phil.barker@pjjk.co.uk
- Message-ID: <CAHoiOBy7RV4MBfngygxsaeFLekwoAa-Uj_DDgaqhovj1qh=B-g@mail.gmail.com>
This analysis is great! It makes sense that there should be a means for providing contact information. Though most larger companies use an ATS system that obsolesce a non-form means of contact, job boards and countless smaller/ mid-sized companies that aren't integrated with an automated suite would benefit from surfacing the field. Department linkage via subOrganization also seems like a clean and non-contentious solution... department would give additional clarity to job roles that aren't clearly interpretable by the layperson (i.e. jargony names like Scrum Master) or are innately cross-functional (i.e. Director of Sales Marketing, Product Marketing Manager). This may merit a separate thread, but has there ever been talk about something like 'applicationEntails?' I imagine it would be valuable to hirers and applicants alike if there was a way to indicate that a job requires an in-person interview, a coding challenge, an essay, etc. Thanks, Nate --- Nate Harris @ nateonawalk <https://nateonawalk.com> On Mon, Jun 10, 2019 at 9:07 AM Phil Barker <phil.barker@pjjk.co.uk> wrote: > Hello all, a couple of weeks ago I shared a fictional example job posting > <https://docs.google.com/document/d/1vD19BSnaxkf9qahYeGBw19YKPFi2McFEuJOE9a5K_KY/edit> > [1] that originated from the job data exchange project. > > I have analysed this against schema.org JobPosting > <https://schema.org/JobPosting> [2] and the Google JobPosting Search > guidance > <https://developers.google.com/search/docs/data-types/job-posting> [3], > producing an example of a full JobPosting and some potential issues arising. > > The issues are: > > - There should be a means of providing contact details for a JobPosting > - There should be a means of providing information about the > department within a hiring organization within which a job in a job posting > is situated. > - There should be a means of combining requirements for a job posting > - employmentType covers different categories of information which > leads to some complications when more than one is present. > > You can see the full analysis on the TalentSignal wiki > <https://www.w3.org/community/talent-signal/wiki/Examples:_Junior_software_developer> > [4] > > Do you think that these are significant issues worth addressing? > > Regards, Phil > 1. > https://docs.google.com/document/d/1vD19BSnaxkf9qahYeGBw19YKPFi2McFEuJOE9a5K_KY/edit > 2. https://schema.org/JobPosting > 3. https://developers.google.com/search/docs/data-types/job-posting > 4. > https://www.w3.org/community/talent-signal/wiki/Examples:_Junior_software_developer > -- > > Phil Barker <http://people.pjjk.net/phil>. http://people.pjjk.net/phil > CETIS LLP <https://www.cetis.org.uk>: a cooperative consultancy for > innovation in education technology. > PJJK Limited <https://www.pjjk.co.uk>: technology to enhance learning; > information systems for education. > > CETIS is a co-operative limited liability partnership, registered in > England number OC399090 > PJJK Limited is registered in Scotland as a private limited company, > number SC569282. > -- Nate Harris (314) 443-7236 nate.sirrah@gmail.com Numenna! Auta i re. Yallume! Hilya!
Received on Monday, 10 June 2019 17:23:31 UTC