[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Re: [uddi-spec] Question regarding to tracking removed publisherassertion for UDDI v3 subscription.
The bag inside a delete_publisherAssertions request isn't a keyBag, it's a bag of publisher assertions.When you delete a publisher assertion you don't do so by specifying its key. You do so by specifying all the parts that make that publisher assertion unique - that's the two business keys and the relationship keyed reference. I suppose you could call the composite of those three things a synthetic key, if you wanted to, but that's stretching things a bitTony Rogers-----Original Message-----Dear Spec TC,
From: Zhe (Alan) Wu [mailto:Alan.Wu@oracle.com]
Sent: Wed 22/10/2003 5:22
To: Luc Clement
Cc: UDDI Spec TC
Subject: [uddi-spec] Question regarding to tracking removed publisher assertion for UDDI v3 subscription.
It seems that UDDI v3 subscription API does address the changes
relevant to publisherAssertion. My question is that if a publisher
assertion is deleted, how can we put it inside the keyBag?
The xml schema does not support that for the time being. However,
allowing a publisher assertion reside in keyBag sounds weird too because
'keyBag' is supposed to be a bag of keys and publisher assertion does not
have a key.
Is it reasonable to assign a key to publisher assertion, just to make it
consistent with other entities? That way, tracking deleted publisher assertions
can also be done consistently.
Another way is to extend the xml schema to allow keyBag include
publisher assertions. But then it is better off to rename keyBag to
something else.
Thanks,
Zhe (Alan) Wu
Oracle UDDI Server Team
The PDF and HTML versions of the spec were updated and available at:
HTML versions at:
PDF version at http://uddi.org/drafts/pubs/uddi-v3.0.1-20031014.pdf
Note that:
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]