- From: Annette Greiner via GitHub <sysbot+gh@w3.org>
- Date: Thu, 27 Jan 2022 22:46:19 +0000
- To: public-dxwg-wg@w3.org
@kcoyle, I see the distinction you and others are making here, but I read it quite differently. I think we agree on what downloadURL is asking for. I think the operative words are under the definition of accessURL, where it says "A landing page, feed, SPARQL endpoint or other type of resource". It's very clear that they never intended to limit it to landing pages, and that they did intend it to apply to multiple types of resources. I read "access" as to obtain in some way, be it through a direct download, an API, or through a link on a landing page. @smrgeoinfo is right in noting the error in the ODI example of failing to include a downloadURL for a download, but that would be an error in any of our views. If we required only one of the two, users could still just as easily fail to include a downloadURL when they had one. What I wanted to point out there is that they interpret accessURL as legitimately describing a download location. That shouldn't be surprising, given that several other types of resource are explicitly mentioned in the definition, along with "other type(s) of resource". I don't see that as ambiguous at all. -- GitHub Notification of comment by agreiner Please view or discuss this issue at https://github.com/w3c/dxwg/issues/1437#issuecomment-1023710823 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 27 January 2022 22:46:20 UTC