search

cts2 / cts2-specification

The CTS2 OMG Specification
http://informatics.mayo.edu/cts2
11 stars 2 forks source link

OMG Issue 18490: AssociationDirectory needs "associationID" #118

Open hsolbrig opened 11 years ago

hsolbrig commented 11 years ago

In cases where the associationID is supplied, it is the ID that gets you from the directory contents to the actual association.

This change has been added to revision 7733 in cts2/spec/submission/OMGServerMap/association/Association.xsd on 10/4/2012

http://www.omg.org/issues/cts2-rtf#Issue18490

craigstancl commented 11 years ago

Reason For Change

In cases where the associationID is supplied, it is the ID that gets you from the directory contents to the actual association.

Severity: Minor

Proposed Resolution (PIM)

* Change Location1
 Document "CTS2 - Entity Description Services, v1.0"
 Section 4.3
 Page 50
 Figure 4.3
* Change Description 1
 Updated diagram in Figure 4.3
 Old Diagram:

2bf8478a929d34d1af7ae26ddce2b2e1

 New Diagram:
 No Change Required.
* Change Description 2
 Document "CTS2 - Entity Description Services, v1.0"
 Section 4.3.2
 Page 51
* Change Location 2
 Change made to Attributes section of Class AssociationDirectoryEntry.

 Old Text:

associationID - the unique identifier of the association instance.

 New Text:

associationID - the unique identifier of the association instance. While the update mechanism of the CTS2 specifications requires that all Changeable elements have unique identifiers, the rules and mechanism for assigning unique identifiers to statements and associations are non-trivial. At the moment, the CTS2 specification remains silent when it comes to arriving at how this identifier is generated except to note that, if two service implementations do not generate the same unique identifier for the same assertion, then the prevImage element in Changeable becomes the only way to identify which Association instance is being updated or deleted.

Proposed Resolution (PSM)

* Change Location

Association.xsd

* Change Description

View changes: https://github.com/cts2/cts2-specification/commit/f3285d056d641ad7eb2ee0680c986fb2394d3238

8a6a5bb2c48715e1ed1aeeb2c56c6cc6

Proposed Revised Text

the unique identifier of the association instance. While the update mechanism of the CTS2 specifications requires that all Changeable elements have unique identifiers, the rules and mechanism for assigning unique identifiers to statements and associations are non-trivial. At the moment, the CTS2 specification remains silent when it comes to arriving at how this identifier is generated except to note that, if two service implementations do not generate the same unique identifier for the same assertion, then the prevImage element in Changeable becomes the only way to identify which Association instance is being updated or deleted.