Issues for Mailing list of the PLM Services V2.0 Finalization Task Force

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

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

Issue 10970: Section "7 Use Cases" - no flow diagram exists
Issue 10971: Section "7.2.4.9 Topics under discussion"
Issue 10972: Section "7.2.5.7 Constraints and assertions" -- none defined at the moment
Issue 10973: PLM 2 FTF -- Editorial issues
Issue 11088: Specification of Relationship_predicate
Issue 11096: Chapter 8.9.1
Issue 11202: Relationship_predicate Reference
Issue 11203: Associated_item_property_query Reference
Issue 11205: Sort_predicate Reference
Issue 11206: Activity_query Reference
Issue 11207: Activity_resolved_request_query Reference
Issue 11208: Associated_project_query Reference
Issue 11209: Design_discipline_item_definition_query Reference
Issue 11210: Document_classification_query Reference
Issue 11211: Document_query Reference
Issue 11212: Document_representation_query Reference:
Issue 11213: Document_version_query Reference
Issue 11214: Document_classification_hierarchy_query Reference
Issue 11215: Effectivity_assignment_query Reference
Issue 11216: Effectivity_query Reference
Issue 11217: File_property_query Reference
Issue 11218: Item_classification_hierarchy_query Reference
Issue 11219: Item_use_query Reference
Issue 11220: Product_identification_query Reference
Issue 11221: Compositions in the Computational Model Reference
Issue 11222: Generic Queries Conformance Point Reference
Issue 11223: Proxy Queries Conformance Point Reference
Issue 11224: Project_assignment_query Reference
Issue 11225: Associated_file_query Reference:
Issue 11226: Configuration_query Reference
Issue 11227: Design_discipline_item_definition_query Reference:
Issue 11228: Event_reference_query Reference
Issue 11229: Item_instance_query Reference
Issue 11230: Product_structure_query Reference
Issue 11231: Work_request_scope_query Reference
Issue 11232: Item_traversal_query Reference
Issue 11233: General_detail_query Reference
Issue 11614: Join PLM_properties_descriptors query operations
Issue 11615: Join operations 'write' and 'import_data' into one single operation
Issue 11616: Add optional generic property list parameter to some service operations
Issue 11617: Join operations 'query' and 'export_data' into one single operation
Issue 11618: remove composition 'axis2_placement_3d' from type 'PLM_container
Issue 11624: Section: 9.7.39
Issue 11638: Chapter 9.7.49, SpecificQueries.xsd, Chapter 9.8.7
Issue 11645: Section: 8.1
Issue 11816: PLM 2 FTF Security chapter issue
Issue 12164: Informational Model (xsd)
Issue 12187: The type Axis2_placement_3d shall be removed from the class PLM_container
Issue 12188: The function Get_download_URL shall be enhanced to download multiple files
Issue 12189: Section: InformationalModel.xsd
Issue 12190: Section: InformationalModel.xsd last lines
Issue 12191: informational model, object "Document_file"
Issue 12192: Attribute Description for Entities Document_file and Person_in_organization

Issue 10970: Section "7 Use Cases" - no flow diagram exists (plm2-ftf)

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.

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.

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.

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

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.

Disposition:	See issue 11202  for disposition

Document mantis/07-03-01
Chapter 8.9.1


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

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. 

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

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.

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.

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. 

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

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. 

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.

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.

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. 

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.

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.

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.

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.

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.

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.

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.

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. 

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.

The design intent is to allow for flexible instantiation of referenced elements. Apply no changes.

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.

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.

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.

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.

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

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. 

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.

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.

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.

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.

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.

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..*].

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

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.

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

It is already mentioned in the explanatory text how the properties values are to be used for more generic and flexible server implementations. Therefore, the properties mechanisms are in place for the analyzed use cases and no changes need to be be applied.
Disposition:	Closed, no change

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.

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.

This issue is already fixed with FAS.
Disposition:	Closed, no change

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

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]

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

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.

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. 

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.

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.

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

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

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.

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