Issue 10675: In section 3.1.6.3.6 regarding the Contract clarify some things (data-distribution-rtf) Source: PrismTech (Mr. Erik Hendriks, erik.hendriks(at)prismtech.com) Nature: Clarification Severity: Summary: Problem (1/4) (typo): Each attribute and operation description wrongly starts with a quotation mark, these should be removed. Problem (2/4) (typo): The description of attribute depth talks about a RELATED_OBJECT_SCOPE. This should be RELATED_OBJECTS_SCOPE (objects should thus be plural). Problem (3/4) (clarification): During the description of the scope attribute the various scopes are explained, for clarification purposes insert the type of scope right after the explaination. Problem (4/4) (clarification): In the description for the set_depth operation, indicate that the depth is ignored unless the scope is set to RELATED_OBJECTS_SCOPE, just like it says at the getter for the depth attribute. Solution: Replace: o "The top-level object (contracted_object). This is the object that acts as the starting point for the cloning contract. o "The scope of the cloning request (i.e., the object itself, or the object with all its (nested) compositions, or the object with all its (nested) compositions and all the objects that are navigable from it up till the specified depth). o "The depth of the cloning contract. This defines how many levels of relationships will be covered by the contract (UNLIMITED_RELATED_OBJECTS when all navigable objects must be cloned recursively). The depth only applies to a RELATED_OBJECT_SCOPE. It offers methods to: o "Change the depth of an existing contract (set_depth). This change will only be taken into account at the next refresh of the CacheAccess. o "Change the scope of an existing contract (set_scope). This change will only be taken into account at the next refresh of the CacheAccess. With: o The top-level object (contracted_object). This is the object that acts as the starting point for the cloning contract. o The scope of the cloning request (i.e., the object itself (SIMPLE_OBJECT_SCOPE), or the object itself along with all its (nested) compositions (CONTAINED_OBJECTS_SCOPE), or the object itself along with all its (nested) compositions and all the objects that are navigable from it up till the specified depth (RELATED_OBJECTS_SCOPE)). o The depth of the cloning contract. This defines how many levels of relationships will be covered by the contract (UNLIMITED_RELATED_OBJECTS when all navigable objects must be cloned recursively). The depth only applies to a RELATED_OBJECTS_SCOPE. It offers methods to: o Change the depth of an existing contract (set_depth). This change will only be taken into account at the next refresh of the CacheAccess. The depth only applies to a RELATED_OBJECTS_SCOPE. o Change the scope of an existing contract (set_scope). This change will only be taken into account at the next refresh of the CacheAccess. Resolution: Revised Text: Actions taken: February 12, 2007: received issue Discussion: In section 3.1.6.3.6 regarding the Contract clarify some things… And remove some typos End of Annotations:===== iler: QUALCOMM Windows Eudora Version 7.0.1.0 Date: Mon, 12 Feb 2007 14:57:52 -0500 To: issues@omg.org, data-distribution-rtf@omg.org From: Juergen Boldt Subject: issue 10675 -- DDS RTF issue X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at omg.org This is issue # 10675 From: "Erik Hendriks" In section 3.1.6.3.6 regarding the Contract clarify some things In section 3.1.6.3.6 regarding the Contract clarify some things. And remove some typos Problem (1/4) (typo): Each attribute and operation description wrongly starts with a quotation mark, these should be removed. Problem (2/4) (typo): The description of attribute depth talks about a RELATED_OBJECT_SCOPE. This should be RELATED_OBJECTS_SCOPE (objects should thus be plural). Problem (3/4) (clarification): During the description of the scope attribute the various scopes are explained, for clarification purposes insert the type of scope right after the explaination. Problem (4/4) (clarification): In the description for the set_depth operation, indicate that the depth is ignored unless the scope is set to RELATED_OBJECTS_SCOPE, just like it says at the getter for the depth attribute. Solution: Replace: o "The top-level object (contracted_object). This is the object that acts as the starting point for the cloning contract. o "The scope of the cloning request (i.e., the object itself, or the object with all its (nested) compositions, or the object with all its (nested) compositions and all the objects that are navigable from it up till the specified depth). o "The depth of the cloning contract. This defines how many levels of relationships will be covered by the contract (UNLIMITED_RELATED_OBJECTS when all navigable objects must be cloned recursively). The depth only applies to a RELATED_OBJECT_SCOPE. It offers methods to: o "Change the depth of an existing contract (set_depth). This change will only be taken into account at the next refresh of the CacheAccess. o "Change the scope of an existing contract (set_scope). This change will only be taken into account at the next refresh of the CacheAccess. With: o The top-level object (contracted_object). This is the object that acts as the starting point for the cloning contract. o The scope of the cloning request (i.e., the object itself (SIMPLE_OBJECT_SCOPE), or the object itself along with all its (nested) compositions (CONTAINED_OBJECTS_SCOPE), or the object itself along with all its (nested) compositions and all the objects that are navigable from it up till the specified depth (RELATED_OBJECTS_SCOPE)). o The depth of the cloning contract. This defines how many levels of relationships will be covered by the contract (UNLIMITED_RELATED_OBJECTS when all navigable objects must be cloned recursively). The depth only applies to a RELATED_OBJECTS_SCOPE. It offers methods to: o Change the depth of an existing contract (set_depth). This change will only be taken into account at the next refresh of the CacheAccess. The depth only applies to a RELATED_OBJECTS_SCOPE. o Change the scope of an existing contract (set_scope). This change will only be taken into account at the next refresh of the CacheAccess. Juergen Boldt Director, Member Services Object Management Group 140 Kendrick St Building A Suite 300 Needham, MA 02494 USA tel: +1 781 444 0404 x 132 fax: +1 781 444 0320 email: juergen@omg.org www.omg.org