Re: AW: Error Parsing xml document

2012-05-15 Thread Michael Glavassevich
kesh...@us.ibm.com wrote on 15/05/2012 02:57:58 PM: > I sit corrected... though if you want the document to be > interoperable with other XML tools, you should hew close to the standard. > > BTW, I was just reminded that XML Namespaces 1.1 declared that > namespace names should be IRIs, not ju

Re: AW: Error Parsing xml document

2012-05-15 Thread keshlam
I sit corrected... though if you want the document to be interoperable with other XML tools, you should hew close to the standard. BTW, I was just reminded that XML Namespaces 1.1 declared that namespace names should be IRIs, not just URIs. Of course how many tools tracked that chance is an op

Re: AW: Error Parsing xml document

2012-05-15 Thread Michael Glavassevich
The type of the targetNamespace attribute is xs:anyURI. The xs:anyURI type [1] allows many characters (which are not allowed in vanilla URIs) without requiring escaping. However, there are still many classes of strings which are not valid xs:anyURI values. Thanks. [1] http://www.w3.org/TR/xmls

Re: AW: Error Parsing xml document

2012-05-15 Thread keshlam
> in your XML-Documet change //$xrd*($v*2.0) to a valid URI Websearching for "URI RFC" will find the formal specification for URIs, including the grammar that defines what is and isn't legal; namespace names must meet the syntactic constraints of URI References. You may have to escape some char

AW: Error Parsing xml document

2012-05-15 Thread Papendieck, Thomas
Hi, in your XML-Documet change //$xrd*($v*2.0) to a valid URI bye Thomas - Von: priyanka rawat [mailto:rpriyanka.scor...@gmail.com] Gesendet: Dienstag, 15. Mai 2012 09:19 An: j-users@xerces.apache.org Betreff: Error Parsing