[ 06 Jan 03 21:18, Peter Knapper wrote to Scott Little ]

 PK> As an XML illiterate here, if I read what you wrote above correctly,
 PK> are you suggesting that it may be possible to construct an XML
 PK> Nodelist segment "assembly" tool, using only source data files, XML
 PK> "definition" files and a "standard" XML
processing engine to interpret
 PK> and action those definitions and data files?

Hmm.. you can use generic tools to create a segment and/or check it for
legality and compliance with a certain format, you may even be able to
merge XML segments with a generic tool (a simple overlay algorithm), but
you'll need a custom tool to accept incoming segments, apply a header or
something, and send outgoing segments.

 PK> If so, can you suggest such an engine for OS/2?......;-)

If I ever get around to it.. whatever I write will most likely be in
Python, so install Python/2 and you're golden :)

 SL>> Given the availability of XML libraries, it probably
 SL>> won't be too out of the question for a dedicated XML
 SL>> Nodelist editor to be written somewhere along the line,
 SL>> rather than rely on generic XML editors.

 PK> Does XML include the capabilty to define this sort of operation (IE
 PK> creating and editor) within the definition files themselves?

Umm.. wot?  I suppose a very good XML editor could use a def to construct
appropriate input templates, but I don't know of any that do that.   If
that's what you meant.. ?


-- Scott Little  [fidonet#3:712/848 / sysgod{at}sysgod.org]

--- FMail/Win32 1.60+