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.

Edit InformationalModel.xsd as described.

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

Edit InformationalModel.xsd as described.

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

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.

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.

Accepted as proposed.

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.

Disposition: See issue 11618 for disposition

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.

Accepted as proposed. Change information model object inheritance as described in 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

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

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

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

XSD files lack default namespace

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.

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 ?

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.