Subj : Net Development
To   : Scott Little
From : Jan Vermeulen
Date : Sat Jan 04 2003 03:26 pm

    Quoting Scott Little on Sat 4 Jan 2003  9:27 to Jan Vermeulen:

 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?

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

    In a separate posting I have done so.

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

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

    Good.

 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?).

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

    How can you be 100% sure that you will get the old data back when generaing 
an SLF list from the XML data?

 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?

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

    Which will not happen. Is that what you want to say?


    -=<[ JV ]>=-

 
* Origin: The Poor Man's Workstation -- Wormerveer NL (2:280/100)

.