1. OMG Mailing List
  2. Open Architecture RADAR Interface Standard (OARIS) 3.1 Revision Task Force

Open Issues

  • Issues not resolved
  • Name: oaris-3-1-rtf
  • Issues Count: 4

Issues Descriptions

Encyclopaedic Data could support dedicated discovery of data sets that can be imported or exported

  • Key: OARIS31-4
  • Status: open  
  • Source: BAE SYSTEMS ( Mr. Ollie Newman)
  • Summary:

    Currently the specification implies that the manage subsystem parameters service is used to be able to provide a list of encyclopaedic data alongside other subsystem parameters. It might be a nice separation of concerns if the encyclopaedic data service provided a dedicated means for subsystems to advertise data sets that they are prepared to import and export

  • Reported: OARIS 3.0b2 — Tue, 30 Jun 2026 09:40 GMT
  • Updated: Tue, 30 Jun 2026 13:00 GMT

Encyclopaedic Data services could support data export

  • Key: OARIS31-3
  • Status: open  
  • Source: BAE SYSTEMS ( Mr. Ollie Newman)
  • Summary:

    It would be desirable for the services to support data export as well such that any encyclopaedic data that had been tailored by a user could then be exported for use on other systems or to be archived for later reloading after events such as a system reinstallation.

  • Reported: OARIS 3.0b2 — Tue, 30 Jun 2026 09:31 GMT
  • Updated: Tue, 30 Jun 2026 13:00 GMT

Encyclopaedic Data import could support progress reporting

  • Key: OARIS31-2
  • Status: open  
  • Source: BAE SYSTEMS ( Mr. Ollie Newman)
  • Summary:

    Some encyclopaedic data sets can be quite large and therefore giving a subsystem the ability to report progress updates to the CMS such that a user can be kept informed could be beneficial

  • Reported: OARIS 3.0b2 — Tue, 30 Jun 2026 09:29 GMT
  • Updated: Tue, 30 Jun 2026 12:59 GMT

end_sensor_track_type should key on the_sensor_track_id

  • Key: OARIS31-1
  • Status: open  
  • Source: BAE SYSTEMS ( Mr. Ollie Newman)
  • Summary:

    In the DDS PSM IDL the end_sensor_track_type has a key on subsystem_id. As each message is related to a particular track id then it should also be keyed on the_sensor_track_id such that subsequent instances relating to other tracks do not overwrite the current instance before it is able to be read by subscribers.

  • Reported: OARIS 3.0b1 — Wed, 30 Oct 2024 12:04 GMT
  • Updated: Wed, 30 Oct 2024 12:04 GMT