Lists Home |
Date Index |
- From: "Joel Riedesel" <email@example.com>
- To: "'Peter Murray-Rust'" <firstname.lastname@example.org>, <email@example.com>
- Date: Thu, 4 Jun 1998 11:36:25 -0600
I'm using this vhg.dtd to test out some work we're doing with parsing out
the DTD and using that to allow authors to reference data in documents
use that DTD (and subsequently be able to reason upon that data).
DTD Parsing Assumption:
I had made an assumption (probably quite incorrectly) that there would
element in the DTD that wasn't referenced by other elements and therefore
would use that element as my "top" element.
This vhg.dtd has a locatorLink that is not referenced by any other
element in the DTD. The semantics of extendedLink say that it will
always contain locatorLink elements, but the DTD for extendedLink doesn't
actually state that.
So... somewhat obviously, I end up with the locatorLink as my top element.
Oops. (Looks like I need to at least provide for the possibility of
top elements and let our author choose the correct one.)
Is this type of DTD practice in any way standard? It sure feels a bit
messy to define things this way (makes it tough to use the DTD by another
program and actually automate XML things...). If the authors of the VHG.dtd
find the need to define things this way, is that due to a current limitation
of DTDs in general?
Feel free to correct any misunderstanding I may have (which I won't
be at all surprised about).
> The VHG (Virtual Hyperglossary) is a simple but powerful approach for
> supporting semantics and terminology using XML technology. The first
> publicly available DTD (with documentation and examples) is at:
Jnana Technologies Corporation
303 805 8275
xml-dev: A list for W3C XML Developers. To post, mailto:firstname.lastname@example.org
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To (un)subscribe, mailto:email@example.com the following message;
To subscribe to the digests, mailto:firstname.lastname@example.org the following message;
List coordinator, Henry Rzepa (mailto:email@example.com)