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

indicate on a JobPosting whether direct application on the same site is possible #2907

Open
danbri opened this issue Jun 16, 2021 · 2 comments
Assignees
Labels
no-issue-activity Discuss has gone quiet. Auto-tagging to encourage people to re-engage with the issue (or close it!).

Comments

@danbri
Copy link
Contributor

danbri commented Jun 16, 2021

Context: This is a proposal from Google, feedback based on experience with building user-facing job search based on schema.org/JobPosting data (see https://developers.google.com/search/docs/data-types/job-posting for current documentation). If adopted by schema.org and publishers, Google expects to explore improvements the job search experience using this additional information.

The proposal is to add a property for JobPosting to help clarify the nature of the posting: /directApply.

Rationale: It is common to encounter JobPosting descriptions in which is it is impossible to tell from the metadata supplied whether there is a straightforward way for applicants to apply on the site where the posting is described (and marked up using schema.org/JobPosting).

Draft definition for /directApply:

  • Applies on JobPosting, values are Boolean.
  • Definition: "Indicates whether an /url that is associated with with /JobPosting enables direct application for the job, via the posting website. A job posting is considered to have directApply of 'True' if an application process for the specified job can be directly initiated via the url(s) given (noting that multiple internet domains might nevertheless be involved at an implementation level). A value of 'False' is appropriate if there is no clear path to applying directly online for the specified job, navigating directly from the JobPosting url(s) supplied."

Editorial comment from Dan Brickley (in schema.org capacity, and noting my Google affiliation):

I will proceed to add this to schema.org Pending area, where we should take care to solicit review from folk who may not be monitoring Github or other schema discussions. I am satisfied that something like this would be a positive improvement to schema.org's expressivity, but anticipate there may be feedback on the clearest and most appropriate way to express the distinction. As always, Schema.org will review implementation situation (publishers, consumers, definitions) as part of the process for terms progressing beyond Pending status, see how we work for details.

@danbri danbri self-assigned this Jun 16, 2021
danbri added a commit that referenced this issue Jun 16, 2021
there's a way to directly apply via the URLs supplied.
@danbri
Copy link
Contributor Author

danbri commented Jun 16, 2021

@github-actions
Copy link

This issue is being nudged due to inactivity.

@github-actions github-actions bot added the no-issue-activity Discuss has gone quiet. Auto-tagging to encourage people to re-engage with the issue (or close it!). label Sep 15, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
no-issue-activity Discuss has gone quiet. Auto-tagging to encourage people to re-engage with the issue (or close it!).
Projects
None yet
Development

No branches or pull requests

1 participant