More on HTTP/S

More on the topic of HTTP or HTTPS.

Context: W3C and others are encouraging the greater use of HTTPS, we'd 
like this to be the norm as the Web becomes more secure and trusted.

The automatic switching to https seen on w3.org now uses new fangled 
ways of doing stuff that avoid us having to make any changes to 
long-established resources.

For new resources, we have more choice of course. For example, in BP 1 
the Intended Outcome is (currently):

Entities (SpatialThings) described in a dataset will each be identified 
using a globally unique HTTP URI so that a given entity can be 
unambiguously identified in statements that refer to that entity.


I would suggest that this could say:

"...using a globally unique HTTP or HTTPS URI..."

We may want to include wording somewhere along the lines of

"The upside of using HTTPS URIs is increased security for applications 
that dereference them.  A downside could be that existing tools might 
not handle HTTPS "well".  An upside could be that such tools would be 
upgraded to have better security or would be upgraded to use a cached 
copy of the namespace."

HTH

Phil.


For tracker: Action-107

-- 


Phil Archer
W3C Data Activity Lead
http://www.w3.org/2013/data/

http://philarcher.org
+44 (0)7887 767755
@philarcher1

Received on Wednesday, 20 April 2016 15:42:49 UTC