/ Graham <[EMAIL PROTECTED]> was heard to say: | -1 on the regex. It's completely | unreadable and hides whatever | additional constraints it adds. Write | those down in English please.
Well, how about English and the regex? I'm worrying about
interoperability here. There's considerable pressure to use RFC 3339,
but I can't think of any practical, interoperable way to use RELAX NG
or W3C XML Schema to constrain the value of Date Constructs to RFC
3339. (I could do it by defining my own data type in RELAX NG, but
that wouldn't be interoperable; I could do it by using just
xsd:dateTime, but that wouldn't be constraining enough.)
I suppose I could just use the combination of xsd:dateTime and the
regular expression in my schema to implement the prose if we took the
regex out of the spec.
*shrug* It's been a long, hard day and I don't have any fight left in
me. Given that I'm reasonably confident that xsd:dateTime+regex is
isomorphic to the set of RFC 3339 date-times that we want to allow,
I'll accept whatever the group decides.
Be seeing you,
norm
--
Norman Walsh <[EMAIL PROTECTED]> | We learn from experience that not
http://nwalsh.com/ | everything which is incredible is
| untrue.--Cardinal De Retz
pgp0ZHDBcLdRp.pgp
Description: PGP signature
