Re: Handling unknown elements in an entry

[Dare Obasanjo <kpako@xxxxxxxxx>]

--- Robert Sayre <mint@xxxxxxxxxxxxxxx> wrote:
> 
> It's probably more productive to look at this as a
> storage operation. We 
> need to define the extent to which clients can
> expect to pick up what 
> they drop off. For example, storing atom:summary
> wouldn't be a guarantee 
> that it's useful on the site, but at least it would
> continue to be 
> present in the editor.

>From the perspective as the person responsible for a
lot of the server back end of MSN Spaces, it's a
non-starter to expect that we'll store arbitrary XML
sent from clients that doesn't map to properties in
our internal data model. 

> > 
> > However it is a significant burden for clients
> because
> > it means they'll have to know every single entry
> > element supported by every single blog service
> they
> > support posting to. I'd find this to be just as
> bad as
> > the MetaWeblog API mess that we have today. 
> 
> Yes, it would be, if we insist that elements
> directly reflect some 
> property of the site instead of treating them as
> stored annotations.
> 
> Am I making sense?

I see your perspective but I don't agree with it. HTTP
allows servers to ignore headers they don't support
and still return 200, I don't see why Atom should try
to be any different. 

THINGS TO DO IF I BECOME AN EVIL OVERLORD #222
I reserve the right to execute any henchmen who appear to be a little too intelligent, powerful, or devious. However if I do so, I will not at some subsequent point shout "Why am I surrounded by these incompetent fools?!"


		
__________________________________ 
Do you Yahoo!? 
Yahoo! Mail - Helps protect you from nasty viruses. 
http://promotions.yahoo.com/new_mail