Product Lifecycle Management Services Avatar
  1. OMG Specification

Product Lifecycle Management Services — All Issues

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

Issues Descriptions

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