Groups - New Action Item #0026 Update CR-0053 based on TC's feedback

[luc@iclement.net]

OASIS UDDI Specification TC member,

Luc Clement (luc@iclement.net) has created a new action item.

Number: #0026
Description: Update CR-0053 based on TC's feedback
Owner: Claus von Riegen (claus.von.riegen@sap.com)
Due: 03 Mar 2004

Comments:
Luc Clement  2004-02-18 22:33 GMT
See http://lists.oasis-open.org/archives/uddi-spec/200401/msg00110.html and the following comments.

This CR discusses the use of the keyGenerator categorization defined by the uddi.org:categorization:types value set.  At issue is that if you specify this categorization on a tModel, you create a keyGenerator. However, there is no behavior listed if you were to save it on a bindingTemplate, for example. The intent is that it only has behavior when it’s specified for a tModel, but it’s not explicitly said in the spec.   There are two issues:

1.	All keyGenerator tModels must be categorized as shown.
2.	Only keyGenerator tModels may be categorized as shown.
3.	It is impossible to create a keyGenerator tModel with a UDDI V2 API call.

Luc would prefer that we not update the behavior sections, and just define the valid usage in Ch. 11 so we don’t have to sprinkle explanations everywhere.

The last clarification is that an error is produced if you try to update a non-tModel entity with this classification.  (E_valueNotAllowed).  This needs to be described in the categorizationTypes tModel definition (Ch.11.1.1.4 Valid Values) too.  Tony would like the table in this section to indicate “Special Treatment” and have an explanation for its use following the table.

The TC decided that the specification will not restrict the entirety of the value set specifically to tModels due to migration concerns and the need support the wsdlDeployment value which represents the sole exception.

While we agreed that allowing keyGenerator in V2 might save implementation costs, we also agreed it would be the wrong thing to do, and thus, the CR needs to address this issue.

A further change suggested by John was that we should make a clearer separation between the “create” and “update” cases.

View Details:
http://www.oasis-open.org/apps/org/workgroup/uddi-spec/members/action_item.php?action_item_id=421



PLEASE NOTE:  If the above links do not work for you, your email application
may be breaking the link into two pieces.  You may be able to copy and paste
the entire link address into the address field of your web browser.