Difference between revisions of "Component database XML format"

From OpenRocket wiki
Jump to navigation Jump to search
(initial component database format design)
 
m (1 revision: Import existing wiki English pages)
(No difference)

Revision as of 00:17, 16 February 2013

Ideas for the design of an XML format for component databases.

Please clean this up, it's horribly messy...


<componentdatabase> - base container element, surrounds everything


<manufacturers> - list of manufacturers used in this database file

<manufacturer id="mfgid"> - definition of a single manufacturer
(id must be unique within this file, does not need to be globally unique)

<displayname> - a short display/common name of the manufacturer
<fullname> - the full name of the manufacturer
<url> - Manufacturer URL
<logo> - Manufacturer logo (? - maybe a bit problematic)


<materials> - list of materials used in this database file

<material id="matid">
<name lang="">
<type>bulk|surface|line</type>
<density>

  • Are materials really needed? For most components the total mass should be known, and the best way to use it is to compute the component density from the mass. This allows the user to modify the component (e.g. shorten a body tube) and the mass changes correspondingly.


<components>

<bodytube> Common data:

<name> - short name of the part (? - is this necessary, or should it just be labeled by mfg and partno)
<partno> - Part number / ID
<description> - longer description of the part
<manufacturer ref="mfgid">
<url> - URL related to the component (? - is this useful)

<diameter>
<length>
...