- From: <bugzilla@wiggum.w3.org>
- Date: Fri, 18 Jan 2008 09:11:53 +0000
- To: www-xml-schema-comments@w3.org
- CC:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=5003 ------- Comment #14 from mike@saxonica.com 2008-01-18 09:11 ------- I'm fine having a rule that says "if the language is DE then the currency must be EUR". But what is the object to which this rule relates? I don't think it's a rule about the validity of the currency, I think it's a rule about the validity of some object that contains both a language and a currency. Now we could have done this differently, of course. The principle outlined above is not an absolute. But it happens to be an assumption that's built pretty deeply into QT's adoption of a type system based on XML Schema. When in XSLT I do: <invoice xml:lang="en"> <xsl:copy-of select="$payment" validation="preserve"/> </invoice> I'm relying on the fact that if the payment was valid in one context, then it is going to remain valid in a different context. So I don't think there's anything philosophically absurd about the idea that the validity of an object should be context-sensitive, I'm just saying that changing the rules of the game in this way is going to be unacceptable to two of the important stakeholders.
Received on Friday, 18 January 2008 09:15:57 UTC