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

by following the schema.org answer:

> this is a lengthy way of saying that both 'https://schema.org' and 
'http://schema.org' are fine. 

Is there a technical solution to solve this issue on the server side?
I assume that there is no problem to put the schema available both 
under 
http://www.w3.org/ns/anno.jsonld and 
https://www.w3.org/ns/anno.jsonld.
(probably a forward rule in apache server is suffiecient)

@azaroth42 @BigBlueHat 
Could we write a non normative note, indicating that server 
implementations that run on https, may use the https context?

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

Received on Thursday, 1 September 2016 14:31:14 UTC