Product Lifecycle Management Services Avatar
  1. OMG Specification

Product Lifecycle Management Services — All Issues

  • Acronym: PLM
  • Issues Count: 159
  • Description: All Issues
Open Closed All
All Issues

Issues Summary

Key Issue Reported Fixed Disposition Status
PLM2_-10 Activity_query Reference PLM 1.0.1 PLM 2.0 Resolved closed
PLM2_-9 Associated_process_property_query Reference PLM 1.0.1 PLM 2.0 Resolved closed
PLM2_-8 informational model, object "Document_file" PLM 2.0b2 PLM 2.0 Resolved closed
PLM2_-7 Section: InformationalModel.xsd last lines PLM 2.0b2 PLM 2.0 Resolved closed
PLM2_-6 Section: InformationalModel.xsd PLM 2.0b2 PLM 2.0 Resolved closed
PLM2_-5 The function Get_download_URL shall be enhanced to download multiple files PLM 2.0b2 PLM 2.0 Resolved closed
PLM2_-4 The type Axis2_placement_3d shall be removed from the class PLM_container PLM 2.0b2 PLM 2.0 Resolved closed
PLM2_-3 Informational Model (xsd) PLM 2.0b2 PLM 2.0 Resolved closed
PLM2_-2 Section: 8.1 PLM 2.0b2 PLM 2.0 Resolved closed
PLM2_-1 Section: 9.7.39 PLM 2.0b2 PLM 2.0 Resolved closed
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
PLM21-2 XSD files lack default namespace PLM 2.0 PLM 2.1 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
PLM2-43 PLM 2 FTF Security chapter issue PLM 1.0.1 PLM 2.0b2 Resolved closed
PLM2-44 Attribute Description for Entities Document_file and Person_in_organization PLM 1.0.1 PLM 2.0b2 Resolved closed
PLM2-6 Chapter 8.9.1 PLM 1.0.1 PLM 2.0b2 Resolved closed
PLM2-5 Specification of Relationship_predicate PLM 1.0.1 PLM 2.0b2 Resolved closed
PLM2-4 PLM 2 FTF -- Editorial issues PLM 1.0.1 PLM 2.0b2 Resolved closed
PLM2-3 Section "7.2.5.7 Constraints and assertions" -- none defined at the moment PLM 1.0.1 PLM 2.0b2 Resolved closed
PLM2-1 Section "7 Use Cases" - no flow diagram exists PLM 1.0.1 PLM 2.0b2 Resolved closed
PLM2-2 Section "7.2.4.9 Topics under discussion" PLM 1.0.1 PLM 2.0b2 Resolved closed
PLM2-27 Project_assignment_query Reference PLM 1.0.1 PLM 2.0b2 Resolved closed
PLM2-26 Proxy Queries Conformance Point Reference PLM 1.0.1 PLM 2.0b2 Resolved closed
PLM2-42 Chapter 9.7.49, SpecificQueries.xsd, Chapter 9.8.7 PLM 1.0.1 PLM 2.0b2 Resolved closed
PLM2-41 remove composition 'axis2_placement_3d' from type 'PLM_container PLM 1.0.1 PLM 2.0b2 Resolved closed
PLM2-40 Join operations 'query' and 'export_data' into one single operation PLM 1.0.1 PLM 2.0b2 Resolved closed
PLM2-35 Item_traversal_query Reference PLM 1.0.1 PLM 2.0b2 Resolved closed
PLM2-34 Work_request_scope_query Reference PLM 1.0.1 PLM 2.0b2 Resolved closed
PLM2-37 Join PLM_properties_descriptors query operations PLM 1.0.1 PLM 2.0b2 Resolved closed
PLM2-36 General_detail_query Reference PLM 1.0.1 PLM 2.0b2 Resolved closed
PLM2-31 Event_reference_query Reference PLM 1.0.1 PLM 2.0b2 Resolved closed
PLM2-30 Design_discipline_item_definition_query Reference: PLM 1.0.1 PLM 2.0b2 Resolved closed
PLM2-39 Add optional generic property list parameter to some service operations PLM 1.0.1 PLM 2.0b2 Resolved closed
PLM2-38 Join operations 'write' and 'import_data' into one single operation PLM 1.0.1 PLM 2.0b2 Resolved closed
PLM2-25 Generic Queries Conformance Point Reference PLM 1.0.1 PLM 2.0b2 Resolved closed
PLM2-24 Compositions in the Computational Model Reference PLM 1.0.1 PLM 2.0b2 Resolved closed
PLM2-29 Configuration_query Reference PLM 1.0.1 PLM 2.0b2 Resolved closed
PLM2-28 Associated_file_query Reference: PLM 1.0.1 PLM 2.0b2 Resolved closed
PLM2-33 Product_structure_query Reference PLM 1.0.1 PLM 2.0b2 Resolved closed
PLM2-32 Item_instance_query Reference PLM 1.0.1 PLM 2.0b2 Resolved closed
PLM2-9 Sort_predicate Reference PLM 1.0.1 PLM 2.0b2 Resolved closed
PLM2-8 Associated_item_property_query Reference PLM 1.0.1 PLM 2.0b2 Resolved closed
PLM2-23 Product_identification_query Reference PLM 1.0.1 PLM 2.0b2 Resolved closed
PLM2-22 Item_use_query Reference PLM 1.0.1 PLM 2.0b2 Resolved closed
PLM2-21 Item_classification_hierarchy_query Reference PLM 1.0.1 PLM 2.0b2 Resolved closed
PLM2-20 File_property_query Reference PLM 1.0.1 PLM 2.0b2 Resolved closed
PLM2-17 Document_classification_hierarchy_query Reference PLM 1.0.1 PLM 2.0b2 Resolved closed
PLM2-16 Document_version_query Reference PLM 1.0.1 PLM 2.0b2 Resolved closed
PLM2-7 Relationship_predicate Reference PLM 1.0.1 PLM 2.0b2 Resolved closed
PLM2-19 Effectivity_query Reference PLM 1.0.1 PLM 2.0b2 Resolved closed
PLM2-18 Effectivity_assignment_query Reference PLM 1.0.1 PLM 2.0b2 Resolved closed
PLM2-13 Document_classification_query Reference PLM 1.0.1 PLM 2.0b2 Resolved closed
PLM2-12 Design_discipline_item_definition_query Reference PLM 1.0.1 PLM 2.0b2 Resolved closed
PLM2-15 Document_representation_query Reference: PLM 1.0.1 PLM 2.0b2 Resolved closed
PLM2-14 Document_query Reference PLM 1.0.1 PLM 2.0b2 Resolved closed
PLM2-11 Associated_project_query Reference PLM 1.0.1 PLM 2.0b2 Resolved closed
PLM2-10 Activity_resolved_request_query Reference PLM 1.0.1 PLM 2.0b2 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
PLM21-1 Class definition of Document_file is different between specification document and XSD PLM 2.0 PLM 2.1 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

Activity_query Reference

  • Key: PLM2_-10
  • Legacy Issue Number: 11206
  • Status: closed  
  • Source: PROSTEP AG ( Guido Adolphi)
  • Summary:

    PLM Services 2.0, mantis/07-03-01 Update, Chapter 9.7.2 Cause: The description "The Activity_authorization_query selects Activity objects." is wrong; no Activity_authorization_query is involved here. Furthermore, the semi-formal UML definition of the Activity_query is missing. New Specification Text: New description: The Activity_query selects Activity objects. The semi-formal UML definition of the Activity_query has to be added.

  • Reported: PLM 1.0.1 — Fri, 27 Jul 2007 04:00 GMT
  • Disposition: Resolved — PLM 2.0
  • Disposition Summary:

    Correct, change as proposed in summary.

  • Updated: Sat, 7 Mar 2015 04:22 GMT

Associated_process_property_query Reference

  • Key: PLM2_-9
  • Legacy Issue Number: 11204
  • Status: closed  
  • Source: PROSTEP AG ( Guido Adolphi)
  • Summary:

    PLM Services 2.0, mantis/07-03-01 Update, Chapter 9.7.23 and Figure 9.39 Cause The location step property_value_association_step is unable to select instances of Property_value_representation since inverse is implicitly set to false. Furthermore, location step property_value_representation_step is unable to select instances of Property_value since inverse is implicitly set to false. Finally, location step global_unit_step cannot select instances of type Unit since the named relationship global_unit is defined in Property_value_representation, but the result-set of the preceding location step does not contain any Property_value_representation at all. For consistency reasons the names of the mentioned location steps shall be adjusted. New Specification Text: The following is a literal description of the changes to be made in figure~9.39. The location steps property_value_association_step and property_value_representation_step must have the attribute inverse set to true in order to select instances of Property_value_representation and Property_value properly. Furthermore, the location step global_unit_step has to be the next step of location step property_value_association_step to select Unit instances by the named relationship Property_value_representation.global_unit. For consistency reasons location step property_value_association_step has to be renamed into inverse_property_value_representation_step (since the inverse location step selects instances of type Property_value_representation) and property_value_representation_step has to be renamed into inverse_property_value_step (since the inverse location step selects instances of type Property_value).

  • Reported: PLM 1.0.1 — Fri, 27 Jul 2007 04:00 GMT
  • Disposition: Resolved — PLM 2.0
  • Disposition Summary:

    Accepted as summarized.

  • Updated: Sat, 7 Mar 2015 04:20 GMT

informational model, object "Document_file"

  • Key: PLM2_-8
  • Legacy Issue Number: 12191
  • Status: closed  
  • Source: T-Systems Enterprise Services ( Hirel, Guillaume)
  • Summary:

    In the informational model, the object "Document_file" shall have the annotation: <info:base name="Identifiable"/> since it has an identifying attribute 'id' and potentially an 'id owner'. This annotation was part of the previous informational model => should be introduced again.

  • Reported: PLM 2.0b2 — Fri, 18 Jan 2008 05:00 GMT
  • Disposition: Resolved — PLM 2.0
  • Disposition Summary:

    Edit InformationalModel.xsd as described.

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

Section: InformationalModel.xsd last lines

  • Key: PLM2_-7
  • Legacy Issue Number: 12190
  • Status: closed  
  • Source: T-Systems Enterprise Services ( Hirel, Guillaume)
  • Summary:

    The last lines in the InformationalModel.xsd: <info:javaInfo javaBaseClassExtended="de.partmaster.xml.bind.adaptable.AdaptableJAXBObjectImplExtended"/> <info:javaInfo javaBaseClass="de.partmaster.xml.bind.adaptable.AdaptableJAXBObjectImpl"/> <info:javaInfo javaBaseName="InformationalModel"/> <info:javaInfo javaBasePackage="de.partmaster.plm.informational.model"/> shall be removed, since they are specific to the company Part Master GmbH

  • Reported: PLM 2.0b2 — Fri, 18 Jan 2008 05:00 GMT
  • Disposition: Resolved — PLM 2.0
  • Disposition Summary:

    Edit InformationalModel.xsd as described.

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

Section: InformationalModel.xsd

  • Key: PLM2_-6
  • Legacy Issue Number: 12189
  • Status: closed  
  • Source: T-Systems Enterprise Services ( Hirel, Guillaume)
  • Summary:

    In the informational model, explicit_transformation shall be renamed to explicit_transformation. Like all other objects, the first character shall be in uppercase

  • Reported: PLM 2.0b2 — Fri, 18 Jan 2008 05:00 GMT
  • Disposition: Resolved — PLM 2.0
  • Disposition Summary:

    The current InformationModel.xsd is already correct as noted in the summary. But, there is a problem with the explanation in Chapter 8.5.1.15 which shall not be a heading.

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

The function Get_download_URL shall be enhanced to download multiple files

  • Key: PLM2_-5
  • Legacy Issue Number: 12188
  • Status: closed  
  • Source: T-Systems Enterprise Services ( Hirel, Guillaume)
  • Summary:

    The function Get_download_URL shall be enhanced to download multiple files at once Proposal to change the declaration from: get_download_URL(in_file_uid UID, properties: ...): URL to: get_download_URL(in_file_uid UID[0..*], properties: ...): URL[0..*] The value of the properties apply to all files (I they shall get different values for the different files, single calls to get_download_URL with a single file shall be done). The number of URLs shall be equal to the number of given file_uids. If semanticaly defined by [0..*], the order of the URLs shall be the same as the order of the in_file_uids.

  • Reported: PLM 2.0b2 — Fri, 18 Jan 2008 05:00 GMT
  • Disposition: Resolved — PLM 2.0
  • Disposition Summary:

    Accepted as proposed.

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

The type Axis2_placement_3d shall be removed from the class PLM_container

  • Key: PLM2_-4
  • Legacy Issue Number: 12187
  • Status: closed  
  • Source: T-Systems Enterprise Services ( Hirel, Guillaume)
  • Summary:

    The type Axis2_placement_3d shall be removed from the class PLM_container, since its supertype Axis2_placement is already part of the PLM_container.

  • Reported: PLM 2.0b2 — Fri, 18 Jan 2008 05:00 GMT
  • Disposition: Resolved — PLM 2.0
  • Disposition Summary:

    Disposition: See issue 11618 for disposition

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

Informational Model (xsd)

  • Key: PLM2_-3
  • Legacy Issue Number: 12164
  • Status: closed  
  • Source: PDTec AG ( Günter Staub)
  • Summary:

    There is a problem with Cartesian_point element. In InformationalModel it is included in the PLM_container but in its inheritance it does not inherit from PLM_root_object. Its grandparent inhertis from PLM_object. All other objects that reside directly under PLM_container inherit from PLM_root_object.

  • Reported: PLM 2.0b2 — Tue, 8 Jan 2008 05:00 GMT
  • Disposition: Resolved — PLM 2.0
  • Disposition Summary:

    Accepted as proposed. Change information model object inheritance as described in summary

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

Section: 8.1

  • Key: PLM2_-2
  • Legacy Issue Number: 11645
  • Status: closed  
  • Source: PROSTEP AG ( Guido Adolphi)
  • Summary:

    In Figure 8.16 (PLM_base) both associations PLM_message.PLM_context and PLM_message.PLM_core_container shall be denoted as compositions (since they are defined as such in 8.1.1.4) instead of simple directed associations

  • Reported: PLM 2.0b2 — Tue, 6 Nov 2007 05:00 GMT
  • Disposition: Resolved — PLM 2.0
  • Disposition Summary:

    In Figure 8.16 (PLM_base) both associations PLM_message.PLM_context and PLM_message.PLM_core_container shall be denoted as compositions (since they are defined as such in 8.1.1.4) instead of simple directed associations

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

Section: 9.7.39

  • Key: PLM2_-1
  • Legacy Issue Number: 11624
  • Status: closed  
  • Source: T-Systems Enterprise Services ( Hirel, Guillaume)
  • Summary:

    The parameters Add_period, Add_start_definition and Add_end_definition are missing (refer to the WSDL). Add_concerned_organization should be also added as parameter and in the WSDL. More generally, the handling of WSDL-Attribute of kind: type="xsd:IDREFS" minOccurs="0" is not handled in an homogen way throughout the specification: . some of them are retrieved by a dedicated specific_query (for example work_request_scope_query) . some of them are retrieved automatically when the object is retrieved (for example Associated_aproval_query always retrieve is_approved_by and scope) . some of them are retrieved if some parameter of kind add_... is set to TRUE (for example in effectivity_query) . some of them are not retrieved at all, since they are not handled in the 3 ways described above. These are for example: activity.concerned_organization activity.supplying_organization cartesian_coordinate_space.unit_of_values ddid.additional_context document_property.languages document_file.external_id_and_location product_component.is_influenced_by product_component.is_relevant_for product_function.is_relevant_for property.allowed_unit work_request.notified_person Proposal: define add_parameter (analog to effectivity_query) for simple objects which do not imply the retrieval of too many objects. For the other ones: define a dedicated specific query that may be combined with further queries to complete the result

  • Reported: PLM 2.0b2 — Fri, 19 Oct 2007 04:00 GMT
  • Disposition: Resolved — PLM 2.0
  • Disposition Summary:

    Add the requested three attributes Add_period, Add_start_definition and Add_end_definition to the signature of the Effectivity_query.

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

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

XSD files lack default namespace

  • Key: PLM21-2
  • Legacy Issue Number: 15576
  • Status: closed  
  • Source: 88solutions ( Mr. Manfred R. Koethe)
  • Summary:

    XSD files lack default namespace

  • Reported: PLM 2.0 — Thu, 23 Sep 2010 04:00 GMT
  • Disposition: Resolved — PLM 2.1
  • Disposition Summary:

    The RTF agrees that the xsd files require corrections of the namespace declarations to validate. The RTF takes this opportunity to convert the XSD files to the new namespace convention of the OMG. This requires corresponding changes in the WSDL files too.

  • Updated: Fri, 6 Mar 2015 23:15 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

PLM 2 FTF Security chapter issue

  • Key: PLM2-43
  • Legacy Issue Number: 11816
  • Status: closed  
  • Source: Anonymous
  • Summary:

    beeing in charge of the security chapter of the PLM Services, we overworked the chapter 10.7 according to our latest experiences.
    This overwork actually does not invalid any statement of the previous version of the security chapter, but we completed it with more examples, a picture and some additional explanations.

    Since it would be very difficult to describe all changes in single issues, we prefer to send it the whole pack as 'one' issue, which is the attached MS Word document. All changes are documented using MS Word features, so that the differences from the old to the new text are clearly visible.

  • Reported: PLM 1.0.1 — Wed, 24 Oct 2007 04:00 GMT
  • Disposition: Resolved — PLM 2.0b2
  • Disposition Summary:

    New text for chapter security

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

Attribute Description for Entities Document_file and Person_in_organization

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

    To align the PLM Services Informational Model with the STEP AP 214 Data Model
    the Attribute "description" of type "Translatable_string" should be added
    to the entities "Document_file" and "Person_in_organization_relationship".

  • Reported: PLM 1.0.1 — Fri, 18 Jan 2008 05:00 GMT
  • Disposition: Resolved — PLM 2.0b2
  • Disposition Summary:

    Add this new attributes added in STEP AP214 Rev 3.

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

Chapter 8.9.1

  • Key: PLM2-6
  • Legacy Issue Number: 11096
  • Status: closed  
  • Source: Zentrum fuer Graphische Datenverarbeitung e.V. ( Steffen Nowacki)
  • Summary:

    Document mantis/07-03-01
    Chapter 8.9.1

    Specification of class Person_in_organization_relationship is missing
    for full STEP AP214 CC21 conformance.

  • Reported: PLM 1.0.1 — Fri, 8 Jun 2007 04:00 GMT
  • Disposition: Resolved — PLM 2.0b2
  • Disposition Summary:

    Add Person_in_organization_relationship in Chapter 8.9.1

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

Specification of Relationship_predicate

  • Key: PLM2-5
  • Legacy Issue Number: 11088
  • Status: closed  
  • Source: Zentrum fuer Graphische Datenverarbeitung e.V. ( Steffen Nowacki)
  • Summary:

    PLM Services 2.0
    Document mantis/07-03-01
    Chapter 9.4.7

    Specification of Relationship_predicate

    The Specification of the Relationship_predicate is not precise and need some bug fixes and additions:

    1. ALL constraints must be fullfilled.
    2. The attribute 'predicate' is now named 'related_object_predicate'
    3. A new constraint for the attribute 'relating_object_predicate' has to be added.

    Here is the new Text:

    An object fulfill a Relationship_predicate constraint if it fulfill all the following partial constraints:

    • The object fulfill all the Predicate instances referenced by the relationship relating_object_predicate of the Relationship_predicate.

    • The object is related with another object that fulfill all the Predicate instances referenced by the relationship related_object_predicate of the Relationship_predicate.

    • If the value of the attribute inverse of the Relationship_predicate is not true and if the attribute role_name is set, the role name of the other object in the relationship must be equals to the value of the attribute role_name of the Relationship_predicate.

    • If the value of the attribute inverse of the Relationship_predicate is true and if the attribute role_name is set, the role name of this object in the relationship must be equals to the value of the attribute role_name of the Relationship_predicate.

    • If the attribute role_declaring_type_name is set, the relationship must be defined in a type which name is equals to the value of the attribute role_declaring_type_name.

  • Reported: PLM 1.0.1 — Thu, 31 May 2007 04:00 GMT
  • Disposition: Resolved — PLM 2.0b2
  • Disposition Summary:

    Disposition: See issue 11202 for disposition

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

PLM 2 FTF -- Editorial issues

  • Key: PLM2-4
  • Legacy Issue Number: 10973
  • Status: closed  
  • Source: Object Management Group ( Andrew Watson)
  • Summary:

    E1. Section "0.5 Proof of Concept"

    If this section gets transferred to the Final Adopted Specification, please fix the following:

    E1.1 Every instance of "it's" (with an apostrophe) should be "its" (no apostrophe). 3 instances.

    E1.2 "... evaluated in a interaction scenario ..." should be "... evaluated in an interaction scenario ..."

    E2. Section "0.8 Edit Directions Against PLM Services V1.0 (dtc/2005-03-08)"

    As we discussed at the AB meeting, this title should be "Changes from PLM Services V1.0 (dtc/2005-03-08)" (or some similar language).

    E3. Section "3 Normative References"

    The document number for Meta Object Facility (MOF) 2.0 XMI Mapping Specification contains a typo - "OMG Document formal.-5-09-01" should be "OMG Document formal/05-09-01".

    E4. Section "7.2.5.3 Partner role descriptions"

    The table contains a superfluous hyphen in "person" in one role description "per-son".

    E5. Section "7.2.11.3 Process definition"

    Contains mis-hyphenation of "example" ("ex-ample").

    E6. Figures 7-11, 7-12, 7-13, 7-14 garbled in the PDF

    (But I believe this was fixed in the errata during the meeting).

    E7. Section "7.2.2 UML package"

    The phrase "XML provides an own mechanism ..." should be "XML provides its own mechanism ..."

    E8. Section "7.2 UML profile for XML Schema (Informative)"

    The phrase "An UML profile ..." occurs 5 times on pages 371, 376 & 378. Should be "a UML profile".

    E9. Section "7.2 UML profile for XML Schema (Informative)"

    The phrase "... stereotypes, tagged value called properties ...." should be "... stereotypes, tagged values called properties ....".

  • Reported: PLM 1.0.1 — Wed, 25 Apr 2007 04:00 GMT
  • Disposition: Resolved — PLM 2.0b2
  • Disposition Summary:

    change as described in the summary

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

Section "7.2.5.7 Constraints and assertions" -- none defined at the moment

  • Key: PLM2-3
  • Legacy Issue Number: 10972
  • Status: closed  
  • Source: Object Management Group ( Andrew Watson)
  • Summary:

    Issue name: "None are defined at the Moment"

    Contains the text "At the moment none are defined." Either this section should be removed from the specification, or at the very least the words "At the moment" should be removed.

  • Reported: PLM 1.0.1 — Wed, 25 Apr 2007 04:00 GMT
  • Disposition: Resolved — PLM 2.0b2
  • Disposition Summary:

    Delete all empty constraints and assertions chapters from the specification document.

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

Section "7 Use Cases" - no flow diagram exists

  • Key: PLM2-1
  • Legacy Issue Number: 10970
  • Status: closed  
  • Source: Object Management Group ( Andrew Watson)
  • Summary:

    This section contains several sections entitled "Process Flow Diagram", containing the text "At the moment no flow diagram exists". I suggest these sections be removed from the specification, or process diagrams supplied. At the very least, the words "At the moment" should be removed.

  • Reported: PLM 1.0.1 — Wed, 25 Apr 2007 04:00 GMT
  • Disposition: Resolved — PLM 2.0b2
  • Disposition Summary:

    Delete all empty Process Flow Diagram chapters from the specification document.

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

Section "7.2.4.9 Topics under discussion"

  • Key: PLM2-2
  • Legacy Issue Number: 10971
  • Status: closed  
  • Source: Object Management Group ( Andrew Watson)
  • Summary:

    Issue name: "Authorization under discussion"

    Contains the text "The topic "Authorization and Network Security" is under discussion and will be documented in a separate specification". This section should be removed from the specification.

  • Reported: PLM 1.0.1 — Wed, 25 Apr 2007 04:00 GMT
  • Disposition: Resolved — PLM 2.0b2
  • Disposition Summary:

    Change as described in summary.

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

Project_assignment_query Reference

  • Key: PLM2-27
  • Legacy Issue Number: 11224
  • Status: closed  
  • Source: PROSTEP AG ( Guido Adolphi)
  • Summary:

    PLM Services 2.0, mantis/07-03-01 Update, Chapter 9.7.63 Cause: Location step instance project_assignment_step is incorrect. The type Project_information_select given by attribute role_declaring_type_name does not provide the named relationship project_assignment as given by the attribute role_name. Furthermore, an additional Location_step instance is needed in order to select instances of Project_information_select filtered by the existing Type_predicate instance. New Specification Text: Since the specific query is called Project_assignment_query the intended semantics is to select instances of type Project_assignment for the identical named relationship of instances of type Project. From this it follows that Location_step instance project_assignment_step has to be assigned attribute values as follows: * attribute role_declaring_type_name has to be set to Project and * attribute role_name remains project_assignment. Furthermore, Location_step instance project_assignment_step has to be assigned another Location_step instance named project_information_select_step by the named relationship next_query with the following attribute values: * attribute role_declaring_type_name has to be set to Project_assignment and * attribute role_name remains is_applied_to. Finally, the existing instance of Alternative_predicate assigned to Location_step instance project_assignment_step by the named relationship related_object_predicate has to be assigned (i.e. moved) to Location_step instance project_information_select_step by the identical named relationship.

  • Reported: PLM 1.0.1 — Fri, 27 Jul 2007 04:00 GMT
  • Disposition: Resolved — PLM 2.0b2
  • Disposition Summary:

    Since the specific query is called Project_assignment_query the intended semantics is to select instances of type Project_assignment for the identical named relationship of instances of type Project. From this it follows that Location_step instance project_assignment_step has to be assigned attribute values as follows:
    · attribute role_declaring_type_name has to be set to Project and
    · attribute role_name remains project_assignment.
    Furthermore, Location_step instance project_assignment_step has to be assigned another Location_step instance named project_information_select_step by the named relationship next_query with the following attribute values:
    · attribute role_declaring_type_name has to be set to Project_assignment and
    · attribute role_name remains is_applied_to.
    Finally, the existing instance of Alternative_predicate assigned to Location_step instance project_assignment_step by the named relationship related_object_predicate has to be assigned (i.e. moved) to Location_step instance project_information_select_step by the identical named relationship.

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

Proxy Queries Conformance Point Reference

  • Key: PLM2-26
  • Legacy Issue Number: 11223
  • Status: closed  
  • Source: PROSTEP AG ( Guido Adolphi)
  • Summary:

    PLM Services 2.0, mantis/07-03-01 Update, Chapter 9.6 and Figure 9.16 Cause: Cardinality of aggregation from PLM_reference_feature to PLM_root_object is wrong. Furthermore, the directed relationships from PLM_containment_feature and PLM_reference_feature to PLM_root_object are wrong; both relationships have to point to PLM_object. Additional types defined by the proxy queries conformance point (including PLM_int_feature, PLM_double_feature, etc.) are missing as well. New Specification Text: Figure 9.16: The cardinality of the aggregation from PLM_reference_feature to PLM_root_object has to be 1..* at the directed end-point toward PLM_root_object. Furthermore, the directed relationships from PLM_containment_feature and PLM_reference_feature to PLM_root_object have to point to PLM_object. Finally, the missing types PLM_string_feature, PLM_boolean_feature, PLM_int_feature and PLM_double_feature have to be included.

  • Reported: PLM 1.0.1 — Fri, 27 Jul 2007 04:00 GMT
  • Disposition: Resolved — PLM 2.0b2
  • Disposition Summary:

    Resolution:
    Figure 9.16: The cardinality of the aggregation from PLM_reference_feature to PLM_root_object has to be 0..* at the directed end-point toward PLM_root_object. Furthermore, the directed relationships from PLM_containment_feature and PLM_reference_feature to PLM_root_object have to point to PLM_object. Finally, the missing types PLM_string_feature, PLM_boolean_feature, PLM_int_feature and PLM_double_feature have to be included.

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

Chapter 9.7.49, SpecificQueries.xsd, Chapter 9.8.7

  • Key: PLM2-42
  • Legacy Issue Number: 11638
  • Status: closed  
  • Source: PROSTEP AG ( Guido Adolphi)
  • Summary:

    PLM Services 2.0
    mantis/07-03-01 Update
    March 29th 2007

    Chapter 9.7.49, SpecificQueries.xsd, Chapter 9.8.7

    Author:

    Guido Adolphi, PROSTEP AG

    Subject:

    1. Issue 11232 shall be rejected, reason: technically incorrect
    2. New Issue:
    a. Item_use_query shall obtain status "deprecated" (both in the specification and SpecificQueries.xsd)
    b. Assembly_structure_query shall be removed from SpecificQueries.xsd
    c. Re-definition of chapter 9.8.7 Item_traversal_query as specified below

    New specification Text for Chapter 9.8.7:

    The Item_traversal_query traverses from a Design_discipline_item_definition object to the next higher or next lower Design_discipline_item_definition objects in an assembly structure.

    Parameters

    · uid: UID
    · inverse_direction: Boolean[0..1]

  • Reported: PLM 1.0.1 — Thu, 1 Nov 2007 04:00 GMT
  • Disposition: Resolved — PLM 2.0b2
  • Disposition Summary:

    Part c accepted as proposed in summary.

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

remove composition 'axis2_placement_3d' from type 'PLM_container

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

    because type Axis2_placement_3d is a derived type of Axis_placement
    and PLM_container has a composition for type Axis_placement
    and so there is no need for the 'axis2_placement_3d' composition.

  • Reported: PLM 1.0.1 — Tue, 16 Oct 2007 04:00 GMT
  • Disposition: Resolved — PLM 2.0b2
  • Disposition Summary:

    No Data Available

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

Join operations 'query' and 'export_data' into one single operation

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

    To reduce complexity of service interfaces the operations

    query(query: PLM_query)

    and

    export_data(PLM_query query, properties: PLM_property[0..*])

    should be joined to one single operation

    query(query: PLM_query, properties: PLM_property[0..*])

    with the semantics of actual 'query' operation if the 'properties' parameter is empty and
    with the semantics of the actual 'export_data' operation otherwise.

  • Reported: PLM 1.0.1 — Tue, 16 Oct 2007 04:00 GMT
  • Disposition: Resolved — PLM 2.0b2
  • Disposition Summary:

    Merge the two operations into one by deleting the more specialized export_data operation from chapter 9.2.6.

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

Item_traversal_query Reference

  • Key: PLM2-35
  • Legacy Issue Number: 11232
  • Status: closed  
  • Source: PROSTEP AG ( Guido Adolphi)
  • Summary:

    PLM Services 2.0, mantis/07-03-01 Update, Chapter 9.8.7 and Figure 9.95 Cause: The two instances of type Conditional_query named item_use_query and assembly_structure_query use the same boolean value for their attribute condition. Hence, both instances of type Conditional_query shall be combined into one single Conditional_query instance. Furthermore, the type Assembly_structure_query is undefined in the computational model. Instead Item_instance_query shall be used. New Specification Text: In figure 9.95 the instances of type Conditional_query named item_use_query and assembly_structure_query have to be combined into one single Conditional_query instance named item_traversal_query. The named relationship when_true has to be assigned the existing Item_use_query instance, and the named relationship when_not_true has to be assigned an instance of type Item_instance_query. The instance of type Assembly_structure_query has to be removed.

  • Reported: PLM 1.0.1 — Fri, 27 Jul 2007 04:00 GMT
  • Disposition: Resolved — PLM 2.0b2
  • Disposition Summary:

    In figure 9.95 the instances of type Conditional_query named item_use_query and assembly_structure_query have to be combined into one single Conditional_query instance named item_traversal_query. The named relationship when_true has to be assigned the existing Item_use_query instance, and the named relationship when_not_true has to be assigned an instance of type Item_instance_query. The instance of type Assembly_structure_query has to be removed.

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

Work_request_scope_query Reference

  • Key: PLM2-34
  • Legacy Issue Number: 11231
  • Status: closed  
  • Source: PROSTEP AG ( Guido Adolphi)
  • Summary:

    PLM Services 2.0, mantis/07-03-01 Update, Chapter 9.7.71 and Figure 9.87 Cause: For consistency reasons the Location_step instance work_request_relationship_step has to be renamed into scope_step. New Specification Text: In figure 9.87 the Location_step instance work_request_relationship_step has to be renamed into scope_step.

  • Reported: PLM 1.0.1 — Fri, 27 Jul 2007 04:00 GMT
  • Disposition: Resolved — PLM 2.0b2
  • Disposition Summary:

    Resolution:
    In figure 9.87 the Location_step instance work_request_relationship_step has to be renamed into scope_step.

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

Join PLM_properties_descriptors query operations

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

    Join operations for query 'PLM_properties_descriptors' of an operation with an 'properties' parameter:

    get_general_connection_properties_descriptors()
    get_message_connection_properties_descriptors()
    get_export_data_properties_descriptors()
    ...

    into one operation:

    get_operation_properties_descriptors(operation_name: Strring)

    to reduce complexity of service interfaces

  • Reported: PLM 1.0.1 — Tue, 16 Oct 2007 04:00 GMT
  • Disposition: Resolved — PLM 2.0b2
  • Disposition Summary:

    Delete get_export_data_properties_descriptors() only.

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

General_detail_query Reference

  • Key: PLM2-36
  • Legacy Issue Number: 11233
  • Status: closed  
  • Source: PROSTEP AG ( Guido Adolphi)
  • Summary:

    PLM Services 2.0, mantis/07-03-01 Update, Chapter 9.8.1 and Figure 9.89 Cause: The parameter listing of the General_detail_query is erroneous regarding the parameter uid. The General_detail_query is meant to select details for a set of objects identified by their identifying attribute uid. As figure~9.89 shows, the set of uids will be passed to the Objects_by_uid_query instance equivalent_specific_query_instance. But the General_detail_query provides only a parameter called uid with cardinality 1..1 while the specialization General_detail_query in figure~9.89 correctly introduces a parameter named uids with cardinality 1..*. New Specification Text: The parameter list of General_detail_query within the description text has to correct the declaration of parameter uid: UID into uids: UID[1..*].

  • Reported: PLM 1.0.1 — Fri, 27 Jul 2007 04:00 GMT
  • Disposition: Resolved — PLM 2.0b2
  • Disposition Summary:

    The parameter list of General_detail_query within the description text has to correct the declaration of parameter uid: UID into uids: UID[1..*].

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

Event_reference_query Reference

  • Key: PLM2-31
  • Legacy Issue Number: 11228
  • Status: closed  
  • Source: PROSTEP AG ( Guido Adolphi)
  • Summary:

    PLM Services 2.0, mantis/07-03-01 Update, Chapter 9.7.40 and Figure 9.56 Cause: The Location_path instance assigned to the named relationship first_query of the Concatenated_query instance equivalent_query has no instance-name. The same holds for the first Location_step instance assigned to the named relationship first_step. New Specification Text: In figure 9.56 the Location_path instance assigned to the named relationship first_query of the Concatenated_query instance equivalent_query has to be named event_reference_path, and the Location_step instance assigned to the named relationship first_step of that Location_path instance has to be named event_reference_step.

  • Reported: PLM 1.0.1 — Fri, 27 Jul 2007 04:00 GMT
  • Disposition: Resolved — PLM 2.0b2
  • Disposition Summary:

    In figure 9.56 the Location_path instance assigned to the named relationship first_query of the Concatenated_query instance equivalent_query has to be named event_reference_path, and the Location_step instance assigned to the named relationship first_step of that Location_path instance has to be named event_reference_step.

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

Design_discipline_item_definition_query Reference:

  • Key: PLM2-30
  • Legacy Issue Number: 11227
  • Status: closed  
  • Source: PROSTEP AG ( Guido Adolphi)
  • Summary:

    PLM Services 2.0, mantis/07-03-01 Update, Chapter 9.7.30 and Figure 9.46 Cause: For consistency reasons the Location_step instance design_discipline_definition_step has to be renamed into design_discipline_item_definition_step according to the identical element of the informational model. New Specification Text: In figure 9.46 the Location_step instance design_discipline_definition_step has to be renamed into design_discipline_item_definition_step.

  • Reported: PLM 1.0.1 — Fri, 27 Jul 2007 04:00 GMT
  • Disposition: Resolved — PLM 2.0b2
  • Disposition Summary:

    In figure 9.46 the Location_step instance design_discipline_definition_step has to be renamed into design_discipline_item_definition_step.

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

Add optional generic property list parameter to some service operations

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

    Check the operations without a generic property list parameter if it make sense to add such a parameter.
    to allow more system specific functionality via the PLM Services interfaces

    For instance in interface PLM_general_connection
    delete(uids : UID[1..*], properties: PLM_property[0..*])
    the parameter properties can control the recurrsive removal of whole structures.

    or get_download_URL(uid: UID, , properties: PLM_property[0..*])
    the parameter properties can control the protocol of the URL (ftp, http, ...), of the result.

    If the PLM Services interfaces are used by more specific applications the product life cycle,
    for instance project management or engineering change management, they can specify
    conformant property values of the generic and optional properties parameters for their domain

  • Reported: PLM 1.0.1 — Tue, 16 Oct 2007 04:00 GMT
  • Disposition: Resolved — PLM 2.0b2
  • Disposition Summary:

    No Data Available

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

Join operations 'write' and 'import_data' into one single operation

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

    To reduce complexity of service interfaces the operations

    write(container: PLM_core_container, fill_result_list: boolean)

    and

    import_data(container: PLM_core_container, properties: PLM_property[0..*])

    should be joined to one single operation

    write(container: PLM_core_container, fill_result_list: boolean, properties: PLM_property[0..*])

    with the semantics of actual 'write' operation if the 'properties' parameter is empty and
    with the semantics of the actual 'import_data' operation otherwise.

  • Reported: PLM 1.0.1 — Tue, 16 Oct 2007 04:00 GMT
  • Disposition: Resolved — PLM 2.0b2
  • Disposition Summary:

    Merge the two operations into one by deleting the more specialized import_data operation from chapter 9.2.6.

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

Generic Queries Conformance Point Reference

  • Key: PLM2-25
  • Legacy Issue Number: 11222
  • Status: closed  
  • Source: PROSTEP AG ( Guido Adolphi)
  • Summary:

    PLM Services 2.0, mantis/07-03-01 Update, Chapter 9.4 and Figures 9.13 and 9.14 Cause: Some cardinalities are wrong in the definition of Location_path and Location_step, and compositions are missing in the definition of Relationship_predicate. New Specification Text: Figure 9.13: The reflexive composition +next_step of Location_step has to be assigned cardinality 0..* at the directed end-point toward Location_step. Figure 9.14: The compositions of related_object_predicate and relating_object_predicate of Relationship_predicate have to be added.

  • Reported: PLM 1.0.1 — Fri, 27 Jul 2007 04:00 GMT
  • Disposition: Resolved — PLM 2.0b2
  • Disposition Summary:

    Figure 9.13: The reflexive composition +next_step of Location_step has to be assigned cardinality 0..* at the directed end-point toward Location_step. Figure 9.14: The compositions of related_object_predicate and relating_object_predicate of Relationship_predicate have to be added.

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

Compositions in the Computational Model Reference

  • Key: PLM2-24
  • Legacy Issue Number: 11221
  • Status: closed  
  • Source: PROSTEP AG ( Guido Adolphi)
  • Summary:

    PLM Services 2.0, mantis/07-03-01 Update, Chapters 9.3, 9.4, 9.7, 9.8 and Figures 9.12, 9.13, all figures from chapters 9.7 and 9.8 Cause: Throughout the computational model compositions are either missing or denoted as aggregations. New Specification Text: Figure 9.12: Composition from Recursive_query to PLM_query with role-name query is missing. Figure 9.13: All aggregations have to be denoted as compositions. All figures from chapter 9.7: All aggregations have to be denoted as compositions. All figures from chapter 9.8: All aggregations have to be denoted as compositions.

  • Reported: PLM 1.0.1 — Fri, 27 Jul 2007 04:00 GMT
  • Disposition: Resolved — PLM 2.0b2
  • Disposition Summary:

    No Data Available

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

Configuration_query Reference

  • Key: PLM2-29
  • Legacy Issue Number: 11226
  • Status: closed  
  • Source: PROSTEP AG ( Guido Adolphi)
  • Summary:

    PLM Services 2.0, mantis/07-03-01 Update, Chapter 9.7.28 and Figure 9.44 Cause: In Location_step instance configuration_step the type Configuration_item_select given by the attribute role_declaring_type_name does not exist in the informational model. Instead the attribute role_declaring_type_name has to be set to Configured_item_select. New Specification Text: In figure 9.44 attribute role_declaring_type_name of Location_step instance configuration_step has to be set to Configured_item_select

  • Reported: PLM 1.0.1 — Fri, 27 Jul 2007 04:00 GMT
  • Disposition: Resolved — PLM 2.0b2
  • Disposition Summary:

    In figure 9.44 attribute role_declaring_type_name of Location_step instance configuration_step has to be set to Configured_item_select

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

Associated_file_query Reference:

  • Key: PLM2-28
  • Legacy Issue Number: 11225
  • Status: closed  
  • Source: PROSTEP AG ( Guido Adolphi)
  • Summary:

    PLM Services 2.0, mantis/07-03-01 Update, Chapter 9.7.19 and Figure 9.35 Cause: Type Document_representation has no named relationship file. Digital_document--a derivation of Document_representation--provides the named relationship file. New Specification Text: In figure 9.35 Location_step instance associated_file_step has to be assigned attribute role_declaring_type_name to value Digital_document.

  • Reported: PLM 1.0.1 — Fri, 27 Jul 2007 04:00 GMT
  • Disposition: Resolved — PLM 2.0b2
  • Disposition Summary:

    In figure 9.35 Location_step instance associated_file_step has to be assigned attribute role_declaring_type_name to value Digital_document.

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

Product_structure_query Reference

  • Key: PLM2-33
  • Legacy Issue Number: 11230
  • Status: closed  
  • Source: PROSTEP AG ( Guido Adolphi)
  • Summary:

    PLM Services 2.0, mantis/07-03-01 Update, Chapter 9.7.62 and Figure 9.78 Cause: For consistency reasons the Location_step instance product_structure_location_step has to be renamed into product_structure_relationship_step according to the identical element of the informational model. New Specification Text: In figure 9.78 the Location_step instance product_structure_location_step has to be renamed into product_structure_relationship_step.

  • Reported: PLM 1.0.1 — Fri, 27 Jul 2007 04:00 GMT
  • Disposition: Resolved — PLM 2.0b2
  • Disposition Summary:

    In figure 9.78 the Location_step instance product_structure_location_step has to be renamed into product_structure_relationship_step.

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

Item_instance_query Reference

  • Key: PLM2-32
  • Legacy Issue Number: 11229
  • Status: closed  
  • Source: PROSTEP AG ( Guido Adolphi)
  • Summary:

    PLM Services 2.0, mantis/07-03-01 Update, Chapter 9.7.42 and Figure 9.63 Cause: The type Product_information as declared in the Location_step instance item_instance_step2 by attribute role_declaring_type_name does not exist in the informational model. Instead attribute role_declaring_type_name has to be set to Product_identification. New Specification Text: In figure 9.63 the attribute role_declaring_type_name of Location_step instance item_instance_step2 has to be set to Product_identification.

  • Reported: PLM 1.0.1 — Fri, 27 Jul 2007 04:00 GMT
  • Disposition: Resolved — PLM 2.0b2
  • Disposition Summary:

    In figure 9.63 the attribute role_declaring_type_name of Location_step instance item_instance_step2 has to be set to Product_identification.

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

Sort_predicate Reference

  • Key: PLM2-9
  • Legacy Issue Number: 11205
  • Status: closed  
  • Source: PROSTEP AG ( Guido Adolphi)
  • Summary:

    PLM Services 2.0, mantis/07-03-01 Update, Chapter 9.4.10 Cause: Some editorial and spelling mistakes. The attribute Maximum_number determines the maximum number of objects selected from the sorted initial node-set of a location step. However, Start_index+Maximum_number selects one more object as intended. Start_index+Maximum_number-1 is appropriate for the semantics of Sort_predicate. New Specification Text: The Sort_predicate arranges objects of the initial node-set of a Location_step by the attribute specified by the attribute attribute_name of the Sort_predicate. The type of the attribute specified by attribute_name has to be a type for which a greater-than and less-than relation is defined. The default sort order is ascending order. If the attribute Descending_order of the Sort_predicate is set to true the selected objects are sorted in descending order. If the attribute Start_index is set all objects of the sorted node-set before the start index are filtered out. The default start index is 0. If the attribute Maximum_number is set objects before and after the closed range [Start_index, Start_index+Maximum_number-1] are filtered out.

  • Reported: PLM 1.0.1 — Fri, 27 Jul 2007 04:00 GMT
  • Disposition: Resolved — PLM 2.0b2
  • Disposition Summary:

    Correct, change according to summary.

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

Associated_item_property_query Reference

  • Key: PLM2-8
  • Legacy Issue Number: 11203
  • Status: closed  
  • Source: PROSTEP AG ( Guido Adolphi)
  • Summary:

    PLM Services 2.0, mantis/07-03-01 Update, Chapter 9.7.21 and Figure 9.37 Cause: The location step property_value_association_step is unable to select instances of Property_value_representation since inverse is implicitly set to false. Furthermore, location step property_value_representation_step is unable to select instances of Property_value since inverse is implicitly set to false. Finally, location step global_unit_step cannot select instances of type Unit since the named relationship global_unit is defined in Property_value_representation, but the result-set of the preceding location step does not contain any Property_value_representation at all. For consistency reasons the names of the mentioned location steps shall be adjusted. New Specification Text: The following is a literal description of the changes to be made in figure~9.37. The location steps property_value_association_step and property_value_representation_step must have the attribute inverse set to true in order to select instances of Property_value_representation and Property_value properly. Furthermore, the location step global_unit_step has to be the next step of location step property_value_association_step to select Unit instances by the named relationship Property_value_representation.global_unit. For consistency reasons location step property_value_association_step has to be renamed into inverse_property_value_representation_step (since the inverse location step selects instances of type Property_value_representation) and property_value_representation_step has to be renamed into inverse_property_value_step (since the inverse location step selects instances of type Property_value).

  • Reported: PLM 1.0.1 — Fri, 27 Jul 2007 04:00 GMT
  • Disposition: Resolved — PLM 2.0b2
  • Disposition Summary:

    For consistency reasons the names of the mentioned location steps shall be adjusted.

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

Product_identification_query Reference

  • Key: PLM2-23
  • Legacy Issue Number: 11220
  • Status: closed  
  • Source: PROSTEP AG ( Guido Adolphi)
  • Summary:

    PLM Services 2.0, mantis/07-03-01 Update, Chapter 9.7.61 and Figure 9.77 Cause: Composition between Location_path and Location_step instances is missing. No role-names given for predicates. New Specification Text: In figure 9.77 a composition has to be included between the instances of Location_path and Location_step. The role-name of this composition has to be +first_step. Furthermore, all compositions to predicates have to be assigned the role-name +related_object_predicate.

  • Reported: PLM 1.0.1 — Fri, 27 Jul 2007 04:00 GMT
  • Disposition: Resolved — PLM 2.0b2
  • Disposition Summary:

    In Figure 9.77 a composition has to be included between the instances of Location_path and Location_step. The role-name of this composition has to be +first_step. Furthermore, all compositions to predicates have to be assigned the role-name +related_object_predicate.

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

Item_use_query Reference

  • Key: PLM2-22
  • Legacy Issue Number: 11219
  • Status: closed  
  • Source: PROSTEP AG ( Guido Adolphi)
  • Summary:

    PLM Services 2.0, mantis/07-03-01 Update, Chapter 9.7.49 and Figure 9.65 Cause: Item_use_query does not provide an attribute called maximum_resursion_number---this is only provided by the Recursive_query. Furthermore, the Location_step instance item_instance_step selects all Item_instance instances no matter if they are related (i.e. used) by another Item_instance instance via Item_definition_instance_relationship elements or not. In order to constrain the set of selected Item_instance instances with respect to the semantics intended by the Item_use_query, an additional Relationship_predicate has to be added to Location_step instance item_instance_step. New Specification Text: In figure 9.65 the Location_step instance item_instance_step has to be added a Relationship_predicate to the named relationship related_object_predicate of the Location_step. The predicate instance has to be named inverse_item_definition_instance_relationship_predicate with its attributes initialized as follows: * attribute inverse is set to true, * attribute role_name is set to related and * attribute role_declaring_type_name is set to Item_definition_instance_relationship. Finally, for consistency reasons, the Location_step instance inverse_assembly_component_relationship_step has to be renamed to inverse_item_definition_instance_relationship_step.

  • Reported: PLM 1.0.1 — Fri, 27 Jul 2007 04:00 GMT
  • Disposition: Resolved — PLM 2.0b2
  • Disposition Summary:

    In Figure 9.65 the Location_step instance item_instance_step has to be added a Relationship_predicate to the named relationship related_object_predicate of the Location_step. The predicate instance has to be named inverse_item_definition_instance_relationship_predicate with its attributes initialized as follows:
    · attribute inverse is set to true,
    · attribute role_name is set to related and
    · attribute role_declaring_type_name is set to Item_definition_instance_relationship
    Finally, for consistency reasons, the Location_step instance inverse_assembly_component_relationship_step has to be renamed to inverse_item_definition_instance_relationship_step

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

Item_classification_hierarchy_query Reference

  • Key: PLM2-21
  • Legacy Issue Number: 11218
  • Status: closed  
  • Source: PROSTEP AG ( Guido Adolphi)
  • Summary:

    PLM Services 2.0, mantis/07-03-01 Update, Chapter 9.7.45 and Figure 9.61 Cause: The Conditional_query has no relationships to Location_step but to PLM_query. The Location_path instances are missing as glue between the instances of Conditional_query and Location_step. Furthermore, Location_step instance inverse_item_classification_hierarchy_step wants to select elements by the no named relationship related (denoted by role_name="related") from Specific_item_classification_hierarchy elements. However, Specific_item_classification_hierarchy only provides the named relationship sub_classification. New Specification Text: In figure 9.61 two Location_path instances have to be included each referencing one of the existing Location_step instances. The Conditional_query instance equivalent_query_instance has to refer to the new Location_path instances instead. In Location_step instance inverse_item_classification_hierarchy_step the attribute role_name has to be set sub_classification.

  • Reported: PLM 1.0.1 — Fri, 27 Jul 2007 04:00 GMT
  • Disposition: Resolved — PLM 2.0b2
  • Disposition Summary:

    In figure 9.61 two Location_path instances have to be included each referencing one of the existing Location_step instances. The Conditional_query instance equivalent_query_instance has to refer to the new Location_path instances instead. In Location_step instance inverse_item_classification_hierarchy_step the attribute role_name has to be set sub_classification.

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

File_property_query Reference

  • Key: PLM2-20
  • Legacy Issue Number: 11217
  • Status: closed  
  • Source: PROSTEP AG ( Guido Adolphi)
  • Summary:

    PLM Services 2.0, mantis/07-03-01 Update, Chapter 9.7.42 and Figure 9.58 Cause: All Location_step instances are erroneous. New Specification Text: In the following each Location_step instance of figure 9.58 is described with the required corrections: * file_creation_step: The attribute role_name has to be set to creation. * file_content_step: The attribute role_name has to be set to content. * file_type_location_step: Instance-name has to be set to file_type_step, and attribute role_name has to be set to document_file_type. * file_format_step: The attribute role_name has to be set to file_format. * file_location_step: The attribute role_name has to be set to external_id_and_location. * file_size_step: The attribute role_name has to be set to size.

  • Reported: PLM 1.0.1 — Fri, 27 Jul 2007 04:00 GMT
  • Disposition: Resolved — PLM 2.0b2
  • Disposition Summary:

    In the following each Location_step instance of figure 9.58 is described with the required corrections:
    · file_creation_step: The attribute role_name has to be set to creation.
    · file_content_step: The attribute role_name has to be set to content.
    · file_type_location_step: Instance-name has to be set to file_type_step, and attribute role_name has to be set to document_file_type.
    · file_format_step: The attribute role_name has to be set to file_format.
    · file_location_step: The attribute role_name has to be set to external_id_and_location.
    · file_size_step: The attribute role_name has to be set to size.

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

Document_classification_hierarchy_query Reference

  • Key: PLM2-17
  • Legacy Issue Number: 11214
  • Status: closed  
  • Source: PROSTEP AG ( Guido Adolphi)
  • Summary:

    PLM Services 2.0, mantis/07-03-01 Update, Chapter 9.7.32 and Figure 9.48 Cause: The Conditional_query has no relationships to Location_step but to PLM_query. The Location_path instances are missing as glue between the instances of Conditional_query and Location_step. Furthermore, Location_step instance inverse_document_classification_hierarchy_step wants to select elements by the no named relationship related (denoted by role_name="related") from Specific_document_classification_hierarchy elements. However, Specific_document_classification_hierarchy only provides the named relationship sub_classification. New Specification Text: In figure 9.48 two Location_path instances have to be included each referencing one of the existing Location_step instances. The Conditional_query instance equivalent_query_instance has to refer to the new Location_path instances instead. In Location_step instance inverse_document_classification_hierarchy_step the attribute role_name has to be set sub_classification.

  • Reported: PLM 1.0.1 — Fri, 27 Jul 2007 04:00 GMT
  • Disposition: Resolved — PLM 2.0b2
  • Disposition Summary:

    In figure 9.48 two Location_path instances have to be included each referencing one of the existing Location_step instances. The Conditional_query instance equivalent_query_instance has to refer to the new Location_path instances instead. In Location_step instance inverse_document_classification_hierarchy_step the attribute role_name has to be set sub_classification.

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

Document_version_query Reference

  • Key: PLM2-16
  • Legacy Issue Number: 11213
  • Status: closed  
  • Source: PROSTEP AG ( Guido Adolphi)
  • Summary:

    PLM Services 2.0, mantis/07-03-01 Update, Chapter 9.7.37 and Figure 9.53 Cause: Base class of specific query Document_representation_query is PLM_query rather than Specific_query since Document_representation_query is an element of the specific queries conformance point. New Specification Text: Changes to figure 9.53: base class of Document_representation_query has to be Specific_query.

  • Reported: PLM 1.0.1 — Fri, 27 Jul 2007 04:00 GMT
  • Disposition: Resolved — PLM 2.0b2
  • Disposition Summary:

    Correct reference is to Document_version_query in Chapter 9.7.37:Base class of Document_version_query has to be Specific_query. Update Figure 9.53

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

Relationship_predicate Reference

  • Key: PLM2-7
  • Legacy Issue Number: 11202
  • Status: closed  
  • Source: PROSTEP AG ( Guido Adolphi)
  • Summary:

    PLM Services 2.0, mantis/07-03-01 Update, Chapter 9.4.7 Cause: The specification of the Relationship_predicate is imprecise, need some bug fixes and additions: * All partial constraints have to be fulfilled. * A new constraint for the named relationship relating_object_predicate has to be added. New Specification Text: An object fulfills a Relationship_predicate constraint if it fulfills all of the following partial constraints: * The object fulfills all predicate instances referenced by the named relationship relating_object_predicate of the Relationship_predicate. * The object is related with another object that fulfills all predicate instances referenced by the named relationship related_object_predicate of the Relationship_predicate. * If the value of the attribute inverse of the Relationship_predicate is set to false, and if the attribute role_name is set, the role name of the other object in the relationship must be equal to the value of the attribute role_name of the Relationship_predicate. * If the value of the attribute inverse of the Relationship_predicate is set to true, and if the attribute role_name is set, the role name of this object in the relationship must be equal to the value of the attribute role_name of the Relationship_predicate. * If the attribute role_declaring_type_name is set, the relationship must be defined in a type which name is equal to the value of the attribute role_declaring_type_name.

  • Reported: PLM 1.0.1 — Fri, 27 Jul 2007 04:00 GMT
  • Disposition: Resolved — PLM 2.0b2
  • Disposition Summary:

    1. ALL constraints must be fullfilled.
    2. The attribute 'predicate' is now named 'related_object_predicate'
    3. A new constraint for the attribute 'relating_object_predicate' has to be added.

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

Effectivity_query Reference

  • Key: PLM2-19
  • Legacy Issue Number: 11216
  • Status: closed  
  • Source: PROSTEP AG ( Guido Adolphi)
  • Summary:

    PLM Services 2.0, mantis/07-03-01 Update, Chapter 9.7.39 Cause: Description is incomplete. Beside Effectivity elements instances of Duration, Organization and Event_or_date_select are selected. New Specification Text: The Effectivity_query selects Effectivity objects with additional related instances of Duration, Organization and Event_or_date_select.

  • Reported: PLM 1.0.1 — Fri, 27 Jul 2007 04:00 GMT
  • Disposition: Resolved — PLM 2.0b2
  • Disposition Summary:

    The Effectivity_query selects Effectivity objects with additional related instances of Duration, Organization and Event_or_date_select.

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

Effectivity_assignment_query Reference

  • Key: PLM2-18
  • Legacy Issue Number: 11215
  • Status: closed  
  • Source: PROSTEP AG ( Guido Adolphi)
  • Summary:

    PLM Services 2.0, mantis/07-03-01 Update, Chapter 9.7.38 and Figure 9.54 Cause: Location step instance effective_element_step is defined incompletely. New Specification Text: Location step instance effective_element_step in figure 9.54 needs attribute role_declaring_type_name set to Effectivity_assignment and attribute role_name set to effective_element.

  • Reported: PLM 1.0.1 — Fri, 27 Jul 2007 04:00 GMT
  • Disposition: Resolved — PLM 2.0b2
  • Disposition Summary:

    Location step instance effective_element_step in figure 9.54 needs attribute role_declaring_type_name set to Effectivity_assignment and attribute role_name set to effective_element.

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

Document_classification_query Reference

  • Key: PLM2-13
  • Legacy Issue Number: 11210
  • Status: closed  
  • Source: PROSTEP AG ( Guido Adolphi)
  • Summary:

    PLM Services 2.0, mantis/07-03-01 Update, Chapter 9.7.31 and Figure 9.47 Cause: Base class of specific query Document_classification_query is PLM_query rather than Specific_query since Document_classification_query is an element of the specific queries conformance point. New Specification Text: Changes to figure 9.47: base class of Document_classification_query has to be Specific_query.

  • Reported: PLM 1.0.1 — Fri, 27 Jul 2007 04:00 GMT
  • Disposition: Resolved — PLM 2.0b2
  • Disposition Summary:

    Correct, change as summarized.

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

Design_discipline_item_definition_query Reference

  • Key: PLM2-12
  • Legacy Issue Number: 11209
  • Status: closed  
  • Source: PROSTEP AG ( Guido Adolphi)
  • Summary:

    PLM Services 2.0, mantis/07-03-01 Update, Chapter 9.7.30 and Figure 9.46 Cause: Base class of specific query Design_discipline_item_definition_query is PLM_query rather than Specific_query since Design_discipline_item_definition_query is an element of the specific queries conformance point. New Specification Text: Changes to figure 9.46: base class of Design_discipline_item_definition_query has to be Specific_query.

  • Reported: PLM 1.0.1 — Fri, 27 Jul 2007 04:00 GMT
  • Disposition: Resolved — PLM 2.0b2
  • Disposition Summary:

    Change in Figure 9.46: base class of Design_discipline_item_definition_query has to be Specific_query. See solution to issue 11227 for the finally updated figure.

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

Document_representation_query Reference:

  • Key: PLM2-15
  • Legacy Issue Number: 11212
  • Status: closed  
  • Source: PROSTEP AG ( Guido Adolphi)
  • Summary:

    PLM Services 2.0, mantis/07-03-01 Update, Chapter 9.7.35 and Figure 9.51 Cause: Base class of specific query Document_representation_query is PLM_query rather than Specific_query since Document_representation_query is an element of the specific queries conformance point. New Specification Text: Changes to figure 9.51: base class of Document_representation_query has to be Specific_query.

  • Reported: PLM 1.0.1 — Fri, 27 Jul 2007 04:00 GMT
  • Disposition: Resolved — PLM 2.0b2
  • Disposition Summary:

    Changes to figure 9.51: base class of Document_representation_query has to be Specific_query.

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

Document_query Reference

  • Key: PLM2-14
  • Legacy Issue Number: 11211
  • Status: closed  
  • Source: PROSTEP AG ( Guido Adolphi)
  • Summary:

    PLM Services 2.0, mantis/07-03-01 Update, Chapter 9.7.34 and Figure 9.50 Cause: Base class of specific query Document_query is PLM_query rather than Specific_query since Document_query is an element of the specific queries conformance point. New Specification Text: Changes to figure 9.50: base class of Document_query has to be Specific_query.

  • Reported: PLM 1.0.1 — Fri, 27 Jul 2007 04:00 GMT
  • Disposition: Resolved — PLM 2.0b2
  • Disposition Summary:

    changes to figure 9.50: base class of Document_query has to be Specific_query.

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

Associated_project_query Reference

  • Key: PLM2-11
  • Legacy Issue Number: 11208
  • Status: closed  
  • Source: PROSTEP AG ( Guido Adolphi)
  • Summary:

    PLM Services 2.0, mantis/07-03-01 Update, Chapter 9.7.24 Cause: The chapter caption includes a blank character. New Specification Text: New chapter caption has to be "Associated_project_query".

  • Reported: PLM 1.0.1 — Fri, 27 Jul 2007 04:00 GMT
  • Disposition: Resolved — PLM 2.0b2
  • Disposition Summary:

    Delete extra characters. New chapter caption has to be "Associated_project_query".

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

Activity_resolved_request_query Reference

  • Key: PLM2-10
  • Legacy Issue Number: 11207
  • Status: closed  
  • Source: PROSTEP AG ( Guido Adolphi)
  • Summary:

    PLM Services 2.0, mantis/07-03-01 Update, Chapter 9.7.6 and Figure 9.22 Cause: The Location_step instance resolved:request_step is misspelled. New Specification Text: The location step instance has to be renamed to resolved_request_step.

  • Reported: PLM 1.0.1 — Fri, 27 Jul 2007 04:00 GMT
  • Disposition: Resolved — PLM 2.0b2
  • Disposition Summary:

    Correct as described in summary.

  • 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

Class definition of Document_file is different between specification document and XSD

  • Key: PLM21-1
  • Legacy Issue Number: 15210
  • Status: closed  
  • Source: IBM ( Shoichiro Watanabe)
  • Summary:

    In 8.4.1.7 Class Document_file, Document_file has a attribute named "description".
    However, in InformationalModel.xsd, Document_file does NOT have the attribete named "description".
    I downloaded the InformationalModel.xsd from http://www.omg.org/spec/PLM/2.0/schema/InformationalModel.xsd.

    I'd like to know which of spec or XSD is valid for Class Document_file. And if the spec is valid, would you please correct the XSD ?

  • Reported: PLM 2.0 — Tue, 20 Apr 2010 04:00 GMT
  • Disposition: Resolved — PLM 2.1
  • Disposition Summary:

    The RTF agrees that the xsd file is in error. Update the xsd file at http://www.omg.org/spec/PLM/2.0/schema/InformationalModel.xsd. by inserting the missing element definition line into the definition of Document_file.

  • 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