Lists Home |
Date Index |
- From: Jacek Ambroziak - Sun Microsystems Labs BOS <Jacek.Ambroziak@East.Sun.COM>
- To: Tim Bray <firstname.lastname@example.org>
- Date: Fri, 29 May 1998 11:41:23 -0400 (EDT)
> At 03:04 PM 5/28/98 -0700, Andrew Layman wrote:
> >(As I use the terms, "metadata" means descriptive information summarizing or
> >supplementing a document, while "schema" means a collection of named items
> >and their definitions, which names and definitions are necessary for
> >understanding the document. For example, a card catalog entry and a book
> >review are both metadata (relative to the book) while a dictionary and
> >grammar are schema.)
> Supposing for the sake of argument that we accept these definitions
> of the two terms, is the difference important?
Personally, I like the distinction.
> It's far from clear to me that all information about information can be
> partitioned into "that which summarizes/supplements" and "that which is
> necessary to understand". Hmmm, if you re-write that second
The first class is external,additional,open-ended...
The second is essentially a part of the document itself
and a part of the interpretation ("understanding") of the doc:
it is constitutive for what the doc IS.
> condition as
> "that which can be used to support formal validation" then it starts
> to sound like a really material distinction... boy, I get nervous when
> we start bandying about the term "understand".
How about "Understand" == "interpret, have a blueprint for
assigning intended design to document's data".
> interesting. But these
> are matters certainly open to debate.
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/
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)