This is the mail archive of the
xsl-list@mulberrytech.com
mailing list .
Re: Parsing Problem with Default XML Namespace - xmlns
- From: "Thomas B. Passin" <tpassin at mitretek dot org>
- To: <xsl-list at lists dot mulberrytech dot com>
- Date: Thu, 30 May 2002 11:20:14 -0400
- Subject: Re: [xsl] Parsing Problem with Default XML Namespace - xmlns
- References: <AECFD68A2039D611929D00508BBD699C85875D@FSJREZ02.adm.rl.af.mil>
- Reply-to: xsl-list at lists dot mulberrytech dot com
[Daley Thomas Contr AFRL/IFGB]
> I am having a problem parsing an XML document, which was generated
according
> to the
> Intrusion Detection Message Exchange Format (IDMEF) Data Model and XML
DTD,
> in
> http://www.silicondefense.com/idwg/draft-ietf-idwg-idmef-xml-07.txt ,
> starting on page 91.
> Specifically, the problem lies with the default namespace declaration, "
> xmlns="urn:iana:xml:ns:idmef" ", which appears in the following top level
> node line:
>
Unfortunately, there are processors that only accept http: schemes for
namespaces, although any URI scheme is supposed to be allowed. I know of an
RDF processor that has this problem, and it seems that the Microsoft .NET
SOAP machinery also has it.
If the Oracle processor has this limitation, it would not be conformant to
the XML Namespaces Rec, but that doesn't help you a bit.
Cheers,
Tom P
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list