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

When to use service vs extension vs seeAlso vs annotation? #1269

Closed
azaroth42 opened this issue Sep 28, 2017 · 8 comments
Closed

When to use service vs extension vs seeAlso vs annotation? #1269

azaroth42 opened this issue Sep 28, 2017 · 8 comments

Comments

@azaroth42
Copy link
Member

Can we be more explicit in order to encourage consistency?

@azaroth42 azaroth42 added this to the Presentation 3.0 milestone Sep 29, 2017
@azaroth42
Copy link
Member Author

azaroth42 commented Sep 29, 2017

Proposal:

service is an endpoint that is intended to be interacted with by the client directly. Thus image, auth, search, ldn, and the W3C Annotation Protocol all fall into this category.

seeAlso is a machine readable external resource that is related to the current resource, but not necessarily describing it as per current definition. If it's necessary to be more precise about the relationship, then the external resource should provide that clarification with a link back to the appropriate resource.

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.

@zimeon
Copy link
Member

zimeon commented Sep 29, 2017

Note that other than clarifications, key change is move of geojson and phydim from services to extensions -- this is the key part to discuss in Toronto

@azaroth42
Copy link
Member Author

This should probably subsume #1012 and #893. Propose to close those issues in favor of this one.

@tomcrane
Copy link
Contributor

tomcrane commented Oct 3, 2017

👍 to having this issue as the forum for all things related to the proposal above (#1269 (comment))

@zimeon
Copy link
Member

zimeon commented Oct 12, 2017

👍 at Toronto WG meeting to go with proposal in #1269 (comment)

@azaroth42
Copy link
Member Author

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 ?

@azaroth42
Copy link
Member Author

#1310 is closed. Propose that we can close this one too. Updating the "services" from v2 is a separate issue -- #1358.

@azaroth42
Copy link
Member Author

Closing, fixed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants