Subject: [Simple] Comments on draft-ietf-simple-xcap-00

From: [email-masked]
Date: Sun, 29 Feb 2004 15:11:45 +0200

- Section 5.2 and 6.4: 6.4 says that "if the node selector, when evaluated against the current document, results in a no-match, the server performs a creation operation". The problem here is that section 5.2 defines a no-match to be when the evaluation of a node selector results in more than 1 element or more than 1 attribute.  I think section 5.2 needs fixing here. An evaluation that results in more than 1 element or attribute being selected should be considered an error. An evaluation that results in no selection should be a no-match.

- Fetching with GET: some text needs to be added in sections 6.3, 6.6 and 6.9 that specifies the behaviour when a client receives a 404 for a fetch. (I have a comment about the 404 response later).

- Section 7: Is it worth mentioning that other authentication protocols can also be used? Or are we restricting the XCAP authentication digest?

- Section 7.2: This relates to the first comment. There is no text saying that happens if the evaluation matches more than 1 element or attribute. It should say that this is an error and a 409 is returned (with some specific error).

- Section 7.2: There is a paragraph that talks about the need for the server to check the "mandatory-schemas" element. This should be the "mandatory-ns" element. Also, this paragraph is towards the end of the section. I think it should be the first paragraph indicating that this is the first thing a server does after authentication.

- Section 7.2.1.1: The schema is chopped off on the right in almost of all the <xs:documentation> elements.

- Section 7.3: again here about the evaluation resulting in more than 1 element or attribute. There should be an error returned to the client. Need to specify the error code (409?). If 409, you might need to add an element name for this kind of error. Actually, this is also useful for PUT.

- Section 7.3: Is returning a 404 for a GET the normal behaviour if evaluating a URL results in an empty selection? Can a server return a 200 with empty body? (I'm just curious. 404 is fine with me).

- The document mentions namespace attribute a couple of times. What is that? Is that the attribute in the root element?

Regards,
Hisham

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