Issue 7826: Common Interfaces for common relationships (plm-ftf) Source: Zentrum fuer Graphische Datenverarbeitung e.V. (Mr. Steffen Nowacki, steffen.nowacki(at)partmaster.de) Nature: Uncategorized Issue Severity: Summary: All relationships in the PIM which are defined in different types but which are (potentially) used together in queries, (f.i. Associated_document_query for associated documents independend of the association source type) should have common base interfaces in the PIM which define this relationships. These interfaces and relationships have no impact for the web service PSM but eventually for future PSM. Interface Alias_select Compositions: Alias_identification Implemtented By: Organization Complex_product Classification_attribute Item Document_type_property Product_class Document_version Specification_category Document Specification Item_version Classification_system Item_instance Document_representation Property General_classification Design_discipline_item_definition Physical_instance Approval_status Interface Configured_item_select Compositions: Configuration Implemented By: Process_operation_occurrence Product_function Product_component Alternative_solution Process_plan Item_instance Interface Documented_element_select Compositions: Document_assignment Implemented By: Shape_element_relationship Process_operation_occurrence Work_order Product_identification Organization Physical_instance_test_result Item_definition_instance_relationship Complex_product Classification_attribute Item Product_class Item_definition_relationship Specification_category Change Specific_item_classification Material Specification Item_version Activity_element Project Classification_system Process_plan Activity_method Approval Item_instance Descriptive_specification Property Product_structure_relationship Shape_element General_classification Design_discipline_item_definition Item_instance_relationship Physical_instance Work_request Item_shape Design_constraint Physical_assembly_relationship Activity Class_structure_relationship Person Interface person_organization_select Compositions: Date_and_person_organization Person_organization_assignment Implemented By: Person_in_organization Organization Interface instance_definition_select Compositions: Item_instance Implemented By: Product_identification Design_discipline_item_definition Interface Shape_information_select Compositions: Shape_description_association Implemented By: Shape_element_relationship Shape_element Item_shape Interface Specification_operand_select Composition: Specification_inclusion Implemented By: Specification Specification_expression Interface Change_relationship_select Compositions: Change Implemented By: Process_operation_occurrence_relationship Process_plan_relationship Shape_element Replaced_definition_relationship Item_version_relationship The following Compositions should be added to existing interfaces in the PIM: Interface Process_property_select Compositions: Simple_property_value Interface Item_property_select Compositions: Simple_property_value Interface Geometric_or_external_model_select Compositions: Geometric_model_relationship Resolution: Revised Text: Actions taken: October 1, 2004: received issue Discussion: It was a design decision to omit all empty interfaces which origin from nested subselect types until no inheritance of interfaces is required anymore. This decision shall be reviewed in more detail and consequently may result in an issue with EXPRESS-XMI mapping in general. The impact on the existing XML Schema binding is minimal. See issue 8448 for a provisional resolution. It was a design decision to omit all empty interfaces which origin from nested subselect types until no inheritance of interfaces is required anymore. This decision shall be reviewed in more detail and consequently may result in an issue with EXPRESS-XMI mapping in general. The impact on the existing XML Schema binding is minimal. This change will be made to the PIM of PLM Services 2.0 End of Annotations:===== te: Fri, 01 Oct 2004 10:56:38 +0200 From: Steffen Nowacki User-Agent: Thunderbird 0.6 (Windows/20040502) X-Accept-Language: de-de, de-at, de, en-us, en To: issues@omg.org Subject: Issue for PLM Services 1.0 PLM Services 1.0 Document mantis/04-04-01 Revision Date 05/05/2004 Common Interfaces for common relationships All relationships in the PIM which are defined in different types but which are (potentially) used together in queries, (f.i. Associated_document_query for associated documents independend of the association source type) should have common base interfaces in the PIM which define this relationships. These interfaces and relationships have no impact for the web service PSM but eventually for future PSM. Interface Alias_select Compositions: Alias_identification Implemtented By: Organization Complex_product Classification_attribute Item Document_type_property Product_class Document_version Specification_category Document Specification Item_version Classification_system Item_instance Document_representation Property General_classification Design_discipline_item_definition Physical_instance Approval_status Interface Configured_item_select Compositions: Configuration Implemented By: Process_operation_occurrence Product_function Product_component Alternative_solution Process_plan Item_instance Interface Documented_element_select Compositions: Document_assignment Implemented By: Shape_element_relationship Process_operation_occurrence Work_order Product_identification Organization Physical_instance_test_result Item_definition_instance_relationship Complex_product Classification_attribute Item Product_class Item_definition_relationship Specification_category Change Specific_item_classification Material Specification Item_version Activity_element Project Classification_system Process_plan Activity_method Approval Item_instance Descriptive_specification Property Product_structure_relationship Shape_element General_classification Design_discipline_item_definition Item_instance_relationship Physical_instance Work_request Item_shape Design_constraint Physical_assembly_relationship Activity Class_structure_relationship Person Interface person_organization_select Compositions: Date_and_person_organization Person_organization_assignment Implemented By: Person_in_organization Organization Interface instance_definition_select Compositions: Item_instance Implemented By: Product_identification Design_discipline_item_definition Interface Shape_information_select Compositions: Shape_description_association Implemented By: Shape_element_relationship Shape_element Item_shape Interface Specification_operand_select Composition: Specification_inclusion Implemented By: Specification Specification_expression Interface Change_relationship_select Compositions: Change Implemented By: Process_operation_occurrence_relationship Process_plan_relationship Shape_element Replaced_definition_relationship Item_version_relationship The following Compositions should be added to existing interfaces in the PIM: Interface Process_property_select Compositions: Simple_property_value Interface Item_property_select Compositions: Simple_property_value Interface Geometric_or_external_model_select Compositions: Geometric_model_relationship Guillaume.Hirel@t-systems.com schrieb: Hallo Herr Nowacki, Dafür gibt es den process_property_select. Mit freundlichen Grüßen, _____________________________________________________________________________ Guillaume Hirel T-Systems International GmbH Project Manager Service Line Systems Integration Business Unit Digital Engineering Solutions (DES) Software & Integration (DES/SI) Fasanenweg 5 D-70771 Leinfelden-Echterdingen Tel: +49 / 711 972-43709 Fax: +49 / 711 972-41670 Mobiltelefon: +49 / 171 4453317 mailto:Guillaume.Hirel@t-systems.com http://www.t-systems.com _____________________________________________________________________________ -----Ursprüngliche Nachricht----- Von: Steffen Nowacki [mailto:steffen.nowacki@partmaster.de] Gesendet: Freitag, 1. Oktober 2004 09:18 An: Hirel, Guillaume; staub@pdtec.de; "Lämmer, Lutz"; Habel, Peter Betreff: XPDI Simple_property_value Hallo, der Simple_property_value wurde als Alternative zum Property_value eingeführt. Warum enthalten Activity_method_assignment Activity Process_operation_resource_assignment Process_operation_occurrence Process_operation_definition und Process_plan einen Simple_property_value, obwohl sie nicht im Item_property_select enthalten sind? Viele Grüße, Steffen Nowacki.