On 1/27/06, James M Snell <[EMAIL PROTECTED]> wrote: > > > Joe Gregorio wrote: > > How is a client supposed to detect that a server > > rejects any entry with a title/@type="xhtml"? > > I know that's probably going to be rare, but iti is currently > > allowed since there is currently no spec text which states: > > > > May not be as rare as you think. The APP implementation I'm currently > working on is being grafted over an existing data model in which titles > are, you guessed it, text only. Markup in titles is not allowed. If > you pass in markup, it would come out as escaped text. Rather than lose > data by dropping the tags and changing the type to text, we're rejecting > the posts with a 403 Forbidden (possibly changing to a 422).
Hmm, besides being a clear violation of Postel's law, how is my client supposed to detect/recover from this? > > "A server MUST NOT reject a POSTed entry because of the > > choice of @type for any of it's Text Constructs." > > > > This would be a mistake. Implementations should have the sole > discretion as to what kinds of inputs they will allow; the protocol > should not be dictating content requirements. The server can reject based on other criteria, such foul language, text length restrictions, etc, but unless the server is able to announce the kinds of Text Constructs it is willing to accept I think this is a reasonable constaint that will aid interop, otherwise clients will quickly converge to the least common denominator (text) and we won't have gained anything by using Atom as a base. -joe -- Joe Gregorio http://bitworking.org
