Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add a property to JobPosting to describe restrictions on applicant location #2083

Closed
vholland opened this issue Oct 16, 2018 · 7 comments
Closed
Assignees

Comments

@vholland
Copy link
Contributor

Some jobs (particularly telecommuting jobs) have requirements on the applicant's location. For example, can work remotely, but must be in USA or Europe. I propose adding a property applicantLocationRequirements to describe this situation.

For example:

{
  "@context": "http://schema.org/",
  "@type": "JobPosting",
  "name": "Telecommute from anywhere in USA!",
  "applicantLocationRequirements": {
    "@type": "Country",
    "sameAs": "https://www.wikidata.org/wiki/Q30",
    "name": "USA"
  }
}

Note: This is separate from citizenship or work visa requirements, which I think are complicated enough that we should handle those separately.

@vholland vholland self-assigned this Oct 19, 2018
vholland added a commit to vholland/schemaorg that referenced this issue Nov 5, 2018
@vholland
Copy link
Contributor Author

vholland commented Nov 5, 2018

See PR #2092

@RichardWallis
Copy link
Contributor

Implemented in release 3.5

@alexrodba
Copy link

How would you restrain to only Europe if it is not a country?

@RichardWallis
Copy link
Contributor

As the expected value type for the applicantLocationRequirements property is AdministrativeArea you could define it simply thus:

  "applicantLocationRequirements": {
    "@type": "AdministrativeArea",
    "sameAs": "http://www.wikidata.org/entity/Q458",
    "name": "European Union"
  }

@alexrodba
Copy link

Oh, that's brilliant, thank you!

@alexrodba
Copy link

It throws a warning:
image

Was that expected?

@jvandriel
Copy link

That's a Google specific issue (which aren't handled here). If you run the markup through http://linter.structured-data.org/ all's fine.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants