[Bug 5319] [DM] Default value now well-defined for mixed content

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


C. M. Sperberg-McQueen <cmsmcq@blackmesatech.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |cmsmcq@blackmesatech.com




--- Comment #3 from C. M. Sperberg-McQueen <cmsmcq@blackmesatech.com>  2010-07-03 00:00:23 ---
Responding to comment 2:  if the draft erratum for XSD 1.0 is eventually
accepted, it does indeed make clear (in its current form) that no new character
information items are added to empty elements with a declared default or fixed
value.  In the case of elements with simple content, the default is used to
populate the [schema normalized value], but mixed-content elements don't have a
[schema normalized value].  (They could, but as XSD 1.0 and 1.1 are currently
specified, they don't.)

The effect is essentially that a default value supplied for an element with
mixed content doesn't seem to have much effect.  (That may be a sign that the
decision made by the Schema WG is a bad one and that QT should push back
against it.  I don't know.)

If I were responsible for a processor that did supply default values for such
elements, I would (a) plan to make the newly-clarified behavior an option for
my users and (b) describe the existing behavior as a non-standard method of
building the XDM instance, which supplies a value from the [schema default]
property of the PSVI under certain conditions (specifically, when the element
has no character information item children, and a [schema default] property is
given -- if you ONLY supply the default value when the type is a complex type
with complex content, then add also 'and if no [schema normalized value] is
present in the PSVI for the element).  But I am speaking only for myself.

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Saturday, 3 July 2010 00:00:26 UTC