${taskforce.name} Avatar
  1. OMG Task Force

PSS FTF — Open Issues

  • Key: PSS
  • Issues Count: 19
Open Closed All
Issues not resolved

Issues Descriptions

Eliminate PID_DA definition

  • Key: PSS-47
  • Legacy Issue Number: 43
  • Status: open  
  • Source: Anonymous
  • Summary:

    Summary: The definition for the PID_DA should be eliminated and the old attribute moved to the base PID definition. This will provide an invariant and abstract representation for all persistence state.

  • Reported: PSS 1.0b1 — Wed, 3 Jul 1996 04:00 GMT
  • Updated: Sat, 7 Mar 2015 06:10 GMT

PDS_DA::DAObjectID

  • Key: PSS-46
  • Legacy Issue Number: 42
  • Status: open  
  • Source: Anonymous
  • Summary:

    Summary: typedef string DAObjectID should be typedef sequence<octet> DAObjectID. This will allow more flexibility in the PDS_DA implementation without breaking any functionality.

  • Reported: PSS 1.0b1 — Wed, 3 Jul 1996 04:00 GMT
  • Updated: Sat, 7 Mar 2015 06:10 GMT

PDS_DA DDL should exclude type Any

  • Key: PSS-45
  • Legacy Issue Number: 41
  • Status: open  
  • Source: Anonymous
  • Summary:

    Summary: The inclusion of type Any in object definitions should be eliminated, because it makes schema evolution completely unmanageable.

  • Reported: PSS 1.0b1 — Wed, 3 Jul 1996 04:00 GMT
  • Updated: Sat, 7 Mar 2015 06:10 GMT

SD interface

  • Key: PSS-44
  • Legacy Issue Number: 40
  • Status: open  
  • Source: Anonymous
  • Summary:

    Summary: It is unclear how SD object implementations get intially connected to the POS implementation.

  • Reported: PSS 1.0b1 — Wed, 3 Jul 1996 04:00 GMT
  • Updated: Sat, 7 Mar 2015 06:10 GMT

Support for DAObject interface

  • Key: PSS-48
  • Legacy Issue Number: 44
  • Status: open  
  • Source: Anonymous
  • Summary:

    Summary: pg. 5-24, paragraph 1, section 5.10.2 states that "a data object is not require to support this interface." If so, there is not a way to free the storage for a data object or generate a PID.

  • Reported: PSS 1.0b1 — Wed, 3 Jul 1996 04:00 GMT
  • Updated: Sat, 7 Mar 2015 06:10 GMT

PO::delete and POM::delete

  • Key: PSS-43
  • Legacy Issue Number: 39
  • Status: open  
  • Source: Anonymous
  • Summary:

    Summary: The delete operation should not have a PID parameter – what does it mean if the PID specified is not the currently connected PID?

  • Reported: PSS 1.0b1 — Wed, 3 Jul 1996 04:00 GMT
  • Updated: Sat, 7 Mar 2015 06:10 GMT

PO::store/restore

  • Key: PSS-42
  • Legacy Issue Number: 38
  • Status: open  
  • Source: Anonymous
  • Summary:

    Summary: Because para. 3, pg. 5-12 states that a PO can only have a single connection at a time, all behavior of these operations would need to be provided by the POM, which is difficult to do interoperably.

  • Reported: PSS 1.0b1 — Wed, 3 Jul 1996 04:00 GMT
  • Updated: Sat, 7 Mar 2015 06:10 GMT

PO::disconnect and POM::disconnect parameters

  • Key: PSS-41
  • Legacy Issue Number: 37
  • Status: open  
  • Source: Anonymous
  • Summary:

    Summary: The PID parameter is extraneous, as the specification states that a PO can only have a single connection at a time.

  • Reported: PSS 1.0b1 — Wed, 3 Jul 1996 04:00 GMT
  • Updated: Sat, 7 Mar 2015 06:10 GMT

PO::connect and POM::connect exception needed

  • Key: PSS-40
  • Legacy Issue Number: 36
  • Status: open  
  • Source: Anonymous
  • Summary:

    Summary: An exception is needed to inform of an invalid connection (DDL type, protocol, etc.).

  • Reported: PSS 1.0b1 — Wed, 3 Jul 1996 04:00 GMT
  • Updated: Sat, 7 Mar 2015 06:10 GMT

PIDFactory::create_PID* definitions

  • Key: PSS-37
  • Legacy Issue Number: 33
  • Status: open  
  • Source: Anonymous
  • Summary:

    Summary: The definition should not contain "...key that identifies a particular PID implementation." Overall these definitions contains a lot of confusion about PID identity.

  • Reported: PSS 1.0b1 — Wed, 3 Jul 1996 04:00 GMT
  • Updated: Sat, 7 Mar 2015 06:10 GMT

PID derivation

  • Key: PSS-36
  • Legacy Issue Number: 32
  • Status: open  
  • Source: Anonymous
  • Summary:

    Summary: The PID interface derivation usage in the PID_DA and other examples in the specification limit the ability of the protocol to be decoupled from the datastore as intended.

  • Reported: PSS 1.0b1 — Wed, 3 Jul 1996 04:00 GMT
  • Updated: Sat, 7 Mar 2015 06:10 GMT

PO::p attribute should be readonly

  • Key: PSS-39
  • Legacy Issue Number: 35
  • Status: open  
  • Source: Anonymous
  • Summary:

    Summary: This attribute should simply reflect the currently connected PID, to avoid placing an additional burden on the PO implementation which is not needed.

  • Reported: PSS 1.0b1 — Wed, 3 Jul 1996 04:00 GMT
  • Updated: Sat, 7 Mar 2015 06:10 GMT

Returning PDS from PO::connect

  • Key: PSS-38
  • Legacy Issue Number: 34
  • Status: open  
  • Source: Anonymous
  • Summary:

    Summary: The PDS reference should not be returned from the PO::connect operation, as this creates a number of implementation problems.

  • Reported: PSS 1.0b1 — Wed, 3 Jul 1996 04:00 GMT
  • Updated: Sat, 7 Mar 2015 06:10 GMT

PID attributes should be readonly

  • Key: PSS-33
  • Legacy Issue Number: 29
  • Status: open  
  • Source: Anonymous
  • Summary:

    Summary: Attributes of the PID interface should be readonly and only settable through their initial creation by the PIDFactory and the service implementation.

  • Reported: PSS 1.0b1 — Wed, 3 Jul 1996 04:00 GMT
  • Updated: Sat, 7 Mar 2015 06:10 GMT

PID additional attributes

  • Key: PSS-32
  • Legacy Issue Number: 28
  • Status: open  
  • Source: Anonymous
  • Summary:

    Summary: The PID should add attributes for the Datastore object reference and an opaque PersistentStateIdentifier. This allows maximum flexibility without the need to subclass the PID interface.

  • Reported: PSS 1.0b1 — Wed, 3 Jul 1996 04:00 GMT
  • Updated: Sat, 7 Mar 2015 06:10 GMT

Factory interface should be specified

  • Key: PSS-31
  • Legacy Issue Number: 27
  • Status: open  
  • Source: Anonymous
  • Summary:

    Summary: The Factory interfaces should be specified for all service component interfaces to provide for integration with the Lifecycle Service.

  • Reported: PSS 1.0b1 — Wed, 3 Jul 1996 04:00 GMT
  • Updated: Sat, 7 Mar 2015 06:10 GMT

Issue POS 2.0 RFP

  • Key: PSS-30
  • Legacy Issue Number: 26
  • Status: open  
  • Source: Anonymous
  • Summary:

    Summary: TRC has found several issues that cannot be addressed within this forum and which would need to be addressed in a new POS 2.0 spec.

  • Reported: PSS 1.0b1 — Wed, 3 Jul 1996 04:00 GMT
  • Updated: Sat, 7 Mar 2015 06:10 GMT

Typo in PID section

  • Key: PSS-35
  • Legacy Issue Number: 31
  • Status: open  
  • Source: Anonymous
  • Summary:

    Summary: pg. 5-9, paragraph 6, remove extra p from "the ppersistent object..."

  • Reported: PSS 1.0b1 — Wed, 3 Jul 1996 04:00 GMT
  • Updated: Sat, 7 Mar 2015 06:10 GMT

PID vs. OID definition

  • Key: PSS-34
  • Legacy Issue Number: 30
  • Status: open  
  • Source: Anonymous
  • Summary:

    Summary: The last sentence of para. 4 on pg. 5-9 is not implementable. How is the new storage allocation and location determined?

  • Reported: PSS 1.0b1 — Wed, 3 Jul 1996 04:00 GMT
  • Updated: Sat, 7 Mar 2015 06:10 GMT