Lists Home |
Date Index |
- From: Vane Lashua <vlashua@RSGsystems.com>
- Date: Fri, 22 Oct 1999 14:06:08 -0400
Aren't you doing the same thing with the namespace tag idea (except that it
won't work with an XML parser)? It seems like you _create_ the need for new
tagging. If these data tags were all derived from MARC(?) and they strictly
point to the same MARC "elements" (ha ha ha ....!), then one dtd will fit
the bill with a common definition,
<!ELEMENT (Creator|Originator|docAuthor) (...definition...)>
If you're going to keep the source tags, then you could use multiple copies
of the data, but use "dynamically generated" entities from a master dataset.
In each copy, use entity references (with unique ids) to point to entity
definitions in the same way. There are probably definitions in one
database/dtd that do not occur in others.
More than likely you will have to create an esperanto dtd and more than
likely if you have to process the data at all, you may as well process the
From: John Robert Gardner [mailto:firstname.lastname@example.org]
Sent: Friday, October 22, 1999 1:27 PM
To: Vane Lashua
Subject: RE: "Multiple" Namespaces? (but NOT for HTML)
On Fri, 22 Oct 1999, Vane Lashua wrote:
> Use attributes.
> Pick a master dtd element nomenclature ... DC, say ... or use your own and
> <ONEWHOCREATES DC="Creator" GILS="Originator"
Thanks, but to clarify in case it wasn't clear in my first post, the
search needs to be transparent. Under your solution, how is a DC engine
to recognize "ONEWHOCREATES"? We could of course use attributes, but then
everyone would have to readjust. The key point here is _transparent_
--otherwise we're just proliferating _yet another_ DTD, NOT transparently
interfacing with well-established archival standards.
xml-dev: A list for W3C XML Developers. To post, mailto:email@example.com
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To unsubscribe, mailto:firstname.lastname@example.org the following message;
To subscribe to the digests, mailto:email@example.com the following message;
List coordinator, Henry Rzepa (mailto:firstname.lastname@example.org)