${taskforce.name} Avatar
  1. OMG Task Force

PLM Services FTF — All Issues

  • Key: PLM
  • Issues Count: 103
Open Closed All
All Issues

Issues Summary

Key Issue Reported Fixed Disposition Status
PLM-101 Section: 8.14 p. 342 (04) PLM 1.0 PLM 1.0.1 Resolved closed
PLM-100 Section: 8.14.16 PLM 1.0 PLM 1.0.1 Resolved closed
PLM-102 Section: 8.9 PLM 1.0 PLM 1.0.1 Resolved closed
PLM-103 Section: 8.14 p. 342 (05) PLM 1.0 PLM 1.0.1 Resolved closed
PLM-99 Section: 8.14 p. 342 (03) PLM 1.0 PLM 1.0.1 Resolved closed
PLM-98 Section: 8.14 p. 342 (02) PLM 1.0 PLM 1.0.1 Resolved closed
PLM-97 Section: 8.14 p. 342 PLM 1.0 PLM 1.0.1 Resolved closed
PLM-96 Section: 8.14 p. 360 PLM 1.0 PLM 1.0.1 Resolved closed
PLM-94 Section: 8.14 PLM 1.0 PLM 1.0.1 Resolved closed
PLM-93 Section: 8.14.49 PLM 1.0 PLM 1.0.1 Resolved closed
PLM-92 Section: 8.14 PLM 1.0 PLM 1.0.1 Resolved closed
PLM-95 Section: 8.14.16 PLM 1.0 PLM 1.0.1 Resolved closed
PLM-91 'activity_authorization_query' PLM 1.0b1 PLM 1.0 Resolved closed
PLM-90 'activity_resolved_requests_query' PLM 1.0b1 PLM 1.0 Resolved closed
PLM-89 chapter 8.12 (Generic Queries Conformance Point PLM 1.0b1 PLM 1.0 Resolved closed
PLM-87 some numbering mismatch in chapter 7.7 7.7.11.1 PLM 1.0 PLM 1.0.1 Resolved closed
PLM-88 First sentence in Chapter 7.4.3.1 PLM 1.0 PLM 1.0.1 Resolved closed
PLM-84 Person_in_organization_relationship PLM 1.0 PLM 1.0.1 Resolved closed
PLM-86 figures missing PLM 1.0 PLM 1.0.1 Resolved closed
PLM-85 Align simple property assignment mechanism with STEP AP214 maint. version PLM 1.0 PLM 1.0.1 Resolved closed
PLM-83 Date and Time types shall be mapped according to ISO 8601. PLM 1.0 PLM 1.0.1 Resolved closed
PLM-82 Definition of project PLM 1.0 PLM 1.0.1 Resolved closed
PLM-81 Organization_relationhip PLM 1.0 PLM 1.0.1 Resolved closed
PLM-80 Work_request and Work_order are Root_objects PLM 1.0 PLM 1.0.1 Resolved closed
PLM-79 New element type required PLM 1.0 PLM 1.0.1 Resolved closed
PLM-78 Clarify "Signature" attribute of PLM_session_context type PLM 1.0 PLM 1.0.1 Resolved closed
PLM-77 append examples PLM 1.0 PLM 1.0.1 Resolved closed
PLM-76 "predicates" data type PLM 1.0 PLM 1.0.1 Resolved closed
PLM-75 The predicates data type shall be clarified and described in more detail. PLM 1.0 PLM 1.0.1 Resolved closed
PLM-74 Rename insert-Operation into import_data PLM 1.0 PLM 1.0.1 Resolved closed
PLM-73 PLM_message[0..*] type PLM 1.0 PLM 1.0.1 Resolved closed
PLM-72 Delete-Operation PLM 1.0 PLM 1.0.1 Resolved closed
PLM-71 New Query for Assembly component placement PLM 1.0b1 PLM 1.0 Resolved closed
PLM-68 Enumerations of query start and target types PLM 1.0b1 PLM 1.0 Resolved closed
PLM-67 New Queries to resolve aliases. PLM 1.0b1 PLM 1.0 Resolved closed
PLM-70 New Query type Conditional_query PLM 1.0b1 PLM 1.0 Resolved closed
PLM-69 Some numbering mismatch in section 8.9 PLM 1.0b1 PLM 1.0 Resolved closed
PLM-66 Labeling of optional attributes PLM 1.0b1 PLM 1.0 Resolved closed
PLM-64 New Abstract Base Class for Relationship_queries PLM 1.0b1 PLM 1.0 Resolved closed
PLM-65 Redundant attribute identifier_name in Identifier_predicate PLM 1.0b1 PLM 1.0 Resolved closed
PLM-63 Add missing query Work_request_relationship_query PLM 1.0b1 PLM 1.0 Resolved closed
PLM-58 Section: 8.12.11 PLM 1.0b1 PLM 1.0 Resolved closed
PLM-57 Add missing query Project_assignment_query PLM 1.0b1 PLM 1.0 Resolved closed
PLM-62 Description of use of type PLM_container PLM 1.0b1 PLM 1.0 Resolved closed
PLM-61 Batch Queries PLM 1.0b1 PLM 1.0 Resolved closed
PLM-54 Add missing query Work_request_classification_query PLM 1.0b1 PLM 1.0 Resolved closed
PLM-53 Add missing Work_request_query PLM 1.0b1 PLM 1.0 Resolved closed
PLM-60 Special Exception for unsupported operations PLM 1.0b1 PLM 1.0 Resolved closed
PLM-59 Section: 8.12.10 PLM 1.0b1 PLM 1.0 Resolved closed
PLM-56 Add missing query Person_in_organization_relationship_query PLM 1.0b1 PLM 1.0 Resolved closed
PLM-55 Add missing query Work_request_scope_ PLM 1.0b1 PLM 1.0 Resolved closed
PLM-50 Add missing Associated_date_organization_query PLM 1.0b1 PLM 1.0 Resolved closed
PLM-49 Add missing Associated_activity_query PLM 1.0b1 PLM 1.0 Resolved closed
PLM-46 Add complex type Person_in_organization_relationship PLM 1.0b1 PLM 1.0 Resolved closed
PLM-45 Predicates for relating objects PLM 1.0b1 PLM 1.0 Resolved closed
PLM-38 Rename Item_relationship_query to Item_version_relationship_query PLM 1.0b1 PLM 1.0 Resolved closed
PLM-37 Attributes of the Alias_identification_query PLM 1.0b1 PLM 1.0 Resolved closed
PLM-36 Rename Approval_query to Associated_approval_query PLM 1.0b1 PLM 1.0 Resolved closed
PLM-35 Root Elements of XML Schemas PLM 1.0b1 PLM 1.0 Resolved closed
PLM-52 Add missing Organization_relationship_query PLM 1.0b1 PLM 1.0 Resolved closed
PLM-51 Add missing Associated_person_organization_query PLM 1.0b1 PLM 1.0 Resolved closed
PLM-48 Add missing query Activity_relationship_query PLM 1.0b1 PLM 1.0 Resolved closed
PLM-47 Add missing query Activity_element_query PLM 1.0b1 PLM 1.0 Resolved closed
PLM-44 Separation of Timeout_exception PLM 1.0b1 PLM 1.0 Resolved closed
PLM-43 Use of the Attribute_pattern_attribute in the specified queries PLM 1.0b1 PLM 1.0 Resolved closed
PLM-42 Required Property for get_connection_factory and get_connection PLM 1.0b1 PLM 1.0 Resolved closed
PLM-41 New exception type Invalid_session_id_exception PLM 1.0b1 PLM 1.0 Resolved closed
PLM-40 Rename Authentification_exception to Authentication_exception PLM 1.0b1 PLM 1.0 Resolved closed
PLM-39 Rename Object_not_exist_exception to Unknown_object_uid_exception PLM 1.0b1 PLM 1.0 Resolved closed
PLM-30 chapter 8.9 (Query Type), PLM 1.0b1 PLM 1.0 Resolved closed
PLM-29 Chapter 8.9 (Query Type) PLM 1.0b1 PLM 1.0 Resolved closed
PLM-28 chapter 8.10 (Generic Queries Conformance Point PLM 1.0b1 PLM 1.0 Resolved closed
PLM-27 How to satisfy relationship multiplicities of '1..*' in query results? PLM 1.0b1 PLM 1.0 Resolved closed
PLM-34 New Predicate Types for Negation and Attribute Pattern PLM 1.0b1 PLM 1.0 Resolved closed
PLM-33 Filter start nodes of queries for associated nodes by type PLM 1.0b1 PLM 1.0 Resolved closed
PLM-24 New PLM_messages PLM 1.0b1 PLM 1.0 Resolved closed
PLM-23 Value of PLM_container.version_id PLM 1.0b1 PLM 1.0 Resolved closed
PLM-32 New Attributes for Item- and Document_query PLM 1.0b1 PLM 1.0 Resolved closed
PLM-31 chapter 8.12.4 (Approval Query) PLM 1.0b1 PLM 1.0 Resolved closed
PLM-26 Downloadable URIs for PLMServices documents PLM 1.0b1 PLM 1.0 Resolved closed
PLM-25 typo in namespace of soap body of write operation PLM 1.0b1 PLM 1.0 Resolved closed
PLM-18 PropertiesDescriptors for Operations with properties parameter PLM 1.0b1 PLM 1.0 Resolved closed
PLM-17 PDTnet Queries Conformance Point PLM 1.0b1 PLM 1.0 Resolved closed
PLM-16 Separate Soap Header Elements PLM 1.0b1 PLM 1.0 Resolved closed
PLM-22 change name of element Cause in PLM_exception to Linked_exception PLM 1.0b1 PLM 1.0 Resolved closed
PLM-21 Extract Schema-Element from WSDL into separate File PLM 1.0b1 PLM 1.0 Resolved closed
PLM-20 Replace Simple_property_value by Simple_property_association PLM 1.0b1 PLM 1.0 Resolved closed
PLM-19 XML Mapping of PIM Type Integer PLM 1.0b1 PLM 1.0 Resolved closed
PLM-15 Implementation of the operation 'write' PLM 1.0b1 PLM 1.0 Resolved closed
PLM-14 complexTypes 'Item_version' and 'Document_version' PLM 1.0b1 PLM 1.0 Resolved closed
PLM-13 Attributes PLM 1.0b1 PLM 1.0 Resolved closed
PLM-3 Common Interfaces for common relationships PLM 1.0b1 open
PLM-2 "associated" prefix PLM 1.0 open
PLM-12 typo in section 7.7.12.39 PLM 1.0b1 PLM 1.0 Resolved closed
PLM-11 Empty Interfaces in PLM Services Specification dtc/04-05-05 PLM 1.0b1 PLM 1.0 Resolved closed
PLM-10 targetNamespace of the xs:schema element in the wsdl:types section PLM 1.0b1 PLM 1.0 Resolved closed
PLM-9 typo in line 299 PLM 1.0b1 PLM 1.0 Resolved closed
PLM-5 Granularity of Computational Model PLM 1.0b1 open
PLM-4 Intermediate Queries PLM 1.0b1 open
PLM-6 Add complex type Section_context PLM 1.0b1 open
PLM-7 multiplicity of relations PLM 1.0b1 open
PLM-1 The WSDL and the XML Schema should be extended PLM 1.0b1 open
PLM-8 Name of Alternative_solution_query PLM 1.0 open

Issues Descriptions

Section: 8.14 p. 342 (04)

  • Key: PLM-101
  • Legacy Issue Number: 9135
  • Status: closed  
  • Source: T-Systems Enterprise Services ( Hirel, Guillaume)
  • 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

  • Reported: PLM 1.0 — Wed, 2 Nov 2005 05:00 GMT
  • Disposition: Resolved — PLM 1.0.1
  • Disposition Summary:

    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

  • Updated: Sat, 7 Mar 2015 03:25 GMT

Section: 8.14.16

  • Key: PLM-100
  • Legacy Issue Number: 9134
  • Status: closed  
  • Source: T-Systems Enterprise Services ( Hirel, Guillaume)
  • 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

  • Reported: PLM 1.0 — Wed, 2 Nov 2005 05:00 GMT
  • Disposition: Resolved — PLM 1.0.1
  • Disposition Summary:

    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

  • Updated: Sat, 7 Mar 2015 03:25 GMT

Section: 8.9

  • Key: PLM-102
  • Legacy Issue Number: 9136
  • Status: closed  
  • Source: T-Systems Enterprise Services ( Hirel, Guillaume)
  • 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>

  • Reported: PLM 1.0 — Wed, 2 Nov 2005 05:00 GMT
  • Disposition: Resolved — PLM 1.0.1
  • Disposition Summary:

    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

  • Updated: Sat, 7 Mar 2015 03:25 GMT

Section: 8.14 p. 342 (05)

  • Key: PLM-103
  • Legacy Issue Number: 9137
  • Status: closed  
  • Source: T-Systems Enterprise Services ( Hirel, Guillaume)
  • 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>

  • Reported: PLM 1.0 — Wed, 2 Nov 2005 05:00 GMT
  • Disposition: Resolved — PLM 1.0.1
  • Disposition Summary:

    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

  • Updated: Sat, 7 Mar 2015 03:25 GMT

Section: 8.14 p. 342 (03)

  • Key: PLM-99
  • Legacy Issue Number: 9133
  • Status: closed  
  • Source: T-Systems Enterprise Services ( Hirel, Guillaume)
  • 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>

  • Reported: PLM 1.0 — Wed, 2 Nov 2005 05:00 GMT
  • Disposition: Resolved — PLM 1.0.1
  • Disposition Summary:

    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

  • Updated: Sat, 7 Mar 2015 03:25 GMT

Section: 8.14 p. 342 (02)

  • Key: PLM-98
  • Legacy Issue Number: 9132
  • Status: closed  
  • Source: T-Systems Enterprise Services ( Hirel, Guillaume)
  • 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>

  • Reported: PLM 1.0 — Wed, 2 Nov 2005 05:00 GMT
  • Disposition: Resolved — PLM 1.0.1
  • Disposition Summary:

    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

  • Updated: Sat, 7 Mar 2015 03:25 GMT

Section: 8.14 p. 342

  • Key: PLM-97
  • Legacy Issue Number: 9131
  • Status: closed  
  • Source: T-Systems Enterprise Services ( Hirel, Guillaume)
  • 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>

  • Reported: PLM 1.0 — Wed, 2 Nov 2005 05:00 GMT
  • Disposition: Resolved — PLM 1.0.1
  • Disposition Summary:

    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

  • Updated: Sat, 7 Mar 2015 03:25 GMT

Section: 8.14 p. 360

  • Key: PLM-96
  • Legacy Issue Number: 9130
  • Status: closed  
  • Source: T-Systems Enterprise Services ( Hirel, Guillaume)
  • 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

  • Reported: PLM 1.0 — Wed, 2 Nov 2005 05:00 GMT
  • Disposition: Resolved — PLM 1.0.1
  • Disposition Summary:

    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

  • Updated: Sat, 7 Mar 2015 03:25 GMT

Section: 8.14

  • Key: PLM-94
  • Legacy Issue Number: 9128
  • Status: closed  
  • Source: T-Systems Enterprise Services ( Hirel, Guillaume)
  • 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>

  • Reported: PLM 1.0 — Wed, 2 Nov 2005 05:00 GMT
  • Disposition: Resolved — PLM 1.0.1
  • Disposition Summary:

    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

  • Updated: Sat, 7 Mar 2015 03:25 GMT

Section: 8.14.49

  • Key: PLM-93
  • Legacy Issue Number: 9127
  • Status: closed  
  • Source: T-Systems Enterprise Services ( Hirel, Guillaume)
  • 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>

  • Reported: PLM 1.0 — Wed, 2 Nov 2005 05:00 GMT
  • Disposition: Resolved — PLM 1.0.1
  • Disposition Summary:

    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

  • Updated: Sat, 7 Mar 2015 03:25 GMT

Section: 8.14

  • Key: PLM-92
  • Legacy Issue Number: 9126
  • Status: closed  
  • Source: T-Systems Enterprise Services ( Hirel, Guillaume)
  • 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>

  • Reported: PLM 1.0 — Wed, 2 Nov 2005 05:00 GMT
  • Disposition: Resolved — PLM 1.0.1
  • Disposition Summary:

    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

  • Updated: Sat, 7 Mar 2015 03:25 GMT

Section: 8.14.16

  • Key: PLM-95
  • Legacy Issue Number: 9129
  • Status: closed  
  • Source: T-Systems Enterprise Services ( Hirel, Guillaume)
  • 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

  • Reported: PLM 1.0 — Wed, 2 Nov 2005 05:00 GMT
  • Disposition: Resolved — PLM 1.0.1
  • Disposition Summary:

    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

  • Updated: Sat, 7 Mar 2015 03:25 GMT

'activity_authorization_query'

  • Key: PLM-91
  • Legacy Issue Number: 8942
  • Status: closed  
  • Source: T-Systems Enterprise Services ( Hirel, Guillaume)
  • 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.

  • Reported: PLM 1.0b1 — Thu, 28 Jul 2005 04:00 GMT
  • Disposition: Resolved — PLM 1.0
  • Disposition Summary:

    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

  • Updated: Sat, 7 Mar 2015 03:24 GMT

'activity_resolved_requests_query'

  • Key: PLM-90
  • Legacy Issue Number: 8941
  • Status: closed  
  • Source: T-Systems Enterprise Services ( Hirel, Guillaume)
  • 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.

  • Reported: PLM 1.0b1 — Thu, 28 Jul 2005 04:00 GMT
  • Disposition: Resolved — PLM 1.0
  • Disposition Summary:

    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

  • Updated: Sat, 7 Mar 2015 03:24 GMT

chapter 8.12 (Generic Queries Conformance Point

  • Key: PLM-89
  • Legacy Issue Number: 8940
  • Status: closed  
  • Source: T-Systems Enterprise Services ( Hirel, Guillaume)
  • 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]

  • Reported: PLM 1.0b1 — Thu, 28 Jul 2005 04:00 GMT
  • Disposition: Resolved — PLM 1.0
  • Disposition Summary:

    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

  • Updated: Sat, 7 Mar 2015 03:24 GMT

some numbering mismatch in chapter 7.7 7.7.11.1

  • Key: PLM-87
  • Legacy Issue Number: 7936
  • Status: closed  
  • Source: PROSTEP AG ( Lutz Laemmer)
  • Summary:

    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

  • Reported: PLM 1.0 — Fri, 19 Nov 2004 05:00 GMT
  • Disposition: Resolved — PLM 1.0.1
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 22:55 GMT

First sentence in Chapter 7.4.3.1

  • Key: PLM-88
  • Legacy Issue Number: 7937
  • Status: closed  
  • Source: PROSTEP AG ( Lutz Laemmer)
  • Summary:

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

  • Reported: PLM 1.0 — Fri, 19 Nov 2004 05:00 GMT
  • Disposition: Resolved — PLM 1.0.1
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 22:55 GMT

Person_in_organization_relationship

  • Key: PLM-84
  • Legacy Issue Number: 7843
  • Status: closed  
  • Source: PROSTEP AG ( Lutz Laemmer)
  • Summary:

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

  • Reported: PLM 1.0 — Thu, 7 Oct 2004 04:00 GMT
  • Disposition: Resolved — PLM 1.0.1
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 22:55 GMT

figures missing

  • Key: PLM-86
  • Legacy Issue Number: 7935
  • Status: closed  
  • Source: PROSTEP AG ( Lutz Laemmer)
  • Summary:

    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

  • Reported: PLM 1.0 — Fri, 19 Nov 2004 05:00 GMT
  • Disposition: Resolved — PLM 1.0.1
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 22:55 GMT

Align simple property assignment mechanism with STEP AP214 maint. version

  • Key: PLM-85
  • Legacy Issue Number: 7844
  • Status: closed  
  • Source: PROSTEP AG ( Lutz Laemmer)
  • Summary:

    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;

  • Reported: PLM 1.0 — Thu, 7 Oct 2004 04:00 GMT
  • Disposition: Resolved — PLM 1.0.1
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 22:55 GMT

Date and Time types shall be mapped according to ISO 8601.

  • Key: PLM-83
  • Legacy Issue Number: 7842
  • Status: closed  
  • Source: PROSTEP AG ( Lutz Laemmer)
  • Summary:

    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

  • Reported: PLM 1.0 — Thu, 7 Oct 2004 04:00 GMT
  • Disposition: Resolved — PLM 1.0.1
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 22:55 GMT

Definition of project

  • Key: PLM-82
  • Legacy Issue Number: 7841
  • Status: closed  
  • Source: PROSTEP AG ( Lutz Laemmer)
  • Summary:

    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;

  • Reported: PLM 1.0 — Thu, 7 Oct 2004 04:00 GMT
  • Disposition: Resolved — PLM 1.0.1
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 22:55 GMT

Organization_relationhip

  • Key: PLM-81
  • Legacy Issue Number: 7840
  • Status: closed  
  • Source: PROSTEP AG ( Lutz Laemmer)
  • Summary:

    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

  • Reported: PLM 1.0 — Fri, 13 Aug 1999 04:00 GMT
  • Disposition: Resolved — PLM 1.0.1
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 22:55 GMT

Work_request and Work_order are Root_objects

  • Key: PLM-80
  • Legacy Issue Number: 7839
  • Status: closed  
  • Source: PROSTEP AG ( Lutz Laemmer)
  • Summary:

    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.

  • Reported: PLM 1.0 — Thu, 7 Oct 2004 04:00 GMT
  • Disposition: Resolved — PLM 1.0.1
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 22:55 GMT

New element type required

  • Key: PLM-79
  • Legacy Issue Number: 7838
  • Status: closed  
  • Source: PROSTEP AG ( Lutz Laemmer)
  • Summary:

    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

  • Reported: PLM 1.0 — Thu, 7 Oct 2004 04:00 GMT
  • Disposition: Resolved — PLM 1.0.1
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 22:55 GMT

Clarify "Signature" attribute of PLM_session_context type

  • Key: PLM-78
  • Legacy Issue Number: 7775
  • Status: closed  
  • Source: PROSTEP AG ( Lutz Laemmer)
  • Summary:

    Clarify "Signature" attribute of PLM_session_context type

  • Reported: PLM 1.0 — Mon, 20 Sep 2004 04:00 GMT
  • Disposition: Resolved — PLM 1.0.1
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 22:55 GMT

append examples

  • Key: PLM-77
  • Legacy Issue Number: 7774
  • Status: closed  
  • Source: PROSTEP AG ( Lutz Laemmer)
  • Summary:

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

  • Reported: PLM 1.0 — Mon, 20 Sep 2004 04:00 GMT
  • Disposition: Resolved — PLM 1.0.1
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 22:55 GMT

"predicates" data type

  • Key: PLM-76
  • Legacy Issue Number: 7772
  • Status: closed  
  • Source: PROSTEP AG ( Lutz Laemmer)
  • Summary:

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

  • Reported: PLM 1.0 — Mon, 20 Sep 2004 04:00 GMT
  • Disposition: Resolved — PLM 1.0.1
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 22:55 GMT

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

  • Key: PLM-75
  • Legacy Issue Number: 7771
  • Status: closed  
  • Source: PROSTEP AG ( Lutz Laemmer)
  • Summary:

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

  • Reported: PLM 1.0 — Mon, 20 Sep 2004 04:00 GMT
  • Disposition: Resolved — PLM 1.0.1
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 22:55 GMT

Rename insert-Operation into import_data

  • Key: PLM-74
  • Legacy Issue Number: 7770
  • Status: closed  
  • Source: PROSTEP AG ( Lutz Laemmer)
  • Summary:

    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.

  • Reported: PLM 1.0 — Mon, 20 Sep 2004 04:00 GMT
  • Disposition: Resolved — PLM 1.0.1
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 22:55 GMT

PLM_message[0..*] type

  • Key: PLM-73
  • Legacy Issue Number: 7769
  • Status: closed  
  • Source: PROSTEP AG ( Lutz Laemmer)
  • Summary:

    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.

  • Reported: PLM 1.0 — Mon, 20 Sep 2004 04:00 GMT
  • Disposition: Resolved — PLM 1.0.1
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 22:55 GMT

Delete-Operation

  • Key: PLM-72
  • Legacy Issue Number: 7768
  • Status: closed  
  • Source: PROSTEP AG ( Lutz Laemmer)
  • Summary:

    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.

  • Reported: PLM 1.0 — Mon, 20 Sep 2004 04:00 GMT
  • Disposition: Resolved — PLM 1.0.1
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 22:55 GMT

New Query for Assembly component placement

  • Key: PLM-71
  • Legacy Issue Number: 8585
  • Status: closed  
  • Source: Zentrum fuer Graphische Datenverarbeitung e.V. ( Steffen Nowacki)
  • Summary:

    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>

  • Reported: PLM 1.0b1 — Wed, 16 Mar 2005 05:00 GMT
  • Disposition: Resolved — PLM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 22:25 GMT

Enumerations of query start and target types

  • Key: PLM-68
  • Legacy Issue Number: 8448
  • Status: closed  
  • Source: Zentrum fuer Graphische Datenverarbeitung e.V. ( Steffen Nowacki)
  • Summary:

    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.

  • Reported: PLM 1.0b1 — Fri, 4 Mar 2005 05:00 GMT
  • Disposition: Resolved — PLM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 22:25 GMT

New Queries to resolve aliases.

  • Key: PLM-67
  • Legacy Issue Number: 8441
  • Status: closed  
  • Source: Zentrum fuer Graphische Datenverarbeitung e.V. ( Steffen Nowacki)
  • Summary:

    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.

  • Reported: PLM 1.0b1 — Thu, 3 Mar 2005 05:00 GMT
  • Disposition: Resolved — PLM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 22:25 GMT

New Query type Conditional_query

  • Key: PLM-70
  • Legacy Issue Number: 8584
  • Status: closed  
  • Source: Zentrum fuer Graphische Datenverarbeitung e.V. ( Steffen Nowacki)
  • Summary:

    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>

  • Reported: PLM 1.0b1 — Wed, 16 Mar 2005 05:00 GMT
  • Disposition: Resolved — PLM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 22:25 GMT

Some numbering mismatch in section 8.9

  • Key: PLM-69
  • Legacy Issue Number: 8583
  • Status: closed  
  • Source: Zentrum fuer Graphische Datenverarbeitung e.V. ( Steffen Nowacki)
  • Summary:

    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.

  • Reported: PLM 1.0b1 — Wed, 16 Mar 2005 05:00 GMT
  • Disposition: Resolved — PLM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 22:25 GMT

Labeling of optional attributes

  • Key: PLM-66
  • Legacy Issue Number: 8436
  • Status: closed  
  • Source: Zentrum fuer Graphische Datenverarbeitung e.V. ( Steffen Nowacki)
  • Summary:

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

  • Reported: PLM 1.0b1 — Wed, 2 Mar 2005 05:00 GMT
  • Disposition: Resolved — PLM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 22:25 GMT

New Abstract Base Class for Relationship_queries

  • Key: PLM-64
  • Legacy Issue Number: 8434
  • Status: closed  
  • Source: Zentrum fuer Graphische Datenverarbeitung e.V. ( Steffen Nowacki)
  • Summary:

    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.

  • Reported: PLM 1.0b1 — Wed, 2 Mar 2005 05:00 GMT
  • Disposition: Resolved — PLM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 22:25 GMT

Redundant attribute identifier_name in Identifier_predicate

  • Key: PLM-65
  • Legacy Issue Number: 8435
  • Status: closed  
  • Source: Zentrum fuer Graphische Datenverarbeitung e.V. ( Steffen Nowacki)
  • Summary:

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

  • Reported: PLM 1.0b1 — Wed, 2 Mar 2005 05:00 GMT
  • Disposition: Resolved — PLM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 22:25 GMT

Add missing query Work_request_relationship_query

  • Key: PLM-63
  • Legacy Issue Number: 8006
  • Status: closed  
  • Source: PDTec AG ( Günter Staub)
  • Summary:

    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>

  • Reported: PLM 1.0b1 — Thu, 23 Dec 2004 05:00 GMT
  • Disposition: Resolved — PLM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Section: 8.12.11

  • Key: PLM-58
  • Legacy Issue Number: 8299
  • Status: closed  
  • Source: T-Systems Enterprise Services ( Hirel, Guillaume)
  • Summary:

    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.

  • Reported: PLM 1.0b1 — Tue, 22 Feb 2005 05:00 GMT
  • Disposition: Resolved — PLM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Add missing query Project_assignment_query

  • Key: PLM-57
  • Legacy Issue Number: 8010
  • Status: closed  
  • Source: PDTec AG ( Günter Staub)
  • Summary:

    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>

  • Reported: PLM 1.0b1 — Thu, 23 Dec 2004 05:00 GMT
  • Disposition: Resolved — PLM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Description of use of type PLM_container

  • Key: PLM-62
  • Legacy Issue Number: 8400
  • Status: closed  
  • Source: Zentrum fuer Graphische Datenverarbeitung e.V. ( Steffen Nowacki)
  • Summary:

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

  • Reported: PLM 1.0b1 — Mon, 28 Feb 2005 05:00 GMT
  • Disposition: Resolved — PLM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Batch Queries

  • Key: PLM-61
  • Legacy Issue Number: 8334
  • Status: closed  
  • Source: Zentrum fuer Graphische Datenverarbeitung e.V. ( Steffen Nowacki)
  • Summary:

    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.

  • Reported: PLM 1.0b1 — Thu, 24 Feb 2005 05:00 GMT
  • Disposition: Resolved — PLM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Add missing query Work_request_classification_query

  • Key: PLM-54
  • Legacy Issue Number: 8007
  • Status: closed  
  • Source: PDTec AG ( Günter Staub)
  • Summary:

    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>

  • Reported: PLM 1.0b1 — Thu, 23 Dec 2004 05:00 GMT
  • Disposition: Resolved — PLM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Add missing Work_request_query

  • Key: PLM-53
  • Legacy Issue Number: 8005
  • Status: closed  
  • Source: PDTec AG ( Günter Staub)
  • Summary:

    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>

  • Reported: PLM 1.0b1 — Thu, 23 Dec 2004 05:00 GMT
  • Disposition: Resolved — PLM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Special Exception for unsupported operations

  • Key: PLM-60
  • Legacy Issue Number: 8333
  • Status: closed  
  • Source: Zentrum fuer Graphische Datenverarbeitung e.V. ( Steffen Nowacki)
  • Summary:

    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.

  • Reported: PLM 1.0b1 — Thu, 24 Feb 2005 05:00 GMT
  • Disposition: Resolved — PLM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Section: 8.12.10

  • Key: PLM-59
  • Legacy Issue Number: 8300
  • Status: closed  
  • Source: T-Systems Enterprise Services ( Hirel, Guillaume)
  • Summary:

    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.

  • Reported: PLM 1.0b1 — Tue, 22 Feb 2005 05:00 GMT
  • Disposition: Resolved — PLM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Add missing query Person_in_organization_relationship_query

  • Key: PLM-56
  • Legacy Issue Number: 8009
  • Status: closed  
  • Source: PDTec AG ( Günter Staub)
  • Summary:

    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>

  • Reported: PLM 1.0b1 — Thu, 23 Dec 2004 05:00 GMT
  • Disposition: Resolved — PLM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Add missing query Work_request_scope_

  • Key: PLM-55
  • Legacy Issue Number: 8008
  • Status: closed  
  • Source: PDTec AG ( Günter Staub)
  • Summary:

    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>

  • Reported: PLM 1.0b1 — Thu, 23 Dec 2004 05:00 GMT
  • Disposition: Resolved — PLM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Add missing Associated_date_organization_query

  • Key: PLM-50
  • Legacy Issue Number: 8002
  • Status: closed  
  • Source: PDTec AG ( Günter Staub)
  • Summary:

    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>

  • Reported: PLM 1.0b1 — Thu, 23 Dec 2004 05:00 GMT
  • Disposition: Resolved — PLM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Add missing Associated_activity_query

  • Key: PLM-49
  • Legacy Issue Number: 8001
  • Status: closed  
  • Source: PDTec AG ( Günter Staub)
  • Summary:

    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>

  • Reported: PLM 1.0b1 — Thu, 23 Dec 2004 05:00 GMT
  • Disposition: Resolved — PLM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Add complex type Person_in_organization_relationship

  • Key: PLM-46
  • Legacy Issue Number: 7998
  • Status: closed  
  • Source: PDTec AG ( Günter Staub)
  • Summary:

    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>

  • Reported: PLM 1.0b1 — Thu, 23 Dec 2004 05:00 GMT
  • Disposition: Resolved — PLM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Predicates for relating objects

  • Key: PLM-45
  • Legacy Issue Number: 7992
  • Status: closed  
  • Source: Zentrum fuer Graphische Datenverarbeitung e.V. ( Steffen Nowacki)
  • Summary:

    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"

  • Reported: PLM 1.0b1 — Mon, 20 Dec 2004 05:00 GMT
  • Disposition: Resolved — PLM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Rename Item_relationship_query to Item_version_relationship_query

  • Key: PLM-38
  • Legacy Issue Number: 7930
  • Status: closed  
  • Source: Zentrum fuer Graphische Datenverarbeitung e.V. ( Steffen Nowacki)
  • Summary:

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

  • Reported: PLM 1.0b1 — Thu, 18 Nov 2004 05:00 GMT
  • Disposition: Resolved — PLM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Attributes of the Alias_identification_query

  • Key: PLM-37
  • Legacy Issue Number: 7929
  • Status: closed  
  • Source: Zentrum fuer Graphische Datenverarbeitung e.V. ( Steffen Nowacki)
  • Summary:

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

  • Reported: PLM 1.0b1 — Thu, 18 Nov 2004 05:00 GMT
  • Disposition: Resolved — PLM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Rename Approval_query to Associated_approval_query

  • Key: PLM-36
  • Legacy Issue Number: 7928
  • Status: closed  
  • Source: Zentrum fuer Graphische Datenverarbeitung e.V. ( Steffen Nowacki)
  • Summary:

    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.

  • Reported: PLM 1.0b1 — Thu, 18 Nov 2004 05:00 GMT
  • Disposition: Resolved — PLM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Root Elements of XML Schemas

  • Key: PLM-35
  • Legacy Issue Number: 7927
  • Status: closed  
  • Source: Zentrum fuer Graphische Datenverarbeitung e.V. ( Steffen Nowacki)
  • Summary:

    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.

  • Reported: PLM 1.0b1 — Thu, 18 Nov 2004 05:00 GMT
  • Disposition: Resolved — PLM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Add missing Organization_relationship_query

  • Key: PLM-52
  • Legacy Issue Number: 8004
  • Status: closed  
  • Source: PDTec AG ( Günter Staub)
  • Summary:

    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>

  • Reported: PLM 1.0b1 — Thu, 23 Dec 2004 05:00 GMT
  • Disposition: Resolved — PLM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Add missing Associated_person_organization_query

  • Key: PLM-51
  • Legacy Issue Number: 8003
  • Status: closed  
  • Source: PDTec AG ( Günter Staub)
  • Summary:

    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>

  • Reported: PLM 1.0b1 — Thu, 23 Dec 2004 05:00 GMT
  • Disposition: Resolved — PLM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Add missing query Activity_relationship_query

  • Key: PLM-48
  • Legacy Issue Number: 8000
  • Status: closed  
  • Source: PDTec AG ( Günter Staub)
  • Summary:

    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>

  • Reported: PLM 1.0b1 — Thu, 23 Dec 2004 05:00 GMT
  • Disposition: Resolved — PLM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Add missing query Activity_element_query

  • Key: PLM-47
  • Legacy Issue Number: 7999
  • Status: closed  
  • Source: PDTec AG ( Günter Staub)
  • Summary:

    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>

  • Reported: PLM 1.0b1 — Thu, 23 Dec 2004 05:00 GMT
  • Disposition: Resolved — PLM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Separation of Timeout_exception

  • Key: PLM-44
  • Legacy Issue Number: 7944
  • Status: closed  
  • Source: Zentrum fuer Graphische Datenverarbeitung e.V. ( Steffen Nowacki)
  • Summary:

    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

  • Reported: PLM 1.0b1 — Mon, 22 Nov 2004 05:00 GMT
  • Disposition: Resolved — PLM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Use of the Attribute_pattern_attribute in the specified queries

  • Key: PLM-43
  • Legacy Issue Number: 7943
  • Status: closed  
  • Source: Zentrum fuer Graphische Datenverarbeitung e.V. ( Steffen Nowacki)
  • Summary:

    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.

  • Reported: PLM 1.0b1 — Mon, 22 Nov 2004 05:00 GMT
  • Disposition: Resolved — PLM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Required Property for get_connection_factory and get_connection

  • Key: PLM-42
  • Legacy Issue Number: 7934
  • Status: closed  
  • Source: Zentrum fuer Graphische Datenverarbeitung e.V. ( Steffen Nowacki)
  • Summary:

    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.

  • Reported: PLM 1.0b1 — Thu, 18 Nov 2004 05:00 GMT
  • Disposition: Resolved — PLM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:58 GMT

New exception type Invalid_session_id_exception

  • Key: PLM-41
  • Legacy Issue Number: 7933
  • Status: closed  
  • Source: Zentrum fuer Graphische Datenverarbeitung e.V. ( Steffen Nowacki)
  • Summary:

    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.

  • Reported: PLM 1.0b1 — Thu, 18 Nov 2004 05:00 GMT
  • Disposition: Resolved — PLM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Rename Authentification_exception to Authentication_exception

  • Key: PLM-40
  • Legacy Issue Number: 7932
  • Status: closed  
  • Source: Zentrum fuer Graphische Datenverarbeitung e.V. ( Steffen Nowacki)
  • Summary:

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

  • Reported: PLM 1.0b1 — Thu, 18 Nov 2004 05:00 GMT
  • Disposition: Resolved — PLM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Rename Object_not_exist_exception to Unknown_object_uid_exception

  • Key: PLM-39
  • Legacy Issue Number: 7931
  • Status: closed  
  • Source: Zentrum fuer Graphische Datenverarbeitung e.V. ( Steffen Nowacki)
  • Summary:

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

  • Reported: PLM 1.0b1 — Thu, 18 Nov 2004 05:00 GMT
  • Disposition: Resolved — PLM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:58 GMT

chapter 8.9 (Query Type),

  • Key: PLM-30
  • Legacy Issue Number: 7897
  • Status: closed  
  • Source: T-Systems Enterprise Services ( Hirel, Guillaume)
  • Summary:

    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,

  • Reported: PLM 1.0b1 — Tue, 2 Nov 2004 05:00 GMT
  • Disposition: Resolved — PLM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Chapter 8.9 (Query Type)

  • Key: PLM-29
  • Legacy Issue Number: 7886
  • Status: closed  
  • Source: T-Systems International GmbH ( Hirel, Guillaume)
  • Summary:

    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.

  • Reported: PLM 1.0b1 — Thu, 28 Oct 2004 04:00 GMT
  • Disposition: Resolved — PLM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:58 GMT

chapter 8.10 (Generic Queries Conformance Point

  • Key: PLM-28
  • Legacy Issue Number: 7885
  • Status: closed  
  • Source: T-Systems Enterprise Services ( Hirel, Guillaume)
  • Summary:

    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,

  • Reported: PLM 1.0b1 — Thu, 28 Oct 2004 04:00 GMT
  • Disposition: Resolved — PLM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:58 GMT

How to satisfy relationship multiplicities of '1..*' in query results?

  • Key: PLM-27
  • Legacy Issue Number: 7883
  • Status: closed  
  • Source: Anonymous
  • Summary:

    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

  • Reported: PLM 1.0b1 — Wed, 27 Oct 2004 04:00 GMT
  • Disposition: Resolved — PLM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:58 GMT

New Predicate Types for Negation and Attribute Pattern

  • Key: PLM-34
  • Legacy Issue Number: 7926
  • Status: closed  
  • Source: Zentrum fuer Graphische Datenverarbeitung e.V. ( Steffen Nowacki)
  • Summary:

    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

  • Reported: PLM 1.0b1 — Thu, 18 Nov 2004 05:00 GMT
  • Disposition: Resolved — PLM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Filter start nodes of queries for associated nodes by type

  • Key: PLM-33
  • Legacy Issue Number: 7925
  • Status: closed  
  • Source: Zentrum fuer Graphische Datenverarbeitung e.V. ( Steffen Nowacki)
  • Summary:

    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.

  • Reported: PLM 1.0b1 — Thu, 18 Nov 2004 05:00 GMT
  • Disposition: Resolved — PLM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:58 GMT

New PLM_messages

  • Key: PLM-24
  • Legacy Issue Number: 7872
  • Status: closed  
  • Source: Zentrum fuer Graphische Datenverarbeitung e.V. ( Steffen Nowacki)
  • Summary:

    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.

  • Reported: PLM 1.0b1 — Tue, 19 Oct 2004 04:00 GMT
  • Disposition: Resolved — PLM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Value of PLM_container.version_id

  • Key: PLM-23
  • Legacy Issue Number: 7871
  • Status: closed  
  • Source: Zentrum fuer Graphische Datenverarbeitung e.V. ( Steffen Nowacki)
  • Summary:

    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.

  • Reported: PLM 1.0b1 — Tue, 19 Oct 2004 04:00 GMT
  • Disposition: Resolved — PLM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:58 GMT

New Attributes for Item- and Document_query

  • Key: PLM-32
  • Legacy Issue Number: 7924
  • Status: closed  
  • Source: Zentrum fuer Graphische Datenverarbeitung e.V. ( Steffen Nowacki)
  • Summary:

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

  • Reported: PLM 1.0b1 — Thu, 18 Nov 2004 05:00 GMT
  • Disposition: Resolved — PLM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:58 GMT

chapter 8.12.4 (Approval Query)

  • Key: PLM-31
  • Legacy Issue Number: 7899
  • Status: closed  
  • Source: T-Systems Enterprise Services ( Hirel, Guillaume)
  • Summary:

    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

  • Reported: PLM 1.0b1 — Wed, 3 Nov 2004 05:00 GMT
  • Disposition: Resolved — PLM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Downloadable URIs for PLMServices documents

  • Key: PLM-26
  • Legacy Issue Number: 7874
  • Status: closed  
  • Source: Zentrum fuer Graphische Datenverarbeitung e.V. ( Steffen Nowacki)
  • Summary:

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

  • Reported: PLM 1.0b1 — Tue, 19 Oct 2004 04:00 GMT
  • Disposition: Resolved — PLM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:58 GMT

typo in namespace of soap body of write operation

  • Key: PLM-25
  • Legacy Issue Number: 7873
  • Status: closed  
  • Source: Zentrum fuer Graphische Datenverarbeitung e.V. ( Steffen Nowacki)
  • Summary:

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

  • Reported: PLM 1.0b1 — Tue, 19 Oct 2004 04:00 GMT
  • Disposition: Resolved — PLM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:58 GMT

PropertiesDescriptors for Operations with properties parameter

  • Key: PLM-18
  • Legacy Issue Number: 7830
  • Status: closed  
  • Source: Zentrum fuer Graphische Datenverarbeitung e.V. ( Steffen Nowacki)
  • Summary:

    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.

  • Reported: PLM 1.0b1 — Fri, 1 Oct 2004 04:00 GMT
  • Disposition: Resolved — PLM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:58 GMT

PDTnet Queries Conformance Point

  • Key: PLM-17
  • Legacy Issue Number: 7828
  • Status: closed  
  • Source: Zentrum fuer Graphische Datenverarbeitung e.V. ( Steffen Nowacki)
  • Summary:

    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.

  • Reported: PLM 1.0b1 — Fri, 1 Oct 2004 04:00 GMT
  • Disposition: Resolved — PLM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Separate Soap Header Elements

  • Key: PLM-16
  • Legacy Issue Number: 7827
  • Status: closed  
  • Source: Zentrum fuer Graphische Datenverarbeitung e.V. ( Steffen Nowacki)
  • Summary:

    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

  • Reported: PLM 1.0b1 — Fri, 1 Oct 2004 04:00 GMT
  • Disposition: Resolved — PLM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:58 GMT

change name of element Cause in PLM_exception to Linked_exception

  • Key: PLM-22
  • Legacy Issue Number: 7870
  • Status: closed  
  • Source: Zentrum fuer Graphische Datenverarbeitung e.V. ( Steffen Nowacki)
  • Summary:

    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"

  • Reported: PLM 1.0b1 — Tue, 19 Oct 2004 04:00 GMT
  • Disposition: Resolved — PLM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Extract Schema-Element from WSDL into separate File

  • Key: PLM-21
  • Legacy Issue Number: 7867
  • Status: closed  
  • Source: Zentrum fuer Graphische Datenverarbeitung e.V. ( Steffen Nowacki)
  • Summary:

    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.

  • Reported: PLM 1.0b1 — Mon, 18 Oct 2004 04:00 GMT
  • Disposition: Resolved — PLM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Replace Simple_property_value by Simple_property_association

  • Key: PLM-20
  • Legacy Issue Number: 7837
  • Status: closed  
  • Source: Zentrum fuer Graphische Datenverarbeitung e.V. ( Steffen Nowacki)
  • Summary:

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

  • Reported: PLM 1.0b1 — Mon, 4 Oct 2004 04:00 GMT
  • Disposition: Resolved — PLM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:58 GMT

XML Mapping of PIM Type Integer

  • Key: PLM-19
  • Legacy Issue Number: 7836
  • Status: closed  
  • Source: Zentrum fuer Graphische Datenverarbeitung e.V. ( Steffen Nowacki)
  • Summary:

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

  • Reported: PLM 1.0b1 — Mon, 4 Oct 2004 04:00 GMT
  • Disposition: Resolved — PLM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Implementation of the operation 'write'

  • Key: PLM-15
  • Legacy Issue Number: 7745
  • Status: closed  
  • Source: Zentrum fuer Graphische Datenverarbeitung e.V. ( Steffen Nowacki)
  • Summary:

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

  • Reported: PLM 1.0b1 — Wed, 15 Sep 2004 04:00 GMT
  • Disposition: Resolved — PLM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:58 GMT

complexTypes 'Item_version' and 'Document_version'

  • Key: PLM-14
  • Legacy Issue Number: 7741
  • Status: closed  
  • Source: Zentrum fuer Graphische Datenverarbeitung e.V. ( Steffen Nowacki)
  • Summary:

    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.

  • Reported: PLM 1.0b1 — Mon, 13 Sep 2004 04:00 GMT
  • Disposition: Resolved — PLM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Attributes

  • Key: PLM-13
  • Legacy Issue Number: 7740
  • Status: closed  
  • Source: Zentrum fuer Graphische Datenverarbeitung e.V. ( Steffen Nowacki)
  • Summary:

    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.

  • Reported: PLM 1.0b1 — Mon, 13 Sep 2004 04:00 GMT
  • Disposition: Resolved — PLM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Common Interfaces for common relationships

  • Key: PLM-3
  • Legacy Issue Number: 7826
  • Status: open  
  • Source: Zentrum fuer Graphische Datenverarbeitung e.V. ( Steffen Nowacki)
  • 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

  • Reported: PLM 1.0b1 — Fri, 1 Oct 2004 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT

"associated" prefix

  • Key: PLM-2
  • Legacy Issue Number: 7773
  • Status: open  
  • Source: PROSTEP AG ( Lutz Laemmer)
  • Summary:

    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.

  • Reported: PLM 1.0 — Mon, 20 Sep 2004 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT

typo in section 7.7.12.39

  • Key: PLM-12
  • Legacy Issue Number: 7724
  • Status: closed  
  • Source: PROSTEP AG ( Lutz Laemmer)
  • Summary:

    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

  • Reported: PLM 1.0b1 — Thu, 9 Sep 2004 04:00 GMT
  • Disposition: Resolved — PLM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Empty Interfaces in PLM Services Specification dtc/04-05-05

  • Key: PLM-11
  • Legacy Issue Number: 7723
  • Status: closed  
  • Source: PROSTEP AG ( Lutz Laemmer)
  • Summary:

    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?

  • Reported: PLM 1.0b1 — Thu, 9 Sep 2004 04:00 GMT
  • Disposition: Resolved — PLM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:58 GMT

targetNamespace of the xs:schema element in the wsdl:types section

  • Key: PLM-10
  • Legacy Issue Number: 7685
  • Status: closed  
  • Source: Zentrum fuer Graphische Datenverarbeitung e.V. ( Steffen Nowacki)
  • Summary:

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

  • Reported: PLM 1.0b1 — Wed, 8 Sep 2004 04:00 GMT
  • Disposition: Resolved — PLM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:58 GMT

typo in line 299

  • Key: PLM-9
  • Legacy Issue Number: 7566
  • Status: closed  
  • Source: Zentrum fuer Graphische Datenverarbeitung e.V. ( Steffen Nowacki)
  • Summary:

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

  • Reported: PLM 1.0b1 — Wed, 7 Jul 2004 04:00 GMT
  • Disposition: Resolved — PLM 1.0
  • Disposition Summary:

    No Data Available

  • Updated: Fri, 6 Mar 2015 20:58 GMT

Granularity of Computational Model

  • Key: PLM-5
  • Legacy Issue Number: 7887
  • Status: open  
  • Source: Zentrum fuer Graphische Datenverarbeitung e.V. ( Steffen Nowacki)
  • Summary:

    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.

  • Reported: PLM 1.0b1 — Thu, 28 Oct 2004 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT

Intermediate Queries

  • Key: PLM-4
  • Legacy Issue Number: 7829
  • Status: open  
  • Source: Zentrum fuer Graphische Datenverarbeitung e.V. ( Steffen Nowacki)
  • Summary:

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

  • Reported: PLM 1.0b1 — Fri, 1 Oct 2004 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT

Add complex type Section_context

  • Key: PLM-6
  • Legacy Issue Number: 8011
  • Status: open  
  • Source: PDTec AG ( Günter Staub)
  • Summary:

    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>

  • Reported: PLM 1.0b1 — Thu, 23 Dec 2004 05:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT

multiplicity of relations

  • Key: PLM-7
  • Legacy Issue Number: 8013
  • Status: open  
  • Source: PDTec AG ( Günter Staub)
  • Summary:

    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:?]”.

  • Reported: PLM 1.0b1 — Thu, 30 Dec 2004 05:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT

The WSDL and the XML Schema should be extended

  • Key: PLM-1
  • Legacy Issue Number: 7739
  • Status: open  
  • Source: Zentrum fuer Graphische Datenverarbeitung e.V. ( Steffen Nowacki)
  • 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.

  • Reported: PLM 1.0b1 — Mon, 13 Sep 2004 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT

Name of Alternative_solution_query

  • Key: PLM-8
  • Legacy Issue Number: 8442
  • Status: open  
  • Source: Zentrum fuer Graphische Datenverarbeitung e.V. ( Steffen Nowacki)
  • Summary:

    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.

  • Reported: PLM 1.0 — Thu, 3 Mar 2005 05:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT