TACSIT Controller Interface Avatar
  1. OMG Specification

TACSIT Controller Interface — Open Issues

  • Acronym: TCI
  • Issues Count: 17
  • Description: Issues not resolved
Open Closed All
Issues not resolved

Issues Descriptions

Selection by track number

  • Key: TCI11-43
  • Legacy Issue Number: 15799
  • Status: open  
  • Source: THALES ( Hugues Vincent)
  • Summary:

    TACSIT Controller Interface for CMS Systems
    Version 1.0 - Beta 1
    Date: October 2010
    dtc/10-10-11

    Chapter/Section: 7.1
    Title: Selection by track number
    Nature: Enhancement
    Severity: Significant

    The ways to select by track number as well as to select within geographic geometry seem to me inefficient. Indeed, in that way there are 2 accesses to the TACSIT server(s): one to query on one to effectively select when an interface proposing to select from a an interface with a query as parameter would be more efficient since it implied just one access call to the TACSIT server.

  • Reported: TCI 1.0b1 — Wed, 3 Nov 2010 04:00 GMT
  • Updated: Wed, 1 Feb 2023 21:57 GMT

addSelectionListener

  • Key: TCI11-45
  • Legacy Issue Number: 15797
  • Status: open  
  • Source: THALES ( Hugues Vincent)
  • Summary:

    TACSIT Controller Interface for CMS Systems
    Version 1.0 - Beta 1
    Date: October 2010
    dtc/10-10-11

    -------------------------------
    Chapter/Section: 7.1
    Title: addSelectionListener
    Nature: Enhancement
    Severity: Significant

    This API seems to me very poor. Wouldn't it be possible to add some convenience APIs allowing a listener on the primary selection, the secondary selection, on setting or unsetting on of these selection... This would lower the number of server-client exchanges for nothing but test that this not something of interest.

  • Reported: TCI 1.0b1 — Wed, 3 Nov 2010 04:00 GMT
  • Updated: Wed, 1 Feb 2023 21:57 GMT

GeoPosition vs. GeodeticPosition

  • Key: TCI11-48
  • Legacy Issue Number: 15792
  • Status: open  
  • Source: THALES ( Hugues Vincent)
  • Summary:

    TACSIT Controller Interface for CMS Systems
    Version 1.0 - Beta 1
    Date: October 2010
    dtc/10-10-11

    -------------------------------
    Chapter/Section: all
    Title: GeoPosition vs. GeodeticPosition
    Nature: Revision
    Severity: Significant

    Two classes seems to speak of the same stuff: GeoPosition (see Section 2.3.1.3) and GeodeticPosition. My guess is that GeoPosition should be renamed ad GeodeticPosition. Please fix or explain.

  • Reported: TCI 1.0b1 — Wed, 3 Nov 2010 04:00 GMT
  • Updated: Wed, 1 Feb 2023 21:57 GMT

Dealing with error at PIM level

  • Key: TCI11-47
  • Legacy Issue Number: 15793
  • Status: open  
  • Source: THALES ( Hugues Vincent)
  • Summary:

    TACSIT Controller Interface for CMS Systems
    Version 1.0 - Beta 1
    Date: October 2010
    dtc/10-10-11

    Chapter/Section: all
    Title: Dealing with error at PIM level
    Nature: Revision
    Severity: Significant

    Error should be dealt with at the PIM level for each method.

  • Reported: TCI 1.0b1 — Wed, 3 Nov 2010 04:00 GMT
  • Updated: Wed, 1 Feb 2023 21:57 GMT

SelectionType

  • Key: TCI11-44
  • Legacy Issue Number: 15798
  • Status: open  
  • Source: THALES ( Hugues Vincent)
  • Summary:

    TACSIT Controller Interface for CMS Systems
    Version 1.0 - Beta 1
    Date: October 2010
    dtc/10-10-11

    Chapter/Section: 7.1
    Title: SelectionType
    Nature: Clarification
    Severity: Minor

    It is not clear what "OTHER" is for.

  • Reported: TCI 1.0b1 — Wed, 3 Nov 2010 04:00 GMT
  • Updated: Wed, 1 Feb 2023 21:57 GMT

Stanard - editorial

  • Key: TCI11-46
  • Legacy Issue Number: 15796
  • Status: open  
  • Source: THALES ( Hugues Vincent)
  • Summary:

    TACSIT Controller Interface for CMS Systems
    Version 1.0 - Beta 1
    Date: October 2010
    dtc/10-10-11

    -------------------------------
    Page: 7
    Title: Stanard
    Nature: Clarification
    Severity: Minor

    "stanard" instead of "standard".

  • Reported: TCI 1.0b1 — Wed, 3 Nov 2010 04:00 GMT
  • Updated: Wed, 1 Feb 2023 21:57 GMT

Conformance Criteria

  • Key: TCI11-42
  • Legacy Issue Number: 15794
  • Status: open  
  • Source: THALES ( Hugues Vincent)
  • Summary:

    Chapter/Section: 2
    Title: Conformance Criteria
    Nature: Revision
    Severity: Significant

    Please add "completely" between "match" and "one or more of".

  • Reported: TCI 1.0b1 — Wed, 3 Nov 2010 04:00 GMT
  • Updated: Wed, 1 Feb 2023 21:57 GMT

Setting the categories of selectable items

  • Key: TCI11-40
  • Legacy Issue Number: 15800
  • Status: open  
  • Source: THALES ( Hugues Vincent)
  • Summary:

    TACSIT Controller Interface for CMS Systems
    Version 1.0 - Beta 1
    Date: October 2010
    dtc/10-10-11

    Chapter/Section: 7.1
    Title: Setting the categories of selectable items
    Nature: Enhancement
    Severity: Significant

    I didn't find any interface allowing to set the categories of selectable items.

  • Reported: TCI 1.0b1 — Wed, 3 Nov 2010 04:00 GMT
  • Updated: Wed, 1 Feb 2023 21:57 GMT

Consistent centring with a moving entity

  • Key: TCI11-38
  • Legacy Issue Number: 15802
  • Status: open  
  • Source: THALES ( Hugues Vincent)
  • Summary:

    The proposed way to do the consistent centring with a moving entity seems inefficient and will imply unsmooth multiple movements of the viewport.
    A specific interface allowing such a slaved centring with an entity would be, in my point of view, by far better than this.

  • Reported: TCI 1.0b1 — Wed, 3 Nov 2010 04:00 GMT
  • Updated: Wed, 1 Feb 2023 21:57 GMT

Sample C++ header files

  • Key: TCI11-37
  • Legacy Issue Number: 15803
  • Status: open  
  • Source: THALES ( Hugues Vincent)
  • Summary:

    Chapter/Section: 9
    Title: Sample C++ header files
    Nature: Enhancement
    Severity: Significant

    Please replace the "sample" before "C++ header files" with "normative".

  • Reported: TCI 1.0b1 — Wed, 3 Nov 2010 04:00 GMT
  • Updated: Wed, 1 Feb 2023 21:57 GMT

getEntityTypes

  • Key: TCI11-39
  • Legacy Issue Number: 15801
  • Status: open  
  • Source: THALES ( Hugues Vincent)
  • Summary:

    "getEntityTypes" is misnamed because it doesn't get all the entity types, hence a name such as "getSelectableEntityTypes" would be more explicit.

  • Reported: TCI 1.0b1 — Wed, 3 Nov 2010 04:00 GMT
  • Updated: Wed, 1 Feb 2023 21:57 GMT

Ref. to 6.3.2

  • Key: TCI11-41
  • Legacy Issue Number: 15795
  • Status: open  
  • Source: THALES ( Hugues Vincent)
  • Summary:

    TACSIT Controller Interface for CMS Systems
    Version 1.0 - Beta 1
    Date: October 2010
    dtc/10-10-11

    Page: 7
    Title: Ref. to 6.3.2
    Nature: Clarification
    Severity: Minor

    Broken reference to section 6.3.2.

  • Reported: TCI 1.0b1 — Wed, 3 Nov 2010 04:00 GMT
  • Updated: Wed, 1 Feb 2023 21:57 GMT

normative PIM is expressed as a MagicDraw file

  • Key: TCI11-3
  • Legacy Issue Number: 15603
  • Status: open  
  • Source: Model Driven Solutions ( Mr. Steve Cook)
  • Summary:

    In the AB today, when the TACSIT submission was presented, I noted that the normative PIM is expressed as a MagicDraw file, not a pure OMG-compliant XMI file. The normative PIM should be an OMG-compliant file and the MagicDraw file should be a convenience artifact.

  • Reported: TCI 1.0b1 — Mon, 20 Sep 2010 04:00 GMT
  • Updated: Wed, 1 Feb 2023 21:57 GMT

The machine readable files include redundant and/or useless files

  • Key: TCI11-1
  • Legacy Issue Number: 15607
  • Status: open  
  • Source: Adaptive ( Mr. Pete Rivett)
  • Summary:

    The machine readable files include redundant and/or useless files – the .mdr and mdr.bak files are useless and the mdzip is not needed as well as the .xml file since one is a compressed version of the other.

  • Reported: TCI 1.0b1 — Mon, 20 Sep 2010 04:00 GMT
  • Updated: Wed, 1 Feb 2023 21:57 GMT

Compliance Section issue

  • Key: TCI11-4
  • Legacy Issue Number: 15605
  • Status: open  
  • Source: Adaptive ( Mr. Pete Rivett)
  • Summary:

    The Compliance section should state how software complies e.g. it might say that for the Java PSM that software will implement all the normative APIs and exhibit the behavior for each as defined in the specification.

  • Reported: TCI 1.0b1 — Mon, 20 Sep 2010 04:00 GMT
  • Updated: Wed, 1 Feb 2023 21:57 GMT

The Normative References section should be in part 2

  • Key: TCI11-5
  • Legacy Issue Number: 15604
  • Status: open  
  • Source: Adaptive ( Mr. Pete Rivett)
  • Summary:

    The Normative References section should be in part 2. However the current reference is not Normative and so the section should be blank

  • Reported: TCI 1.0b1 — Mon, 20 Sep 2010 04:00 GMT
  • Updated: Wed, 1 Feb 2023 21:57 GMT

There is a Model file for the Java PSM but not the C++ PSM as claimed in the Manifest.

  • Key: TCI11-2
  • Legacy Issue Number: 15606
  • Status: open  
  • Source: Adaptive ( Mr. Pete Rivett)
  • Summary:

    There is a Model file for the Java PSM but not the C++ PSM as claimed in the Manifest.

  • Reported: TCI 1.0b1 — Mon, 20 Sep 2010 04:00 GMT
  • Updated: Wed, 1 Feb 2023 21:57 GMT