Re: Handling unknown elements in an entry

[jpanzer@xxxxxxx (John Panzer)]

Dare Obasanjo wrote:

> From my perspective the APP would be a way to create
> content on our servers. We at no time guarantee that
> we will store what was sent with full fidelity. For
> example, we support a subset of HTML (e.g. no script
> blocks) but we don't error when users post blog
> entries with 'banned' HTML elements instead we just
> strip them. 
>  
AOL Journals does the same thing.  And so will every service that hosts 
on a single domain (that cares about cookie security, anyway).

And I think it's very relevant to this discussion -- a server has to 
transform some of the core content in some way when posting an entry; 
should it return a "201" even though it had to change something on 
upload?  I think it should.  And if it can do this for core stuff like 
the HTML content in a post, I think the same relaxed rules should apply 
for things like unknown elements.

Though it might be nice to be able to inform the client some other way 
that full fidelity is not to be expected, the way certain applications 
warn you when saving in a foreign file format that some data might be 
lost (but still save everything they can).

-John