Skip to content

Simple URLs for extension terms should re-assure publishers #1165

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.

Sign up for GitHub

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

Jump to bottom
Closed
danbri opened this issue May 17, 2016 · 2 comments
Closed

Simple URLs for extension terms should re-assure publishers #1165

danbri opened this issue May 17, 2016 · 2 comments
Labels
guidelines docs examples Work on our supporting materials rather than on schema definitions site tools + python code Infrastructural issues around schema.org site. Most can ignore this!

Comments

@danbri
Copy link
Contributor

danbri commented May 17, 2016

Instead of just "The term 'MedicalEntity' is not in the schema.org core vocabulary, but is described by the following extension(s):" let's add:

"Note: extension terms can be used in schema.org markup in the normal manner; it is not necessary for markup publishers to indicate which extension (currently) a term is in."

The options around JSON-LD are complex and evolving but I think we can safely say this immediately, to reassure some publishers. See also: #1164
danbri added a commit that referenced this issue May 17, 2016
@danbri
Added a brief note addressing webmaster concerns about extensions.
abe238e 
Specifically, when we moved many terms into health-lifesci it caused
some needless alarm. The docs/extension.html page could also do with
clarifications but this simple fix should help for now.

See #1165
danbri added a commit that referenced this issue May 17, 2016
@danbri
Updated to match implementation: we now only list the extension defin…
d5609e3 
…ing a term.

Previously we listed all extensions that mentioned a term.
See #1165
danbri added a commit that referenced this issue May 17, 2016
@danbri
Noted improvement for #1165
1a91893
danbri added a commit that referenced this issue May 17, 2016
@danbri
Improved hyperlink to include term name.
785e377 
See #1165
@danbri
Copy link
Contributor Author

danbri commented May 17, 2016

Site should now (or shortly, might cache a while) be showing this for e.g. http://schema.org/Drug

"Schema.org Extensions
The term 'Drug' is not in the schema.org core vocabulary, but is defined in an extension:
health-lifesci: Drug
Note: extension terms can be used in schema.org markup in the normal manner; it is not necessary for markup publishers to indicate which extension a term is currently in. Terms may move between extensions over time (e.g. from pending to the core) without the need for the corresponding markup to change."

@danbri danbri added site tools + python code Infrastructural issues around schema.org site. Most can ignore this! guidelines docs examples Work on our supporting materials rather than on schema definitions status:implementing labels May 17, 2016
@danbri danbri mentioned this issue May 17, 2016
Closed
@danbri
Copy link
Contributor Author

danbri commented Aug 10, 2016

Published via http://schema.org/docs/releases.html#v3.1
http://blog.schema.org/2016/08/schemaorg-update-hotels-datasets-health.html

@danbri danbri closed this as completed Aug 10, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
guidelines docs examples Work on our supporting materials rather than on schema definitions site tools + python code Infrastructural issues around schema.org site. Most can ignore this!
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@danbri