Lists Home |
Date Index |
- From: Ketil Z Malde <firstname.lastname@example.org>
- To: "Rick Jelliffe" <email@example.com>
- Date: 23 Jun 1999 11:20:58 +0200
"Rick Jelliffe" <firstname.lastname@example.org> writes:
> There is nothing more semantic about <name> than <font>.
Yes there is, if you look at it in the proper context.
For one thing, a search engine that could tell me that it found my
search string within a <name> is probably more helpful in than one that
found it within a <font>.
The DTD can also tell me something about the semantics of <name>,
especially if it is annotated with explanatory comments, or through a
schema (although it needs to be simpler for a machine to look this
up), but just by looking at the contexts where it can appear can be
informative - <font> tags are likely to be legal just about anywhere.
Further, element content that happen to have the same presentation
fontwise don't necessarily mean the same thing, (in theory) nobody would
put their phone number in a <name> element to get the right
And, semantics are provided through style sheets or transformation/
formatting processes, just because one kind of use - e.g. formatting
for display - treats <name>a and <phone>s the same, doesn't mean that
other processing does.
Finally, meaning can be provided to tags through shared tag sets ("DTD
inheritance"), ideally, XML documents on the web should use standard
formats for common elements (names, urls, dates...) as much as
If I haven't seen further, it is by standing in the footprints of giants
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 (un)subscribe, 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)