Simple URLs for extension terms should re-assure publishers #1165
Comments
danbri
added a commit
that referenced
this issue
May 17, 2016
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
…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
|
Site should now (or shortly, might cache a while) be showing this for e.g. http://schema.org/Drug
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
The text was updated successfully, but these errors were encountered: