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

Robotic Localization Service (RLS) RTF — Open Issues

  • Key: RLS11
  • Issues Count: 4
Open Closed All
Issues not resolved

Issues Descriptions

Mismatch in Error Type (Figure 6) and Error Information (Figure 7) definitions

  • Key: RLS11-1
  • Legacy Issue Number: 13130
  • Status: open  
  • Source: JARA ( Shuichi Nishio)
  • Summary:

    There are mismatches in the hierarchical structure of Error Type
    classes and Error Information classes, which shall correspond to each
    other. One solution will be to:

    • add ET_ErrorDistribution, derived from 'RoLo Error Type'
    • make ET_Gaussian, ET_UniformGaussian, ET_ParticleSet and
      ET_MixtureModel to be derived from ET_ErrorDistribution
  • Reported: RLS 1.0b1 — Mon, 1 Dec 2008 05:00 GMT
  • Updated: Wed, 11 Mar 2015 11:15 GMT

XML target namespace incorrect

  • Key: RLS11-4
  • Legacy Issue Number: 17368
  • Status: open  
  • Source: Object Management Group ( Andrew Watson)
  • Summary:

    A.1 paragraph 3 says "Hereafter, the target namespace of the given XML schemas is assumed to be “http://www.omg.org/rls/1.1.” Also, the prefix “rls” indicates the same namespace."

    However, in fact this URL should be "http://www.omg.org/spec/RLS/1.1".

    This needs to be corrected in the text of the specification (3 places, all on page 79), and in the Schema file dtc/2011-05-13, linked from http://www.omg.org/spec/RLS/1.1/. A corrected version of this file is available as dtc/12-05-01.

  • Reported: RLS 1.1 — Tue, 15 May 2012 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT

Specifying a set of CRS instances

  • Key: RLS11-3
  • Legacy Issue Number: 16188
  • Status: open  
  • Source: JARA ( Shuichi Nishio)
  • Summary:

    Occasionally, there are situation where a set of CRSs needs to be defined as acceptable for a specific Interface::Stream, such as accepting a set of IDs based on several CRSs for a single stream. This cannot be realized in the current specification

  • Reported: RLS 1.0 — Sun, 8 May 2011 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT

Data Format definitions

  • Key: RLS11-2
  • Legacy Issue Number: 16181
  • Status: open  
  • Source: JARA ( Shuichi Nishio)
  • Summary:

    Data formats that each Interface::Stream can handle are defined in Interface::StreamAbility. dataFormat. However, in certain cases, data formats may be automatically handled by middlewares. We shall reconsider to what extent data formats are treated as part of the RLS specification. Also, definition of each data format is currently not described. As other parts, such as coordinate reference system definitions, specification for describing data format definitions shall be defined.

  • Reported: RLS 1.0 — Sun, 8 May 2011 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT