Ground Equipment Monitoring Service Avatar
  1. OMG Specification

Ground Equipment Monitoring Service — Closed Issues

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

Issues Summary

Key Issue Reported Fixed Disposition Status
GEMS15-1 Extend PIM to allow "leaf" values to be referenced directly GEMS 1.3 GEMS 1.5 Deferred closed
GEMS15-2 Examples GEMS 1.4 GEMS 1.5 Closed; No Change closed

Issues Descriptions

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

  • Key: GEMS15-1
  • Legacy Issue Number: 19627
  • Status: closed  
  • 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
  • Disposition: Deferred — GEMS 1.5
  • Disposition Summary:

    Defer to GEMS 2.0 RFP

    The GEMS 1.5 Revision Task Force met today (June 24, 2020) and we agreed to defer this ticket to the GEMS 2.0 RFP where we can discuss it in the context of an additional PSM, i.e. JSON over REST.

  • Updated: Wed, 6 Jan 2021 15:10 GMT

Examples

  • Key: GEMS15-2
  • Status: closed  
  • Source: Terma B.V. ( Andy Armitage)
  • Summary:

    The text says:

    7.3 XML Examples
    Examples of the GEMS XML messages are available on the OMG website at http://www.omg.org/space. Navigate to
    the GEMS specific page and look for GEMS Examples.

    I can't find any such examples! (humble apologies if they are there but I have looked)

  • Reported: GEMS 1.4 — Tue, 28 Apr 2020 16:33 GMT
  • Disposition: Closed; No Change — GEMS 1.5
  • Disposition Summary:

    GEMS examples are available

    The GEMS 1.5 Revision Task Force met today (June 24, 2020) and we agreed to close this ticket since the examples are available per the 07/May/20 comment in the original Jira ticket as follows:

    “The examples can be found by browsing to that same OMG page at https://www.omg.org/space then click on the link "GEMS™ (Ground Equipment Monitoring Service™)" which takes you to http://www.omgwiki.org/space/doku.php?id=gems that has a link to the examples at http://www.omgwiki.org/space/doku.php?id=gems_examples

  • Updated: Wed, 6 Jan 2021 15:10 GMT