Re: [uddi-spec] Question regarding to tracking removed publisher assertionfor UDDI v3 subscription.

[Tom Bellwood <bellwood@us.ibm.com>]

Zhe,,

This will be in the minutes from the FTF, but we discussed this item today
and came up with a somewhat cleaner solution:

·     Update completionStatus in base schema to include a
“status:both_incomplete” (or similarly worded) option
·     Annotate spec where this is discussed outside of subscription to
indicate that use of status:both_incomplete only applies to subscription
·     Add explanation in subscription text in spec describing how
assertionStatusReport in subscriptionResults supports deletion by examining
the completionStatus for presence of “status:both_incomplete”.

   We also need to clarify what is reported in the keyBag when the key
   which is part of the filter citeria itself is deleted.  For example, if
   a businessKey is deleted and the filter criteria is a find_service for
   one of the services in that business, do we report back the deleted
   serviceKey, all of the deleted serviceKeys from that business, or the
   businessKey, or all of the above?  We agreed that the serviceKey in
   question is the one that should be returned.

   We also need to add an attribute to the subscriptionResultsList which
   indicates when a subscriptionFilter criteria is now broken.  This can
   occur if the filter was searching for specific keys which have been
   deleted.  Subsequent use of the filter would no longer be applicable and
   the subscriber needs to be informed that this has occurred.

You got the TODO for writing up a formal CR to this effect.   You ok with
that?

Thanks,
Tom Bellwood       Phone:  (512) 838-9957 (external);   TL:  678/9957
(internal)
Co-Chair, OASIS UDDI Specification TC
STSM - Emerging Technologies
IBM Corporation

"Zhe (Alan) Wu" <Alan.Wu@oracle.com> on 10/28/2003 10:15:35 AM

To:    Tom Bellwood/Austin/IBM@IBMUS
cc:    "Rogers, Tony" <Tony.Rogers@ca.com>, Luc Clement
       <lclement@windows.microsoft.com>, UDDI Spec TC
       <uddi-spec@lists.oasis-open.org>
Subject:    Re: [uddi-spec] Question regarding to tracking removed
       publisher assertion for UDDI v3 subscription.



Hi Tom/Luc,

I've read the comments from both of you. I tend to agree more
with Tom on that adding assertion or
relatedBusinessInfo (for the case of find_relatedBusiness) into
keyBag sounds a little bit confusing, even keyBag is renamed.

How about removing the <deleted> subelement from keyBag and adding
a <removed> element into subscriptionResultsList? That way, keyBag
means just a bag of keys, nothing more than that. Whether it specifies
a bag of deleted entities or briefed entities depends on its context.
If it's a subelement of <removed>, then it specifies a bag of deleted
entities.

Specifically, in the language of schema (changes are highlighted in
colors):
    <xsd:element name="keyBag" type="uddi_sub:keyBag" final="restriction"/>
    <xsd:complexType name="keyBag" final="restriction">
        <xsd:sequence>
            <!-- <xsd:element ref="uddi_sub:deleted"/> -->
            <xsd:choice>
                <xsd:element ref="uddi:tModelKey" maxOccurs="unbounded"/>
                <xsd:element ref="uddi:businessKey" maxOccurs="unbounded"/>
                <xsd:element ref="uddi:serviceKey" maxOccurs="unbounded"/>
                <xsd:element ref="uddi:bindingKey" maxOccurs="unbounded"/>
            </xsd:choice>
        </xsd:sequence>
    </xsd:complexType>

    <xsd:element name="subscriptionResultsList"
type="uddi_sub:subscriptionResultsList" final="restriction"/>
    <xsd:complexType name="subscriptionResultsList" final="restriction">
        <xsd:sequence>
            <xsd:element ref="uddi_sub:chunkToken" minOccurs="0"/>
            <xsd:element ref="uddi_sub:coveragePeriod"/>
            <xsd:element ref="uddi_sub:subscription"/>
            <xsd:choice minOccurs="0">
                <xsd:element ref="uddi:bindingDetail"/>
                <xsd:element ref="uddi:businessDetail"/>
                <xsd:element ref="uddi:serviceDetail"/>
                <xsd:element ref="uddi:tModelDetail"/>
                <xsd:element ref="uddi:businessList"/>
                <xsd:element ref="uddi:relatedBusinessesList"/>
                <xsd:element ref="uddi:serviceList"/>
                <xsd:element ref="uddi:tModelList"/>
                <xsd:element ref="uddi:assertionStatusReport"/>
            </xsd:choice>
            <xsd:element ref="uddi_sub:keyBag" minOccurs="0"
maxOccurs="unbounded"/>
            <xsd:element ref="uddi_sub:removed" minOccurs="0"/>
        </xsd:sequence>
        <xsd:attribute name="someResultsUnavailable" type="xsd:boolean"
use="optional"/>
    </xsd:complexType>

    <xsd:element name="removed" type="uddi_sub:removed"/>
    <xsd:complexType name="removed">
        <xsd:sequence>
            <xsd:element ref="uddi_sub:keyBag" minOccurs="0"
maxOccurs="unbounded"/>
            <xsd:choice>
                <xsd:element ref="uddi:relatedBusinessInfo" minOccurs="0"
maxOccurs="unbounded"/>
                <xsd:element ref="uddi:assertionStatusItem" minOccurs="0"
maxOccurs="unbounded"/>
            </xsd:choice>
        </xsd:sequence>
    </xsd:complexType>

Zhe (Alan) Wu
Oracle UDDI Server Team


Tom Bellwood wrote:

Alan,

Well, I think we definitely have something to fix here.   First off, the
"brief" attribute specifically states that the keyBag does not apply to
assertions.   Only problem with that is that there is no othre place to
specify something has been deleted.   I don't think we want to add an
asssertionStatusReport as a valid option to be in a keyBag - it is both
somewhat counter-intuitive and would affect uses of keyBag elsewhere in the
spec (e.g., in custody transfer).  The easiest thing may be to create an
entity specific to subscription which contains an assertionStatusReport and
an attribute indicating deletion.   We could alternatively add a deleted
attribute to the subscription structure (probably a better answer), but I
need to think through the ramificaitons of this a bit further I think.
let's discuss it at the FTF.

Thanks,
Tom Bellwood       Phone:  (512) 838-9957 (external);   TL:  678/9957
(internal)
Co-Chair, OASIS UDDI Specification TC