Subj : XML
To   : Jan Vermeulen
From : Scott Little
Date : Mon Dec 30 2002 04:48 am

[ 29 Dec 02 17:01, Jan Vermeulen wrote to Scott Little ]

JV>     And then you get back a standard nodelist - which you will need to
JV> convert into XML

True, but probably not in the way you think, as long as the software is
correctly written.  I can take that SLF nodelist, and incorporate it into the
XML nodelist, filling in the missing pieces.  Only those nodes that don't have
a native XML listing will need to be converted.

This is where the alternate-distribution comes in.  If some *Cs don't
distribute XML segments, XML systems will find alternate means by which to
compile a more complete XML native nodelist, with less converted parts.

JV> in order you have a complete nodelist as required by policy.

Eh, what?  Which part of Policy 4.07 requires every node to have a full copy of
the nodelist (as issued by the IC)?

JV>     Again and once more: you will need nodelist-to-xml software, you
JV> know, that software they said is a PITA to code.

Users of XML or any alternate nodelists will have to accept that there may be
inaccuracies in the converted portions, such as a system's name with a dot in
it ending up in the domain name field as well.  Such nodes can be flagged as
suspicious during the conversion, and treated with caution by XML software.


-- Scott Little  [fidonet#3:712/848 / [email protected]]

--- FMail/Win32 1.60+
* Origin:  Cyberia: All your msgbase are belong to us! (3:712/848)

You are viewing proxied material from cvs.synchro.net. The copyright of proxied material belongs to its original authors. Any comments or complaints in relation to proxied material should be directed to the original authors of the content concerned. Please see the disclaimer for more details.