W3C home > Mailing lists > Public > www-tag@w3.org > January 2004

RE: Updated finding: QNames in Content

From: Paul Cotton <pcotton@microsoft.com>
Date: Mon, 12 Jan 2004 07:36:16 -0800
Message-ID: <33D970235519324D988AFFDE7EA2E24C92CB2A@RED-MSG-41.redmond.corp.microsoft.com>
To: "Norman Walsh" <Norman.Walsh@Sun.COM>
Cc: <www-tag@w3.org>

I would like to suggest that we add another example of using QNames to
this finding.

The XQuery/XPath specifications [1] use QNames to identify functions in
these languages.  Since this is another example of a different use of
QNames it might be good if the finding could state that this is okay.


[1] http://www.w3.org/TR/xquery-operators/#namespace-prefixes 

Paul Cotton, Microsoft Canada 
17 Eleanor Drive, Nepean, Ontario K2E 6A3 
Tel: (613) 225-5445 Fax: (425) 936-7329 


> -----Original Message-----
> From: www-tag-request@w3.org [mailto:www-tag-request@w3.org] On Behalf
> Norman Walsh
> Sent: January 6, 2004 3:19 PM
> To: www-tag@w3.org
> Subject: Updated finding: QNames in Content
> Before the winter break (Happy New Year!), I took an action to revise
> the "Using Qualified Names (QNames) as Identifiers in Content"
> Finding. The editorial draft of my revisions is available now at
>   http://www.w3.org/2001/tag/doc/qnameids.html
> I've added some explicit references to C14N, DSig, and other specs
> that have experienced difficulties with QNames in content.
> I've also made the "Architectural Statement" at the end significantly
> more assertive. Several folks expressed concern that I was not making
> a strong enough case in the conclusion.
>                                         Be seeing you,
>                                           norm
> --
> Norman.Walsh@Sun.COM / XML Standards Architect / Sun Microsystems,
> NOTICE: This email message is for the sole use of the intended
> recipient(s) and may contain confidential and privileged information.
> Any unauthorized review, use, disclosure or distribution is
> If you are not the intended recipient, please contact the sender by
> reply email and destroy all copies of the original message.
Received on Monday, 12 January 2004 10:39:14 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:56:03 UTC