Re: [web-annotation] Avoid mixed-content error with JSON-LD context in HTTPS

I think it is an edge case, as the number of browser based clients 
that will dynamically dereference the context and use it to interpret 
the content that it has received as triples is probably countable on 
zero fingers. Any realistic browser-based client that needs the 
context will simply provide a copy of it, as it can't change once we 
hit TR so there's no risk of it going stale.

Annotations MUST use the http context URI. So publishers MUST, in 
fact, copy the examples as use that URI:
> The Annotation MUST have 1 or more @context values and MUST be one of them.

GitHub Notification of comment by azaroth42
Please view or discuss this issue at
 using your GitHub account

Received on Thursday, 1 September 2016 16:02:58 UTC