Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Question on unparsed entities & DTDs

From: D McGilvray <d.mcgilvray@----.---.--.-->
To: NULL
Date: 8/1/2007 1:15:00 PM


Hi there, I've been searching in vain for an example of exactly *how* 
notations are to be used beyond simply declaring external entities.

To avoid flogging a dead horse, other considerations force me to use 
DTD's, I'm not against discussion about Schemas, but I cannot use them 
at the moment.

I understand that different types of unparsed entities can be declared 
by declaring the notation. eg.

<!NOTATION 	GIF 		SYSTEM "some reference to gif">
<!ENTITY 	mypicture 	SYSTEM "aphoto.gif" GIF>


I can say that my element must contain an ENTITY attribute, but can I 
specify what notation that entity should be?

I haven't seen any example of this, so I'm assuming that it isn't 
possible, but to me it seems like a very powerful feature - for example, 
I want to specify extra processing attributes tailored to the type of file.



Thanks for your time and expertise,
Dougie



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