-
Notifications
You must be signed in to change notification settings - Fork 54
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
When to use service vs extension vs seeAlso vs annotation? #1269
Comments
Proposal:
Extensions are used for any inline JSON-LD based data associated with a resource, with an additional context at the top of the document. Geo-JSON and physical dimensions thus become extensions, and we will have an extensions annex that mirrors the services annex that list the known extension patterns. Annotations are used just as they are today. Content creator services were identified as not needing to be referenced from the presentation API documents, although their outputs would fall into the above categories. A community maintained list might be appropriate for this, but not an API annex. |
Note that other than clarifications, key change is move of |
👍 to having this issue as the forum for all things related to the proposal above (#1269 (comment)) |
👍 at Toronto WG meeting to go with proposal in #1269 (comment) |
As the clarifications have been made, retagging with notes as we still need to update the "services" document. This is possibly just one task under #1310 ? |
Closing, fixed. |
Can we be more explicit in order to encourage consistency?
The text was updated successfully, but these errors were encountered: