Lists Home |
Date Index |
>And if the user interface is an xml editor into which the user enters
>the content for their E-Catalog or what have you. To my mind the person
>using the editor is still a user.
then you have to employ a human to interpret the dates and validate the
numbers. Either that or specify the fields as strings, possibly
incorporating loose validation via regular expressions, if you have a
recipient program that expects that level of validation.
XSD types are great for Web Service (program-to-program) use cases in my
opinion - you get the choice of specifying language-level types (eg
xs:byte) where appropriate, or application-specific (eg xs:long, with
maxExclusive and minInclusive) where more appropriate. And for
human-to-human use cases, you can just leave them all as strings if
that's the functionality you want. So what's the problem?