W3C home > Mailing lists > Public > public-qt-comments@w3.org > January 2013

[Bug 20828] Typed Data Feature

From: <bugzilla@jessica.w3.org>
Date: Wed, 30 Jan 2013 21:16:12 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-20828-523-83BflexBYj@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=20828

Michael Kay <mike@saxonica.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mike@saxonica.com

--- Comment #1 from Michael Kay <mike@saxonica.com> ---
We need to say a little bit more than this.

We need to say something about the validate expression. Either we say that a
processor that does not support typed data must not support validate (that is,
it must not support the schema-aware feature). Or we might allow a processor to
support validate, but to do so in such a way that no type annotations are
present in the result.

Furthermore (and this is where the whole thing started), 3.9.1.3 ยง5.j says
this: 

"If construction mode in the static context is strip, the type-name property is
xs:untyped. On the other hand, if construction mode is preserve, the type-name
property is xs:anyType."

we should change this rule to say that if the typed data feature is not
supported then the type is xs:untyped regardless of construction mode; or
alternatively, to say that if the typed data feature is not supported then the
construction mode must be strip.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Wednesday, 30 January 2013 21:16:15 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 30 January 2013 21:16:16 GMT