-
Notifications
You must be signed in to change notification settings - Fork 23
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
Suggestion: Expected behavior for profile URIs not listed in Appendix C? #170
Labels
Comments
Thanks @swickr. I agree in reserving the |
This issue was discussed in a meeting.
View the transcript3.1. Profile IRIsIvan Herman: #170 Ivan Herman: one background - transition calls with WOT people … they were interested in a profile for their own needs … but what came up is what is policy with regard to what is said in W3C documents … by default each WG has its own profile space (e.g., ns/jsonld…) … and that’s it Rob Sanderson: there are profile URIs (e.g., Web Annotation) … if you don’t understand it, you must ignore it Proposed resolution: Accept #170, with the clarification that processors MUST ignore IRIs that that they do not recognize, and that json-ld* IRIs are reserved for future WG use (Rob Sanderson) Rob Sanderson: +1 Adam Soroka: +1 Tim Cole: +1 Ruben Taelman: +1 Ivan Herman: +1 Benjamin Young: +1 Pierre-Antoine Champin: +1 David I. Lehn: +1 David Newbury: +1 Resolution #2: Accept #170, with the clarification that processors MUST ignore IRIs that that they do not recognize, and that json-ld IRIs are reserved for future WG use* Rob Sanderson: Action to implement this resolution is on pchampin or greg Action #1: update syntax with issue #170 resolution (Pierre-Antoine Champin) |
pchampin
added a commit
that referenced
this issue
Jun 13, 2019
pchampin
added a commit
that referenced
this issue
Jun 13, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The specification of application/ld+json defines three profile URIs. The expected behavior when some other URI is given appears to be unspecified.
If JSON-LD were to specify that
this would provide an additional point of extensibility.
(*) behave as if that URI were not present
The text was updated successfully, but these errors were encountered: