Re: ACTION-94 a few thoughts

Hi Bill - I've incorporated your comments (in somewhat draft form) into the
BP document; see PR https://github.com/w3c/sdw/pull/71 (commit details
<https://github.com/6a6d74/sdw/commit/26364a5c4e25786427d51aa8500ea35eaa619383>
).

FWIW, note that the catalogue discovery mode (search for the record, read
the record to find the access point. query the access point) is covered by
the DWBP. Furthermore, I'd be bold enough to say that data that's accessed
only from an opaque service endpoint is not really on the web. I think to
be "on the web" the data needs to be visible to (and crawlable by) search
engines.

'reconciliation apis' / 'search apis' were added in a previous PR.

Thanks for the input. Keep it coming please :-)

Jeremy

On Wed, 25 Nov 2015 at 16:26 Bill Roberts <bill@swirrl.com> wrote:

> Hi Bart
>
> Feel free to ignore or use these as you see fit, but I made a few notes
> the other day about ACTION-94 (at a point when I had got confused and
> thought it was one for me!)
>
> how to "make the links within the dataset discoverable" ?
>
> We assume we have a dataset containing information about spatial things.
> To be able to link to that information via the web, each spatial thing
> (and/or each information object about a thing) should have a URI - see 7.6.
>
> How does a user discover what information is contained within the dataset?
>
> - 'reconciliation APIs' - allowing the user to do a text search on labels
> or other API request to help them find a URI that matches an entity that
> they have some description of
> - allow search engines to index the data - if each URI responds sensibly
> to a HTTP GET, and something links to it, then a search engine crawler can
> find it and index it.
> - catalogues - perhaps a simple list page, perhaps also containing
> metadata or a subset of the information about each resource
> - site search features
> - SPARQL endpoint
>