Altova Mailing List Archives
>xml-dev Archive Home
>Recent entries
>Thread Prev - Re: Re:Automating Search Interfaces"
[Thread Next]
Re: Re:Automating Search Interfaces"
To: "Matthew Gertner" <matthewg@----.-->
Date: 2/20/1998 7:45:00 PM
Matthew Gertner writes: > One approach that really appeals to me is based on a two-pronged effort to > create standard tags *and* standard DTDs, and relies on the fact that there > is really a working mechanism for extending DTDs through inheritance (which > I guess is still not entirely the case). > > Standard tags would be a bit of a hack, but probably very useful in a > pragmatic sense. For example, you might be able to say certain things about > a TITLE tag, or a PRICE tag, or whatever, just on the basis of the name, > regardless of the actual DTD being used. If these conventions were > well-known, this could be of great use when defining a new DTD (i.e. "Let's > call the tag PARAGRAPH and not PARA because this is what will be recognized > by search engines"). The idea is actually quite sound, but the implementation could be a little cleaner. Instead of relying on the element type name (which may vary for different domains of information), why not have a standard attribute (such as 'standard-doc') that gives the equivalent standard name in the architecture. That way, just as you write public class Cost implements Price { } in Java, you can write <!ELEMENT cost (#PCDATA)> <!ATTLIST cost standard-doc CDATA #FIXED "price"> in XML, or even <cost standard-doc="price">xxx</foo> This makes multiple inheritance easy: <!ELEMENT cost (#PCDATA)> <!ATTLIST cost standard-doc CDATA #FIXED "price" alt-doc CDATA #FIXED "value"> Now, that `cost' inherits from `price' in the standard-doc architecture and from `value' in the alt-doc architecture. All the best, David -- David Megginson ak117@f... Microstar Software Ltd. dmeggins@m... http://home.sprynet.com/sprynet/dmeggins/ xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@i... Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ To (un)subscribe, mailto:majordomo@i... the following message; (un)subscribe xml-dev To subscribe to the digests, mailto:majordomo@i... the following message; subscribe xml-dev-digest List coordinator, Henry Rzepa (mailto:rzepa@i...)
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.

