W3C home > Mailing lists > Public > public-semweb-lifesci@w3.org > April 2005

Using LSIDs with rdf:ID attributes

From: Peter Hussey <peterhus@gmail.com>
Date: Fri, 29 Apr 2005 09:14:59 -0700
Message-ID: <16a2f4eb05042909145f42b936@mail.gmail.com>
To: public-semweb-lifesci@w3.org
Cc: Mark Igra <migra@fhcrc.org>

I am working on an XML schema for describing experiment data to be
loaded into a repository.  I want to use LSIDs for the identifiers of
things in the database.  I want these identifiers to be described in
an instance document using the RDF/XML syntax for identifiers.  In
particular I want to use the rdf:ID attribute within an xml:base URI
to assign an LSID to an entity that will be loaded into the
repository.

The spec for the rdf:ID attribute says that the resolved name of a
rdf:ID attribute contains a "#" fragment separator.  For example,

  <?xml version="1.0" ?> 
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
              xml:base="URN:LSID:ebi.ac.uk:SWISS-PROT.accession:P34355">
<rdf:Description rdf:ID="FractionA15">
</rdf:Description>
  </rdf:RDF>

The rdf rules say that the resulting id looks like

URN:LSID:ebi.ac.uk:SWISS-PROT.accession:P34355#FractionA15

I can't find any examples nor any references that state clearly
whether this is a legal LSID.   An LSID is a URN, the only URN spec I
can find says that "#" is reserved.  Subsequent URI specs describe
URNs as a subset of URIs, and the rules for fragments in URIs (there
can be only one, the right-most portion of the URI).

If fragments are legal in LSIDs, the following questions also arise: 
is an LSID  allowed to have a fragment separator in either the object
identifier OR the revision identifier?  If an LSID has a fragment in
the obejct identifier is a revision identifier still allowed?

thanks in advance,
Peter Hussey
LabKey Software

the specs I've been trying to understand are the following:
RDF/XML spec:
http://www.w3.org/TR/rdf-syntax-grammar/#section-Syntax-ID-xml-base

URN spec:
http://www.rfc-archive.org/getrfc.php?rfc=2141

latest URI spec 
http://www.rfc-archive.org/getrfc.php?rfc=3986
Received on Saturday, 30 April 2005 08:06:38 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:00:40 GMT