Skip to content

JobPosting and skills #1167

Open
gigster99 opened this Issue May 18, 2016 · 4 comments

5 participants

@gigster99
gigster99 commented May 18, 2016 edited

Is there a method to express skills associated with a @Person? For example, we tried this, but it violates the JobPosting domain.

<script type="application/ld+json">
{
"@context": {
    "@vocab": "http://schema.org/",
    "id": "@id",
    "type": "@type"
    },
    "type": "Person",
    "id": "#person-name",
    "name": "John Doe"
}
</script>

<script type="application/ld+json">
{
"@context": {
    "@vocab": "http://schema.org/",
    "id": "@id",
    "reverse": "@reverse",
    "type": "@type"
    },
    "type": "JobPosting",
    "reverse": { "skills": { "id": "#person-name" } }
}
</script>

The only other alternative we see is to use additionalType for @Person and then use name to expose the label for the skill. But this approach 'dangles' when juxtaposed with other statements using additionalType. Are we missing a cleaner solution hiding in plain sight?

@DDeering

+1 on adding a property for skills to the Person type to help specify what a person does or is able to do.

@twamarc
twamarc commented May 18, 2016

It seems this request in a real need as its pops up again. Should we suggest already a pull request?
see also:#789
see also:#807 (comment)

@danbri
danbri commented May 20, 2016

There is some very active work underway currently for describing courses - see #195 - I suggest we see what comes out of that effort regarding description of skills and documented topical credentials.

@danbri danbri self-assigned this May 20, 2016
@jaygray0919

Works for us. One note of advice. In our humble opinion skills for the domain JobPosting should be different than the future term for skills that may be in domain Person. We can explain when the new proposal surfaces.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.