See the RDFS. To use the ontology use the following line in the <rdf:RDF> tag:
Currently the following certification blocks from PADI are supported, see padi.rdf:
If you have the Open Water Certification add the following line to your diver block:
<dive:Certification rdf:resource="http://scubadive.networld.to/padi.rdf#OW" />If you have a certificate from another organisation than PADI or if you grade is missing please contact us.
There are a few air mix predefined under airmix.rdf
If you dive with normal air add the following line to your dive:Diver block.
<dive:airMix rdf:resource="http://scubadive.networld.to/airmix.rdf#Air" />
As scuba diver you have the same equipment types as others. For this reason there are predefined types under equipment.rdf. See the following example how such a resource URL look like.
<dive:Equipment> ... <dive:EquipmentType rdf:resource="http://scubadive.networld.to/equipment.rdf#mask" /> ... </dive:Equipment>
If you have a dive computer you want to store a detailed dive profile with depth, temperature, time, bookmark for each sample. For this purpose it is recommended to store the profile in an external RDF file and link it from the related dive. See the example file how such a profile should look like. To link the dive profile with the related dive you should use the following line in the Dive block (or a subclass of it):
Normally your dive partners have to sign the dive in the logbook. You could reach the same effect if you are lucky and dive with partners who have a gpg/pgp key. Add for each of your partners the following block and beg your partners to sign your dive file with there key (the resulting signature file is named "diveX_buddyY.asc" and located in the same directory as the dive file.
<wot:assurance> <wot:Endorsement rdf:about="diveX_buddyY.asc" /> <dc:title>Dive Confirmation by BuddyY</dc:title> <wot:endorser rdf:nodeID="KeyBuddyY"/> </wot:Endorsement> </wot:assurance>The code above comes in the same block as the dive data and in the partner section (in the block of the partner that owns the key) comes the information about the key.
<wot:PubKey rdf:nodeID="KeyBuddyY"> <wot:hex_id>1234567</wot:hex_id> <wot:length>1024</wot:length> <wot:fingerprint>1234567890123456789012345678901234567890</wot:fingerprint> </wot:PubKey>Don't forget to add the namespace definition of wot and dc.
This ontology describes only scuba diving relevant vocabulary and for sure you would use other RDFS/OWL languages to receive a full description of your dives.