Proposal for new Occupation type

[vickitardif]

A few times we have discussed adding an Occupation or Profession type (most recently issue #1410), but always from the perspective of the Person with the Occupation. For example, Jane is a Software Engineer or Joe is a Dentist.

For my work, I am more interested in the occupations themselves. What qualifications do you need? What is the estimated salary? Do these things vary by jurisdiction? (For example licensure requirements can differ from country to country.)

After reading through the past discussions, I have put together the following proposal, which I hope addresses the issues raised without having to create a lot of complexity.

• New type Occupation: A profession, may involve prolonged training and/or a formal qualification.

  • Many of the relevant properties already exist for JobPosting. The domains would be extended to include Occupation for:
    • educationRequirements
    • experienceRequirements
    • occupationalCategory
    • qualifications
    • responsibilities
    • skills
  • New properties would be:
    • estimatedSalary: The estimated salary for this occupation. The salary would be expressed as a MonetaryAmountDistribution. (See below.)
    • occupationLocation: The region/country for which this occupational description is appropriate. Note that educational requirements and qualifications can vary between jurisdictions.

• New type QuantitativeValueDistribution: A subtype of QuantitativeValue for describing a statistical distribution of values. Properties include:

  • duration: The time period the distribution is measured over.
  • percentile10: The 10th percentile value
  • percentile25: The 25th percentile value
  • median: The median value
  • percentile75: The 75th percentile value
  • percentile90: The 90th percentile value

• New type MonetaryAmountDistribution: A subtype of QuantitativeValueDistribution for describing a statistical distribution of monetary amounts. Properties include:

  • currency: The currency for the monetary values.

• New property on JobPosting:

  • relevantOccupation: The Occupation for the JobPosting.

• New property on Person:

  • hasOccupation: The Person's occupation. For past professions, use Role for expressing dates.

[thadguidry]

+1 generally Vicki. You did a great job ! covering the major potential pieces. Let's ensure we are not missing anything else. To that point, perhaps browsing actual datasets available can be helpful https://www.bls.gov/data/

One that I found just browsing the datasets is that of "Unions or Labor Unions" for particular Occupations ?
Probably others... just dig around and browse there. Great job again Vicki, I like it !

[jvandriel]

The only thing I have difficulty with is occupationLocation as it doesn't take (international) remote workers into account - a target group that's rapidly growing (which is an issue for JobPosting's jobLocation as well).

[vickitardif]

@jvandriel Agreed. I have been trying to figure out a clean way to fix this for JobPosting, but have not come up with an idea I liked well enough to propose.

[vickitardif]

See PR #1709

[philbarker]

Definition for occupationalCategory: "Category or categories describing the job. Use BLS O*NET-SOC taxonomy: http://www.onetcenter.org/taxonomy.html. ..." seems unnecessarily US-centric.

UK has SOC 2010, I'm sure other countries have their own, and there is the international ISCO-08. Ideally I guess that the coding scheme used would be that relevant for the occupationLocation

Perhaps list O*NET-SOC as an example rather than phrase as an imperative.

[vickitardif]

@philbarker I thought of that when I copied the existing text over. Ideally, we would allow authors to use any taxonomy. Whatever happened to the work to allow other vocabularies?

[philbarker]

@vholland Ah, yes, sorry only just noticed that occupationalCategory is an existing property reused. Is it worth noting this as an issue against that property? (and adding it as a use case for external enumerations!)

[danbri]

Talking with Sally and @subbuvincent from @TheTrustProject, there's a desire (see #1525) to be able to describe the skills/expertise of journalists on news sites. We thought about extending the use of http://schema.org/keywords but are now considering whether there's a connection to Occupation...

[thadguidry]

@danbri Journalists should be able to use skills and qualifications , once added to Occupation as @vholland laid out. (and that I and others are waiting on)

[mindyshaw33]

Why not connect everyone using maps, family search, facebook, google etc.. That way if ever a child gets lost we then could right away pull up google earth and in real time check the area, right? I keep thinking we need to connect everything, there could be a place that people could go to fill out forms on others too - for outside perspectives such as a boss (in relation to another) or a family friend or relative. It would be a huge project but a necessary one if we are going to live in "the future" one day.

…

On Wed, Aug 30, 2017 at 5:57 PM, Dan Brickley ***@***.***> wrote: Talking with Sally and @subbuvincent <https://github.com/subbuvincent> from @TheTrustProject <https://github.com/thetrustproject>, there's a desire (see #1525 <#1525>) to be able to describe the skills/expertise of journalists on news sites. We thought about extending the use of http://schema.org/keywords but are now considering whether there's a connection to Occupation... — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#1698 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AGa9ec6eVThy8s4dMvLWljM0kVyRVSpIks5sdfbkgaJpZM4OXPBn> .