- From: Phil Archer <phila@w3.org>
- Date: Fri, 01 May 2015 09:14:39 +0100
- To: Christophe Guéret <christophe.gueret@dans.knaw.nl>, Makx Dekkers <mail@makxdekkers.com>
- CC: Public DWBP WG <public-dwbp-wg@w3.org>
May I offer this as 'the resources to implement it' ;-) RewriteEngine On RewriteBase /2013/share-psi/bp/cas/ RewriteCond %{REQUEST_URI} !/2013/share-psi/bp/cas-[0-9]{8}/ RewriteRule ^(.*)$ /2013/share-psi/bp/cas-20150113/$1 [P] This is the .htaccess file at http://www.w3.org/2013/share-psi/bp/cas/ - the 'latest version' URI for a best practice from the Share-PSI project. Dated versions are at http://www.w3.org/2013/share-psi/bp/cas-20150113/ http://www.w3.org/2013/share-psi/bp/cas-20150105/ The third line is the key one. If the request URI does not include the date string, line 4 redirects the request to the dated version. This is edited by hand but you could presumably set up a system that updated the .htaccess file as part of the publishing process. When I was first shown this I wondered why it included the capture and back reference. That's to handle fragment IDs (or query strings). HTH Phil. On 01/05/2015 09:01, Christophe Guéret wrote: > Hoi Phil, Makx, > > We ran into similar issues when working on the publication of the UDC > master reference file as LOD. For it there is a need for both version-based > URI so that people can point to a specific release of the concept and > version-free URIs to point to whatever is the current version. > > It has been decided to always create versioned URIs and establish redirects > from their version-less counterparts. Works fine on the paper, we are still > looking for the resources to implement it ;-) > > Cheers, > Christophe > > -- > Sent with difficulties. Sorry for the brievety and typos... > Op 30 apr. 2015 19:29 schreef "Makx Dekkers" <mail@makxdekkers.com>: > >> Phil, >> >> Interesting issue. I'd like to mention that in work that is being done >> around the DCAT application profile for data portals in Europe ( >> https://joinup.ec.europa.eu/node/137964/), it has been noted that in >> DCAT, the W3C recommendation for describing datasets, there is currently no >> recommended way to describe time series. >> >> As far as I am aware, the approach you suggest cannot be expressed in DCAT >> as it is now. For the Application Profile, there is a discussion on how to >> model time series in DCAT, and it is scheduled that a draft for public >> review will be issued in the middle of May. >> >> Makx. >> >> >>> -----Original Message----- >>> From: Phil Archer [mailto:phila@w3.org] >>> Sent: 30 April 2015 18:28 >>> To: Public DWBP WG >>> Subject: Thought for URI section >>> >>> I'm using this as a jotter so I don't forget. >>> >>> I'm writing a doc and want to link to the 2014 Global Open Data Index. >>> Well, the index is at http://index.okfn.org/place/ and that shows the >>> 2014 results. If I want last year's I go to >> http://index.okfn.org/place/2013/. >>> But I want to link persistently to the 2014 set *today* that happens to >> be the >>> current one. Presumably when they do next year's index that will be at >>> http://index.okfn.org/place/ and the 2014 data will be at >>> http://index.okfn.org/place/2014 - but that doesn't exist yet. >>> >>> That's more evidence, IMO, that for any time series you always need a >> dated >>> URI and a latest version URI. >>> >>> Rant over. >>> >>> >>> >>> -- >>> >>> >>> Phil Archer >>> W3C Data Activity Lead >>> http://www.w3.org/2013/data/ >>> >>> http://philarcher.org >>> +44 (0)7887 767755 >>> @philarcher1 >> >> >> > -- Phil Archer W3C Data Activity Lead http://www.w3.org/2013/data/ http://philarcher.org +44 (0)7887 767755 @philarcher1
Received on Friday, 1 May 2015 08:14:44 UTC