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

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 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

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 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

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

In document mantis/dtc/05-03-08 from the PLM Services 1.0 specification, chapter 8.12 (Generic Queries Conformance Point), a new query 'activity_authorization_query' should be included to enable the traversal from activity objects to the work_order objects which are the authorization of the activity objects, having none parameters.

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

In document mantis/dtc/05-03-08 from the PLM Services 1.0 specification, chapter 8.12 (Generic Queries Conformance Point), a new query 'activity_resolved_requests_query' should be included to enable the traversal from activity objects to the work_request objects which are the resolved request of the activity objects, having none parameters.

This issue is a leftover from the PLM 1.x RTF, when the requested change was out of scope for an RTF. The issue was then forwarded to, and addressed by the PLM Services 2.0 submission team.

Revised Text:

• none -

Proposed Disposition: Closed – No Change

In document mantis/dtc/05-03-08 from the PLM Services 1.0 specification, chapter 8.12 (Generic Queries Conformance Point), a new query 'work_order_query' should be included to enable the selection of work_order objects, having following parameters: id: String [0..1] work_order_type [0..1]

This issue is a leftover from the PLM 1.x RTF, when the requested change was out of scope for an RTF. The issue was then forwarded to, and addressed by the PLM Services 2.0 submission team.

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

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

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

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

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

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

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

To define the semantics of the queries of the new high level
queries conformance point (issue 7828) we need a new query
to ask for placement information of Assembly_component_relationship objects.

<xs:complexType name="Assembly_component_placement_query">
<xs:complexContent>
<xs:extension base="Query"/>
</xs:complexContent>
</xs:complexType>

No Data Available

Section 8.9 should be a subsection of 8.8
Change 8.9 to 8.8.1
This automaticly changes old subsections of 8.9 to new subsections of 8.8.

No Data Available

The enumerations of the start and destination types in the
specification of the queries of the PDTnet queries conformance point
should be replaced by grouping interfaces of those types.

No Data Available

The specific conformance Point should define queries for resolving Alias_identifications.
Some of these queries are already defined,
for instance Item_query, Item_version_query, Design_discipline_item_definition_query.
But some queries are missing,
for instance Item_instance_query, Specification_query, Product_class_query.

No Data Available

Optional attributes should be defined by a multiplicity of [0..1] instead of the label <<optional>>.

No Data Available

To define the semantics of the queries in the new high level
conformance point suggested in issue 7828 we need a new
construct for queries, which execution depends
on some conditions. Such condition could be:

• if a boolean value is true
• if a boolean value is not true
• if a value is set
• if a value is not set

<xs:complexType name="Conditional_query">
<xs:complexContent>
<xs:extension base="Query">
<xs:sequence>
<xs:element name="Attribute_is_true" type="xs:boolean" minOccurs="0"/>
<xs:element name="Attribute_is_not_true" type="xs:boolean" minOccurs="0"/>
<xs:element name="Attribute_is_set" type="xs:string" minOccurs="0"/>
<xs:element name="Attribute_is_not_set" type="xs:string" minOccurs="0"/>
<xs:element name="Query" type="Query"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>

No Data Available

The attribute identifier_name in class Identifier_predicate is redundant.
The predicate is only relevant for PLM_objects which have an Alias_identification.
If the PLM_object is an instance of Document the name of the identifier attribute is "document_id".
If the PLM_object is an instance of Physical_instance the name of the identifier attribute is "lot_id".
If the PLM_object is an instance of Document_type_property the name of the identifier attribute is "document_type_name".
If the PLM_object is an instance of Approval_status the name of the identifier attribute is "status_name".
In all other cases the name of the identifier attribute is "id".

No Data Available

It would be a good generalization of the new Relationship_queries
suggested in the issues #8000, #8004, #8006 and #8009,
to introduce an common base class for the relationship queries
with the attributes relation_type and inverse.
If the boolean attribute inverse is set to TRUE, the derived
Relationship has to be traversed in inverse direction
with respect to the default direction defined in the informational model.

No Data Available

Add missing query Work_request_relationship_query in order to allow searching for specific Work_request objects related by a Work_request_relationship object starting at an given work_request object Proposed solution: <xs:complexType name="Work_request_relationship_query"> <xs:complexContent> <xs:extension base="Query"> <xs:sequence> <xs:element name="Relation_type" type="xs:string" minOccurs="0"/> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType>

No Data Available

Add missing Associated_person_organization_query in order to allow searching for organizational objects (person, organization, person_in_organization) that are assigned to a given object, or to allow searching for objects that are referenced by a given organizational object (person, organization, person_in_organization). Proposed solution: <xs:complexType name="Associated_person_organization_query"> <xs:complexContent> <xs:extension base="Query_with_relating_type_predicate"> <xs:sequence> <xs:element name="Role" type="xs:string" minOccurs="0"/> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType>

No Data Available

Add missing Associated_date_organization_query in order to allow searching for organizational objects (date_time comined with person, organization, person_in_organization) that are assigned to a given object, or to allow searching for objects that are referenced by a given organizational object (date, person, organization, person_in_organization). Proposed solution: <xs:complexType name="Associated_date_organization_query"> <xs:complexContent> <xs:extension base="Query_with_relating_type_predicate"> <xs:sequence> <xs:element name="Role" type="xs:string" minOccurs="0"/> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType>

No Data Available

In chapter 8.12.11 (Associated_property_query), as well as Chapter 8.12.34 (Simple_property_query), the attribute unit_component of value_with_unit should be retrieved automatically (although it is an optional attribute), since it makes more sense than to introduce a new Query to retrieve it. The same applies to property_value_representation.global_unit in Associated_property_query.

No Data Available

Add missing query Project_assignment_query in order to allow searching for objects assigned to a given project object, or to allow searching for the project objects that are assigned to a given object. Proposed solution: <xs:complexType name="Project_assignment_query"> <xs:complexContent> <xs:extension base="Query_with_relating_type_predicate "> <xs:sequence> <xs:element name="Role" type="xs:string" minOccurs="0"/> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType>

No Data Available

Add complex type Person_in_organization_relationship according to STEP AP214 IS version. Proposed solution: <xs:complexType name="Person_in_organization_relationship"> <xs:complexContent> <xs:extension base="PLM_object"> <xs:sequence> <xs:element name="Related" type="xs:IDREF"/> <xs:element name="Relation_type" type="xs:string"/> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType>

No Data Available

The predicates of a location step filter the related objects only.
To define the semantic of the attribute "relating_type_names"
of the associatedXyzQueries we need the possibility to filter
the relating objects (the start nodes of a location step) too.

This could be done by an additional feature for the types
"Location_step" and "Relationship_predicate" of type "Predicate"
named "relating_object_predicate".
For consistency the existing feature "Predicate" of these types
should be renamed in "related_object_predicate"

No Data Available

Add missing Associated_activity_query in order to allow searching for activity objects that are associated to a specific work_request object. Proposed solution: <xs:complexType name="Associated_activity_query"> <xs:complexContent> <xs:extension base="Query"> <xs:sequence> <xs:element name="Activity_type" type="xs:string" minOccurs="0"/> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType>

No Data Available

Add missing query Activity_relationship_query in order to allow searching for specific activity objects related by an Activity_relationship object starting at an given activity object. Proposed solution: <xs:complexType name="Activity_relationship_query"> <xs:complexContent> <xs:extension base="Query"> <xs:sequence> <xs:element name="Relation_type" type="xs:string" minOccurs="0"/> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType>

No Data Available

Add missing query Activity_element_query in order to allow searching for specific activity element objects. Proposed solution: <xs:complexType name="Activity_element_query"> <xs:complexContent> <xs:extension base="Query_with_relating_type_predicate"> <xs:sequence> <xs:element name="Role" type="xs:string" minOccurs="0"/> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType>

No Data Available

The Timeout_exception should be separated into two different Exceptions:

1) a Session_timeout_exception as extension of the Invalid_session_id_exception
2) a Object_uid_timeout_exception as extension of the Invalid_object_uid_exception

No Data Available

All specified queries should be evaluated for the use of
the Attribute_pattern_predicate and the Attribute_predicates
eventually relaced or extended by Attribute_pattern_predicates.
Because pattern could be very complex, an Pattern_not_supported_exception
should be defined, which can be thrown by operations query and export.

No Data Available

To avoid errors caused by the use of different wsdl versions on the
client side and the server side, a required property "PLM_services_version_id"
should be used in operations get_connection_factory and get_connection.

No Data Available

Add missing query Work_request_classification_query in order to allow searching for specific general_classification objects that are associated to a specific Work_request object. Proposed solution: <xs:complexType name="Work_request_classification_query"> <xs:complexContent> <xs:extension base="Query"> <xs:sequence> <xs:element name="Role" type="xs:string" minOccurs="0"/> <xs:element name="Id" type="xs:string" minOccurs="0"/> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType>

No Data Available

Add missing Work_request_query in order to allow searching for specific work_request objects. Proposed solution: <xs:complexType name="Work_request_query"> <xs:complexContent> <xs:extension base="Query"> <xs:sequence> <xs:element name="Id" type="xs:string" minOccurs="0"/> <xs:element name="Request_type" type="xs:string" minOccurs="0"/> <xs:element name="Status" 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>

No Data Available

Add missing Organization_relationship_query in order to allow searching for specific organization objects related by an organization_relationship object starting at an given organization object. Proposed solution: <xs:complexType name="Organization_relationship_query"> <xs:complexContent> <xs:extension base="Query"> <xs:sequence> <xs:element name="Relation_type" type="xs:string" minOccurs="0"/> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType>

No Data Available

Add missing query Person_in_organization_relationship_query in order to allow searching for specific Person_in_organization objects related yo an Person_in_organization_relationship object starting at an given Person_in_organization object. Proposed solution: <xs:complexType name="Person_in_organization_relationship_query"> <xs:complexContent> <xs:extension base="Query"> <xs:sequence> <xs:element name="Relation_type" type="xs:string" minOccurs="0"/> </xs:sequence> </xs:extension> </xs:complexContent> </xs:complexType>

No Data Available

Add missing query Work_request_scope_query in order to allow searching for specific elements of the scope of an given Work_request object. Proposed solution: <xs:complexType name="Work_request_scope_query"> <xs:complexContent> <xs:extension base="Query"/> </xs:complexContent> </xs:complexType>

No Data Available

If the session id used in a request to a PLM_connection is invalid,
and the cause for the invalidity is not a session timeout,
an Invalid_session_id_exception should be thrown.

No Data Available

The english translation for the german word "Authentifizierung"
is "Authentication".

No Data Available

One can concatenate Queries via the next_query Relationship
to a bigger batch job.
But the concatenation implies, that the second query uses
the result of the first query as its start node set.

There should be the possibility to define a batch job of independent queries.
For instance:
<xs:complexType name="Batch_query">
<xs:complexContent>
<xs:extension base="Query">
<xs:sequence>
<xs:element name="Query" type="Query" maxOccurs="unbounded"/>
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
All element queries of the Batch_query will de evaluated independly and the partial results
will be joined and returnd as one single result.

No Data Available

We need a special exception type for unsupported operations,
for instance in an ReadOnly PLMConnector all modifying
operations (PLMConnection.write, PLMConnection.delete, ..)
have to throw an Unsupported_operation_exception.

No Data Available

In chapter 8.12.10 (Associated_organization_query), chapter 8.12.31 (Organization_query), as well as in the newly introduced Associated_date_organization_query, Associated_person_organization_query and Organization_relationship_query the attributes postal_address, delivery_address and visitor_address of organization should be retrieved automatically (although they are optional attribute), since it makes more sense than to introduce a new Query to retrieve them. The same applies to preferred_business_address of person in Associated_date_organization_query and Associated_person_organization_query.

No Data Available

The description of use of type PLM_container in section 8.6 of the computational model
should be more precise.

No Data Available

The Semantic of the attribute "version_id" of the class "PLM_container"
is not specified.
The value of this attribute should represent the version of the PLMServices
specification and should be fixed to the value "1.0" for the PLMService
version 1.0.

No Data Available

in document mantis/04-04-05 from the PLM Services 1.0 specification, chapter 8.9 (Query Type), the behavior a next_query concerning the exact scope of elements applying to it should be precised, for example as following: 'ALL objects which were used as start nodes for the predecessor query, plus ALL the objects selected by the predecessor query, including those objects enclosed through the multiplicity conditions (in the sense of Issue #7883), build the start nodes set for the Next_query.' Because of performance reasons, it should however be possible to restrict this start nodes set to some object types. For example a design_discipline_item_definition_query returns instances of item, item_version and ddid. Each of these objects may be referenced by a person_organization_assignment. A Next_query Associated_organization_query would return the person_organization_assignments of all organizations associated to the item(s), the item_version(s) as well as the ddid(s) => it should be possible to restrict the scope to the item_version(s), for example. An alternative would be to restrict implicitly the scope by replacing the above statement by: 'Only the objects selected by the predecessor query (not the ones which were used as start nodes for the predecessor query, nor the objects enclosed through the multiplicity conditions (in the sense of Issue #7883)), build the start nodes set for the Next_query.' In this case, the Associated_organization_query would be mentioned (if wished) explicitly in each predecessor query. Regards,

No Data Available

in document mantis/04-04-05 from the PLM Services 1.0 specification, Chapter 8.9 (Query Type), it should be mentioned that: . a <Next_query>-Query which returns objects which reference the object(s) of the query(ies) above (i.e. which are not embedded in the object(s) of the query(ies) above) shall fill all these reference attributes with the uid of these objects. . if such a reference attribute hat maxOccurs > 1, the list contains only the uids of the referenced object(s) of the query(ies) above, even if the underlying system contains references to further objects. . Reference attributes with minOccurs=1 shall be set to /nil if they are not filled by the query. . In case of 'intermediate=true', the whole query result contains only the result of the underlying queries but not of the embedding query.

No Data Available

in document mantis/04-04-05 from the PLM Services 1.0 specification, chapter 8.10 (Generic Queries Conformance Point), a new kind of predicate is needed to apply attribute comparison with the operators '<' (less than) or '>' (greater than). For example to select objects having date > '2004-12-12' and < '2004-12-18'. Currently, only '=' is supported. Regards,

No Data Available

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_organization

Associations
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

No Data Available

The URIs of the targetNamespaces of the PLMServices.wsdl,
PLMInformationalModel.xsd and PLMComputationalModel.xsd
should be URLs from which the documents are downloadable.

No Data Available

the namespace of the soap body of the write operation should be changed
to "http://omg.org/PLMServices1-0/PLM_connection#write"

No Data Available

New PLM_messages "Additional_object_written_message" and "Additional_object_deleted_message"

The operation write should return messages of new type Additional_object_written_message
for all PLM_objects which are written to the Server database inside the write operation
but are not in the write parameter of type PLM_container.

The operation delete should return messages of new type Additional_object_deleted_message
for all PLM_objects which are deleted as dependend objects from the PLM server database
inside the delete operation but are not inside the delete parameter list.

No Data Available

All Queries that can traverse Relationships from objects with different types
should have an optional Attribute 'Relating_type_names'
which restricts the start nodes of those queries to the given types.

No Data Available

For better selection possibilities
the Alias_identification_query should be extended with optional Attributes
Alias_id, Alias_version_id and Alias_scope.

No Data Available

Rename Approval_query to Associated_approval_query
For the consistency of query names in the computational model
the Approval_query should be renamed to Associated_approval_query.

No Data Available

A better expression for the Object_not_exist_exception
in the english language would be Unknown_object_uid_exception.

No Data Available

For a better matching of name and semantic
the Item_relationship_query should be renamed to Item_version_relationship_query.

No Data Available

For each Type used as Parameters, Return values or Exceptions in the WSDL
one Root Elements should be defined in the XML Schemas used by the WSDL.
No other type should be used in a root element definition.

No Data Available

The Generic Queries Conformance Point should be extended by
Predicates for negation of the boolean value of another Predicate
and an Attribute_predicate for pattern based filtering

No Data Available

The Item_query and the Document_query
should be extended by optional attributes Version_id and Classification_name.

No Data Available

in document mantis/04-04-05 from the PLM Services 1.0 specification, chapter 8.12.4 (Approval Query), some objects are missing in the list of objects on which an approval query may be applied (according to AP214 ARM): activity_method_assignment physical_instance_test_result activity activity_element work_order, project, work_request, general_classification, classification_association, classification_system Conversely, 'item' should be excluded from this list, since does not comply to AP214 ARM

No Data Available

The Computational Viewpoint defines four Operations with parameter of type PLM_property:

PLM_resource_adapter.get_connection_factory
PLM_connection_factory.get_connection
PLM_connection.insert
PLM_connection.export

The allowed values for the propeties are implementation specific.
To enable an interactive client to provide its user
with the actual allowed or expected property values of a connected PLM Service implementation
The service should have complementary operations for each operation with properties parameter,
which returns descriptors for the actual allowed or expected property value:

PLM_resource_adapter.get_connection_factory_property_descriptors
PLM_connection_factory.get_connection_property_descriptors
PLM_connection.insert_property_descriptors
PLM_connection.export_property_descriptors

The descriptor for a single Property should contain:

the name of the property
the type of the property
the description of the property
an optional pattern to proove user input
and a flag if the property is required

With a PLM_resource_adapter.get_connection_factory_property_descriptors operation
there is no more need for the PLM_resource_adapter.get_connection_factory_names.

No Data Available

The Queries defined in the PDTnet Queries Conformance Point
do not match the Use Cases defined in Chapter 2.2 but are only
specific Queries which can be used as building blocks to define
Queries that fulfill the requirements of the Use Cases.

So this Conformance Point should be renamed in
"Specific Queries Conformance Point" and a new Conformance Point
should be added to the Specification which define the Queries,
which fulfill exactly the requirements of the use cases.

No Data Available

The SOAP Header Elements of ComplexType Session_context
should be separated in a set of single SOAP Header elements
of SimpleType string, because it is difficult to handle SOAP Header
elements of ComplexType with current WebService-Frameworks like AXIS

No Data Available

It should be allowed for the Implementation of the operation 'write' of the interface 'PLM_connection' not only to change the attribute 'uid' of a new PLM_object but also to change the attributes 'Id', 'Document_id', and/or 'File_id'.

No Data Available

To avoid a naming conflict in the Java Binding
with java.lang.Throwable.getCause()
the name of the element "Cause" in PLM_exception
should be changed to "Linked_exception"

No Data Available

The PLMServices WSDL File contains a large xs:schema element.
For better convenience move this element from "PLMServices.wsdl"
to a separate File "PLMComputationalModel.xsd"
and reference this file by an "xs:import" element from the wsdl.

No Data Available

The STEP AP214 Standardization Group has changed its
simple property concept from Simple_property_value to
Simple_property_association. To close the gap to the STEP
specification the PLM Services should also use the
final STEP simple property concept:

Old:
<xs:complexType name="Simple_property_value" abstract="true">
<xs:complexContent>
<xs:extension base="PLM_object">
<xs:sequence>
<xs:element name="Value_name" type="xs:string" />
<xs:element name="Value_type" type="xs:string" />
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
<xs:complexType name="Simple_string_value">
<xs:complexContent>
<xs:extension base="Simple_property_value">
<xs:sequence>
<xs:element name="Value_specification" type="Translatable_string" />
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>
New:
<xs:complexType name="Simple_property_association">
<xs:complexContent>
<xs:extension base="PLM_object">
<xs:sequence>
<xs:element name="Specified_value" type="xs:IDREF" />
<xs:element name="Value_type" type="xs:string" />
</xs:sequence>
</xs:extension>
</xs:complexContent>
</xs:complexType>

Replace all occurrences of
<xs:element name="Simple_property_value" type="Simple_property_value" minOccurs="0" maxOccurs="unbounded" />
With
<xs:element name="Simple_property_association" type="Simple_property_association" minOccurs="0" maxOccurs="unbounded" />

No Data Available

The Datatype "Integer" of the PIM should be mapped to "xs:int" instead of "xs:integer"
in the WebService PSM
because the JAX-RPC Mapping of "xs:integer" is "java.lang.BigInteger"
and the JAX-RPC Mapping of "xs:int" is "int".

No Data Available

The complexTypes 'Item_version' and 'Document_version' should have an attribute 'xs:nillable' with value 'true' to allow dummy Item_versions in the results of Item_Queries and dummy Document_versions in the results of Document_queries.

No Data Available

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.

No Data Available

I'll would also like to point to section 7.7.12.39 which I think is a typo. It think that it should be the associations subsection of 7.7.12.38 that talks about Specification_inclusion

No Data Available

In several places in the model, there are classes that have both realization and association relationships with interfaces. An example is the Specification_expression class that holds association and realization relationships with the Specification_operand_select interface. The PLM Adopted Specification (OMG document dtc/04-05-05) in its section 7.7.12 describes the PLM Configuration Management Package. In it, figure 104 illustrates the association relationship between the Specification_expression and the Specification_operand_select. Later in section 7.7.12.42 the interface Specification_operand_select is defined as: " This empty interface is defined to provide a placeholder for the following classes: Specification_expression and Specification"

The realization relationhsip between a class and an interface is perfectly clear to me. It is the association relationships that "provides a placeholder" that I cannot understand. Does it mean that such a placeholder is an instance of an element that implements the interface?

No Data Available

The targetNamespace of the xs:schema element in the wsdl:types section of the PLM Services WSDL document schould have a different value as the targetNamespace of the root element of the WSDL. (Both targetNamespace values are "http://www.omg.org/PLMServices1.0/Services")

No Data Available

in document mantis/04-04-05 from the PLM Services 1.0 specification is a typo in line 299: <xs:element name="Effectifity_context" type="xs:string" minOccurs="0"/> The element name should be "Effectivity_context".

No Data Available