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

@azaroth42 
you are right ... I was just thinking if we should prevent people of 
doing stupid things. 
So .. the conclusion is that "https://www.w3.org/ns/anno.jsonld" is 
not allowed/(recommended) to be used in the context according to the 
current specification.

Should we really have such a constraint?
Could we say that "http://www.w3.org/ns/anno.jsonld" or 
"https://www.w3.org/ns/anno.jsonld" must be in the context list?

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

Received on Thursday, 1 September 2016 16:34:18 UTC