From commonskthomas@example.org Fri Dec 21 08:31:43 2007
Return-Path: <commonskthomas@example.org>
Delivered-To: kthomas@example.org
Received: (qmail 36721 invoked from network); 21 Dec 2007 08:31:43 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155)
  by minotaur.apache.org with SMTP; 21 Dec 2007 08:31:43 -0000
Received: (qmail 56710 invoked by uid 500); 21 Dec 2007 08:31:32 -0000
Delivered-To: kthomas@example.org
Received: (qmail 56604 invoked by uid 500); 21 Dec 2007 08:31:32 -0000
Mailing-List: contact kthomas@example.org; run by ezmlm
Precedence: bulk
list-help: <mailto:kthomas@example.org>
list-unsubscribe: <mailto:kthomas@example.org>
List-Post: <mailto:kthomas@example.org>
List-Id: <commons-dev.xml.apache.org>
Delivered-To: mailing list kthomas@example.org
Received: (qmail 56593 invoked by uid 99); 21 Dec 2007 08:31:32 -0000
Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 21 Dec 2007 00:31:32 -0800
X-ASF-Spam-Status: No, hits=-2.0 required=10.0
	tests=HTML_MESSAGE,RCVD_IN_DNSWL_MED,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of kthomas@example.org designates 83.161.120.155 as permitted sender)
Received: from [83.161.120.155] (HELO e36.co.us.ibm.com) (83.161.120.155)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 21 Dec 2007 08:31:08 +0000
Received: from d03relay02.boulder.ibm.com (d03relay02.boulder.ibm.com [83.161.120.155])
	by e36.co.us.ibm.com (8.13.8/8.13.8) with ESMTP id lBL8VBF3029461
	for <kthomas@example.org>; Fri, 21 Dec 2007 03:31:11 -0500
Received: from d03av01.boulder.ibm.com (d03av01.boulder.ibm.com [83.161.120.155])
	by d03relay02.boulder.ibm.com (8.13.8/8.13.8/NCO v8.7) with ESMTP id lBL8VBbd160890
	for <kthomas@example.org>; Fri, 21 Dec 2007 01:31:11 -0700
Received: from d03av01.boulder.ibm.com (loopback [83.161.120.155])
	by d03av01.boulder.ibm.com (83.161.120.15560308/8.13.3) with ESMTP id lBL8VBUI016717
	for <kthomas@example.org>; Fri, 21 Dec 2007 01:31:11 -0700
Received: from d03nm120.boulder.ibm.com (d03nm120.boulder.ibm.com [83.161.120.155])
	by d03av01.boulder.ibm.com (83.161.120.15560308/8.12.11) with ESMTP id lBL8VBj6016710
	for <kthomas@example.org>; Fri, 21 Dec 2007 01:31:11 -0700
To: kthomas@example.org
MIME-Version: 1.0
Subject: Question on catalog.xsd in xml-resolver 1.2
X-Mailer: Lotus Notes Release 8.0 August 02, 2007
From: David M Williams <kthomas@example.org>
Message-ID: <kthomas@example.org>
Date: Fri, 21 Dec 2007 03:31:06 -0500
X-MIMETrack: Serialize by Router on D03NM120/03/M/IBM(Release 7.0.2FP2HF300 | September
 14, 2007) at 12/21/2007 01:31:10,
	Serialize complete at 12/21/2007 01:31:10
Content-Type: multipart/alternative; boundary="=_alternative 002ECA18852573B8_="
X-Virus-Checked: Checked by ClamAV on apache.org

This is a multipart message in MIME format.
--=_alternative 002ECA18852573B8_=
Content-Type: text/plain; charset="US-ASCII"

I've recently started using Xerces 2.9.0, which has 
xml-commons-resolver-1_2

It has a catalog.xsd file, in org.apache.xml.resolver.etc

This schema doesn't validate, even by Xerces 2.9 itself!!?? 

The schema has 

  <xs:simpleType name='pubIdChars'>
    <!-- A string of the characters defined as pubIdChar in production 13
         of the Second Edition of the XML 1.0 Recommendation. Does not 
include
         the whitespace characters because they're normalized by XML 
parsing. -->
    <xs:restriction base='xs:string'>
      <xs:pattern value="[a-zA-Z0-9-'()+,./:=?;!*#@$_%]*"/>
    </xs:restriction>
  </xs:simpleType>


But the validator says the pattern value should be 

    <xs:pattern value="[a-zA-Z0-9\-'()+,./:=?;!*#@$_%]*"/>

That is, have an escaped '-' character where it's used literally. 
Some googling around implied the parentheses '(' and ')' should also be 
escaped, giving 

      <xs:pattern value="[a-zA-Z0-9\-'\(\)+,./:=?;!*#@$_%]*"/>


So ... I'm curious, is this a simple bug and the file that's being 
distributed should be fixed? 
Or, is there some complex special case here where is doesn't matter? Or 
that is should be escaped for 
one type of context or processing but not escaped for another? 

I don't know of any cases of the resolving functionality actually failing 
because of this ... but, 
seems it should shipped in a valid form? 

Thanks for any education/insight you can give me. 




--=_alternative 002ECA18852573B8_=
Content-Type: text/html; charset="US-ASCII"


<br><font size=3 face="Consolas">I've recently started using Xerces 2.9.0,
which has xml-commons-resolver-1_2</font>
<br>
<br><font size=3 face="Consolas">It has a catalog.xsd file, in org.apache.xml.resolver.etc</font>
<br>
<br><font size=3 face="Consolas">This schema doesn't validate, even by
Xerces 2.9 itself!!?? </font>
<br>
<br><font size=3 face="Consolas">The schema has </font>
<br>
<br><font size=3 face="Consolas">&nbsp; </font><font size=3 color=#008080 face="Consolas">&lt;</font><font size=3 color=#3f8080 face="Consolas">xs:simpleType
</font><font size=3 color=#800080 face="Consolas">name</font><font size=3 face="Consolas">=</font><font size=3 color=#4200ff face="Consolas"><i>'pubIdChars'</i></font><font size=3 color=#008080 face="Consolas">&gt;</font>
<br><font size=3 face="Consolas">&nbsp; &nbsp; </font><font size=3 color=#4040c2 face="Consolas">&lt;!--
A string of the characters defined as pubIdChar in production 13</font>
<br><font size=3 color=#4040c2 face="Consolas">&nbsp; &nbsp; &nbsp; &nbsp;
&nbsp;of the Second Edition of the XML 1.0 Recommendation. Does not include</font>
<br><font size=3 color=#4040c2 face="Consolas">&nbsp; &nbsp; &nbsp; &nbsp;
&nbsp;the whitespace characters because they're normalized by XML parsing.
--&gt;</font>
<br><font size=3 face="Consolas">&nbsp; &nbsp; </font><font size=3 color=#008080 face="Consolas">&lt;</font><font size=3 color=#3f8080 face="Consolas">xs:restriction
</font><font size=3 color=#800080 face="Consolas">base</font><font size=3 face="Consolas">=</font><font size=3 color=#4200ff face="Consolas"><i>'xs:string'</i></font><font size=3 color=#008080 face="Consolas">&gt;</font>
<br><font size=3 face="Consolas">&nbsp; &nbsp; &nbsp; </font><font size=3 color=#008080 face="Consolas">&lt;</font><font size=3 color=#3f8080 face="Consolas">xs:pattern
</font><font size=3 color=#800080 face="Consolas">value</font><font size=3 face="Consolas">=</font><font size=3 color=#4200ff face="Consolas"><i>&quot;[a-zA-Z0-9-'()+,./:=?;!*#@$_%]*&quot;</i></font><font size=3 color=#008080 face="Consolas">/&gt;</font>
<br><font size=3 face="Consolas">&nbsp; &nbsp; </font><font size=3 color=#008080 face="Consolas">&lt;/</font><font size=3 color=#3f8080 face="Consolas">xs:restriction</font><font size=3 color=#008080 face="Consolas">&gt;</font>
<br><font size=3 face="Consolas">&nbsp; </font><font size=3 color=#008080 face="Consolas">&lt;/</font><font size=3 color=#3f8080 face="Consolas">xs:simpleType</font><font size=3 color=#008080 face="Consolas">&gt;</font>
<br>
<br>
<br><font size=3 face="Consolas">But the validator says the pattern value
should be </font>
<br>
<br><font size=3 face="Consolas">&nbsp; &nbsp; </font><font size=3 color=#008080 face="Consolas">&lt;</font><font size=3 color=#3f8080 face="Consolas">xs:pattern
</font><font size=3 color=#800080 face="Consolas">value</font><font size=3 face="Consolas">=</font><font size=3 color=#4200ff face="Consolas"><i>&quot;[a-zA-Z0-9\-'()+,./:=?;!*#@$_%]*&quot;</i></font><font size=3 color=#008080 face="Consolas">/&gt;</font>
<br>
<br><font size=3 face="Consolas">That is, have an escaped '-' character
where it's used literally. </font>
<br><font size=3 face="Consolas">Some googling around implied the parentheses
'(' and ')' should also be escaped, giving </font>
<br>
<br><font size=3 face="Consolas">&nbsp; &nbsp; &nbsp; </font><font size=3 color=#008080 face="Consolas">&lt;</font><font size=3 color=#3f8080 face="Consolas">xs:pattern
</font><font size=3 color=#800080 face="Consolas">value</font><font size=3 face="Consolas">=</font><font size=3 color=#4200ff face="Consolas"><i>&quot;[a-zA-Z0-9\-'\(\)+,./:=?;!*#@$_%]*&quot;</i></font><font size=3 color=#008080 face="Consolas">/&gt;</font>
<br>
<br>
<br><font size=3 face="Consolas">So ... I'm curious, is this a simple bug
and the file that's being distributed should be fixed? </font>
<br><font size=3 face="Consolas">Or, is there some complex special case
here where is doesn't matter? Or that is should be escaped for </font>
<br><font size=3 face="Consolas">one type of context or processing but
not escaped for another? </font>
<br>
<br><font size=3 face="Consolas">I don't know of any cases of the resolving
functionality actually failing because of this ... but, </font>
<br><font size=3 face="Consolas">seems it should shipped in a valid form?
</font>
<br>
<br><font size=3 face="Consolas">Thanks for any education/insight you can
give me. </font>
<br>
<br>
<br>
<br>
--=_alternative 002ECA18852573B8_=--

From commonskthomas@example.org Fri Dec 21 22:15:33 2007
Return-Path: <commonskthomas@example.org>
Delivered-To: kthomas@example.org
Received: (qmail 74582 invoked from network); 21 Dec 2007 22:15:33 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155)
  by minotaur.apache.org with SMTP; 21 Dec 2007 22:15:33 -0000
Received: (qmail 41057 invoked by uid 500); 21 Dec 2007 22:15:22 -0000
Delivered-To: kthomas@example.org
Received: (qmail 41033 invoked by uid 500); 21 Dec 2007 22:15:22 -0000
Mailing-List: contact kthomas@example.org; run by ezmlm
Precedence: bulk
list-help: <mailto:kthomas@example.org>
list-unsubscribe: <mailto:kthomas@example.org>
List-Post: <mailto:kthomas@example.org>
List-Id: <commons-dev.xml.apache.org>
Delivered-To: mailing list kthomas@example.org
Received: (qmail 41022 invoked by uid 99); 21 Dec 2007 22:15:22 -0000
Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 21 Dec 2007 14:15:22 -0800
X-ASF-Spam-Status: No, hits=-4.0 required=10.0
	tests=RCVD_IN_DNSWL_MED,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of kthomas@example.org designates 83.161.120.155 as permitted sender)
Received: from [83.161.120.155] (HELO e5.ny.us.ibm.com) (83.161.120.155)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 21 Dec 2007 22:14:57 +0000
Received: from d01relay02.pok.ibm.com (d01relay02.pok.ibm.com [83.161.120.155])
	by e5.ny.us.ibm.com (8.13.8/8.13.8) with ESMTP id lBLMExAu012110
	for <kthomas@example.org>; Fri, 21 Dec 2007 17:14:59 -0500
Received: from d01av01.pok.ibm.com (d01av01.pok.ibm.com [83.161.120.155])
	by d01relay02.pok.ibm.com (8.13.8/8.13.8/NCO v8.7) with ESMTP id lBLMExtv452750
	for <kthomas@example.org>; Fri, 21 Dec 2007 17:14:59 -0500
Received: from d01av01.pok.ibm.com (loopback [83.161.120.155])
	by d01av01.pok.ibm.com (83.161.120.15560308/8.13.3) with ESMTP id lBLMExnd017529
	for <kthomas@example.org>; Fri, 21 Dec 2007 17:14:59 -0500
Received: from d25ml03.torolab.ibm.com (d25ml03.torolab.ibm.com [83.161.120.155])
	by d01av01.pok.ibm.com (83.161.120.15560308/8.12.11) with ESMTP id lBLMEwsN017470
	for <kthomas@example.org>; Fri, 21 Dec 2007 17:14:58 -0500
In-Reply-To: <kthomas@example.org>
Subject: Re: Question on catalog.xsd in xml-resolver 1.2
To: kthomas@example.org
X-Mailer: Lotus Notes Release 7.0 HF277 June 21, 2006
Message-ID: <kthomas@example.org>
From: Michael Glavassevich <kthomas@example.org>
Date: Fri, 21 Dec 2007 17:14:56 -0500
X-MIMETrack: Serialize by Router on D25ML03/25/M/IBM(Release 7.0.2HF446 | March 16, 2007) at
 12/21/2007 17:14:58
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
X-Virus-Checked: Checked by ClamAV on apache.org

Hi David,

Looks like the schema [1] in the XML Catalogs 1.1 spec has the correct
escaping. I have no idea where the currently distributed catalog.xsd [2]
came from but indeed it isn't valid.

Thanks.

[1]
http://www.oasis-open.org/committees/download.php/14809/xml-catalogs.html#a.w3cxmlschema
[2]
http://svn.apache.org/viewvc/xml/commons/trunk/java/etc/catalog.xsd?view=log

Michael Glavassevich
XML Parser Development
IBM Toronto Lab
E-mail: kthomas@example.org
E-mail: kthomas@example.org

David M Williams <kthomas@example.org> wrote on 12/21/2007 03:31:06
AM:

> I've recently started using Xerces 2.9.0, which has
xml-commons-resolver-1_2
>
> It has a catalog.xsd file, in org.apache.xml.resolver.etc
>
> This schema doesn't validate, even by Xerces 2.9 itself!!??
>
> The schema has
>
>   <xs:simpleType name='pubIdChars'>
>     <!-- A string of the characters defined as pubIdChar in production 13

>          of the Second Edition of the XML 1.0 Recommendation. Does not
include
>          the whitespace characters because they're normalized by XML
> parsing. -->
>     <xs:restriction base='xs:string'>
>       <xs:pattern value="[a-zA-Z0-9-'()+,./:=?;!*#@$_%]*"/>
>     </xs:restriction>
>   </xs:simpleType>
>
>
> But the validator says the pattern value should be
>
>     <xs:pattern value="[a-zA-Z0-9\-'()+,./:=?;!*#@$_%]*"/>
>
> That is, have an escaped '-' character where it's used literally.
> Some googling around implied the parentheses '(' and ')' should also
> be escaped, giving
>
>       <xs:pattern value="[a-zA-Z0-9\-'\(\)+,./:=?;!*#@$_%]*"/>
>
>
> So ... I'm curious, is this a simple bug and the file that's being
> distributed should be fixed?
> Or, is there some complex special case here where is doesn't matter?
> Or that is should be escaped for
> one type of context or processing but not escaped for another?
>
> I don't know of any cases of the resolving functionality actually
> failing because of this ... but,
> seems it should shipped in a valid form?
>
> Thanks for any education/insight you can give me.



{'source': 'Apache Software Foundation Public Mail Archives'}