- From: Phil Archer <phila@w3.org>
- Date: Wed, 27 Apr 2016 18:15:44 +0100
- To: Annette Greiner <amgreiner@lbl.gov>, Bernadette Farias Lóscio <bfl@cin.ufpe.br>, "public-dwbp-wg@w3.org" <public-dwbp-wg@w3.org>
Annette, I can live with removing /roads and /bus. Would you be happy with http://data.mycity.example.com/transport/dataset/bus/stops This makes it clear to a human reader that the URI identifies a dataset rather than a bus stop, or a concept. The transport and dataset path elements could be swapped to give http://data.mycity.example.com/dataset/transport/bus/stops - I don't feel strongly either way. Phil. On 26/04/2016 21:52, Annette Greiner wrote: > I can live with "dataset" as a placeholder for a real identifier for the > dataset, if "/road" and "bus-" come out. We should not be suggesting > people build long, redundant URIs. That is not a best practice. > It's not clear to me whether you are thinking that all datasets > published by the transport agency would have /dataset near the end of > the path. That would not be a good idea for a RESTful API, because it > would complicate the regular expressions that filter out the various > requests. You want to be able to chop off a base URI and work on the > stuff that decides the response. > -Annette > > On 4/26/16 11:16 AM, Bernadette Farias Lóscio wrote: >> >> Dear Annette and Phil, >> >> We're trying to resolve the comments about the Data Identifiers >> section, but some comments still need further discussion. We'd like to >> ask your help in order to resolve the following one [2]: >> >> *** Comment 17 (Item 3) Persistent URIs as identifiers [1] >> >> There is no consensus about the URI that we should use in our examples. >> Annette made the following proposal: >> >> -------------------- >> I think we could go with something like this: >> >> http://data.mycity.example.org/transport/ is a base for all the >> example URIs >> Probably a real link would need to identify the dataset somehow rather >> than just say that it's a dataset. >> What do you think about this? >> http://data.mycity.example.org/transport/timetables/bus/stops/ " >> --------------------- >> >> We prefer to use the one initially proposed by Phil: >> http://data.mycity.example.com/public-transport/road/bus/dataset/bus-stops >> >> >> Maybe we can use just "transport" rather than "public-transport", but >> we should keep dataset rather than timetables. >> >> >> What do you think? >> >> Thanks, >> BP Editors >> >> >> >> >> [1] https://lists.w3.org/Archives/Public/public-dwbp-wg/2016Apr/0157.html >> [2] >> https://www.w3.org/2013/dwbp/wiki/Comments_to_be_considered_before_publishing_the_last_working_draft >> >> >> >> -- >> Bernadette Farias Lóscio >> Centro de Informática >> Universidade Federal de Pernambuco - UFPE, Brazil >> ---------------------------------------------------------------------------- >> > -- Phil Archer W3C Data Activity Lead http://www.w3.org/2013/data/ http://philarcher.org +44 (0)7887 767755 @philarcher1
Received on Wednesday, 27 April 2016 17:15:59 UTC