W3C home > Mailing lists > Public > www-tag@w3.org > September 2008

RE: ACTION-156: Review of http://www.w3.org/2001/tag/doc/selfDescribingDocuments-2008-05-12.html

From: Williams, Stuart (HP Labs, Bristol) <skw@hp.com>
Date: Mon, 15 Sep 2008 13:37:02 +0000
To: "noah_mendelsohn@us.ibm.com" <noah_mendelsohn@us.ibm.com>
CC: "www-tag@w3.org" <www-tag@w3.org>
Message-ID: <233101CD2D78D64E8C6691E90030E5C81B6C2D1405@GVW1120EXC.americas.hpqcorp.net>

Hello Noah,

> -----Original Message-----
> From: noah_mendelsohn@us.ibm.com [mailto:noah_mendelsohn@us.ibm.com]
> Sent: 13 September 2008 02:14
> To: Williams, Stuart (HP Labs, Bristol)
> Cc: www-tag@w3.org
> Subject: RE: ACTION-156: Review of
> http://www.w3.org/2001/tag/doc/selfDescribingDocuments-2008-05-12.html
>
> Stuart Willams wrote:
>
>
> > Re 4.2 URI Based Extensibility (anal) comment on:
> >
> > "This [dynamic spec discover, implementation...] is done by:
> >  - ensuring that every specification, and in many cases each markup
> > tag or data value used, is identified with a URI."
> >
> >
> > Maybe we are talking at cross purpose. Maybe you are talking about
> > the markup and data values used in the specifications themselves -
> > eg XPATH/XQuery establish URI both for a bunch of functions and
> > operators, but also the corresponding part of the specification
> > document that describe each function/operator.
>
> I meant to alert you to the fact that in the draft published last week
> [1], I made a small change that I am hoping will ease your
> concern.  The
> phrase in question now reads:
>
> "ensuring that every specification, and in many cases each >markup tag
> name< or data value used, is identified with a URI"
>
> I hope this helps.
>
> Noah
>
> [1] http://www.w3.org/2001/tag/doc/selfDescribingDocuments-2008-09-08
>
>
> --------------------------------------
> Noah Mendelsohn
> IBM Corporation
> One Rogers Street
> Cambridge, MA 02142
> 1-617-693-4036
> --------------------------------------

Thanks for trying - I can live with the change, however, it does remain unclear to me particularly wrt to "markup tag names" whether you are talking of: 1) the name of an occurence of a tag in a document (which might be named by say an xpath based frag id extending a document URI - though formally the FYN story stumbles a little in RFC 3026) or 2) the name of a kind of element eg. the xhtml html element which presumably has to appeal to something like schema component designators. However, I suppose given that I can conceive of way to do either it perhaps doesn't matter what you had intended.

Stuart
--
Hewlett-Packard Limited registered Office: Cain Road, Bracknell, Berks RG12 1HN
Registered No: 690597 England
Received on Monday, 15 September 2008 13:39:58 GMT

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