- 
                            Key: PLM-27
- 
                            Legacy Issue Number: 7883
- 
                            Status: closed
- 
                            Source: Anonymous
- 
                            Summary:For the compositions 'Item_version' and 'Document_version' 
 we have set xs:nillable='true' to satisfy the multipliciy
 constraint '1..*' with nil objects (if required) .The problem appears in other locations in the informational XML Schema too. 
 There are many locations in the informational XML Schema with relationships
 with the multiplicity '1..*'.
 If such a relationship is traversed inside the evaluation of a query in inverse direction
 the source objekct of the traversion can be used to satisfy the multiplicity constraint
 in the result.
 But which objects should be used in other cases to satisfy the multiplicity?If we have a Work_order_query 
 and this query selects a Work_order object.
 Which activity objects should be added to the result
 to satisfy the multiplicity of the Is_controlling association
 of the Work_order object:
 all, one arbitrary or one nil activity object?Here is the hopefully complete list of the concerned relationships: 
 (Referenced_type Referencing_type.Relationship)Compositions 
 Translation Translations.Translation
 Item_version Item.Item_version
 Document_version Document.Document_version
 Person_in_organization Person.Person_in_organizationAssociations 
 Accuracy_select Accuracy.Is_defined_for
 Activity Work_order.Is_controlling
 Approval_element_select Approval.Is_applied_to
 Date_and_person_organization Work_request.Notified_person
 Date_time_person_organization_element_select
 Date_and_person_assignment.Is_applied_to
 Date_time_person_organization_element_select
 Date_time_assignment.Is_applied_to
 Date_time_person_organization_element_select
 Person_organization_assignment.Is_applied_to
 Document Specific_document_classification.Associated_document
 Final_definition_select Final_solution.Final_specification
 Item Specific_item_classification.Associated_item
 Item_property_select Material.Described_element
 Property_value Value_list.Values
 Specification Product_specification.Defining_specification
 Specification_operand_select Specification_expression.Operand
- 
                            Reported: PLM 1.0b1 — Wed, 27 Oct 2004 04:00 GMT
- 
                            Disposition: Resolved — PLM 1.0
- 
                            Disposition Summary:No Data Available 
- 
                            Updated: Fri, 6 Mar 2015 20:58 GMT
PLM — How to satisfy relationship multiplicities of '1..*' in query results?
- Key: PLM-27
- OMG Task Force: PLM Services FTF