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

I only recall the ns staying at HTTP.

I think this is editorial because it exemplifies the use of HTTPS over
 HTTP as the most desirable approach. In my implementation, I've 
noticed that if the context is HTTP, mixed-content error is thrown 
because the client-side RDF library tries to dereference it as is - 
i.e., it doesn't pass the context URL through an HTTPS proxy to avoid 
this when the origin is HTTP. Should libraries and implementations be 
forced to override or ignore the context? This is just additional 
processing that no one wants to deal with. Naturally publishers are 
free to use the HTTP or HTTPS, but why not set a good example?

The schemes of the URLs in context can stay HTTP, it is only the 
reference to the context URL that should be HTTPS.

Just my two :moneybag: 

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

Received on Tuesday, 16 August 2016 01:24:27 UTC