New query Product_identification_query to select product_identification objects. Use case at DaimlerChrysler: select existing product reference configuration by name. <xs:complexType name="Product_identification_query"> <xs:complexContent> <xs:extension base="Query"> <xs:sequence> <xs:element name="Id" type="xs:string" minOccurs="0"/> <xs:element name="Id_scope" type="xs:string" minOccurs="0"/> <xs:element name="Name" type="xs:string" minOccurs="0"/> <xs:element name="Name_language" type="xs:language" minOccurs="0"/> <xs:element name="Version_id" type="xs:string" minOccurs="0"/> <xs:element name="Associated_product_class" type="xs:string" minOccurs="0"/> <xs:element name="Classification_role" type="xs:string" minOccurs="0"/> <xs:element name="Classification_id" type="xs:string" minOccurs="0"/> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType> Dito for the subtype product_specification: product_specification_query with an additional parameter to restrict the selection through one or many specification id's

This is a leftover from the PLM 1.x RTF when it was out of scope. The issue was then addressed by the PLM Services 2.0 Submission.

Revised Text:

• none -

Proposed Disposition: Closed – No Change

The operations get_download_URL and get_upload_URL may not be combined with other operations like Query, Write, Import and Export. They currently support only one file uid. Example: if a complete assembly structure shall be selected via a recursive query, together with the download of all referenced files, it is currently necessary to call get_download_URL as many times as there are files referenced from the assembly structure... Proposal to combine Query and Download through a new parameter in Associated_file_query: <xs:complexType name="Associated_file_query"> <xs:complexContent> <xs:extension base="Query"> <xs:sequence> <xs:element name="download" type="xs:boolean" minOccurs="0"/> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType> If download=TRUE, the corresponding file will be downloaded and the URL will be placed in document_location_property.location_name

This is a leftover from the PLM 1.x RTF when it was out of scope. The issue was then addressed by the PLM Services 2.0 Submission.

Revised Text:

• none -

Proposed Disposition: Closed – No Change

New operation set_product_identification to activate a product configuration. Functionality: the product configuration defined through the given product_identification will be activated, so that the following query operations return only the objects that are provided within this product configuration. In the same way, during write or import operations, the incoming data will be checked according to the activated product configuration, before being written or imported. Input parameter is the uid of a product_identification or product_specification object. Return value is nothing (when OK) or an exception. <wsdl:operation name="set_product_identification"> <soap:operation soapAction="" style="rpc"/> <wsdl:input> <soap:header message="Session_id_header" part="session_id" use="literal"/> <soap:header message="Signature_header" part="signature" use="literal"/> <soap:body use="literal" namespace="http://www.omg.org/PLMServices1.0/PLM_connection#query"/> </wsdl:input> <wsdl:output> <soap:body use="literal" namespace="http://www.omg.org/PLMServices1.0/PLM_connection#query"/> </wsdl:output> <wsdl:fault name="Pid_fault"> <soap:fault name="Pid_fault" use="literal" encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/> </wsdl:fault> </wsdl:operation>

This is a leftover from the PLM 1.x RTF when it was out of scope. The issue was then addressed by the PLM Services 2.0 Submission.

Revised Text:

• none -

Proposed Disposition: Closed – No Change

Neue query Activity_resolved_request_query to traverse from activity objects to work_request objects via the attribute resolved_request. Since this attribute is mandatory but aggregate, it is currently not possible to query all its values if all the referenced work_requests are not part of the query result. <xs:complexType name="Activity_resolved_request_query"> <xs:complexContent> <xs:extension base="Query"/> </xs:complexContent> </xs:complexType>

This is a leftover from the PLM 1.x RTF when it was out of scope. The issue was then addressed by the PLM Services 2.0 Submission.

Revised Text:

• none -

Proposed Disposition: Closed – No Change

New Query Event_reference_context_offset_query to traverse from event_reference objects to general_organizational_data_select objects via the attribute event_context, as well as to duration objects via the attribute offset. Since these attributes are optional, then can currently not be traversed. <xs:complexType name="Event_reference_context_offset_query"> <xs:complexContent> <xs:extension base="Query"/> </xs:complexContent> </xs:complexType>

This is a leftover from the PLM 1.x RTF when it was out of scope. The issue was then addressed by the PLM Services 2.0 Submission.

Revised Text:

• none -

Proposed Disposition: Closed – No Change

New Query Effectivity_start_end_period_definition_query to traverse from effectivity objects to event_or_date_select objects via the attributes start_definition and end_definition, as well as to duration objects via the attribute period. Both aspects are mutually exclusive, i.e. an effectivity has either start/end_definition or a period. Since these attributes are optional, then can currently not be traversed. <xs:complexType name="Effectivity_start_end_period_definition_query"> <xs:complexContent> <xs:extension base="Query"/> </xs:complexContent> </xs:complexType> <xs:complexType name="Effectivity_assignment_query"> <xs:complexContent> <xs:extension base="Query"> <xs:sequence> <xs:element name="Role" type="xs:string" minOccurs="0"/> <xs:element name="Effectivity_indication" type="xs:boolean" minOccurs="0"/> <xs:element name="Element_type_name" type="xs:string" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType>

This is a leftover from the PLM 1.x RTF when it was out of scope. The issue was then addressed by the PLM Services 2.0 Submission.

Revised Text:

• none -

Proposed Disposition: Closed – No Change

New Query Effectivity_assignment_query to traverse from effectivity_element_select objects via effectivity_assignment objects to effectivity objects: <xs:complexType name="Effectivity_assignment_query"> <xs:complexContent> <xs:extension base="Query"> <xs:sequence> <xs:element name="Role" type="xs:string" minOccurs="0"/> <xs:element name="Effectivity_indication" type="xs:boolean" minOccurs="0"/> <xs:element name="Element_type_name" type="xs:string" minOccurs="0" maxOccurs="unbounded"/> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType>

This is a leftover from the PLM 1.x RTF when it was out of scope. The issue was then addressed by the PLM Services 2.0 Submission.

Revised Text:

• none -

Proposed Disposition: Closed – No Change

Associated_file_query currently returns only four of the five document_properties: document_creation_property is missing => should be added in the query definition

This is a leftover from the PLM 1.x RTF when it was out of scope. The issue was then addressed by the PLM Services 2.0 Submission.

Revised Text:

• none -

Proposed Disposition: Closed – No Change

New Query 'Activity_authorization_query' to traverse from activity objects zo work_order objects via the attribute 'authorization'. Since this attribute is optional an INVERSE, it is currently not possible to traverse it. <xs:complexType name="Activity_authorization_query"> <xs:complexContent> <xs:extension base="Query"/> </xs:complexContent> </xs:complexType>

This is a leftover from the PLM 1.x RTF when it was out of scope. The issue was then addressed by the PLM Services 2.0 Submission.

Revised Text:

• none -

Proposed Disposition: Closed – No Change

New parameter 'Id_scope' in Work_request_query, like currently in all queries that have an Id parameter defined unique only within the scope of an organization: <xs:complexType name="Work_request_query"> <xs:complexContent> <xs:extension base="Query"> <xs:sequence> ... <xs:element name="Id_scope" type="xs:string" minOccurs="0"/> ... </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType>

This is a leftover from the PLM 1.x RTF when it was out of scope. The issue was then addressed by the PLM Services 2.0 Submission.

Revised Text:

• none -

Proposed Disposition: Closed – No Change

Introduction of a new 'specific Query' 'work_order_query' to select work_order objects, as needed by Change Management Scenarios: <xs:complexType name="Work_order_query"> <xs:complexContent> <xs:extension base="Query"> <xs:sequence> <xs:element name="Id" type="xs:string" minOccurs="0"/> <xs:element name="Id_scope" type="xs:string" minOccurs="0"/> <xs:element name="Work_order_type" type="xs:string" minOccurs="0"/> <xs:element name="Version_id" type="xs:string" minOccurs="0"/> <xs:element name="Classification_role" type="xs:string" minOccurs="0"/> <xs:element name="Classification_id" type="xs:string" minOccurs="0"/> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType>

This is a leftover from the PLM 1.x RTF when it was out of scope. The issue was then addressed by the PLM Services 2.0 Submission.

Revised Text:

• none -

Proposed Disposition: Closed – No Change

Associated_file_query currently returns only four of the five document_properties: document_creation_property is missing => should be added in the query definition

This is a leftover from the PLM 1.x RTF when it was out of scope. The issue was then addressed by the PLM Services 2.0 Submission.

Revised Text:

• none -

Proposed Disposition: Closed – No Change

some numbering mismatch in chapter 7.7 7.7.11.1 shall be not Classes but Class Address 7.7.10.1 shall be not Classes but Class Alias_identification 7.7.9.1 shall be not Classes but Class Cost_property 7.7.8.1 shall be not Classes but Class Classification_association 7.7.7 shall be 7.7.6.24, subsection heading Heading4 become subsection 7.7.6.1 shall be not Classes but Class Accuracy 7.7.5.1 shall be not Classes but Class Digital_document 7.7.4 shall be deleted 7.7.2.1 shall be not Classes but Class Application_context 7.7.1.1 shall be not Classes but Class PLM_container

No Data Available

First sentence in Chapter 7.4.3.1: "An instance of type Document...", not "...Item..."

No Data Available

Person_in_organization_relationship is element of AP but not of PLM Services 1.0. Use explanatory text as in AP214

No Data Available

figures missing: Figure 2-18 Property Figure 2-19 Property value Figure 2-20 Simple property Figure 2-21 Material property Figure 2-22 Alias identification Figure 2-23 Authorization - Person and organization Figure 2-24 Authorization - Approval Figure 2-25 Authorization - Date and time

No Data Available

Align simple property assignment mechanism with STEP AP214 maintenance version. Use the following STEP EXPRESS constructs: – new in AP214 ENTITY simple_property_association; described_element : simple_property_select; specified_value : property_value; value_type : STRING; END_ENTITY; – already in AP214 ENTITY string_value SUBTYPE OF (property_value); value_specification : string_select; END_ENTITY; TYPE simple_property_select = SELECT ( item_property_select, process_property_select ); END_TYPE;

No Data Available

Date and Time types shall be mapped according to ISO 8601. Where possible, built-in types shall be used: XML model: * xs:date for date_time.date * xs:time for date_time.time

No Data Available

Definition of project is wrong with respect to project.affected_product_class attribute. But the maintenance version of STEP AP214 proposes the split into project and project_assignment with structure corresponding to the following STEP model: ENTITY project; id : STRING; name : string_select; description : OPTIONAL string_select; actual_start_date : OPTIONAL date_time; actual_end_date : OPTIONAL date_time; planned_start_date : OPTIONAL event_or_date_select; work_program : SET [0:?] OF activity; planned_end_date : OPTIONAL period_or_date_select; END_ENTITY; ENITY project_assignment; assigned_project : project; role : STRING; is_applied_to : SET [1:?] OF project_information_select; END_ENTITY;

No Data Available

Organization_relationhip is element of AP214 but not of PLM Services 1.0 This element describes relationships between organizations and ist hierarchical compounds like departments. This organizational hierarchy shall be described in PLM services. Use explanatory text as in AP214

No Data Available

Work_request and Work_order are Root_objects and are usually result of Start_Node_query. It would be much better to support specialized Work_request_query and Work_order_query for this purpose in the PDTnet queries conformance point and in the Web services specification.

No Data Available

New element type required: Work_request_relationship models relations of Work_request in analogy to Activity_request_relationship with relating as containment relationship in XML and related as IDREF to work_request Motivation: For development partners different work_request numbering schemes are in effect which shall be modelled. STEP EXPRESS model for the new element: ENTITY work_request_relationship; related : work_request; relating : work_request; relation_type : STRING; description : OPTIONAL string_select; END_ENTITY

No Data Available

Clarify "Signature" attribute of PLM_session_context type

No Data Available

Examples (incl. SOAP responses) for object_factory, get_connection, close, write, delete, export_data, import_data and exceptions structures shall be appended

No Data Available

The "predicates" data type shall be clarified and described in more detail in section 8.9.

No Data Available

The predicates data type shall be clarified and described in more detail.

No Data Available

Rename insert-Operation into import_data, which reflects better the semantics of the insert operation as described in section 8.7.3. Consequently, rename export-Operation into export_data for consistency.

No Data Available

PLM_message[0..*] type as defined with the write-Operation in section 8.7.1 shall be further detailed to capture more specific information for all methods in PLM_connection interface. Potentially, more subtypes are required to signal error situations. Therefore, this type shall be defined in a separate section.

No Data Available

Delete-Operation, as described for the PLM_connection interface in section 8.8.4 shall return an error message, potentially a PLM_message[0..*] type.

No Data Available