It's apparently permissible for an element with mixed content to have a
default (or fixed) value.

Section 3.3.1 of Part 1 says:

If default is specified, and if the element being =B7validated=B7 is =
empty, then
the canonical form of the supplied constraint value becomes the [schema
normalized value] of the =B7validated=B7 element in the =
=B7post-schema-validation
infoset=B7.

But the definition of [schema normalized value] says:

1 If clause 3.2 of Element Locally Valid (Element) (=A73.3.4) and =
Element
Default Value (=A73.3.5) above have not applied and either the =B7type
definition=B7 is a simple type definition or its {content type} is a =
simple
type definition, then the =B7normalized value=B7 of the item as =
=B7validated=B7.
2 otherwise =B7absent=B7.

which implies that if the type definition is a complex type with complex
content, then the schema normalized value is always absent.

There seems to be a contradiction here: can an element with mixed =
content
have a [schema normalized value], or not?

Furthermore, the definition of [schema normalized value] appears to say =
that
the [schema normalized value] will always be =B7absent=B7 if Element =
Default
Value (=A73.3.5) applies, whereas Element Default Value (=A73.3.5) says =
that in
this situation the [schema normalized value] will be the canonical =
lexical
representation of the {value constraint} value. They can't both be =
right...



Michael Kay
http://www.saxonica.com/ 



From sandygao@c... Tue Jan 03 15:27:01 2006
Received: from aji.w3.org ([133