Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: include file problem: namespaces?

From: richard@------.--.--.-- (------- -----)
To: NULL
Date: 5/6/2006 8:06:00 PM

In article <v7-dnZ_yOoHYs8HZRVn-vg@c...>,
Joe Kesselman  <keshlam-nospam@c...> wrote:

>One of the other reason parsed entities are going away is that they 
>really aren't very useful. They're defined in DTD, which means there's 
>only one set of them for all documents of that type -- as if you had to 
>hardwire all your possible #includes into the compiler. Usually when you 
>want to include something, you want the instance document to decide what 
>it wants to include.

One of the common uses of entities (external and internal) is for
boilerplate that's common across documents - copyright notices for
example - and for that purpose fixed values are what you want.

But the system ID of an external entity can be a relative URI, so it's
also possible to package up a document with a set of external entities
in the same directory.

-- Richard


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