Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: include file problem: namespaces?

From: maxwell@---.-----.---
To: NULL
Date: 5/5/2006 8:44:00 AM

> Remember, inclusion in XML is semantic, NOT string based.

That definitely seems to be what's happening, but it's not what I
expected from statements like
    You can specify an entity that has text defined external to
    the document by using the SYSTEM keyword...
    In this case, the XML processor will parse the content of
    that file as if its content had been typed at the location
   of the entity reference.
(--http://www.javacommerce.com/displaypage.jsp?name=entities.sql&id=18238)

> You provided a <FeatureValueSet>; it expected a
> <FeatureValueSet xmlns="http://lodl.ldc.upenn.edu/ParadigmDefn.xsd">, or
> <foo:FeatureValueSet
> xmlns:foo="http://lodl.ldc.upenn.edu/ParadigmDefn.xsd">, or something
> equivalent.
>
> Fix your external entity.

In the actual file (not the cut down one that I posted here), there is
a long series of these entities
  <FeatureValueSet>foo</FeatureValueSet>
  <FeatureValueSet>bar</FeatureValueSet>
  <FeatureValueSet>baz</FeatureValueSet>
etc., and I want to splice that *sequence* in at several points.  I can
put in the xmlns in each one of these entites, but is there a way in
this external file of specifying the xmlns once, rather than repeatedly?



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