RE: Default values handling

The XQuery DM interprets defaulted attributes in schema as an indication
that they are added as full members in the data model. I would find it
dangerous to the consistency of the user experience, if we start adding
attributes that are there and then disappear.

And I still do not see a good way to preserve and infer your schema
information in a consistent way in all cases and oppose any such effort
at this stage of the XQuery language development. We need to ship and
should postpone features that can be done later.

Best regards
Michael (my opinion)

> -----Original Message-----
> From: public-qt-comments-request@w3.org [mailto:public-qt-comments-
> request@w3.org] On Behalf Of Antoine Mensch
> Sent: Thursday, February 12, 2004 1:10 AM
> To: Public-Qt-Comments@W3. Org
> Subject: Default values handling
> 
> 
> The DM document specifies that elements and attributes use the [schema
> normalized value] when constructing nodes from the PSVI. This means
that
> default values specified in the schema are used to synthetized
attributes
> that are not present in the original infoset. This is clearly needed
when
> performing queries on the data model. However, the DM does not seem to
> keep
> track of the [schema specified] property, which means that attributes
that
> are absent in the original infoset will be copied and serialized as if
> they
> were present. Is this a proper behavior when dealing with documents
that
> rely heavily on schema-specified default values (e.g. an XML Schema
> document)? When using a possible "preserve" validation mode previously
> mentioned by Don Chamberlin, copying and serializing default values is
in
> fact redundant, because the information is already present in the
original
> type (which is preserved).
> 
> Best regards,
> 
> Antoine Mensch
>

Received on Thursday, 12 February 2004 04:19:30 UTC