Via <tripmembership> the dive trip can be indicated during which the dive was made. Because the <profiledata> section (where all dive data are stored) comes before the <divetrip> section — so that a cross-referencing is possible on dive data — in the UDDF file, it is not possible to cross-reference a <trip> within a <dive> element. Therefore, the <tripmembership> element allows for an assignment of a dive to trip.
<dive>, <informationafterdive>
(see also <dive>)
<profiledata>
<repetitiongroup id="rg_23">
<dive id="dive_345">
<informationbeforedive>
<tripmembership ref="dt_red-sea-2006"/>
<!-- here more pre-dive statements -->
</informationbeforedive>
<!-- here more statements describing this dive (profile) -->
</dive>
<dive id="dive_346">
<informationbeforedive>
<tripmembership ref="dt_red-sea-2006"/>
<!-- here more pre-dive statements -->
</informationbeforedive>
<!-- here more statements describing this dive (profile) -->
</dive>
<dive id="dive_347">
<informationbeforedive>
<tripmembership ref="dt_red-sea-2006"/>
<!-- here more pre-dive statements -->
</informationbeforedive>
<!-- here more statements describing this dive (profile) -->
</dive>
<!-- here more dives listed -->
</repetitiongroup>
</profiledata>
<divetrip>
<trip id="dt_red-sea-2006">
<trippart type="boat, organized">
<name>Dive Trip Red Sea 2006</name>
<relateddives>
<link ref="dive_345"/>
<link ref="dive_346"/>
<link ref="dive_347"/>
<!-- here more dives can be cross-referenced -->
</relateddives>
<!-- here more statements -->
</trippart>
</trip>
</divetrip>