1409 2005-05-13 20:13:31 +0000 [DM] are lax attributes of type xdt:untypedAtomic? 2005-09-29 11:03:33 +0000 1 1 1 Unclassified XPath / XQuery / XSLT Data Model 1.0 Last Call drafts PC Windows XP CLOSED FIXED P2 normal --- 1 mrys Norman.Walsh public-qt-comments oldest_to_newest 3336 0 mrys 2005-05-13 20:13:31 +0000 "- The [validity] property exists and is not "valid", or the [validition attempted] property exists and is not "full", the schema type of an element is xs:anyType and the type of an attribute is xdt:untypedAtomic." Wasn't that changed in Brisbane to be xs:anySimpleType for attributes? The Brisbane minutes are not a 100% clear. The advantage of xdt:untypedAtomic is that since that is the atomized dynamic type in this case anyway, it gives a better static type inference since we can statically assume such attributes (eg. in lax validation contexts) to be always untyped. The advantage of xs:anySimpleType is that it is aligned with schema. 3151 1 Norman.Walsh 2005-05-17 15:56:09 +0000 Raleigh f2f resolution: # The [validity] property exists and is "invalid", or the [validition attempted] property exists and is "partial", the schema type of an element is xs:anyType and the type of an attribute is xs:anySimpleType. # The [validity] property exists and is "notKnown", and the [validition attempted] property exists and is "none", the schema type of an element is xdt:untyped and the type of an attribute is xdt:untypedAtomic. # The [validity] or [valadition attempted] properties do not exist, the schema type of an element is xdt:untyped and the type of an attribute is xdt:untypedAtomic. See also http://www.w3.org/XML/2001/06/validity-outcomes.html