Subject: [Simple] Comments on xcap-01

From: [email-masked]
Date: Tue, 4 Nov 2003 16:21:41 +0200

Overall, I think the document is ready. Some minor comments:

- Resource Interdependency: After a server has populated a element or attribute, like the URI for a list, how does this information get communicated to the client (how does the client learn of such information)? Does the server fill it in before the 200 Ok is returned and body of the response contains the xml document (I don't think this is a good solution)?

- Creating a new document: must the document have file type of .xml? In the example in section 6.1, should mybuddies be mybuddies.xml?

- Content-type: I think defining a content-type for xcap is needed for creating/replacing elements and attributes. It is better than using text/plain as currently shown in the examples.

- Replacing an element/attribute: It might be useful to indicate that modifying an element value of an element is not possible, especially if that element has attributes. The whole element, including its attributes must be replaced.

- E-tags: If an element or attribute has been replaced or deleted, how does a client learn of such change? A client can never learn of a change unless is performs a GET and examines the etag. BTW, whatever happened to the event package for xcap?

Regards,
Hisham

_______________________________________________
Simple mailing list
[email-masked]
https://www1.ietf.org/mailman/listinfo/simple