- From: Benja Fallenstein <b.fallenstein@gmx.de>
- Date: Tue, 13 Jan 2004 18:06:07 +0100
- To: Nick Knouf <nknouf@MIT.EDU>
- Cc: Pete Johnston <p.johnston@ukoln.ac.uk>, www-rdf-interest@w3.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Nick Knouf wrote: | As a followup, I was wondering what people consider to be best practices | when using a persistent URL service like purl.org. For my bibTeX in OWL | schema [1] the PURL for the namespace is | | http://purl.oclc.org/NET/nknouf/ns/bibtex | | That PURL, when resolved (it goes to the schema definition), already has | the # appended. On the other hand, I could leave the # sign off of the | PURL and the namespace would be | | http://purl.oclc.org/NET/nknouf/ns/bibtex# | | Does anyone have feelings one way versus the other? Well, if you use the former, you get URIs like ~ http://purl.oclc.org/NET/nknouf/ns/bibtexsomething for e.g. bibtex:something. That seems quite ugly to me -- do you want to redirect all of these independently through PURL? If you use the latter, you get URIs like ~ http://purl.oclc.org/NET/nknouf/ns/bibtex#something which seem much nicer. Cheers, - - Benja -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFABCV/UvR5J6wSKPMRAvRQAKCMn/j6rLPA16WYeTicVTIzTz84lQCfbhev fvXMkSrKaBJeISgl0Ncn4RI= =p+ys -----END PGP SIGNATURE-----
Received on Tuesday, 13 January 2004 12:12:50 UTC