Issues for Mailing list of the PLM Services Revision Task Force

To comment on any of these issues, send email to plm-rtf@omg.org. (Please include the issue number in the Subject: header, thusly: [Issue ###].) To submit a new issue, send email to issues@omg.org.

List of issues (green=resolved, yellow=pending Board vote, red=unresolved)

List options: All ; Open Issues only; or Closed Issues only

Issue 8940: chapter 8.12 (Generic Queries Conformance Point
Issue 8941: 'activity_resolved_requests_query'
Issue 8942: 'activity_authorization_query'
Issue 9126: Section: 8.14
Issue 9127: Section: 8.14.49
Issue 9128: Section: 8.14
Issue 9129: Section: 8.14.16
Issue 9130: Section: 8.14 p. 360
Issue 9131: Section: 8.14 p. 342
Issue 9132: Section: 8.14 p. 342 (02)
Issue 9133: Section: 8.14 p. 342 (03)
Issue 9134: Section: 8.14.16
Issue 9135: Section: 8.14 p. 342 (04)
Issue 9136: Section: 8.9
Issue 9137: Section: 8.14 p. 342 (05)

Issue 8940: chapter 8.12 (Generic Queries Conformance Point (plm-rtf)

Click here for this issue's archive.
Nature: Enhancement
Severity: Significant
Summary: 
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]

Resolution: 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
Revised Text:
Actions taken:
July 28, 2005: received issue
January 14, 2011: closed issue

Discussion: 
The resolution will be part of the changes in PLM Services 2.0

Issue 8941: 'activity_resolved_requests_query' (plm-rtf)

Click here for this issue's archive.
Nature: Enhancement
Severity: Significant
Summary: 
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.

Resolution: 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
Revised Text:
Actions taken:
July 28, 2005: received issue
January 14, 2011: closed issue

Discussion: 
The resolution will be part of the changes in PLM Services 2.0

Issue 8942: 'activity_authorization_query' (plm-rtf)

Click here for this issue's archive.
Nature: Enhancement
Severity: Significant
Summary: 
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.

Resolution: 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
Revised Text:
Actions taken:
July 28, 2005: received issue
January 14, 2011: closed issue

Discussion: 
The resolution will be part of the changes in PLM Services 2.0.

Issue 9126: Section: 8.14 (plm-rtf)

Click here for this issue's archive.
Nature: Enhancement
Severity: Minor
Summary: 
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>

Resolution: 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
Revised Text:
Actions taken:
November 2, 2005: received issue
January 14, 2011: closed issue

Discussion: 
The resolution will be part of the changes in PLM Services 2.0.

Issue 9127: Section: 8.14.49 (plm-rtf)

Click here for this issue's archive.
Nature: Clarification
Severity: Minor
Summary: 
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>

Resolution: 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
Revised Text:
Actions taken:
November 2, 2005: received issue
January 14, 2011: closed issue

Discussion: 
The resolution will be part of the changes in PLM Services 2.0.

Issue 9128: Section: 8.14 (plm-rtf)

Click here for this issue's archive.
Nature: Enhancement
Severity: Minor
Summary: 
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>

Resolution: 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
Revised Text:
Actions taken:
November 2, 2005: received issue
January 14, 2011: closed issue

Discussion: 
The resolution will be part of the changes in PLM Services 2.0.

Issue 9129: Section: 8.14.16 (plm-rtf)

Click here for this issue's archive.
Nature: Enhancement
Severity: Minor
Summary: 
Associated_file_query currently returns only four of the five document_properties: document_creation_property is missing => should be added in the query definition

Resolution: 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
Revised Text:
Actions taken:
November 2, 2005: received issue
January 14, 2011: closed issue

Discussion: 
The resolution will be part of the changes in PLM Services 2.0.

Issue 9130: Section: 8.14 p. 360 (plm-rtf)

Click here for this issue's archive.
Nature: Enhancement
Severity: Minor
Summary: 
Associated_file_query currently returns only four of the five document_properties: document_creation_property is missing => should be added in the query definition

Resolution: 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
Revised Text:
Actions taken:
November 2, 2005: received issue
January 14, 2011: closed issue

Discussion: 
The resolution will be part of the changes in PLM Services 2.0.

Issue 9131: Section: 8.14 p. 342 (plm-rtf)

Click here for this issue's archive.
Nature: Enhancement
Severity: Minor
Summary: 
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>

Resolution: 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
Revised Text:
Actions taken:
November 2, 2005: received issue
January 14, 2011: closed issue

Discussion: 
The resolution will be part of the changes in PLM Services 2.0.

Issue 9132: Section: 8.14 p. 342 (02) (plm-rtf)

Click here for this issue's archive.
Nature: Enhancement
Severity: Minor
Summary: 
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>

Resolution: 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
Revised Text:
Actions taken:
November 2, 2005: received issue
January 14, 2011: closed issue

Discussion: 
The resolution will be part of the changes in PLM Services 2.0.

Issue 9133: Section: 8.14 p. 342 (03) (plm-rtf)

Click here for this issue's archive.
Nature: Enhancement
Severity: Minor
Summary: 
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>

Resolution: 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
Revised Text:
Actions taken:
November 2, 2005: received issue
January 14, 2011: closed issue

Discussion: 
The resolution will be part of the changes in PLM Services 2.0.

Issue 9134: Section: 8.14.16 (plm-rtf)

Click here for this issue's archive.
Nature: Enhancement
Severity: Minor
Summary: 
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

Resolution: 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
Revised Text:
Actions taken:
November 2, 2005: received issue
January 14, 2011: closed issue

Discussion: 
The resolution will be part of the changes in PLM Services 2.0.

Issue 9135: Section: 8.14 p. 342 (04) (plm-rtf)

Click here for this issue's archive.
Nature: Enhancement
Severity: Minor
Summary: 
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

Resolution: 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
Revised Text:
Actions taken:
November 2, 2005: received issue
January 14, 2011: closed issue

Discussion: 
The resolution will be part of the changes in PLM Services 2.0.

Issue 9136: Section: 8.9 (plm-rtf)

Click here for this issue's archive.
Nature: Enhancement
Severity: Minor
Summary: 
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>

Resolution: 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
Revised Text:
Actions taken:
November 2, 2005: received issue
January 14, 2011: closed issue

Discussion: 
The resolution will be part of the changes in PLM Services 2.0.

Issue 9137: Section: 8.14 p. 342 (05) (plm-rtf)

Click here for this issue's archive.
Nature: Enhancement
Severity: Minor
Summary: 
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>

Resolution: 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
Revised Text:
Actions taken:
November 2, 2005: received issue
January 14, 2011: closed issue

Discussion: 
The resolution will be part of the changes in PLM Services 2.0.