Issue 7739: The WSDL and the XML Schema should be extended
Issue 7773: "associated" prefix
Issue 7826: Common Interfaces for common relationships
Issue 7829: Intermediate Queries
Issue 7887: Granularity of Computational Model
Issue 8011: Add complex type Section_context
Issue 8013: multiplicity of relations
Issue 8442: Name of Alternative_solution_query
Issue 7739: The WSDL and the XML Schema should be extended (plm-ftf)
Click here for this issue's archive.
Source: Zentrum fuer Graphische Datenverarbeitung e.V. (Mr. Steffen Nowacki, steffen.nowacki(at)partmaster.de)
Nature: Enhancement
Severity: Minor
Summary:
The WSDL and the XML Schema should be extended by xsd:appinfo's with informations about the allowed types for the xs:IDREF(S) which are modelled as interfaces in the PIM.
The resolution of this issue was postponed due to lacking resources. This change will be incorporated in the new version of the schema defined for PLM Services 2.0
The "associated" prefix for some querie names seems to be used arbitrary. "Associated_document_query" asks for associated documents but "Item_classification_query" asks for associated item_classifications. Clear guidelines shall be given for using that prefix.
For compatibility reasons it is not convenient to change the existing names but to enforce a naming scheme for all update and extensions in the PLM Services 2.0
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_relationshipIt 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
The result of the concatenation of queries
is defined as the union of the result of the
single queries.
Some use cases needs another semantic of concatenated queries.
F.i. for the Start node identification use case
the set of Items selected by an Item_query
have to be filtered by an (optional)
following Item_version_query.
In this case the ItemQuery doesn't contribute directly to the
result of the whole concatenated query
but is only an intermediate step to define the start nodes
of the following Item_version_query.
To switch the semamtics of concatenation between
A) union of single result
B) intermediate step without contribution to the result
but with contribution to the start nodes of the next queries
a flag should be added to the class Query called "Intermediate".
Defer the general solution but solve specific case as in issue 7924. This feature will be realized by an extensions to the query mechanism in PLM Services 2.0
The Computational Model defines many different Types: Service Interfaces Exception Types Generic Query Types PDTnet Query Types Message Types and other. This Types should be separated into different subpackages of the Computational Model PIM and different schemas in the Computational Model WebService PSM.
Restructuring of the specified computational model would have significant impact on the schema but not add any valuable properties to the XML binding. A Java PSM will have a strong relationship (dependency?) to the WebServices PSM and shall not define an independent package structure. Restructuring of the specified computational model would have significant impact on the schema but not add any valuable properties to the XML binding. This issue will be addressed by the PLM Services 2.0 submission.
Add complex type Section_context according to the requirements described in the VDA Recommendations for the Exchange of digital Engineering Change Requests (ECR). Proposed solution: <xs:complexType name="Section_context"> <xs:complexContent> <xs:sequence> <xs:element name="Msg_type" type="xs:string"/> <xs:element name="Dunsnr" type="xs:string"/> <xs:element name="Interactionid" type="xs:string"/> <xs:element name="Newinteractionid" type="xs:string" minOccurs="0"/> <xs:element name="Interactionscenarioname" type="xs:string"/> <xs:element name="Messagename" type="xs:string"/> <xs:element name="Sequenceno" type="xs:integer"/> <xs:element name="Iscomplete" type="xs:boolean"/> </xs:sequence> </xs:complexContent> </xs:complexType>
ECR related use cases are subject to further discussion. Currently, a draft version of spacification for the problems described here is available. Description from VDA 4965-1 (Review Version January 2005), Section 5.3.3 translated into plain English: Data object Description (Type/Format, Example, Meaning) DUNSNR Type: Integer, Format: 9 Digits; Example: 315744388worldwide unique code, recognised as standard for identification of companies (DUNS: Data Universal Numbering System). INTERACTIONID Type: String; Format: DUNSNr "/"ECR_ID.ID; Example "717743322/AEA553421"The INTERACTIONID (and the NewInteractionId) identifies in conjunction with DUNSNR of Coordinator and Participant worldwide unique the association of a message and a interaction dialog, e.g. the . einer in Ausführung befindlichen Interaktionsszenario-Messageabfolgen. Wegen dieser Anforderung zur Eindeutigkeit der Zuordnung auf Seiten des Senders und des Empfängers und wegen der Möglichkeit, diese INTERACTIONID im Verlauf der Interaktion wechseln zu können, sollte sich die INTERACTIONID eindeutig dem Aussteller der INTERACTIONID zuordnen lassen; dieser muss zusätzlich dafür sorgen, dass die INTERACTIONID innerhalb seines Unternehmens eindeutig ist.1. Falls dies die erste Message der Interaktion ist, gilt: Der Sender vergibt eine neue InteractionId.2. Falls dies nicht die erste Message der Interaktion ist, gilt: a) Falls in der vorangehenden Message NEWINTERACTIONID = "" war, gilt: INTERACTIONID muss denselben Wert wie die vorangehende INTERACTIONID aus der letzten Message dieses Interaktionsdialogs enthalten. b) Falls in der vorangehenden Message die NEWINTERACTIONID <> "" war, gilt: INTERACTIONID muss den Wert der NEWINTERACTIONID enthalten. NEWINTERACTIONID Typ/Format/Bsp.: wie INTERACTIONIDEnthält den Wert, der ab der nachfolgenden Message als neue INTERACTIONID zu verwenden ist. Falls gleich "" (leerer String), signalisiert dies, dass die bisherige INTERACTIONID beibehalten wird oder dies die erste Message der Interaktion ist. Falls gleich "": , dann enthält INTERACTIONID die bisher gültige INTERACTIONID, und NEWINTERACTIONID eine neue gültige INTERACTIONID, die eindeutig innerhalb des Requesters/Notifiers eine Interaktion mit einem Partner kennzeichnet. Dieser neue Wert muss in den folgenden Messages dieser Interaktion als INTERACTIONID genannt werden (bis dies ggf. erneut wechselt).Die Möglichkeit, die INTERACTIONID zu wechseln, wird je Interaktionsszenario spezifiziert. INTERACTIONSCENARIONAME Typ: String; Werte: "IS1", "IS2", "IS3", "IS4"Der INTERACTIONSCENARIONAME legt ab der ersten Message fest, gemäß welchem Interaction Scenario der nachfolgende Dialog ablaufen soll. MESSAGENAME Typ: String; Werte: "request_details",…Name der Message, vgl. Abschnitt Error! Reference source not found. SEQUENCENR Typ: Integer; Werte: 1, 2, …Sequenznummer, die angibt, um die wievielte Message eines Senders in diesem IS-Dialog es sich handelt. D. h. SEQUENCENR beginnt bei "1", bezogen auf den durch InteractionId/NewInteractionId identifizierten Dialog auf den durch DUNSNr definierten Sender.SEQUENCENR muss (auch bei Rücksprüngen) erhöht werden, sobald ein Sender eine weitere Message in einem IS-Dialog sendet ISCOMPLETE type: Boolean; values: TRUE, FALSEFALSE marks a Message as preliminary stage, e.g. potentially incomplete, sent for informational purposes only, followed by further intermediate but just one Message indicated as final (compare "Exchange of preliminary stages"). If the object is part of a Request-Message, this Message should not be answered by a Respond-Message; if though, only one or more Respond-Messages with IsComplete = FALSE are allowed. A Respond-Message shall follow a Request-Message with IsComplete = TRUE. Respond-Messages with type preliminary may follow, but shall be concluded by a single mandatory Respond-Message with IsComplete = TRUE. The necessary changes to the specification to capture the functionality described in VDA recommendation is subject ot the extensions of PLM Services 2.0.
There is a discrepancy between the base standard ISO 10303-214 and the OMG PLM Services 1.0 with respect to the multiplicity of relations. While in AP214 of the template “SET [0:?]” is used, in the PLM Services, especially in the XML platform specific model the template “optional SET [1:?]” is used. Although this mapping may be semantically equal, a problem arises with respect to the automatic translation between ISO 10303-21 files and PLM XML files/streams. Proposed solution: consider revising the mapping of cardinalities of type “optional SET [1:?]” in the PLM (XML) Services into “SET [0:?]”.
The resolution will be part of the necessary alignments of PLM Services 2.0 informational model with the AP214 maintenance revision.
The semantics of the specified Alternative_solution_query is to find associated Alternative_solutions for Complex_products. So its name should be changed to Associated_alternative_solution_query.
This problem shall be resolved in future revisions, possibly together with issue 7773. The resolution will be part of the changes in PLM Services 2.0