IOOS Gateway: Difference between revisions

From OPeNDAP Documentation
⧼opendap2-jumptonavigation⧽
(New page: == 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. at...)
 
No edit summary
 
(12 intermediate revisions by one other user not shown)
Line 1: Line 1:
== DAP2.1 Namespace ==
Changes to the DAP, Hyrax, or other proposals stemming from the WCS Gateway Project.  


=== dap2:Container ===


After thinking about it (and looking at the ontology), Container is
Much of the WCS gateway work is focused on:
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:
# Providing DAP2 protocol access to WCS served data.


<owl:DatatypeProperty rdf:about="http://source.url/for/ddx/document.ddx/att#NC_GLOBAL">
=== DAP2 access to data served by WCS ===
  <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
* [[WCS_Data Access|Data access via DAP2 requests]]
&dap2:Container (we decided to leave the range undeclared, though that
* [[WCS Site Analysis |WCS Server Analysis]]
could be &dap2;Float32, etc, except that we would have to define UNION
==== DAP2.1 Namespace ====
classes if two different types were used, which is way more pain than
There have been some proposed changes to the DAP2 namespace (for the DDX) to hep accommodate this work.
it is worth).
* [[WCS DAP Attributes|DAP Attributes]]


In short:
----
<blockquote>'''The rdf:resource attribute of the rdf:domain element is always dap2:Container.'''</blockquote>
 
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.

Latest revision as of 17:30, 29 April 2009

Changes to the DAP, Hyrax, or other proposals stemming from the WCS Gateway Project.


Much of the WCS gateway work is focused on:

  1. Providing DAP2 protocol access to WCS served data.

DAP2 access to data served by WCS

DAP2.1 Namespace

There have been some proposed changes to the DAP2 namespace (for the DDX) to hep accommodate this work.