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

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


Norman.Walsh@Sun.COM changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED




------- Comment #1 from Norman.Walsh@Sun.COM  2006-04-24 16:50 -------
Proposal for resolving this issue:

Section 6.2.4, make the following changes:

is-id

  If the element is a complex type with element-only content, the
  is-id property is false. Otherwise, if any of the atomic values in
  the typed-value of the element is of type xs:ID, or a type derived
  from xs:ID, the is-id property is true, otherwise it is false.

is-idrefs

  If the element is a complex type with element-only content, the
  is-idrefs property is false. Otherwise, if any of the atomic values
  in the typed-value of the element is of type xs:IDREF or xs:IDREFS,
  or a type derived from one of those types, the is-idrefs property is
  true, otherwise it is false.

In 3.3.1.3, replace the bulleted list with the following:

* Where union types occur, the implementation must be able to deliver
  the typed-value as an instance of the appropriate member type. For
  example, if the type an element node is my:integer-or-string, which
  is defined as a union of xs:integer and xs:string, and the
  string-value of the node is "47", the implementation must be able to
  deliver the typed-value of the node as either the integer 47 or the
  string "47", depending on which member type validated the element.

* Where types of xs:QName, xs:NOTATION, or types derived from one of
  these types occur, the implementation must be able to deliver the
  typed-value as a triple including a local name, a namespace prefix,
  and a namespace URI, even though the namespace URI is not part of
  the string-value (see 3.3.3 QNames and NOTATIONS).

Received on Monday, 24 April 2006 16:50:30 UTC