Altova Mailing List Archives


Re: [xsl] Parsing Problem with Default XML Namespace - xmlns

From: "Thomas B. Passin" <tpassin@------------>
To:
Date: 5/30/2002 7:30:00 AM
[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

Disclaimer

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.