RE: mnot-03, Infoset & syntax in sect. 2

[Dare Obasanjo <kpako@xxxxxxxxx>]

--- Bob Wyman <bob@xxxxxxxx> wrote:
> 
> 	Yes, bandwidth is a major concern. I'm building a
> system that
> must consume a significantly large percentage of all
> the RSS and/or
> Atom feeds on the web on a continuous basis. 

What does this have to do with alternate
serializations of the XML Infoset? Are you seriously
suggesting that we should introduce alternatives to
XML on the global, interoperable, cross-platform
network that is the World Wide Web? 

> 	But, understand that I am not suggesting that Atom
> define a
> binary format or even address the issue -- just that
> in the definition
> of Atom, nothing should be done to make it difficult
> or "forbidden" to
> produce binary encodings of Atom data if a
> *standard* binary encoding
> is ever defined and accepted.

What does *standard* binary encoding mean? Haven't a
number of standards organizations have already
produced alternatives to the XML syntax such as
MPEG-7/BiM? If that text is in the ATOM spec then I
can send MPEG-7/BiM documents on the web in response
to HTTP GET requests for my ATOM feed and be
conformant? 

> I've been building commercial software
> systems since the
> late 70's and I've learned the hard way that
> ignoring "pesky little
> issues" like bandwidth and processing efficiency can
> kill otherwise
> elegant systems.

Sounds like premature optimization to me. A lot of
folks don't even support CONDITIONAL GET or mod-gzip
which would significantly reduce the bandwidth
consumed by news aggregators on the WWW. 

=====
THINGS TO DO IF I BECOME AN EVIL OVERLORD #95
My dungeon will have its own qualified medical staff complete with bodyguards. That way if a prisoner becomes sick and his cellmate tells the guard it's an emergency, the guard will fetch a trauma team instead of opening up the cell for a look.

__________________________________
Do you Yahoo!?
New Yahoo! Photos - easier uploading and sharing.
http://photos.yahoo.com/