Lists Home |
Date Index |
- From: "Jonathan Borden" <firstname.lastname@example.org>
- To: <email@example.com>
- Date: Sun, 13 Feb 2000 20:39:33 -0500
W. Eliot Kimber wrote:
> Thierry Bezecourt wrote:
> > [Trying to understand how it works] To do that, if I'm correct, we
> > would have to define a property set for mailing lists, where articles
> > would be nodes, header fields would be properties of these nodes, the
> > "References" header field would be used for links to other articles,
> > and the "contents" would be the body of the article, which could
> > contain links. Then the formatting could be done with DSSSL and Jade
> > to produce an on-line archive. Is this a correct description of how
> > groves could be used in the real world ? It does not seem very
> > difficult.
> You've got it exactly. It's not particularly difficult, once you've got
> the infrastructure for creating and managing grove nodes (e.g., PHyLIS,
> pygrove, GroveMinder). It's just a simple matter of programming. That
> is, if you know how to process the data you want to grovify, and you've
> defined the grove representation of it, implementing the mapping from
> raw data to grove nodes is not any more difficult than any other similar
> programming task (e.g., using the DOM API, creating Java objects,
> creating Python objects, etc.).
> The hard part will be parsing the mail messages, not creating the node
> objects in memory.
In fact this was the idea behind XMTP
and http://www.xml.com/pub/98/12/consult98a.html) specifically to enable
'databasing' of SMTP messages in an XML repository (GroveBase).