On Thu, Sep 2, 2010 at 9:37 AM, Dave Cridland <[email protected]> wrote: > On Wed Sep 1 20:18:22 2010, Kevin Smith wrote: >> >> We could - although it's not clear to me how much of a problem this is >> - other storage specs suffer from it as well - Bookmarks for example >> (either over private or P(E|O|I)P). > > A client can figure out if provate and/or P*P is supported, and use them.
I wasn't talking about that aspect of it. Assuming the server supports P*P, the client will retrieve the list of bookmarks, do something with them, and set them again. We have exactly the same problem with throwing away unknown extensions in all cases like this. What I think we need to say is "Clients: If you're using a data store on the server, and there are unknown child elements, include them when you replace the item" in all such cases (bookmarks, roster, etc). /K
