On 11/1/05, James M Snell <[EMAIL PROTECTED]> wrote: > +1. This whole discussion is a rathole. Sometimes the client > should|can|will generate the id, other times the server should|can|will > generate the id. We should not dictate that the client must be > responsible for generating a globally unique identifier for every > atom:entry it wants to post. But we should also say that that > collection must contain valid atom:entries. This means that for POST'ed > entries that do not contain atom:id and atom:updated, the server MUST > fill them in upon during processing of the POST operation.
Actually, I would prefer that Atom entries be valid, even if the atom:id and atom:updated are stuffed with filler. It will make the service much easier to validate. -joe -- Joe Gregorio http://bitworking.org
