IOOS Gateway

DAP2.1 Namespace

dap2:Container

After thinking about it (and looking at the ontology), Container is the obvious superclass of everything that contains other things, e.g. attributes. So it is the domain of dap:isContainerOf and all the attributes.

So the local attribute declarations at the end are now:

<owl:DatatypeProperty rdf:about="http://source.url/for/ddx/document.ddx/att#NC_GLOBAL">
  <rdfs:domain rdf:resource="http://xml.opendap.org/ns/DAP2#Container" />
  <rdfs:isDefinedBy rdf:resource="" />
</owl:DatatypeProperty>
<owl:DatatypeProperty rdf:about="http://source.url/for/ddx/document.ddx/att#Conventions">
  <rdfs:domain rdf:resource="http://xml.opendap.org/ns/DAP2#String" />
  <rdfs:isDefinedBy rdf:resource="" />
</owl:DatatypeProperty>

and should be:

<owl:DatatypeProperty rdf:about="http://source.url/for/ddx/document.ddx/att#NC_GLOBAL">
   <rdfs:domain rdf:resource="http://xml.opendap.org/ns/DAP2Container" />
   <rdfs:isDefinedBy rdf:resource="" />
</owl:DatatypeProperty>
<owl:DatatypeProperty   rdf:about="http://source.url/for/ddx/document.ddx/att#Conventions">
  <rdfs:domain rdf:resource="http://xml.opendap.org/ns/DAP2Container" />
  <rdfs:isDefinedBy rdf:resource="" />
</owl:DatatypeProperty>

i.e. all the att: properties should have a rdfs:domain of &dap2:Container (we decided to leave the range undeclared, though that could be &dap2;Float32, etc, except that we would have to define UNION classes if two different types were used, which is way more pain than it is worth).

In short:

The rdf:resource attribute of the rdf:domain element is always dap2:Container.

To be clear here: the domain is what is on the left of the property/attribute, i.e. where it belongs, the range is what is on the right of a property, i.e. its value. So saying the domain is a container says that anything that possesses an attribute is a container. The value of the attribute is the range, and they are either atoms, or containers.