W3C home > Mailing lists > Public > public-qt-comments@w3.org > April 2006

[Bug 3032] Setting the is-id and is-idref property on element nodes

From: <bugzilla@wiggum.w3.org>
Date: Mon, 24 Apr 2006 18:17:46 +0000
CC:
To: public-qt-comments@w3.org
Message-Id: <E1FY5d4-0000Rr-CW@wiggum.w3.org>

http://www.w3.org/Bugs/Public/show_bug.cgi?id=3032





------- Comment #4 from mike@saxonica.com  2006-04-24 18:17 -------
Another option is:

for is-id: if the typed value contains exactly one item, and that item is an
instance of xs:ID, then set the is-ID property. (There's not much point in
setting the property if the value contains no items or more than one item, as
id() will never retrieve it anyway).

for is-idref: OK as written, but applying it to both elements and attributes.

I actually think this rule is an improvement: it means that you can create a
subtype of xs:IDREF and then construct a list whose items belong to this
subtype, and this list will now be treated in the same way as an xs:IDREFS,
which was not previously the case. But I'm a little bit concerned that the full
implications need some careful thought.
Received on Monday, 24 April 2006 18:17:55 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:57:11 UTC