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

[Bug 20949] validate type xs:untyped

From: <bugzilla@jessica.w3.org>
Date: Tue, 19 Mar 2013 16:50:23 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-20949-523-CgFK74Z8GG@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=20949

--- Comment #1 from Jonathan Robie <jonathan.robie@gmail.com> ---
I would like to merge these rules into bullet point 3 of 3.18 Validate
Expressions:

* If validation mode is strict, the validated element must have a top-level
element declaration in the effective schema, and must conform to this
declaration.
* If validation mode is lax, the validated element must conform to its
top-level element declaration if such a declaration exists in the effective
schema. If validation mode is lax and there is no top-level element declaration
for the element, and the element has an xsi:type attribute, then the xsi:type
attribute must name a top-level type definition in the effective schema, and
the element must conform to that type.
* If a type name is specified in the validate expression, no attempt is made to
locate an element declaration matching the name of the validated element; the
element can have any name, and its content is validated against the named type.
If the type name is xs:untyped, all elements will receive the type annotation
xs:untyped, and all attributes will receive the type annotation
xs:untypedAtomic. If the type name is xs:untypedAtomic, it checks that the node
has no children, and the node receives the type annotation xs:untypedAtomic.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Tuesday, 19 March 2013 16:50:24 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 15:45:52 UTC