Ground Equipment Monitoring Service Avatar
  1. OMG Specification

Ground Equipment Monitoring Service — All Issues

  • Acronym: GEMS
  • Issues Count: 25
  • Description: All Issues
Open Closed All
All Issues

Issues Summary

Key Issue Reported Fixed Disposition Status
GEMS-24 Sections 9.2.6 & 9.2.7 GEMS 1.0b1 GEMS 1.0 Resolved closed
GEMS-22 header of the GEMS_base_types.xsd file does not match with section 7.1.1 of the GEMS Specification Beta 1 GEMS 1.0b1 GEMS 1.0 Resolved closed
GEMS-21 VALID_RANGE description contains extra copy of message UML image GEMS 1.0b1 GEMS 1.0 Resolved closed
GEMS-14 9.1.1.1 Need to clarify how hex_value types are specified in the ASCII PSM GEMS 1.0b1 GEMS 1.0 Resolved closed
GEMS-13 Response message examples do not clearly show the result_description. GEMS 1.0b1 GEMS 1.0 Resolved closed
GEMS-9 8.1.1.17 The XML schema for GetConfigResponse uses an undefined ConfigResul GEMS 1.0b1 GEMS 1.0 Resolved closed
GEMS-8 GEMS-XML 8.1.1.9 XML Schema for Connect Request includes client_version GEMS 1.0b1 GEMS 1.0 Resolved closed
GEMS-20 Add XML and ASCII as normative references GEMS 1.0b1 GEMS 1.0 Resolved closed
GEMS-19 Need an example of how to represent a parameter array in the GEMS-XML PSM GEMS 1.0b1 GEMS 1.0 Resolved closed
GEMS-10 GEMS-XML 8.2.1 Need two additional examples in Directive Message/Response GEMS 1.0b1 GEMS 1.0 Resolved closed
GEMS-7 GEMS PIM 7.5 Spelling error in section 7.5 GEMS 1.0b1 GEMS 1.0 Resolved closed
GEMS-6 GEMS PIM 7.7 Standard Device definitions not complete GEMS 1.0b1 GEMS 1.0 Resolved closed
GEMS-12 GEMS-ASCII messages do not specify a starting or trailing pipe character GEMS 1.0b1 GEMS 1.0 Resolved closed
GEMS-11 GEMS-XML 8.2.5 Typo in section 8.2.5: example indicates 2 params GEMS 1.0b1 GEMS 1.0 Resolved closed
GEMS-18 9.2.2 Section 9.2.2: The example shows an incorrect message type GEMS 1.0b1 GEMS 1.0 Resolved closed
GEMS-17 9.1.2 Figure in 9.1.2 uses RTL instead of GEMS GEMS 1.0b1 GEMS 1.0 Resolved closed
GEMS-15 GEMS-ASCII PSM is missing the ParameterSet definition GEMS 1.0b1 GEMS 1.0 Resolved closed
GEMS-16 No discussion of escaping or quoting characters in the ASCII PSM GEMS 1.0b1 GEMS 1.0 Resolved closed
GEMS-23 The time format is closer to POSIX than UTC and does not allow for unambiguous leap second resolution GEMS 1.0b1 GEMS 1.0 Resolved closed
GEMS-2 Section 7.3.2 GEMS 1.0b1 GEMS 1.0 Resolved closed
GEMS-4 GEMS PIM 7.3.2.1.5 Time stamp definition is vague and needs to be clarified GEMS 1.0b1 GEMS 1.0 Resolved closed
GEMS-3 GEMS PIM Section 7.3.1.7: 64 Bit Integer Values GEMS 1.0b1 GEMS 1.0 Resolved closed
GEMS-5 GEMS PIM 7.3.2.4.2.1 The valid_state field is confusing GEMS 1.0b1 GEMS 1.0 Resolved closed
GEMS-1 Correct various table and section references throughout the document GEMS 1.0b1 GEMS 1.0 Resolved closed
GEMS11-1 Section 7.3.2.5.1 GEMS 1.0b1 GEMS 1.1 Resolved closed

Issues Descriptions

Sections 9.2.6 & 9.2.7

  • Key: GEMS-24
  • Legacy Issue Number: 12772
  • Status: closed  
  • Source: Amergint Technologies ( Rob Andzik)
  • Summary:

    Section 9.2.6 and 9.2.7: Example response has an extra (typo) parameter. Need to remove the |0| field before the END.

  • Reported: GEMS 1.0b1 — Fri, 8 Aug 2008 04:00 GMT
  • Disposition: Resolved — GEMS 1.0
  • Disposition Summary:

    These serve no purpose and are probably just typos. The typos will be fixed.

  • Updated: Sat, 7 Mar 2015 21:54 GMT

header of the GEMS_base_types.xsd file does not match with section 7.1.1 of the GEMS Specification Beta 1

  • Key: GEMS-22
  • Legacy Issue Number: 13133
  • Status: closed  
  • Source: THALES ( Hugues Vincent)
  • Summary:

    The header of the GEMS_base_types.xsd file does not match with section 7.1.1 of the GEMS Specification Beta 1 document. A. The new issue was mentioned in the AB review of the GEMS FTF report
    B. Reported by Hugues Vincent

  • Reported: GEMS 1.0b1 — Tue, 2 Dec 2008 05:00 GMT
  • Disposition: Resolved — GEMS 1.0
  • Disposition Summary:

    The GEMS XSD file contains the correct header information. Update section 7.1.1 of the document with the correct header found in this XSD file.

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

VALID_RANGE description contains extra copy of message UML image

  • Key: GEMS-21
  • Legacy Issue Number: 12968
  • Status: closed  
  • Source: Amergint Technologies ( Rob Andzik)
  • Summary:

    VALID_RANGE description contains extra copy of message UML image

    a. This was found during our document review

    b. Section 6.3.2.2

    c. Reported by RT Logic

  • Reported: GEMS 1.0b1 — Wed, 22 Oct 2008 04:00 GMT
  • Disposition: Resolved — GEMS 1.0
  • Disposition Summary:

    Remove the offending duplicate diagram from the INVALID_RANGE description.

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

9.1.1.1 Need to clarify how hex_value types are specified in the ASCII PSM

  • Key: GEMS-14
  • Legacy Issue Number: 12767
  • Status: closed  
  • Source: Amergint Technologies ( Rob Andzik)
  • Summary:

    There are two questions regarding hex_value types in the GEMS-ASCII PSM.

    1. Hex value arrays are not well defined and the concept is complicated.
    2. Can we use a 0xFFFF notation?
      Suggestions:
      Yes, the 0xFFFF notation can be used but it should be optional. ''(e.g. FAFA is the same as 0xFAFA)''
      As for arrays, this is a little complicated. Suggestions are as follows:
    • Restrict arrays of hex_values to be the same bit length
    • Move the bit length to the parameter value: e.g. hex_value[2]=22.FAF320,15.EB90 would specify an array with a 22 bit field and a 15 bit field
      RT Logic's recommendation is to use the 2nd option.
  • Reported: GEMS 1.0b1 — Fri, 8 Aug 2008 04:00 GMT
  • Disposition: Resolved — GEMS 1.0
  • Disposition Summary:

    The GEMS PIM hex_value definition will be updated to make clear that all hex_values contained in arrays of hex_values must be of the same bit length.
    The ASCII PSM definition will be updated to make clear what formats are allowable for hex_values.

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

Response message examples do not clearly show the result_description.

  • Key: GEMS-13
  • Legacy Issue Number: 12766
  • Status: closed  
  • Source: Anonymous
  • Summary:

    Dave noted that the examples in the document do not clearly show the result description text. A simple ''Desc'' can be hidden. Better examples will help clear this up

  • Reported: GEMS 1.0b1 — Fri, 8 Aug 2008 04:00 GMT
  • Disposition: Resolved — GEMS 1.0
  • Disposition Summary:

    Replace all 'Desc' text with wordier descriptions that are obviously visible.

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

8.1.1.17 The XML schema for GetConfigResponse uses an undefined ConfigResul

  • Key: GEMS-9
  • Legacy Issue Number: 12762
  • Status: closed  
  • Source: Amergint Technologies ( Rob Andzik)
  • Summary:

    There is no type defined for ConfigResult in either the PSM or the PIM. This is meant to be the result_description

  • Reported: GEMS 1.0b1 — Fri, 8 Aug 2008 04:00 GMT
  • Disposition: Resolved — GEMS 1.0
  • Disposition Summary:

    The 'ConfigResult' type is really meant to be the 'result_description' defined in the base 'ResponseMessageType' in section 7.1.1.19.

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

GEMS-XML 8.1.1.9 XML Schema for Connect Request includes client_version

  • Key: GEMS-8
  • Legacy Issue Number: 12761
  • Status: closed  
  • Source: Amergint Technologies ( Rob Andzik)
  • Summary:

    The client_version is not defined in the PIM but offers the potential for client/server negotiations. This though might be too complex of a notion. Need to either delete it from the schema or update the PIM.
    Recommend deleting it.

  • Reported: GEMS 1.0b1 — Fri, 8 Aug 2008 04:00 GMT
  • Disposition: Resolved — GEMS 1.0
  • Disposition Summary:

    It is recommended that this notion of client_version be left out of the first version and reviewed for possible consideration at a later date.

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

Add XML and ASCII as normative references

  • Key: GEMS-20
  • Legacy Issue Number: 12967
  • Status: closed  
  • Source: Amergint Technologies ( Rob Andzik)
  • Summary:

    Add XML and ASCII as normative references

  • Reported: GEMS 1.0b1 — Wed, 22 Oct 2008 04:00 GMT
  • Disposition: Resolved — GEMS 1.0
  • Disposition Summary:

    Fill in section 3 with normative references for XML and ASCII.

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

Need an example of how to represent a parameter array in the GEMS-XML PSM

  • Key: GEMS-19
  • Legacy Issue Number: 12966
  • Status: closed  
  • Source: Amergint Technologies ( Rob Andzik)
  • Summary:

    Need an example of how to represent a parameter array in the GEMS-XML PSM

    a. This missing example was found during our document review

    b. Reported by RT Logic

  • Reported: GEMS 1.0b1 — Wed, 22 Oct 2008 04:00 GMT
  • Disposition: Resolved — GEMS 1.0
  • Disposition Summary:

    This type of example is not suited to stand alone. Instead one of the existing examples will be modified to include an array of parameters for the purposes of demonstrating this concept.

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

GEMS-XML 8.2.1 Need two additional examples in Directive Message/Response

  • Key: GEMS-10
  • Legacy Issue Number: 12763
  • Status: closed  
  • Source: Amergint Technologies ( Rob Andzik)
  • Summary:

    The examples would be enhanced by providing an example of a directive with parameters and one with return values. Maybe these can be combined.

  • Reported: GEMS 1.0b1 — Fri, 8 Aug 2008 04:00 GMT
  • Disposition: Resolved — GEMS 1.0
  • Disposition Summary:

    It seems appropriate to modify the example of a directive message in section 7.2.1 to include at least one parameter in the directive message and one return value in the directive message response. This would provide one comprehensive example of a directive message in the XML PIM.

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

GEMS PIM 7.5 Spelling error in section 7.5

  • Key: GEMS-7
  • Legacy Issue Number: 12760
  • Status: closed  
  • Source: Amergint Technologies ( Rob Andzik)
  • Summary:

    Incorrect: ''Users connecting to a GEMS device are provide a token...''
    Should be: ''.. are provided a token''

  • Reported: GEMS 1.0b1 — Fri, 8 Aug 2008 04:00 GMT
  • Disposition: Resolved — GEMS 1.0
  • Disposition Summary:

    Simple correct the spelling error.

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

GEMS PIM 7.7 Standard Device definitions not complete

  • Key: GEMS-6
  • Legacy Issue Number: 12759
  • Status: closed  
  • Source: Amergint Technologies ( Rob Andzik)
  • Summary:

    The standard device definitions are not defined yet. The original thought was that this section is populated by later revisions.
    Suggest this be left for future versions/FTF.

  • Reported: GEMS 1.0b1 — Fri, 8 Aug 2008 04:00 GMT
  • Disposition: Resolved — GEMS 1.0
  • Disposition Summary:

    Suggest this section be left empty with a short description regarding the notion of consistency across common devices. Future versions/FTF will expand this section with specific examples.

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

GEMS-ASCII messages do not specify a starting or trailing pipe character

  • Key: GEMS-12
  • Legacy Issue Number: 12765
  • Status: closed  
  • Source: Amergint Technologies ( Rob Andzik)
  • Summary:

    GEMS-ASCII messages do not specify a starting or trailing pipe character in either the table or in the examples. Dave's recommendation is to put this at the beginning of each message.

  • Reported: GEMS 1.0b1 — Fri, 8 Aug 2008 04:00 GMT
  • Disposition: Resolved — GEMS 1.0
  • Disposition Summary:

    A beginning pipe will be added to the definition of the ASCII PSM message header. No ending pipe will be specified as one or the other is sufficient for parsing purposes.

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

GEMS-XML 8.2.5 Typo in section 8.2.5: example indicates 2 params

  • Key: GEMS-11
  • Legacy Issue Number: 12764
  • Status: closed  
  • Source: Amergint Technologies ( Rob Andzik)
  • Summary:

    The example only shows one parameter. Need to update one or the other.

  • Reported: GEMS 1.0b1 — Fri, 8 Aug 2008 04:00 GMT
  • Disposition: Resolved — GEMS 1.0
  • Disposition Summary:

    The example is sufficient so it was decided to update the description to indicate only parameter would be requested.

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

9.2.2 Section 9.2.2: The example shows an incorrect message type

  • Key: GEMS-18
  • Legacy Issue Number: 12771
  • Status: closed  
  • Source: Amergint Technologies ( Rob Andzik)
  • Summary:

    The section provides a disconnect example, but the example has a connect message

  • Reported: GEMS 1.0b1 — Fri, 8 Aug 2008 04:00 GMT
  • Disposition: Resolved — GEMS 1.0
  • Disposition Summary:

    The example will be changed to demonstrate a disconnect message in the GEMS-ASCII PSM.

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

9.1.2 Figure in 9.1.2 uses RTL instead of GEMS

  • Key: GEMS-17
  • Legacy Issue Number: 12770
  • Status: closed  
  • Source: Amergint Technologies ( Rob Andzik)
  • Summary:

    The figure shows RTL instead of GEMS. Need to correct the figure.

  • Reported: GEMS 1.0b1 — Fri, 8 Aug 2008 04:00 GMT
  • Disposition: Resolved — GEMS 1.0
  • Disposition Summary:

    Replace the figure with a correct version.

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

GEMS-ASCII PSM is missing the ParameterSet definition

  • Key: GEMS-15
  • Legacy Issue Number: 12768
  • Status: closed  
  • Source: Amergint Technologies ( Rob Andzik)
  • Summary:

    There is no description of ParameterSets in the GEMS-ASCII PSM. This needs to be added.

  • Reported: GEMS 1.0b1 — Fri, 8 Aug 2008 04:00 GMT
  • Disposition: Resolved — GEMS 1.0
  • Disposition Summary:

    Discuss and flush out appropriately.

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

No discussion of escaping or quoting characters in the ASCII PSM

  • Key: GEMS-16
  • Legacy Issue Number: 12769
  • Status: closed  
  • Source: Amergint Technologies ( Rob Andzik)
  • Summary:

    Need to define a standard way to escape and/or quote characters in string types

  • Reported: GEMS 1.0b1 — Fri, 8 Aug 2008 04:00 GMT
  • Disposition: Resolved — GEMS 1.0
  • Disposition Summary:

    A new section (8.1.2 Reserved Words and Special Characters) will be added to discuss the requirements regarding any special characters and reserved words in the ASCII PSM.

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

The time format is closer to POSIX than UTC and does not allow for unambiguous leap second resolution

  • Key: GEMS-23
  • Legacy Issue Number: 13132
  • Status: closed  
  • Source: Boeing ( Mr. David Overeem)
  • Summary:

    1) The time format is closer to POSIX than UTC and does not allow for unambiguous leap second resolution.
    A. This new issue was raised during the FTF.
    B. Reported by David Overeem at Boeing

  • Reported: GEMS 1.0b1 — Fri, 8 Aug 2008 04:00 GMT
  • Disposition: Resolved — GEMS 1.0
  • Disposition Summary:

    Disposition: See issue 14112 for disposition

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

Section 7.3.2

  • Key: GEMS-2
  • Legacy Issue Number: 12754
  • Status: closed  
  • Source: Amergint Technologies ( Rob Andzik)
  • Summary:

    Need a message to retrieve the list of saved/available configuration files. There is no current way to obtain the list of available configurations.

  • Reported: GEMS 1.0b1 — Fri, 8 Aug 2008 04:00 GMT
  • Disposition: Resolved — GEMS 1.0
  • Disposition Summary:

    In the PIM the new messages are called GetConfigListMessage and GetConfigListResponse. The GetConfigListResponse includes a list of strings. Each string provides the name of a configuration.

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

GEMS PIM 7.3.2.1.5 Time stamp definition is vague and needs to be clarified

  • Key: GEMS-4
  • Legacy Issue Number: 12757
  • Status: closed  
  • Source: Amergint Technologies ( Rob Andzik)
  • Summary:

    The time stamp in the message header is loosely defined in the document. Need to clarify this. Suggest UTC following the time parameter type.

  • Reported: GEMS 1.0b1 — Fri, 8 Aug 2008 04:00 GMT
  • Disposition: Resolved — GEMS 1.0
  • Disposition Summary:

    Update all related time stamp fields to specify UTC. Also changed the examples in the GEMS-ASCII PSM section to us ASCII time parameter format for the time stamp.
    NOTE: There is an associated issue with this that was identified during the voting process. The time format is closer to POSIX than UTC and does not allow for unambiguous leap second resolution. Because the format of the message will likely not change, this should not impact GEMS 1.0 implementations. There are however several considerations that need to be taken in to account before a final decision can be made on using UTC vs POSIX. Therefore, the FTF is accepting the 3/4 yes vote as resolution of issue 12757. A new issue has been created (13132) and will be handled under a subsequent RTF to specifically address the UTC vs POSIX time concerns.

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

GEMS PIM Section 7.3.1.7: 64 Bit Integer Values

  • Key: GEMS-3
  • Legacy Issue Number: 12756
  • Status: closed  
  • Source: Amergint Technologies ( Rob Andzik)
  • Summary:

    Should 64 bit integer values be added to the PIM?

  • Reported: GEMS 1.0b1 — Fri, 8 Aug 2008 04:00 GMT
  • Disposition: Resolved — GEMS 1.0
  • Disposition Summary:

    Define the long type to be 64 bits in length. Originally the long type was redundant with the integer type. This approach matches the types used in XML.

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

GEMS PIM 7.3.2.4.2.1 The valid_state field is confusing

  • Key: GEMS-5
  • Legacy Issue Number: 12758
  • Status: closed  
  • Source: Amergint Technologies ( Rob Andzik)
  • Summary:

    The invalid_state field in the SetConfigResponse and LoadConfigResponse is confusing and might not apply to all cases (e.g. software only implementation). The original idea behind this was to provide a way to
    indicate whether or not the hardware was left in a valid state in the event of an error.
    Suggest moving this to a HARDWARE_ERROR ResultCode

  • Reported: GEMS 1.0b1 — Fri, 8 Aug 2008 04:00 GMT
  • Disposition: Resolved — GEMS 1.0
  • Disposition Summary:

    Remove the valid_state Boolean members of the SetConfigResponse and LoadConfigResponse classes in the PIM. This change also needs propagating throughout the document. All references and sections to valid_state must be removed.

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

Correct various table and section references throughout the document

  • Key: GEMS-1
  • Legacy Issue Number: 12753
  • Status: closed  
  • Source: Amergint Technologies ( Rob Andzik)
  • Summary:

    There are a number of places where internal table references are incorrect. This includes a few places where XXX is used.

  • Reported: GEMS 1.0b1 — Fri, 8 Aug 2008 04:00 GMT
  • Disposition: Resolved — GEMS 1.0
  • Disposition Summary:

    All table references have been updated to reference existing tables with correct table numbers.

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

Section 7.3.2.5.1

  • Key: GEMS11-1
  • Legacy Issue Number: 12755
  • Status: closed  
  • Source: Amergint Technologies ( Rob Andzik)
  • Summary:

    Need to describe what a GET message returns when targeted to a proxy. There is no description of what is returned when a GetMessage is sent to a proxy.
    Options:

    • Return information on the proxy such as an array of target names available ''behind'' the proxy.
    • Return all parameters for all devices behind the proxy
    • Defined standard parameters for the proxy which would then be returned
  • Reported: GEMS 1.0b1 — Fri, 8 Aug 2008 04:00 GMT
  • Disposition: Resolved — GEMS 1.1
  • Disposition Summary:

    Return a parameter with the name 'targets' that provides an array of strings, each array value represents a single target.

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