- From: Michael Kay <mike@saxonica.com>
- Date: Fri, 19 Aug 2022 07:51:33 +0100
- To: Gerald Oskoboiny <gerald@w3.org>
- Cc: Norm Tovey-Walsh <ndw@nwalsh.com>, Michael Sperberg-McQueen <cmsmcq@blackmesatech.com>, xmlschema-dev@w3.org
Some questions: (1) will you be updating all the "well known" W3C resources so their internal cross-references use HTTPS URIs? For example, xhtml11.dtd references http://www.w3.org/TR/xhtml-modularization/DTD/xhtml-inlstyle-1.mod (2) will you be updating TR documents so their external links (including links to resources such as schemas and DTDs) use HTTPS URIs? In both cases, if you do so, (a) you will need to be very careful not to update URIs used as long-term identifiers, for example namespace and collation URIs. (b) there could be problems caused by making in-situ changes to such resources, e.g. digital signature invalidation. (3) will the policy on allocating namespace URIs change? Personally I always thought the use of HTTP URIs as identifiers for namespaces was foolish, and I think this exercise will prove me right. "Stable URIs" was one of the fundamental guiding principles of the web, and it was always going to be difficult to achieve when URIs incorporated the name of a specific comms protocol. Michael Kay Saxonica
Received on Friday, 19 August 2022 06:51:51 UTC