[sc34wg3] TMCL Max int using extended XML Schema DataType

Lars Heuer heuer at semagia.com
Thu Mar 26 10:24:28 EDT 2009

> Interesting, I wasn't aware of it and I am not sure if I understood it
> completely. :) Anyway, isn't this solution more less equivalent to our
> INF-solution: We have to check somewhere if the value is
> '*'^^ctm:integer which would be the same as checking if the value is
> 'INF'^^xsd:double (which would be the only possible datatype !=
> xsd:integer in TMCL-constraints)? The only difference would be that
> all xsd:integers are valid ctm:integers, which is not possible with
> the INF-solution.

... or does CTM drop xsd:integer and ctm:integer is the only datatype
CTM (and TMCL) supports? Otherwise I don't understand the advantage of
ctm:integer since it is still another datatype != xsd:integer.

Best regards,

More information about the sc34wg3 mailing list