1. OMG Mailing List
  2. GEMS 1.5 Revision Task Force

Open Issues

  • Issues not resolved
  • Name: gems-rtf
  • Issues Count: 1

Issues Summary

Key Issue Reported Fixed Disposition Status
GEMS15-1 Extend PIM to allow "leaf" values to be referenced directly GEMS 1.3 open

Issues Descriptions

Extend PIM to allow "leaf" values to be referenced directly

  • Key: GEMS15-1
  • Legacy Issue Number: 19627
  • Status: open  
  • Source: RT Logic ( Nathaniel Colson)
  • Summary:

    The spec currently allows arrays, parameters sets, and arrays of parameter sets. These compound types can make for an API that's difficult to use. Specifically, if you want to modify a single member of a parameter set, you have to read it, deserialize it, modify part of it, re-serialize it, and write it back. This isn't wildly difficult, but I believe it's enough for a customer to complain about usability. This operation is particularly annoying in the case of arrays of parameter sets. Furthermore, the read/modify/write operation isn't atomic, and could result in race conditions that revert a simultaneous change.

    I'd like to suggest that we extend the PIM to allow "leaf" values of compound types to be referenced directly. E.g., array elements and parameter set members could be referenced under the ASCII PSM using the following parameter names:

    Array element: myArray/3
    Set member: myParamSet/memberName
    Array of sets: myArrayOfSets/5/memberName

    ...with a corresponding scheme for the XML PSM. This would require adding the forward slash as a reserved word that should not be used in parameter names, along with "|GEMS" and "|END".

  • Reported: GEMS 1.3 — Tue, 30 Sep 2014 04:00 GMT
  • Updated: Tue, 28 Feb 2017 22:04 GMT