As stated before, I would suggest to use the bare link to the database
plus your public identifier, instead of the direct link with the
internal node identifier. It's not as linked data like as it could be,
but easily readable and independent of the actual hosting location.
Cheers,
Kai
Am 27.08.2015 um 17:34 schrieb Antoine Isaac:
> Hi,
>
> Following today's call [1] I've updated our links to the database [2]
> from the two deliverables [3,4].
> However I've done it only for the 'bare' links to the database.
> The PURL indeed don't work with the parameters that redirect to
> individual elements in the database.
> I.e. it's not possible to change
> http://lelystad.informatik.uni-mannheim.de/rdf-validation/?q=node/424
> into
> http://purl.org/net/rdf-application-profiles/?q=node/424
>
> Unless someone thinks we should really change the links, I'd rather stop
> my effort here.
>
> Best,
>
> Antoine
>
> [1] https://etherpad.wikimedia.org/p/dcmi-ap-27-08-2015
> [2] http://purl.org/net/rdf-application-profiles
> [3]
> http://wiki.dublincore.org/index.php/RDF_Application_Profiles/Requirements
> [4]
> http://wiki.dublincore.org/index.php/RDF_Application_Profiles/UCR_Deliverable
>
--
Prof. Dr. Kai Eckert, Stuttgart Media University
http://www.kaiec.org/
PGP Public Key: http://www.kaiec.org/2012/pgp/pubkey.asc
A987 3760 12A6 35A4 E6D2 577E 513A 6B84 C755 5A67
|