SAC-SWG-ENUM Archives

January 2018

SAC-SWG-ENUM@DISCUSSIONS.SISOSTDS.ORG

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Flemming Joergensen <[log in to unmask]>
Reply To:
SAC-SWG-ENUM <[log in to unmask]>
Date:
Tue, 30 Jan 2018 03:52:35 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (25 lines)
I'm happy with using the acronym in the name and then adding the acronym to table 2 as e.g.:
ALRS Avion Leger de Surveillance and Reconnaissance (Light Surveillance and Reconnaissance Aircraft)

We display the entity name in our simulator and those with very long names are sometimes difficult to read, so that's just my subjective opinion.


You should include a base ID to the original version of the aircraft.
Depending on how many Beechcraft variants France may get, I would suggest updating the CR to either:
Beechcraft Model B300 (King Air 350) 1.2.71.7.4 Variation = y Base ID 1.2.225.85.22.1.5
Beechcraft ALSR 1.2.71.7.4.1

or:
Beechcraft ALSR 1.2.71.7.4 Variation = y Base ID 1.2.225.85.22.1.5


I'm unsure if this CR should be placed on OH or OF until the aircraft is completed. I'm fine with adding it now if France are already using an interim model B300.

Regards
Flemming Joergensen

########################################################################

To unsubscribe from the SAC-SWG-ENUM list, click the following link:
https://discussions.sisostds.org/index.htm?SUBED1=SAC-SWG-ENUM&A=1

ATOM RSS1 RSS2