- From: <bugzilla@wiggum.w3.org>
- Date: Fri, 27 Jul 2007 16:05:18 +0000
- To: public-qt-comments@w3.org
- CC:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=4519
sandygao@ca.ibm.com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |sandygao@ca.ibm.com
------- Comment #3 from sandygao@ca.ibm.com 2007-07-27 16:05 -------
Update from XML Schema WG.
Schema 1.0 has the following rules about id-ness:
- only nodes *declared* with type ID or types derived from it (by
extension/restriction) are viewed as ID values
- only nodes *declared* with type IDREF or types derived from it (by
extension/restriction) are viewed as IDREF values
- only nodes *declared* with type IDREFS or types derived from it (by
extension/restriction) are viewed as IDREFS values
All other cases (ID/IDREF/IDREFS appear in a union; user defined list of IDREF;
...) are *not* viewed as ID/IDREF values.
Schema 1.1 changed the above situation (as part of fixing bug 2041):
- For every atomic *actual value* (may be a member in a list value) whose type
is ID or a type derived (restriction/extension) from it, it's an ID value.
- For every atomic *actual value* (may be a member in a list value) whose type
is IDREF or a type derived (restriction/extension) from it, it's an IDREF
value.
Received on Friday, 27 July 2007 16:05:28 UTC