| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | XML |
[ 23 Dec 02 13:33, Jan Vermeulen wrote to Scott Little ]
JV> It may upgrade to using the data from ESLF.
[snip]
JV> ESLF will contain all data one ever would need; XML may extract
JV> whatever it needs.
If you're thinking that we should use [E]SLF -> XML until everyone can
use XML, forget it. It won't work. There's little incentive to use XML at
all in that scenario.
JV> If the developers will get serious and give priority to serving the
JV> net.
Huh?
BB>>> The list produced by the utility would be in XML already.
BB>>> Then they are not working towards XML but starting from it.
sl>> More or less. It's the only way it can work.
JV> The problem seems to be that the XML developers do not see how
JV> they could extract that data. As if string parsing would be a PITA
JV> (even BASIC could do that in the early eighties...).
Huh?
JV> Which is by far less probable than losing a few legacy nodes in
JV> the process.
You've been told repeatedly this won't happen. Pay attention.
-- Scott Little [fidonet#3:712/848 / sysgod{at}sysgod.org]
--- FMail/Win32 1.60+
* Origin: Cyberia: All your msgbase are belong to us! (3:712/848)SEEN-BY: 633/267 270 @PATH: 712/848 633/260 774/605 123/500 106/1 379/1 633/267 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.