RE: [uddi-spec] Handling large results missing in some publication API calls

["Rogers, Tony" <Tony.Rogers@ca.com>]

Title: Handling large results missing in some publication API calls

I must admit that my first reaction was "but each publisher is limited" :-)

 

I don't see any problem with adding this functionality, although I would not consider it a "bug". An oversight perhaps, but not a bug.

 

Tony Rogers

CA, Inc

Senior Architect, Development

tony.rogers@ca.com

co-chair UDDI TC at OASIS

co-chair WS-Desc WG at W3C

---

From: von Riegen, Claus [mailto:claus.von.riegen@sap.com]
Sent: Tue 11-Jul-06 17:11
To: uddi-spec@lists.oasis-open.org
Subject: [uddi-spec] Handling large results missing in some publication API calls

All,

There are some Publication API calls in UDDI 3.0.2 that don't provide the capability to manage large result sets, particularly

- get_assertionStatusReport
- get_publisherAssertions
- get_registeredInfo

This was not a problem for the UDDI Business Registry nodes because all these API calls relate to the management of entities published by an individual publisher and there were certain publication limits. However, it is up to a UDDI node's policy (as described in section 9.5.6 Node Publication Limits) whether there are actually such limits.

One example when such limits should not apply is the need for the publication of a large set of tModels, let's say something between 1k and 10k, and the publication needs to be done by a technical user in order to guarantee consistency and up-to-dateness. Calling the get_registeredInfo API with the technical user would represent a problem since the result set is too large and there would be no capability to retrieve the result set in chunks.

We believe that this is a bug and propose to clean up the above listed API calls by adding the maxRows and listHead attributes to the API calls and the listDescription element to the return structures with the meaning as described in section 5.1.5 Use of listDescription.

I'd be happy to to provide more background information during today's TC call.

Regards,
 Claus