 |
 |
 |
 |
|
 |
|
 |
|
 |
|
 |
|
|
|
|
|
|
|
|
|
|
|
|
Hi Simon Pietro and others,
I was reading through the last version of your CCMP draft and I got some notes about it. Fowolling there are my comments.
If they are not clear enough, don't hesitate to contact me and I'll try to explain them more carefully.
Cheers,
Oscar
-------------------------------------------------------------------------------------------------------------------
1. Introduction: "CCMP can use a general-purpose protocol such as HTTP [RFC2616] to transfer domain-specific XML-encoded data objects defined in the Conference Information Data Model for Centralized Conferencing. "
[ON] Does it mean CCMP can be use with other protocols? It's a bit confusing reading through the document because in some parts you really state that the use of HTTP is a must.
1. Introduction: "CCMP follows the well-known REST (REpresentational State Transfer) architectural style"
[ON] Well, is it really true? Maybe some clarification to this point should be needed.
6.1 Conference Object: "When creating conferences, the XCON-URI included by the client is only a suggestion."
[ON] Would it not be easier if the client doesn't included any XCON-URI and accepts the one from the server right away?
7.2 Create
[ON] It would be good if you have in the document a diagram of the 'retrieve' operation you explained in this section
[ON] I think the creation mechanism is quiet limited right now. What about the creation of sidebars? Or the creation of other elements in the conference?
7.4 Delete
"A request which attempts to delete a conference object that is being referenced by a child object is an error."
[ON] Would it not be possible to have the option to delete the conference with all the child object included? Is a sidebar consider a child object?
8. Protocol Operations on Conference Objects
"blueprintsRequest/blueprintsResponse: The blueprintsRequest is used to ascertain the list of blueprints available at the conference server. The blueprintsResponse returns a list of the requested blueprints, in the form of XCON URIs."
[ON] Maybe it would be good if the blueprintsResponse returns a description of each blueprint or ,even better, it would be possible to defined in the blueprintsRequest the elements wanted in the response. Sometimes just the name of the blueprint won't be enough to choose the most convenient one. As well, it would be good if the client can defined in the blueprintsRequest some filter criterias, for instance, blueprints that uses the 'foo' media.
8.2.3 Operations Request
[ON] What does the N/A means in the HTTP examples of sidebarRequest?
8.3. Handling a CCMP Response
[ON] I got a bit confused with the set of CCMP Response Codes. Are not the 'forbidden' and the 'operationNotAllowed' the same type of error? And I would re-name the 'deleteFailedParent' to 'forbiddenDeleteParent' and the 'changeFailedProtected' to 'forbiddenChangeProtected'.
8.3.3.2 Create Operation Response
"The only valid responses containing a "create" operation are a "confResponse", a "blueprintResponse" and the "userResponse"."
[ON] what about create sidebars?
"The "blueprintRequest" containing a "create" operation has to be considered a special operation, used by a conference server administrator wishing to remotely add a new blueprint to the conference server. The operation requires that the new blueprint is associated with an XCON-URI."
[ON] I really don't get the point for that. Would it not be easier to remove this element from the create operation if -anyway- it will be considered a suggestion?
"If the confResponse to a "create" operation contains a response code of "modified", along with the XCON-URI for the conference object, the response MUST also contain the entire XML document associated with that conference object for a "confRequest"."
[ON] why it doesn't contain just the modified part of the document? Wouldn't it be more efficient?
"Any other response code indicates an error in the client or conference control server (e.g., "forbidden", "badRequest") and the handling is specific to the conference control client."
[ON] remove 'forbidden' from the sentence.
8.3.3.3. Change Operation Response
"Any other response code indicates an error in the client or conference control server (e.g., "forbidden", "badRequest") and the handling is specific to the conference control client."
[ON] remove 'forbidden' from the sentence.
[ON] If the document is modified succesfully, I wouldn't send in the response message the XML document again. I would send just an empty satisfactory response.
8.3.3.4 Delete Operation Response
"Any other response code indicates an error in the client or conference control server (e.g., "forbidden", "badRequest") and the handling is specific to the conference control client."
[ON] remove 'forbidden' from the sentence.
10.5 Blueprints Parameter
"The "blueprints" attribute is comprised of a list of blueprints supported by the specific conference server and includes a conference system specific "blueprintName" and a "confObjID" in the form of an XCON-URI for each of the blueprints."
[ON] Same comment than section 8. Would it be possible to extend the information in the "blueprints" attribute?
11.2.3. Adding a User to a Conference
In Figure 14, it would be much neat if you use a sequence-ID to identify the message and you get rid of repeat information. Something like:
<userResponse xmlns="urn:ietf-params:xml:ns:xcon:ccmp">
<operation>change</operation>
<responseCode> success </responseCode>
<confObjID> xcon:confxyz987 at example.com </confObjID>
<confUserID> userC-confxyz987 </confUserID>
<sequence-ID>58943</sequence-ID>
</userResponse>
NITS
--------
3. Terminology -> Change 'additon' to 'addition'
4.Rationale and Motivation -> Change 'approach must ensure sure that all...' to 'approach must ensure that all...'
6.2 Conference Users and Participants ->last paragrah, change '<user> attribute' to '<user> element'
8.3.1 change 'blueprintRequest' to 'blueprintsRequest' to
8.3.3.1 add a full stop at the end of the sentence. "associated with the requested blueprint"
8.3.3.3. Change Operation Response change "used by a conference server administrator wishing to remotely an existing blueprint in the conference server." to "used by a conference server administrator wishing to remotely CHANGE OR MODIFY an existing blueprint in the conference server."
10.3 ConfUserID Parameter: change "for an "userRequest" message" to "for A "userRequest" message"
11.1 Change "Figure 3: Getting a List of Active Coferences" to "Figure 3: Getting a List of Active CoNferences"
11.1 Figure 4 Change "GET /confs/confid-34fg67h" to "GET /conf/confid-34fg67h"
11.1 Figure 5 Change " PUT /confs/confid-34fg67h/users/pippo876" to " PUT /conf/confid-34fg67h/users/pippo876"
11.1 Change "Figure 4: Getting a Specific Coference" to "Figure 4: Getting a Specific CoNference"