- From: Phil Archer <phila@w3.org>
- Date: Wed, 08 Apr 2015 10:14:56 +0100
- To: Deirdre Lee <deirdre@derilinx.com>, public-dwbp-wg@w3.org
Thanks Dee, Action-119 asks me (and Ig, Action-118) to look at Jeni's document on URLs in data [1]. This was something she and other members of the TAG worked on in 2013 trying, once more, to resolve HttpRange-14. I absolutely do not want us to get into that debate (which was old in 2002) but I note that the solution proposed in Jeni's document is obviously interesting but, like all solutions, needs community buy-in that, AFAICT, is not present. The doc hasn't been updated since its FPWD and Jeni is no longer on the TAG so its future looks less than clear. It does, however, contain useful info. What I take away from this in terms of DWBP is: - Examples 1, 2 and 3 in the doc all show the same data - it's a useful example of how to be technology neutral (which Jeni went out of her way to remain). - The document highlights the need for data publishers to make it clear when the properties and values they publish describe the data or the metadata record. Example 5 is: { "@id": "http://photo.example.com/psd/12345", "type": "image", "creator": "Paul Downey", "license": "http://creativecommons.org/licenses/by/3.0/", "photo": "http://photo.example.com/psd/12345/original.jpeg", "last-modified": "2012-06-20T08:54:32Z" } So Paul Downey was last updated at 2012-06-20T08:54:32Z ? No, he was not, the landing page was (http://photo.example.com/psd/12345). And that's an image is it? No, it's a landing page. The image is at http://photo.example.com/psd/12345/original.jpeg and so on. All I think we should say is that when providing metadata, you need to be clear what you're describing. And bad practice around this is common. Here's an example: The DOI 10.1103/PhysRevD.89.032002 identifies an article. To look that up we have to put it on the end of the URI of a resolver service, let's use http://dx.doi.org/10.1103/PhysRevD.89.032002 Which, via a 303 redirect, takes us to http://link.aps.org/doi/10.1103/PhysRevD.89.032002 that then uses a 302 redirect to take us to a landing page about that article at http://journals.aps.org/prd/abstract/10.1103/PhysRevD.89.032002 We still haven't got the actual article of course but that's fine, http://dx.doi.org/10.1103/PhysRevD.89.032002 and 10.1103/PhysRevD.89.032002 are different. One identifies the article, one identifies the landing page. No problem there. As a human, I can click the 'Export Citation' button on the landing page that gets me this JSON: @article{PhysRevD.89.032002, title = {Search for a multi-Higgs-boson cascade in ${W}^{+}{W}^{$-${}}b\overline{b}$ events with the ATLAS detector in $pp$ collisions at $\sqrt{s}=8\text{\,}\text{\,}\mathrm{TeV}$}, author = {Aad, G. ...}, journal = {Phys. Rev. D}, volume = {89}, issue = {3}, pages = {032002}, numpages = {23}, year = {2014}, month = {Feb}, publisher = {American Physical Society}, doi = {10.1103/PhysRevD.89.032002}, url = {http://link.aps.org/doi/10.1103/PhysRevD.89.032002} } This provides lots of metadata about the article and everything's going well right up until that last line. The URL of the article is NOT http://link.aps.org/doi/10.1103/PhysRevD.89.032002 - as we've seen that's just a URL that redirects to the landing page, so perhaps that last property name should be landingPage (I'd say dcat:landingPage of course). Oh, and in case anyone is lulled into a false sense of security about URLs that end in DOIs, here's another URL: http://philarcher.org/10.1103/PhysRevD.89.032002 ;-) In terms of actions - action-119 can be closed, I'll bring the issues up when we next debate the relevant BPs. Phil [1] http://www.w3.org/TR/urls-in-data/ On 07/04/2015 22:53, Deirdre Lee wrote: > Hi, > > http://www.w3.org/2013/dwbp/track/actions/open > > In advance of the F2F, it's time for a spring clean. There are currently > 17 open actions, and I believe 15 of them have already been addressed > and can be closed. They are as follows. > > Can each person responsible for an action confirm it can be closed via > email. If I don't hear from you by Thursday, I will email you directly. > > 71 - Antoine > > 76, 115, 122, 128 – Eric S > > 85 – Mark H > > 101 – Sumit > > 102 – Lewis > > 103 – Caroline > > 112 – Newton > > 118, 119 – Ig/Phil > > 121- Ig > > 131- Tomas > > 145 – Carlos (linked to Issue 144) > > http://www.w3.org/2013/dwbp/track/actions/open > > Cheers, > Deirdre > > > > > -------------------------------------- > Deirdre Lee, Director > Derilinx - Linked & Open Data Solutions > > Web: www.derilinx.com > Email: deirdre@derilinx.com > Tel: +353 (0)1 254 4316 > Mob: +353 (0)87 417 2318 > Linkedin: ie.linkedin.com/in/leedeirdre/ > Twitter: @deirdrelee > > -- Phil Archer W3C Data Activity Lead http://www.w3.org/2013/data/ http://philarcher.org +44 (0)7887 767755 @philarcher1
Received on Wednesday, 8 April 2015 09:15:08 UTC