W3C home > Mailing lists > Public > public-dxwg-wg@w3.org > July 2019

Re: [dxwg] Range of dcat:endpointURL (#655)

From: Stephen Richard via GitHub <sysbot+gh@w3.org>
Date: Wed, 03 Jul 2019 21:25:56 +0000
To: public-dxwg-wg@w3.org
Message-ID: <issue_comment.created-508260577-1562189154-sysbot+gh@w3.org>
It seems like in practice many access URLs point to landing pages and there's no difference. 

Sometime the access URL might get you to a form that lets you set up filters to get more precise access to what you want, something like ERDDAP TableDAP [Data Access Pages](https://coastwatch.pfeg.noaa.gov/erddap/tabledap/erdCalCOFIlrvcntAtoAM.html).  In this case I guess you could argue that the form is a UI on top of an accessService, but the user doesn't need to know anything about that--its just a web page to them, and the URL for the form is different from the service endpoint URL that the form is using.

Not all landing pages actually provide a link to access the data, whereas the intention (correct me if this is wrong) of the accessURL is to get the user as close to the data as possible (ideally only one more click).  

GitHub Notification of comment by smrgeoinfo
Please view or discuss this issue at https://github.com/w3c/dxwg/issues/655#issuecomment-508260577 using your GitHub account
Received on Wednesday, 3 July 2019 21:25:57 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:42:18 UTC