- From: Jakub Klímek via GitHub <sysbot+gh@w3.org>
- Date: Thu, 05 Mar 2020 07:41:37 +0000
- To: public-dxwg-wg@w3.org
@agreiner @pwin Actually the issue is not with implementation of dereference (nginx, redirects, etc.) but with the fact that the two IRIs (http and https) are different identifiers, worsening interoperability. Every application working with DCAT will have to know and implement, that sometimes, media types (used in multiple properties) use http and sometimes https identifiers, and that when checking for identity, this has to be taken into account. Saying that "we can ignore the scheme in URL" is IMHO not the right way to go, because it breaks the concept of URIs. I see only three options, where each has to be clearly stated in the documentation, since IANA has no guidance on this and DCAT is the specification saying that the IANA URIs are to be used: 1. Use HTTPS and break backward compatibility 2. Use HTTP - in this case, we need to say that the URI you get from the web browser when viewing the actual Media type document is not the one to use (because it is HTTPS) 3. Allow usage of both. Then we need to say this explicitly, with the consequences for worse interoperability (example above) in mind. -- GitHub Notification of comment by jakubklimek Please view or discuss this issue at https://github.com/w3c/dxwg/issues/1206#issuecomment-595074114 using your GitHub account
Received on Thursday, 5 March 2020 07:41:39 UTC