Re: [web-annotation] Extension Capacity

@azaroth42

> Proposal: Extension section should include:
>    * Use JSON-LD for extensions -- NB this re-introduces JSON-LD 
into the -model document, which has been otherwise excised to -vocab

Sigh. We should be indeed very careful in the way we formulate this, 
because bare JSON processors should still be o.k. with all this. I 
would think that, first of all, this is something for an appendix, not
 the main text (the latter should simply allow for more than one 
`@context` and stop of that). We should also make it clear that 
extensions are to be provided by particular implementations, and their
 usage may damage interoperability. Finally, I wonder whether we 
should not move the details on how to do extensions to the vocabulary 
document altogether rather than keeping it in the model document.

>    * Call out multiple contexts on the Annotation as the way to do 
that

Yes and, if my previous note flies, just refer to the vocab document 
for people who want to do and know more

>    * Ignore unknown keys, or unexpected values, rather than erroring
 out
>

Yes

> Need a recommendation for internationalization of strings, rather 
than resource content?

I am not sure I understand. JSON uses UTF-8, what else do we need at 
this point? How does this relate to I18N?


-- 
GitHub Notification of comment by iherman
Please view or discuss this issue at 
https://github.com/w3c/web-annotation/issues/154#issuecomment-191121703
 using your GitHub account

Received on Wednesday, 2 March 2016 08:11:48 UTC