Subj : Net Development
To   : Jan Vermeulen
From : Scott Little
Date : Sat Jan 04 2003 09:27 am

 [ 03 Jan 03 17:49, Jan Vermeulen wrote to Scott Little ]

 JV>     'Broken data converted from SLF' can only be caused by:

 JV>  1. Broken data in the SLF, i.e. data that is broken in such a way
 JV>     that SLF list compilers and readers can't use them.
 JV>     Please be more explicit: in what circumstances has this happend?

Everywhere - ask David Drummond for a list of broken nodes he's dug up and had 
to request it be fixed.

 JV>  2. Data being broken while being converted.
 JV>     You do not mean that there will a problem, do you?

Unlikely.  The conversion will be closely monitored by the developers as long 
as SLF remains the primary data source, so issues converting ambiguous data 
will be quickly fixed or worked around.

 JV>  I presume that those doing the conversion have a good understanding
 JV> of the data and how to construct the new envelope (after all you will
 JV> not change the data itself, will you?).

The data will be changed to comply with the new format.  Anything that cannot 
be understood will be put in a generic <flags> or <userflags> field.

 JV>  3. The most unlikely of all: that the data will not work in an XML
 JV>     environment.
 JV>     Let's not even think about that one, will we?

The only issues there are buggy or stupidly designed programs..


-- Scott Little  [fidonet#3:712/848 / sysgod@sysgod.org]

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

.