Product Data Management Enablers Avatar
  1. OMG Specification

Product Data Management Enablers — Closed Issues

  • Acronym: PDME
  • Issues Count: 4
  • Description: Issues resolved by a task force and approved by Board
Closed All
Issues resolved by a task force and approved by Board

Issues Descriptions

PdmChangeManagement (page 2-150)

  • Key: PDME12-4
  • Legacy Issue Number: 3761
  • Status: closed  
  • Source: PROSTEP AG ( Lutz Laemmer)
  • Summary:

    6. PdmChangeManagement (page 2-150)
    EngChangeItem should have a attribute "description" of type string,
    according to
    the specification.
    Remark: I am not sure, is this the intent of resolving issue 1744
    (compare
    issue 2150 for the Views-Module)? May be, we need some more changes in
    the
    IDL snippet, in the explanation to EngChangeItem and in the IDL of
    PdmChangeManagement.

  • Reported: PDME 1.0b2 — Thu, 20 Jul 2000 04:00 GMT
  • Disposition: Resolved — PDME 1.2
  • Disposition Summary:

    Duplicate from issue 3760, clos eissue

  • Updated: Sun, 8 Mar 2015 18:39 GMT

PdmContext is insufficient as a TraversalCriteria

  • Key: PDME12-3
  • Legacy Issue Number: 3155
  • Status: closed  
  • Source: Hewlett-Packard ( Duane Silkworth)
  • Summary:

    The CosGraphs module specifies that Traversals are be created by the
    TraversalFactory::create_traversal_on() operation, which returns a Traversal
    and takes 3 input parameters: a root Node, a TraversalCriteria, and a mode flag.

    In the PDM Enablers PdmViews module, it is specified that PdmContext is a subtype of
    TraversalCriteria, and thus a PdmContext can be used to create a Traversal. The
    PdmContext is effective as a filter to specify that only the items of interest to the client
    are returned. However, it is insufficient to create an effective Traversal object.
    Nowhere is there defined a traversal path name, algorithm or strategy which indicates
    which roles and relationships to follow.

    As a possible solution, it is sugggested that the PdmContext not inherit
    TraversalCriteria. Rather a TraversalCriteria should be created by a new interface's
    operation, which takes as input both a PdmContext and some definition of a
    PDM Enablers-specific traversal path.

  • Reported: PDME 1.0b2 — Tue, 21 Dec 1999 05:00 GMT
  • Disposition: Resolved — PDME 1.2
  • Disposition Summary:

    Duplicate of 3154. Closed

  • Updated: Sun, 8 Mar 2015 18:22 GMT

PDM RTF Issue - The Identifiable interface should raise InvalidProperties

  • Key: PDME12-2
  • Legacy Issue Number: 2874
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: Identifiable interfaces should be able to raise InvalidProperties exceptions.

    The PdmFoundation operations Identifiable::change_id and IdentificationContext::generate_id both take a property_set parameter but, unlike other operations that use PropertySets, they are not defined to raise the InvalidProperties exception.

    This is a minor issue. In the interim, implementations can raise the ValidationError exception if the property_set is invalid.

  • Reported: PDME 1.0b2 — Wed, 1 Sep 1999 04:00 GMT
  • Disposition: Resolved — PDME 1.2
  • Disposition Summary:

    resolved in 1.2 RTF

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

PDM Enablers - cannot determine client type for file transfer

  • Key: PDME12-1
  • Legacy Issue Number: 2622
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Summary: In the PdmDocumentManagement module, the SecuredFile interface defines operations begin_put_buffer and begin_get_buffer to initiate file content transfers. Each of these operation has a transfer_encoding parameter to determine whther the transfer should proceed in a straight "binary" mode, or in an "8-bit" character/text mode. In 8-bit mode, between UNIX and MS Windows machines, the buffer transfer operations should adjust the end-of-line CR/LF bytes in the file according to the platform conventions. However, there is no defined way for the server to know what type of platform the client is.

    The begin_put_buffer and begin_get_buffer operations should have a parameter to tell the server what type of platform the client is.

  • Reported: PDME 1.0b2 — Tue, 27 Apr 1999 04:00 GMT
  • Disposition: Resolved — PDME 1.2
  • Disposition Summary:

    resolved by 1.2 RTF

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