[JDEV] Why XML for everything?

[Josh Mitts]

Interleaved Response.

Josh

----------
>From: John Price <linux-guru at gcfl.net>
>To: jdev at jabber.org
>Subject: Re: [JDEV] Why XML for everything?
>Date: Wed, Sep 29, 1999, 11:03 PM
>

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On Wed, 29 Sep 1999, Josh Mitts wrote:
>> Maybe I can help a little.....heh heh you owe me Jer :)
>>
>> The "XML for everything" is just the format that was chosen - I can give you
>> several reasons why it is a good system, though I can't prove if it is
>> better than any other propritary system....here goes:
>>
>> 1. The XML archeticture is totally expandable - that is, new tags and data
>> can be easily added by new markup.
>
> True, but at the cost of complication...  But still, a valid plus.

Maybe - but the complication far outdoes the advantages - file transfer,
buddy chat, admin tools, etc. are all easily expandable.

>
>> 2. The "local server" system similar to email would probobly become to
>> cumbersome for proprietary systems since a lot of those systems use
>> low-level calls, not text-based data like Jabber.
>
> What do you mean low-level calls?  What's that got to do with parsing
> text-based data?

Not everything Jabber does is text-based! You have roster updates, status
changes, admin things. etc. which all are carried out as proprietary
commands in other systems - but in Jabber they are unified XML which is
expandable, standardized, and simple to use and develop with.

>
>> 3. The client development is much smoother and easier because it is
>> standardized XML - and not just by Jabber, but by W3C and other internet
>> standard groups.
>
> I think it's funny every time I read how XML is "totally expandable" on
> the one hand, and "standardized" on the other hand.  Since the client has
> to deal with new tags as the server guys come up with more makes me think
> that it's harder to impliment.

Actually, if you read up on the Info/Query system as well as the <ext>
packets you will see that it is really quite simple to implament. Once you
get your XML Parsed into your client's native code, the rest is simply copy
and pasting for each new command.

>
>> 4. The future of appilcations will probobly be XML-based. For instance,
>> based on some IETF discussions recently, XML or some FORM of XML may become
>> used to appliances and computers to talk together....kinda weird but true :)
>
> If this is true, this would also be an advantage.  So Jabber is planning
> on being able to directly connect appliances to it's servers so people can
> chat with them?  Interesting idea...I guess.
>

One day! One day when the IETF unifies its standards, *possibly* Jabber
could be a major movement in development. See, the whole goal is to unify
communication - someday possibly this could happen:

<message to="toaster at josh" from "tv at upstairs.josh">
<say>Food is ready!</say>
</message>

It's funny now but it may be true!

>
> - --
> John Price <linux-guru at gcfl.net>
>
> PGP key at http://www.gcfl.net/~linux-guru/publickey.txt
>
> John's FreeDOS page -> http://www.gcfl.net/FreeDOS
>
> AIM ID "GCFL Owner"
> ICQ 24079586
>
> - -----BEGIN GEEK CODE BLOCK-----
> Version: 3.21
> GE d-> s++:+ a C++ UL++++ P+ L+++> E- W+++ N+ o+ K- W--- O- M-- V--
> PS-- PE+ Y+ PGP++> t+ 5 X++ R- tv+ b+ DI+ D+ G+ e++> h r+++ y+++
> - ------END GEEK CODE BLOCK------
>
> -----BEGIN PGP SIGNATURE-----
> Version: PGPfreeware 5.0i for non-commercial use
> Charset: noconv
>
> iQA/AwUBN/LFD7R4GidzvvE7EQLuKgCcDTYKKfdTMdaZEOeN5iSTiMxWG9YAoPIt
> 3XBRrQV3hTJAcKGAfHN0WqBQ
> =VUkO
> -----END PGP SIGNATURE-----
>
>
> _______________________________________________
> jdev mailing list
> jdev at jabber.org
> http://mailman.jabber.org/listinfo/jdev
>