W3C home > Mailing lists > Public > www-rdf-interest@w3.org > March 2004

Re: Namespaces

From: Benja Fallenstein <b.fallenstein@gmx.de>
Date: Sat, 27 Mar 2004 01:14:42 +0200
Message-ID: <4064B962.5040407@gmx.de>
To: Eric Jain <Eric.Jain@isb-sib.ch>
Cc: Jeremy Carroll <jjc@hplb.hpl.hp.com>, rdf-interest <www-rdf-interest@w3.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Eric Jain wrote:
| Incidently, is there any good reason to not create resources such as
| http://foo.com/bar/10 which can't be split? I happen to have a lot of
| resources that already have numeric identifiers which people are
| familiar with, so a natural solution would seem to be to specify an
| http://foo.com/bar/ as xml:base and then describe resources using
| rdf:about="10", for example. But if this is likely to cause problems
| with tools, I'd consider using some prefix for the numbers. (Seems to
| work fine with Jena, as far as I can tell.)

It'll cause problems with the RDF/XML serialization if you try to
serialize *properties* named that way. For N3 &c it should not cause
problems because even though these *can* do namespace/name splitting,
they can also always give the full URI. RDF/XML always requires property
URIs to be split, and never splits URIs other than property and class
URIs. (Class URIs can also be serialized without splitting them, using
<rdf:Description><rdf:type rdf:about="..."/></rdf:Description> rather
than <...></...>.)

Hope this clears something up rather than making it even more unclear :-)

- - Benja
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFAZLlhUvR5J6wSKPMRAprbAJ9D4B6pfmWPzmrQuOGq3MkASkDRfQCgykia
AbUYI2LaePqFEEfuVpojN4I=
=ODra
-----END PGP SIGNATURE-----
Received on Friday, 26 March 2004 18:15:25 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 18 February 2014 13:20:07 UTC