Subject: RE: [uddi-spec] Groups - uddi-spec-tc-cr022-serviceProjectionWithServiceMove-20030527.doc uploaded
07/08/2003 12:13 AM
I think that we should add the following as a footnote to the new sentence (in red); it adds important background info that otherwise would be missed by the "casual" reader.:
footnote... This solution emphasizes that in all circumstances the real service should be used to retrieve the properties within a service projection. Based on this premise, there should be no validation or ownership verification done on the businessKey associated with a service during replication.
Your proposed text:
If the referenced businessService is deleted by any means, all references to it associated with other businessEntity structures are left untouched. Such “broken” service projections appear in their businessEntity as businessService elements containing the businessKey and serviceKey attributes as their only content. If the businessService is moved to another business, all projections will be updated to reflect the new businessKey. For this reason, it is good practice to coordinate references to businessService data published under another businessEntity with the party who manages that data.
From: firstname.lastname@example.org [mailto:email@example.com]
Sent: Tuesday, June 17, 2003 13:03
Subject: [uddi-spec] Groups - uddi-spec-tc-cr022-serviceProjectionWithServiceMove-20030527.doc uploaded
The document uddi-spec-tc-cr022-serviceProjectionWithServiceMove-20030527.doc has been submitted by Andrew Hately (firstname.lastname@example.org) to the UDDI Specification TC document repository.
View Document Details:
PLEASE NOTE: If the above links do not work for you, your email application may be breaking the link into two pieces. You may be able to copy and paste the entire link address into the address field of your web browser.
-OASIS Open Administration
You may leave a Technical Committee at any time by visiting http://www.oasis-open.org/apps/org/workgroup/uddi-spec/members/leave_workgroup.php