RE: [uddi-spec] RQ 21 - Federation

["Von Riegen, Claus" <claus.von.riegen@sap.com>]

Max,

Thanks for your additional scenarios.

While the first one may be valid, I don't believe that it represents a new type of usage scenario.

The second one sounds interesting. However, UDDI has a consistent approach of what the response to an Inquiry API call can comprise - it is always limited to the content of the registry itself. Responding with "pointers" to entities in other registries would require to define new APIs. I believe that this should better be addressed by its own requirements document, provided that we agree to work on this.

The third one is really one application of the "registry X registers its services with registry Y" model in that it enables registry Y to allow federated discoveries. But again, without replication, the current Inquiry API can't meet the requirement. Provided that a new requirements document for "federated discovery" is added, we can add this to RQ 21 so that the overall scenario can be enabled by appropriately categorizing nodes/registries in UDDI.

Thoughts?

Claus

-----Original Message-----
From: Max Voskob [mailto:max.voskob@paradise.net.nz] 
Sent: Mittwoch, 15. Oktober 2003 18:08
To: uddi
Subject: [uddi-spec] RQ 21 - Federation


Claus,

I'm not sure that these scenarios are valid, but anyway, here they are:

1. Private implementations may have their own roots not connected to UBR

2. User A sends a GET- request to Registry X for an entitity contained in
Registry Y. Regtistry X is aware that the entity is in Reg Y and acts as a
proxy or responds to the user with approriate information where to go. The
entities are not being replicated, but the keys probably have to.

3. Registries are connected in a network of underfined structure:
any-to-any. One registry (X) can register its services with the other (Y) so
that Reg Y will query/update Reg X on behalf of the user. No actual
replication of entities takes place.

Cheers,
Max







To unsubscribe from this mailing list (and be removed from the roster of the OASIS TC), go to http://www.oasis-open.org/apps/org/workgroup/uddi-spec/members/leave_workgroup.php.