Skip to content

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

Open
danbri opened this Issue May 17, 2016 · 1 comment

1 participant

@danbri
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 danbri pushed a commit that referenced this issue May 17, 2016
Dan Brickley Added a brief note addressing webmaster concerns about extensions.
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
abe238e
@danbri danbri pushed a commit that referenced this issue May 17, 2016
Dan Brickley Updated to match implementation: we now only list the extension defin…
…ing a term.

Previously we listed all extensions that mentioned a term.
See #1165
d5609e3
@danbri danbri pushed a commit that referenced this issue May 17, 2016
Dan Brickley Noted improvement for #1165 1a91893
@danbri danbri pushed a commit that referenced this issue May 17, 2016
Dan Brickley Improved hyperlink to include term name.
See #1165
785e377
@danbri
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."

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.