Issue 10661: Unclarities in section 3.1.4.2.3 (data-distribution-rtf)
Source: PrismTech (Mr. Erik Hendriks, erik.hendriks(at)prismtech.com)
Nature: Clarification
Severity: 
Summary: Problem:
Various things are unclear in this section, for example the last bulleted list in this section does not take the Set type of a multi-valued attribute into account. A bullet needs to be added to state that the set does not contain an index key. Also replace 'row' with the word 'instance' in accordance with other issues. Also it needs to be indicated that in case of predefined mapping that the user defined keys identify the object, not the OID.
In accordance with another issue, replace the word 'row' with 'instance'. Replace the word 'cell' with 'field'

Solution:

Replace:
Mono-valued attributes and relations are mapped to one (or several) cell(s)7 in a single row whose key is the means to unambiguously reference the DLRL object (i.e., its oid or its full oid, depending on the owner class characteristics as indicated in the previous section):
With:
Mono-valued attributes and relations are mapped to one (or several) field(s)7 in a single instance whose key is the means to unambiguously reference the DLRL object (i.e. its oid, its full oid, or its user defined keys, depending on the owner class characteristics as indicated in the previous section):

Replace (in the first bulleted list of the section):
reference to another DLRL object (i.e., relation) -> as many cells as needed to reference unambiguously the referenced object (i.e., its oid, or its full oid as indicated in the previous section).
With:
reference to another DLRL object (i.e., relation) -> as many fields as needed to reference unambiguously the referenced object (i.e., its oid, its full oid, or its user defined keys as indicated in the previous section).

Replace:
Multi-valued attributes are mapped to one (or several) cell(s) in a set of rows (as many as there are items in the collection), whose key is the means to unambiguously designate the DLRL object (i.e., oid or full oid) plus an index in the collection.
o For each item, there is one instance that contains the following, based on the type of attribute:
o simple basic type -> one cell of the corresponding DCPS type;
o enumeration -> one cell of type integer or string;
o simple structures -> as many cells as needed to hold the structure;
o reference to another DLRL object -> as many cells as needed to reference unambiguously the referenced object (i.e., its oid, or its full oid as indicated in the previous section).
o The key for that row is the means to designate the owner's object (i.e., its oid or full oid) + an index, which is:
o An integer if the collection basis is a list (to hold the rank of the item in the list).
o A string or an integer9 if the collection basis is a map (to hold the access key of the item in the map).
With:
Multi-valued attributes are mapped to one (or several) field(s) in a set of instances (as many as there are items in the collection), whose key is the means to unambiguously designate the DLRL object (i.e., oid or full oid, or its user defined keys) plus an optional index in the collection.
o For each item, there is one instance that contains the following, based on the type of attribute:
o simple basic type -> one field of the corresponding DCPS type;
o enumeration -> one field of type integer or string;
o simple structures -> as many fields as needed to hold the structure;
o reference to another DLRL object -> as many fields as needed to reference unambiguously the referenced object (i.e., its oid, its full oid, or its user defined keys as indicated in the previous section).
o The key for that row is the means to designate the owner's object (i.e., its oid, full oid, or its user defined keys) + an optional index, which is:
o An integer if the collection basis is a list (to hold the rank of the item in the list).
o A string or an integer9 if the collection basis is a map (to hold the access key of the item in the map).
o No index if the collection basis is a set (The item value field is implicitly the key in this case)

Resolution: 
Revised Text: 
Actions taken:
February 12, 2007: received issue
Discussion: 

End of Annotations:=====
s is issue # 10661	From: "Erik Hendriks" <Erik.Hendriks@prismtech.com> 

Unclarities in section 3.1.4.2.3

Problem:
Various things are unclear in this section, for example the last bulleted list in this section does not take the Set type of a multi-valued attribute into account. A bullet needs to be added to state that the set does not contain an index key. Also replace 'row' with the word 'instance' in accordance with other issues. Also it needs to be indicated that in case of predefined mapping that the user defined keys identify the object, not the OID.
In accordance with another issue, replace the word 'row' with 'instance'. Replace the word 'cell' with 'field'

Solution:

Replace:
Mono-valued attributes and relations are mapped to one (or several) cell(s)7 in a single row whose key is the means to unambiguously reference the DLRL object (i.e., its oid or its full oid, depending on the owner class characteristics as indicated in the previous section):
With:
Mono-valued attributes and relations are mapped to one (or several) field(s)7 in a single instance whose key is the means to unambiguously reference the DLRL object (i.e. its oid, its full oid, or its user defined keys, depending on the owner class characteristics as indicated in the previous section):

Replace (in the first bulleted list of the section):
reference to another DLRL object (i.e., relation) -> as many cells as needed to reference unambiguously the referenced object (i.e., its oid, or its full oid as indicated in the previous section).
With:
reference to another DLRL object (i.e., relation) -> as many fields as needed to reference unambiguously the referenced object (i.e., its oid, its full oid, or its user defined keys as indicated in the previous section).

Replace:
Multi-valued attributes are mapped to one (or several) cell(s) in a set of rows (as many as there are items in the collection), whose key is the means to unambiguously designate the DLRL object (i.e., oid or full oid) plus an index in the collection.
o For each item, there is one instance that contains the following, based on the type of attribute:
o simple basic type -> one cell of the corresponding DCPS type;
o enumeration -> one cell of type integer or string;
o simple structures -> as many cells as needed to hold the structure;
o reference to another DLRL object -> as many cells as needed to reference unambiguously the referenced object (i.e., its oid, or its full oid as indicated in the previous section).
o The key for that row is the means to designate the owner's object (i.e., its oid or full oid) + an index, which is:
o An integer if the collection basis is a list (to hold the rank of the item in the list).
o A string or an integer9 if the collection basis is a map (to hold the access key of the item in the map).
With:
Multi-valued attributes are mapped to one (or several) field(s) in a set of instances (as many as there are items in the collection), whose key is the means to unambiguously designate the DLRL object (i.e., oid or full oid, or its user defined keys) plus an optional index in the collection.
o For each item, there is one instance that contains the following, based on the type of attribute:
o simple basic type -> one field of the corresponding DCPS type;
o enumeration -> one field of type integer or string;
o simple structures -> as many fields as needed to hold the structure;
o reference to another DLRL object -> as many fields as needed to reference unambiguously the referenced object (i.e., its oid, its full oid, or its user defined keys as indicated in the previous section).
o The key for that row is the means to designate the owner's object (i.e., its oid, full oid, or its user defined keys) + an optional index, which is:
o An integer if the collection basis is a list (to hold the rank of the item in the list).
o A string or an integer9 if the collection basis is a map (to hold the access key of the item in the map).
o No index if the collection basis is a set (The item value field is implicitly the key in this case)