RE: URN as namespace URI for RDF Schema (run away... run away... ;-)

Hi Patrick:
 
One question, one observation.
 
I thought the advantage of using fragments was that (after reconstruction of
the original URI from the QName) one would have a natural means of
addressing into an XML document (describing the schema) using XPointer
methodology. Am I wrong in this?
 
I note that you use the term URIref a la RFC 2396. -bis recognizes fragments
as natural components of URIs. Don't you feel that URIref is a somewhat
challenging concept - relating as it seems to an unrequited URI. ;)
 
Tony

But be very careful to ignore all those schemas which use URIrefs
with fragment identifiers to denote vocabulary terms, including
the official RDF schemas for RDF, RDFS, OWL, etc... ;-) ;-) ;-)
 
Particularly good example schemas to emulate [1] are:
 
 <http://sw.nokia.com/schemas/general/VOC-1.0.rdf>
http://sw.nokia.com/schemas/general/VOC-1.0.rdf 
 <http://sw.nokia.com/schemas/nokia/FN-1.2.rdf>
http://sw.nokia.com/schemas/nokia/FN-1.2.rdf 
 <http://sw.nokia.com/schemas/nokia/MARS-3.1.rdf>
http://sw.nokia.com/schemas/nokia/MARS-3.1.rdf 
 
Note the use of the VOC-1 vocabulary to define functionally
significant sets of terms, including the ability to group
terms by subvocabularies, which fully alleviates the need
to pay any attentions whatsoever to any syntactic features
employed by the RDF/XML serialization, namely XML namespaces.
 
Also, note the benefit of using http: URIs (not URIrefs
with fragment identifiers) to denote your vocabulary
terms per the following real-world examples:




********************************************************************************
DISCLAIMER: This e-mail is confidential and should not be used by anyone who is not the original intended recipient. If you have received this e-mail in error please inform the sender and delete it from your mailbox or any other storage mechanism. Neither Macmillan Publishers Limited nor any of its agents accept liability for any statements made which are clearly the sender's own and not expressly made on behalf of Macmillan Publishers Limited or one of its agents. Please note that neither Macmillan Publishers Limited nor any of its agents accept any responsibility for viruses that may be contained in this e-mail or its attachments and it is your responsibility to scan the e-mail and attachments (if any). No contracts may be concluded on behalf of Macmillan Publishers Limited or its agents by means of e-mail communication. Macmillan Publishers Limited Registered in England and Wales with registered number 785998 Registered Office Brunel Road, Houndmills, Basingstoke RG21 6XS
********************************************************************************