I received no response to my earlier inquiry. If there is no reasonable
explanation to the apparent discrepancy alluded to below, I think a
change request is in order. I will write it, but the lack of
acknowledgement of the issue on the part of TC membership makes me
wonder if I am correct in my assumption that the current V3 spec and
schema are sub-optimal in this respect.
Daniel
> -----Original Message-----
> From: Daniel Feygin [mailto:]
> Sent: Friday, November 01, 2002 2:13 PM
> To:
> Subject: [uddi-spec] subscriptionResultsList in UDDI V3
> Subscription API
>
>
> I am looking through the V3 Subscription API and cannot
> explain one thing about it that I don't think has been
> discussed outside of the UDDI Consortium's Working Group.
> subscriptionFilter is modeled as exactly one of either of the
> get_xx or find_xx operations, which I find quite fitting. At
> the same time subscriptionResultsList is modeled to allow
> multiple get_xx/find_xx responses per subscription, whereas
> subscription can only have one subscriptionFilter.
>
> Can someone please help me understand why
> subscriptionResultsList does not use the "choice" model the
> way subscriptionFilter does? Is this related to the lack of
> adequate development tools support?
>
> Daniel
>
>
> ----------------------------------------------------------------
> To subscribe or unsubscribe from this elist use the subscription
> manager: <http://lists.oasis-open.org/ob/adm.pl>
>
