[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [uddi-spec] Accept CR-071
Per discussion during the telecon, this CR is now accepted
to the v3.0.2 errata.
Luc
Clément
Co-Chair OASIS UDDI
Spec TCSystinet Corporation
Tel: +1.617.395.6798 From: Mirek Novotny [mailto:mirek.novotny@systinet.com] Sent: Sunday, July 25, 2004 10:42 To: uddi-spec@lists.oasis-open.org Subject: [uddi-spec] Accept CR-071 This is just a notification that our engineering
have no issues with CR-071 and we accept
it.
Thanks
Mirek
5.2.7 CR-071The document
uddi-spec-tc-cr071-entityKeyValueSetBehaviorForDeletionsAndCertainUpdates-20040718.doc
has been submitted by Andrew Hately (hately@us.ibm.com) to the OASIS UDDI
Specification TC document repository. Document
Description: The specification does not define treatment of keyValue attributes in
keyedReferences pointing to entityKey value set tModels when the entity
referenced in the keyValue is deleted. The specification also does not define
treatment of keyValue attributes in keyedReferences pointing to value set
tModels that are changed classified as entityKey value set tModels. Similarly,
the specification does not define treatment of keyValue attributes in
keyedReferences pointing to entityKey value set tModels that are changed to no
longer be classified as entityKeyValue set tModels. This change request clarifies the
specification by adding descriptions of how a node should handle these
cases. Due to the peculiarity of
changing value set tModels after they have existed, the behavior for the last
two problems outlined will be that the behavior is undefined for existing
keyValue attributes. Download
Document:
Minutes: Tentatively accepted – We should accept to hold off for Mirek – 2-3 days. |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]