On Wed, 15 Oct 2003 10:08:17 -0400
On Wed, 15 Oct 2003 10:08:17 -0400
Bruce Jackson <[EMAIL PROTECTED]> wrote:
Does anyone on the list have experience using an XML parser with C++?
If so, can you recommend a decent set of parser tools?
--Bruce
Hi, Bruce:
Check out the FlightGear (www.flightgear
Does DAVE-ML only cover vehicle characteristics, or does it (will it)
cover environment and initial conditions?
A question has been raised here in Houston that I found interesting.
Say that a simulation application is serving as a prototyping tool for
a new flight software capability for some v
I've been looking at the data table format for DAVE-ML, for example:
9.5013e-01 6.1543e-01 5.7891e-02 1.5274e-02 8.3812e-01
1.9343e-01
2.3114e-01 7.9194e-01 3.5287e-01 7.4679e-01 1.9640e-02
6.8222e-01
8.2141e-01 4.1027e-01 2.7219e-01 2.0265e-01 3.0462e-01
8.5366e-01
4.4470e-01
I believe it would be desirable to have a text field in AERO-ML to specify a
license for the file, and also to have a field for specifying the
sensitivity (secret, classified, proprietary, etc.).
I suppose that the license field could look like this:
-or-
For more information, see www.gnu.o
> Would there be merit to having an optional subelement to sensitivity,
> such as classification? This would allow, if sensitivity was
> 'classified' to indicate the level of classification (confidential,
> secret, top secret) (at least in the US, that's how this works).
>
> -- Bruce
Actually, pe
> I think the idea has merit.
>
> Am I correct in implying that the "sensitivity" would differ from say
> the classification attributed to a particular reference document?
Yes. The idea is that "sensitivity" - or perhaps more appropriately,
"classification" - would apply to the model itself, not t
