RE: C++ XML Parser of choice

> From: Jeremy Furtek [mailto:[EMAIL PROTECTED] > Sent: Thursday, October 16, 2003 3:43 PM > To: [EMAIL PROTECTED] > Subject: Re: C++ XML Parser of choice > > I have been using the Xerces-C++ parser for an application, and > it has been more than adequate. > > http://xml.apache.org/xerces-c/index.h

Danger from Microsoft?

The following patent may not affect DAVE-ML at all, but it is a strange attempt by Microsoft to patent something that seems unpatentable: http://patft.uspto.gov/netacgi/nph-Parser?Sect1=PTO2&Sect2=HITOFF&u=/netahtm l/search-adv.htm&r=9&p=1&f=G&l=50&d=ptxt&S1=Microsoft.ASNM.&OS=AN/Microsoft& RS=AN/

RE: DAVE-ML aircraft dataset development at DSTO - Australia

on-validating XML parser, though I am looking at turning on that capability if possible. For JSBSim (which can also be run in a standalone mode apart from FlightGear) I am extending the easyXML parser in a C++ class to parse our new aircraft config file format. I would be interested in reading

RE: Data tables

> The suggestion JSB has made looks to be in accordance with a "pure" XML > or HTML layout, but in the DSTO application I'm involved in we're using > the Xerces-C parser to build our DOM at low level, so the approach of > tagging each table point will result in many more short nodes in the DOM > ra

RE: [fs] RE: Data tables

> Summarising, the current DAVE-ML gridded table structure is valid XML > but the gridded tables are not as fine-grained as they could be. > However, the current structure seems to me a reasonable balance between > size of the resulting DOM and accessibility of data points within it. > Division int

RE: Units of Measure for use in Math-ML datasets

= 1.00; convert["RAD"]["RAD"] = 1.00; convert["M2"]["M2"] = 1.00; convert["FT2"]["FT2"] = 1.00; convert["KG*M2"]["KG*M2"] = 1.00; convert["SLUG*FT2"]["SLUG*FT2"] = 1.00; convert["KG"]["KG"] = 1.00; convert["LBS"]["LBS"] = 1.00; convert["LBS/FT"]["LBS/FT"] = 1.00; convert["N/M"]["N/M"] = 1.00; convert["LBS/FT/SEC"]["LBS/FT/SEC"] = 1.00; convert["N/M/SEC"]["N/M/SEC"] = 1.00; convert["PSI"]["PSI"] = 1.00; convert["INHG"]["INHG"] = 1.00; convert["HP"]["HP"] = 1.00; Since this is only done at initialization time, CPU usage is not so critical for us. I'd be interested in hearing more about standard unit abbrev.s, though. Jon Berndt

RE: XML for Stores Load-out Information

> As Geoff Brian has outlined previously, DSTO is in the > process of developing aircraft datasets, including aircraft > configuration properties, aerodynamics, propulsion and mass > properties in DAVE-ML for use with their simulation codes. > We are also developing a C++ library, named Janus, to >

RE: Dave-ML and the Australian Janus C++ Interface class.

> I hope this will be of interest. It is. Unfortunately, the last reference in the paper lists an URL that isn't one: [Brian, 2004] G. Brian, Flight Systems Units of Measure Guidelines, viewed 12 December 2004, http://larda/Reference/UnitStandard/FltSysUnitStandard.html. Is this the same thing

DAVEML XML Schema available?

I visited the DAVEML web page, but did not seem mention of an XML Schema for DAVEML. I seem to recall some mention of the existence of a schema. Is there a Schema for DAVEML? I suspect that there is a way to convert a DTD to a Schema. I'm using oXygenXML as an editor. Jon Berndt

Table data, XSL, and SVG

I was noticing a gridded table definition (from the example on the DAVEML web site): 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