Lists Home |
Date Index |
- From: Peter Murray-Rust <firstname.lastname@example.org>
- To: email@example.com
- Date: Sat, 29 Nov 1997 12:48:16
At 10:20 28/11/97 -0500, Paul Prescod wrote:
>Peter Murray-Rust wrote:
>> [Not a grove at this stage, as
>> no one seems to write their parsers to create groves.]
>I'm not sure what this means.
It means I am still blundering around in ignorance or incompetence. It may
be that the terminology is the problem.
Some people seem to use 'processor' to mean an XML parser. Others seem to
use 'processor' as a piece of software 'after' the parser. I think some
people use 'parser' to mean a piece of software that reads in an XML
document (and associated components and transforms them into some other
information structure or sets of actions. the 'Parsers' at present appear
to be able to emit event Streams and/or build trees.
Since the spec uses 'processor' a lot but does not (I think deliberately)
define the software components, different people have different views.
Perhaps mine is the only one at odds, but I'll elaborate.
>Building a grove is not the job of a
>parser. Typically the parser outputs the events and some other process
>builds the grove from the information. The only way a parser could be
>not written to create groves is if the parser did not output sufficient
Is there a difference between 'build' and 'create'? I don't understand how
a parser can 'not build a grove' and 'be not written to create groves'.
>information to build a grove conforming to a particular grove plan.
Earlier on XML-DEV we discussed at length what the API to a 'parser' (or
was it a 'processor') was. I thought that this could have included building
IOW it would have been possible to build software which used Xapi-J to
create groves from input XML documents. If, within this system, there is a
formal and necessary distinction between 'parser' components and
'processor' components, I'll need some more help.
If I rephrase my statement as 'no-one has written any XML-based software
which interfaces with the current crop of (mainly java-based) parsers to
generate groves'. [I appreciate that James Clark's software will do
everything - unfortunately I need java solutions.]
> Paul Prescod
>xml-dev: A list for W3C XML Developers. To post, mailto:firstname.lastname@example.org
>Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
>To (un)subscribe, mailto:email@example.com the following message;
>To subscribe to the digests, mailto:firstname.lastname@example.org the following message;
>List coordinator, Henry Rzepa (mailto:email@example.com)
Peter Murray-Rust, Director Virtual School of Molecular Sciences, domestic
VSMS http://www.nottingham.ac.uk/vsms, Virtual Hyperglossary
xml-dev: A list for W3C XML Developers. To post, mailto:firstname.lastname@example.org
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To (un)subscribe, mailto:email@example.com the following message;
To subscribe to the digests, mailto:firstname.lastname@example.org the following message;
List coordinator, Henry Rzepa (mailto:email@example.com)