FWD: XLIFF 1.2 Schema(s) xpath expression issue

Hi Bryan and Doug: 
  
 
  
As the editors of the XLIFF XSD's, could you guys please have a look at this email from Asgeir and figure out if we need to revise the XSD or otherwise address the issue?  Input from the TC is encouraged. It seems clear cut but I didn't want to introduce any problems by editing without consulting your expertise.
  
 
  
Doug's been the most recent schema editor,  so we should maintain continuity at this stage of
 the game unless he's unavailable.
  
 
  
Many thanks to Asgeir for his input...
  
 
  
Thanks,
  
Tony
  
 
  
-----Original Message-----
From: Asgeir Frimannsson [mailto:] 
Sent: 09 May 2006 21:22
To: Tony
 Jewtushenko
Subject: XLIFF 1.2 Schema(s) xpath expression issue
  
 
  
Hi Tony,
  
 
  
A small issue in the XLIFF 1.2 schema that causes some issues when
  
validating the schema itself:
  
 
  
(Starting from line 2030 in strict, 2051 in
 transitional)
  
            <xsd:keyref name="KR_tu_segsrc_mid" refer="xlf:U_tu_segsrc_mid">
  
                  <xsd:selector xpath="./xlf:target/xlf:mrk | ./xlf:alt-trans"/>
  
                  <xsd:field xpath="@mid"/>
  
            </xsd:keyref>
  
 
  
The regular expression for the xpath attribute is according to the XML
  
Schema xsd:
  
(\.//)?(((child::)?((\i\c*:)?(\i\c*|\*)))|\.)(/(((child::)?((\i\c*:)?(\i\c*|\*)))|\.))*(\|(\.//)?(((child::)?((\i\c*:)?(\i\c*|\*)))|\.)(/(((child::)?((\i\c*:)?(\i\c*|\*)))|\.))*)*
  
 
  
It seems that unlike other xpath expressions, the spec does not allow
  
spaces between operators like '|'. Hence, the above xpath expression
  
should have the spaces between '|' removed (as it is in all other
  
occurrences in the XLIFF schema).
  
 
  
cheers,
  
asgeir