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

I'd prefer client implementers (and/or their underlying libraries) do 
their own preference handling when it comes to (in)secure requests.

The name we use should remain unchanged and "http://" is the more 
flexible/"upgrade-able" of the two protocol schemes, so using that one
 seems prudent for longevity.

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

Received on Tuesday, 16 August 2016 14:28:07 UTC