Re: Atom and RDF

--- Danny Ayers <[email protected]> wrote:
>  
> Lucas Gonze listed the following problems with the
> enclosure element:
> 
> 1 It causes users to download big files that they
> will never listen to
> or watch, creating pointless overload on web hosts.
> 2 It doesn't allow us to credit the MP3 host, so we
> can't satisfy the
> netiquette of always linking back.
> 3 For broadband users, MP3s are not big enough to
> need advance caching
> in the first place.
> 4 The required content-type attribute is a bad idea
> in the first place. 
> 5 The required content-length attribute should not
> be there. 
> 
> http://gonze.com/weblog/story/5-17-4

I debunked most of these claims at
http://www.25hoursaday.com/weblog/PermaLink.aspx?guid=d9c0205d-3cc1-4efb-a62f-7b0f05fb13af

1. The RSS 2.0 spec never describes this automatic
downloading behavior. This was a suggested usage that
Dave Winer began to evangelize outside the spec which
as many have pointed out has its flaws. 

2. This is true, although it did seem like a weird
special case to me. 

3. See (1) above 

4. No it isn't. Client software should be able, to
decide how to react to the enclosure [e.g. if it is
audio/mpeg display a play button] without having to
make additional HTTP requests to the web server even
if it is just HEAD requests. 

5. Agreed. 

 

=====
THINGS TO DO IF I BECOME AN EVIL OVERLORD #23
I will keep a special cache of low-tech weapons and train my troops in their use. That way -- even if the heroes manage to neutralize my power generator and/or render the standard-issue energy weapons useless -- my troops will not be overrun by a handful of savages armed with spears and rocks.


		
_______________________________
Do you Yahoo!?
Declare Yourself - Register online to vote today!
http://vote.yahoo.com