Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: Enternal entities & namespace

From: Bjoern Hoehrmann <bjoern@---------.-->
To: NULL
Date: 1/3/2006 5:33:00 PM
* Jiri Netolicky wrote in comp.text.xml:
>When I manualy replace "&data;" with the content of "log.xml"
>the validation "xmllint -valid -noout" is OK. But when I try
>to include "log.xml" as external entitity, validator reports
>error:
>
>log.xml:1: namespace error : Namespace prefix log4j on event is not defined

This seems a bug, Namespaces in XML 1.0 does not define well-formedness
for external parsed entities, and a namespace-unaware processor would,
when transforming the document to a standalone one as defined in XML
1.0, generate a namespace-well-formed document, so I don't really see a
reason for generating a namespace error here. I'd file a libxml2 bug.

>What is the right syntax to namespace defined in master document
>will be known during parsing external entity?

Well, declaring the prefix in the external entity would work and is
certainly a better practise, but I don't think it's clearly required.
-- 
Björn Höhrmann · mailto:bjoern@h... · http://bjoern.hoehrmann.de
Weinh. Str. 22 · Telefon: +49(0)621/4309674 · http://www.bjoernsworld.de
68309 Mannheim · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/ 


transparent
Print
Mail
Like It
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.

.
.

transparent

transparent