DAP4: Requests: Difference between revisions

From OPeNDAP Documentation
⧼opendap2-jumptonavigation⧽
No edit summary
No edit summary
 
Line 1: Line 1:
[[Category:Development|Development]] [[Category:DAP4|DAP4]]
<font size="+1" color="red">This is an old document that captures the starting point of the OPULS design work. It's out of date and should be referenced only as a baseline for the work.</font>
[[OPULS_Development | <-- back to OPULS Development]]
Author: NDP
Note that while it's increasingly common for DAP servers to provide different ways that a dataset's metadata may be extended, and often those provide multiple ways of accessing the same underlying data, albeit with different metadata. Those extensions are all accessed by dereferencing a URL and we consider each URL to refer to a unique dataset. This can be confusing because the word 'dataset' is often synonymous with 'file' although there's nothing in DAP2 or DAP4 that makes that association required or calls it out as a case with special treatment
Note that while it's increasingly common for DAP servers to provide different ways that a dataset's metadata may be extended, and often those provide multiple ways of accessing the same underlying data, albeit with different metadata. Those extensions are all accessed by dereferencing a URL and we consider each URL to refer to a unique dataset. This can be confusing because the word 'dataset' is often synonymous with 'file' although there's nothing in DAP2 or DAP4 that makes that association required or calls it out as a case with special treatment



Latest revision as of 19:14, 31 August 2012

This is an old document that captures the starting point of the OPULS design work. It's out of date and should be referenced only as a baseline for the work.

<-- back to OPULS Development

Author: NDP

Note that while it's increasingly common for DAP servers to provide different ways that a dataset's metadata may be extended, and often those provide multiple ways of accessing the same underlying data, albeit with different metadata. Those extensions are all accessed by dereferencing a URL and we consider each URL to refer to a unique dataset. This can be confusing because the word 'dataset' is often synonymous with 'file' although there's nothing in DAP2 or DAP4 that makes that association required or calls it out as a case with special treatment


Dataset Request

DAP4:_Data_Model#Constraint_Expressions

Data Request

DAP4:_Data_Model#Constraint_Expressions


Other Services

RDF Request