Subj : XML
To   : Jan Vermeulen
From : Jesper S�rensen
Date : Sun Jan 05 2003 09:42 pm

js>> ... but when doing it the other way around the result would lack all
js>> the "extended" features that the new format otherwise could provide.

JV>     Really? Would it be so difficult to take a nodelist, transform it
JV> into XML and then add the extended features?

Where would the extended features come from in this case? What algorithm should
you apply to "Sorensen" to get "S�rensen", without also changing "Olsson" to
"�lss�n"? A massive mapping table (for everything from names & locations to
ip-connectivity & flags) would work but then it makes more sence to use that
data from the beginning, in some kind of super data base. It doesn't have to be
XML, but that's the format that makes best sence to me.

JV>     Where would the extended features come from when starting to build
JV> an XML list to begin with?

From the one submitting the data, provided it's submitted using some kind of
"extended features aware" system/format.

 Jesper,
 [email protected]
---
* Origin: Singularity/2 - Swedish Internet Backbone (2:204/255)

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.