2006/6/15, James M Snell <[EMAIL PROTECTED]>:
Absolutely +1 on not allowing the client to change the atom:id.
For the record, absolutely +1 also. But the question was also: how about other fields? I think there could be a real problem wrt authors and contributors: in some constrained environments, server implementations might want to disallow changing the author and/or contributor and managing these informations itself (i.e. the author is the user who submitted the doc, he can add other authors and turn contributors into authors and authors into contributors, but cannot remote himself from the list nor turn himself from an author to a contributor; other users might be able to update the content, they're not allowed to change authors or contributors, the system automatically adds them as contributors when they PUT an updated version if they're not already listed; the list of possible authors and contributors is constrained by the system based on a configuration table). On the other hand, on other environments, server implementations might let anyone change authors and contributors without any constraint. Similar problems could also happen wrt categories, particularly if they're not used to "tag" the entry but rather to "specialize" its type (à la GData). -- Thomas Broyer
