[
Lists Home |
Date Index |
Thread Index
]
- From: "Steven R. Newcomb" <srn@techno.com>
- To: jborden@mediaone.net
- Date: Tue, 23 Feb 1999 14:43:51 -0600
[Len Bullard: ]
> > If there is a significant breakthrough, it has
> > been the introduction of two API/interface
> > standards, one formal, DOM, and one grassroots,
> > SAX, both of which are there to solve different
> > but related problems. The interface standards
> > for markup are unique. Some of us would have
> > killed for those about five years ago.
[Jonathan Borden:]
> Isn't that a grove? I'm saying this
> because when I look at the interfaces in Jade's
> groveoa, they look alot like the DOM (not that
> James defines what a grove is, but by
> implication I assume that this is at least what
> he thinks :-)
I certainly can't speak for James, but I would
like to clear something up:
ISO/IEC 10744:1997 ("HyTime") and, earlier,
ISO/IEC 10179:1996 ("DSSSL") defined and coined
the term "grove". A grove is the set of objects
resulting from parsing an information resource in
some specific notation. EVERY GROVE ALWAYS MUST
CONFORM TO A FORMAL MODEL called a "property set".
The "SGML property set" is one such property set,
and it's the property set that governs the
structure and nature of the objects to which
Jade's groveoa interface provides access. Think
of a property set as a schema for the objects that
result from parsing (and/or from semantic
processing, but that's another story for another
day).
The DOM is not a grove; it is an API. Until the
XML information set is stable, the DOM is an API
to something that's not rigorously defined. The
DOM can be implemented as an interface to XML
groves, but not before there are XML groves. And
there can't be XML groves until there's a property
set for XML. (Well, no, that's not quite right,
because we routinely make SGML groves from XML
documents. But that's just a temporary kludge
that only works because of XML's SGML parentage.
Moreover, the SGML Property Set provides for more
complexity than XML groves will ever need to have,
and simplicity is one of XML's most important
virtues.)
There is every reason to believe that the XML
Information Set, once Recommended, will be
expressible as a property set. Once this is done,
XML objects will be processable, addressable, and
re-usable via the same software that supports the
processing, addressing, and re-use of components
of resources expressed in other notations, with
each such notation described by its own property
set. In that scenario, all information components
conform to the same object model, the ISO "grove"
object model, so we are able to address (link,
re-use) any kind of thing.
-Steve
--
Steven R. Newcomb, President, TechnoTeacher, Inc.
srn@techno.com http://www.techno.com ftp.techno.com
voice: +1 972 231 4098 (at ISOGEN: +1 214 953 0004 x137)
fax +1 972 994 0087 (at ISOGEN: +1 214 953 3152)
3615 Tanner Lane
Richardson, Texas 75082-2618 USA
xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev@ic.ac.uk
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To (un)subscribe, mailto:majordomo@ic.ac.uk the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo@ic.ac.uk the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa@ic.ac.uk)
|
