Also, rangeValue could derive from xsd:token and not just xsd:string so we could pick up the normalization rules.
Hmm, but then people couldn't use spaces - is this going to cause people problems? I tend to write lists "2, 5, 6". Could easily ditch the spaces thoug. Also can you have commas in xsd:tokens? Thoughts please folks.
According to <URL:http://www.w3.org/TR/xmlschema-2/#token> commas are fine in token and non-standard whitespace is collapsed, so that allows the RE for ranges to become: RE: (\d+( ?- ?\d*)?|- ?\d+)( ?, ?(\d+( ?- ?\d*)?|- ?\d+))* ^^^^^^^^^^^^^^ ^^^^^^ ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Expl: D or D- or D-D or -D or a comma-sep list of them
(Yes, the \d is allowed in XSD; I looked it up specifically. <URL:http://www.w3.org/TR/xmlschema-2/#dt-regex> The XSD rules for REs in Appendix F are among the clearest RE syntax descriptions I've seen.)
I've put this version in for now - as it seems the most complete. However, if I'm correct the following is a valid string "34-45 55-66" Am I correct? Is there any way to force people to put a comma between these? steve.. -- ------------------------------------------------------------------------ Dr A. Stephen McGough ------------------------------------------------------------------------ Research Associate, Imperial College London, Department of Computing, 180 Queen's Gate, London SW7 2BZ, UK tel: +44 (0)207-594-8310 fax: +44 (0)207-581-8024 ------------------------------------------------------------------------ Assistant Warden, West Wing, Beit Hall, Imperial College, Prince Consort Road, London, SW7 2BB tel: +44 (0)207-594-9910 ------------------------------------------------------------------------