RE: Pattern matching (XSV vs. Xerces)

Our (TIBCO) validator also agrees with Xerces.  I think this is a case of an
unimplemented part of XSV. From the XSV status page (
http://www.ltg.ed.ac.uk/~ht/xsv-status.html
<http://www.ltg.ed.ac.uk/~ht/xsv-status.html> ):
 
"Partial support for pattern facet (basically everything except named
classes other than \d \s \w \D \S \W)"
 
So not recognizing \i and \c, it probably just reports valid.
 
xan
 
-----Original Message-----
From: Stanley Guan [mailto:stanley.guan@oracle.com]
Sent: Tuesday, December 03, 2002 1:53 PM
To: xmlschema-dev@w3.org
Cc: Henry S. Thompson; Kongyi Zhou
Subject: Pattern matching (XSV vs. Xerces)


Given the following element definition
 
         <element name ="Path2" minOccurs="0" maxOccurs="unbounded">
 
           <simpleType>
 
             <restriction base ="string">
 
               <pattern
value="(\.//)?((child::)?((\i\c*:)?(\i\c*|\*)))|\."/>
 
              </restriction>
 
           </simpleType>
 
         </element>
and an element in an instance document
         <Path2>.//.</Path2>
 
 
XSV thinks this is valid.  But, Xerces thinks this is invalid.  In my
opinion,
Xerces is right because '|' has the lowest precedence.  Am I right?
 
Thx,
 
-Stanley