optional, single



Bracketing of additional, program specific information which are necessary for the calculation of tissue saturation, or software internal parameters for the graphical representation of data.

An UDDF parser does not evaluate statements between <applicationdata> and </applicationdata>, but sends them directly without any interpretation to the calling program. With it it is made possible that programs can store specific meta information not known to UDDF. The only convention is that every program has to put its meta information inside <applicationdata> ... </applicationdata> brackets.

Annotation for programmers: Please, document in which form you store your data for tissue saturation or other parameters, so that third party programs are able to read and process them correctly!

Dear programmers, please send an email to <kai bei streit punkt cc> with your desired element name to include it in the UDDF documentation! Thank you!

At present the following elements are used: <decotrainer>, <hargikas>, <heinrichsweikamp>, <tausim>, <tautabu>. These elements may occur also simultaneously, for example, if a dive profile is read by a program and subsequently is read by another software and is stored again.

Parent Elements

<bottomtimetable>, <dive>, <profile>, <setdcdecomodel>, <table>

Child Elements

<decotrainer>, <hargikas>, <heinrichsweikamp>, <tausim>, <tautabu>

See Also

<decotrainer>, <dive>, <hargikas>, <heinrichsweikamp>, <tausim>, <tautabu>


see <hargikas>, and <tausim>