Issue 7740: Attributes (plm-ftf) Source: Zentrum fuer Graphische Datenverarbeitung e.V. (Mr. Steffen Nowacki, steffen.nowacki@partmaster.de) Nature: Enhancement Severity: Minor Summary: the Occurrencies of the Attributes 'role_name', 'role_declaring_type_name' and 'inverse' of the Class 'Location_step' should be coupled as followed: <xs:complexType name="Location_step"> <xs:sequence> <xs:sequence minOccurs="0"> <xs:element name="Role_name" type="xs:string" /> <xs:element name="Role_declaring_type_name" type="xs:string"/> <xs:element name="Inverse" type="xs:boolean" minOccurs="0"/> </xs:sequence> <xs:element name="Predicate" type="Predicate" minOccurs="0" maxOccurs="unbounded"/> <xs:element name="Next_step" type="Location_step" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> </xs:complexType> because the attributes 'role_declaring_type_name' and 'inverse' make sense only when 'role_name' is set; and a 'role_name' without a 'role_declaring_type' seems problematical. Resolution: Revised Text: Resolution: The general resolution of this issue would require a resolution to the deferred issue 7826. See discussion there, also. All defined queries which allow the definition of a value for the attribute role_ name of their Location_step instances are provided with a value role_ declaring_type_name. Revised Text: Adjust the following definitions (corresponding figure numbers in brackets) by introducing a role_declaring_type_name attribute: 123 Alias_identification_query 125 Application_context_query 126 Approval_query (renamed to Associated_approval_query) 127 Approval_relationship_query ??? Assembly_structure_query 129 Associated_document_query 130 Associated_file_query 132 Associated_property_query (with helper queries Associated_item_property_query and Associated_process_property_query) 133 Class_structure_query 134 Complex_product_query 135 Configuration_query 136 Design_discipline_item_definition_query 138 Document_property_query 139 Document_query 140 Document_representation_query 141 Document_structure_query 144 Effectivity_query 146 Item_query 147 Item_relationship_query (renamed to Item_version_relationship_query) 148 Item_use_query 149 Item_version_query 152 Organization_query 153 Product_class_query 154 Product_structure_query 155 Simple_property_value_query (renamed to Simple_property_query) Actions taken: September 13, 2004: received issue August 1, 2005: closed issue Discussion: End of Annotations:===== m: webmaster@omg.org Date: 13 Sep 2004 02:16:57 -0400 To: Subject: Issue/Bug Report -------------------------------------------------------------------------------- Name: Steffen Nowacki Company: PartMaster GmbH mailFrom: steffen.nowacki@partmaster.de Notification: No Specification: PLM Services Section: 3.9 FormalNumber: mantis/04-04-01 Version: 1.0 RevisionDate: 05/05/2004 Page: 360 Nature: Enhancement Severity: Minor HTTP User Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1) Description the Occurrencies of the Attributes 'role_name', 'role_declaring_type_name' and 'inverse' of the Class 'Location_step' should be coupled as followed: because the attributes 'role_declaring_type_name' and 'inverse' make sense only when 'role_name' is set; and a 'role_name' without a 'role_declaring_type' seems problematical. Date: Thu, 17 Mar 2005 15:11:54 +0100 From: Steffen Nowacki User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: de-DE, de, en-us, en To: "Lämmer, Lutz (PROSTEP)" Cc: plm-ftf@omg.org Subject: PLM Services issues #7740 Hallo Lutz, I have added in all Location_step instances which have a "role_name" a value for "role_declaring_type_name". It concerns Figures 123 Alias_identification_query 125 Application_context_query 126 Approval_query (renamed to Associated_approval_query) 127 Approval_relationship_query ??? Assembly_structure_query 129 Associated_document_query 130 Associated_file_query 132 Associated_property_query (with helper queries Associated_item_property_query and Associated_process_property_query) 133 Class_structure_query 134 Complex_product_query 135 Configuration_query 136 Design_discipline_item_definition_query 138 Document_property_query 139 Document_query 140 Document_representation_query 141 Document_structure_query 144 Effectivity_query 146 Item_query 147 Item_relationship_query (renamed to Item_version_relationship_query) 148 Item_use_query 149 Item_version_query 152 Organization_query 153 Product_class_query 154 Product_structure_query 155 Simple_property_value_query (renamed to Simple_property_query) All new Location_step instances from the finalization have a value for the "role_declaring_type_name" so we can set issue 7740 to resolved. Best regards, Steffen Nowacki. -- PartMaster GmbH E-Mail: steffen.nowacki@partmaster.de Lagerstrasse 44/45 WWW : http://www.partmaster.de D-18055 Rostock, Germany Phone : +49 381 20373996 Fax : +49 381 20373994