W3C home > Mailing lists > Public > www-tag@w3.org > October 2010

Re: Generic processing of Fragment IDs in RFC 3023bis

From: Graham Klyne <GK-lists@ninebynine.org>
Date: Sat, 09 Oct 2010 17:47:43 +0100
Message-ID: <4CB09CAF.1090908@ninebynine.org>
To: Jonathan Rees <jar@creativecommons.org>, "www-tag@w3.org" <www-tag@w3.org>
Jonathan,

I think the muddle you mention is historically justfied ... the original rdf:ID 
(http://www.w3.org/TR/1999/REC-rdf-syntax-19990222/, section 2.2.1) was just ID, 
and it was intended to be the same as the XML ID as defining a fragment.

This constraint has been carried forward in slightly modified form in the later 
RDF/XML spec: http://www.w3.org/TR/REC-rdf-syntax/#constraint-id

#g
--


Jonathan Rees wrote:
> On Thu, Oct 7, 2010 at 10:38 AM, Graham Klyne <GK-lists@ninebynine.org> wrote:
>> Jonathan Rees wrote:
>>> (My factual question of whether generic XML processors must treat
>>> rdf:ID the same as xml:id hasn't been answered, by the way - so we're
>>> not sure there's a problem at all!)
>> I would say not.  Despite the apparent similarity of label, rdf:ID and
>> xml:ID are completely different attributes.  (I've seen suggestions that
>> rdf:ID be deprecated, as the same can be achieved using rdf:about.)
> 
> That's great - then there is no problem at all and we can promote
> generic processing without qualification! How did we get so tied up in
> knots about this?
> 
> Well, we would have to make sure that some generic validation doesn't
> reject fragids that are *not* defined by xml:id, i.e. are defined in
> some other way such as rdf:ID. That doesn't seem like much of a
> hardship - add a few words to 3023bis about it being OK if
> *additional* fragids are defined in other ways.
> 
> Here's how I got confused: The RDF/XML DTD
> (http://www.w3.org/XML/9710rdf-dtd/rdf.dtd) gives the rdf:ID attribute
> type ID, and the XML specs (including xml:id and Xpointer) do their
> very best to ensure that attributes with type ID are as much as
> possible the same as xml:id. The RDF/XML spec also makes rdf:ID very
> similar to xml:id - same syntactic and uniqueness constraints. So it
> seemed highly likely to me that rdf:ID defines fragids the same way
> that xml:id does.
> 
> The flaw in this argument is that this DTD for RDF/XML is not
> normative - nothing in the RDF/XML rec leads to any connection between
> rdf:ID and xml:id. So we should just ignore the DTD, or agitate to get
> it fixed.
> 
> (I still don't know whether having type ID is enough to make an
> attribute fragid-defining.)
> 
> Sorry if I contributed to this muddle.
> 
> Jonathan
> 
Received on Saturday, 9 October 2010 17:09:17 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 26 April 2012 12:48:28 GMT