- From: <bugzilla@wiggum.w3.org>
- Date: Sun, 22 May 2005 15:41:01 +0000
- To: public-qt-comments@w3.org
- Cc:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=1479 Summary: 3.11 Embedded Stylesheet Modules; how to express type information Product: XPath / XQuery / XSLT Version: Last Call drafts Platform: PC OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: XSLT 2.0 AssignedTo: mike@saxonica.com ReportedBy: frans.englich@telia.com QAContact: public-qt-comments@w3.org In the XSLT 2.0 Working Draft 4 April 2005, http://www.w3.org/TR/2005/WD-xslt20-20050404/, the Note paragraph in section "3.11 Embedded Stylesheet Modules" says the following: "In order for such an attribute to be used with the XPath idFO function, it must actually be declared in the DTD or schema as being of type ID. The same requirement typically applies if the identifier is to be used as a fragment identifier in a URI reference." According to my knowledge an attribute must be typed to be of type ID. The paragraphs says that the type information MUST be supplied via a DTD or schema. However, according to my knowledge there is another mechanism for adding ID type information: xml:id. In the similar vene, from what I know one could argue that a DTD is a particular type of schema. In order to not constrain the user's possibilities and be open to future developments in the typing-area, it might be of interest to phrase the paragraph more generically, to only dictate that the attribute needs to be of type ID, and to give DTD as an /example/ of how to express that type information. According to my interpretation, it would be normatively wrong to accepttype information expressed via xml:id. However, considering the controversies over xml:id, this is perhaps intentional. Cheers, Frans Frans Englich KDE Developer
Received on Sunday, 22 May 2005 15:41:04 UTC