Re: [TalentSignal] analysis of example Job Posting

Hello, Phil.

I'd agree with all your points, though it took me a while to read 
through your links and understand that "combining requirements for a job 
posting" referred to the problem of needing to specify both requirements 
and their boolean relationship to each other (e.g., a 4 year degree AND 
six years of experience OR a Ph.D. AND a current cybersecurity 
certification).  It gets even more complicated when realizing you really 
need both the booleans and parentheses (or some kind of 
order-of-operations indicator),  to encode requirement relationships.  I 
have no proposed solution, but one is needed if these data standards are 
to be used in career navigation/career pathways software.

I was at first concerned about how we encode 
remote/telecommuting/virtual jobs, but I see that is taken care of in a 
parameter called jobLocationType.  I do run into a problem often, when 
working with job data, that the listed job location is the main 
company's physical headquarters, even for jobs where the person is 
intended to work offsite anywhere in the US.  This causes the job to 
show up on maps and searches as a fixed location even when it could be 
anywhere.  I wondered at first if this were a data structure issue, but 
apparently not, given we have a way to encode this correctly.  I guess 
it's just a common employer data entry error.

Merrilea

|
|

On 6/10/2019 12:06 PM, Phil Barker 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.
>
-- 

Merrilea J. Mayo, Ph.D.
Mayo Enterprises, LLC
12101 Sheets Farm Rd.
North Potomac, MD 20878

merrileamayo@gmail.com
https://merrileamayo.com/ < >
240-304-0439 (cell)
301-977-2599 (landline)