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

Feature: Add property for remote with datatype boolean in JobPosting #1591

Closed
sstankov opened this issue Apr 17, 2017 · 12 comments
Closed

Feature: Add property for remote with datatype boolean in JobPosting #1591

sstankov opened this issue Apr 17, 2017 · 12 comments

Comments

@sstankov
Copy link

Hi guys,

with more and more jobs are open to be worked from remote location, is good to add property that mark if this is possibility or not.

Keep in mind that sometimes remote is open for a country or region or other subset.

Cheers,
Slav

@vholland
Copy link
Contributor

Rather than a boolean a new subtype like RemoteJobPosting may be better. That would allow us to add properties to specify things like the applicable country or region.

@EricAxel
Copy link
Contributor

EricAxel commented Apr 18, 2017 via email

@vholland
Copy link
Contributor

A boolean would not let an author express in-office or remote.

Overloading jobLocation means you can't differentiate between "remote within the USA" and remote or USA.

@sstankov
Copy link
Author

current there is:

jobLocation:Place

if we add new one:

jobLocationRemote:Place

if we have both, job will be allowed for on site and remote. If we have just one, we know what is the case.

I'm not sure if Place or PostalAddress is better. Pros for the first time is that we follow the same pattern, but PostalAddress is more accurate for remote usage.

@danbri
Copy link
Contributor

danbri commented Apr 19, 2017

Can anyone find examples of sites where the job's remoteness appears to be explicitly represented in their infrastructure?

@sstankov
Copy link
Author

sstankov commented Apr 19, 2017

Hmm, not sure, but you can see sites like:

But cases include:

Remote in a certain area:

2017-04-19_20-52-41

Remote, without limiting the area:

2017-04-19_20-55-05

@RichardWallis
Copy link
Contributor

if we add new one:

jobLocationRemote:Place

Remote could mean "anywhere on the planet" - how would that work as a Place ?

@jvandriel
Copy link

jvandriel commented Apr 19, 2017

"Remote could mean "anywhere on the planet" - how would that work as a Place ?"

Wouldn't this work for that (also for properties like areaServed,eligibleRegion,jobLocation,etc)?

"jobLocationRemote":
{
  "@type":"Place",
  "name":"anywhere on the planet",
  "sameAs":"https://www.wikidata.org/wiki/Q2"
}

@danbri
Copy link
Contributor

danbri commented Aug 3, 2017

Anyone familiar with hropenstandards.org? I looked around a bit there and failed to find a treatment of remote work, but I'm sure the issue must have cropped up. I've asked for pointers on Twitter.

@vholland
Copy link
Contributor

Resurrecting this thread. It would be nice to be able to describe the job location, but there is not a lot of consensus (even on the sites I looked at) about how to designate regions, percent of remote work allowed, etc.

Can we add a jobLocationType property with the expected type Text? If we start to see consensus on what people are using for text, we could create a more meaningful type with properties.

vholland pushed a commit to vholland/schemaorg that referenced this issue Aug 14, 2018
@vholland
Copy link
Contributor

Created PR #2039 to add this to pending.

danbri pushed a commit that referenced this issue Sep 4, 2018
* Issue #1591: Added jobLocationType to pending.

* Fixed formatting.
danbri pushed a commit that referenced this issue Dec 11, 2018
* Issue #1591: Added jobLocationType to pending.

* Fixed formatting.
@RichardWallis
Copy link
Contributor

Implemented in release 3.5

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

6 participants