OPULS Development: Difference between revisions
From OPeNDAP Documentation
⧼opendap2-jumptonavigation⧽
| Line 9: | Line 9: | ||
# [[DAP4: Checksum | Checksum]] | # [[DAP4: Checksum | Checksum]] | ||
# [[DAP Service Terminus]] | # [[DAP Service Terminus]] | ||
# [[DAP4: Data Model | Data Model]] | # [[DAP4: Data Model | Data Model]] and a [http://scm.opendap.org/trac/browser/trunk/xml/dap/dap4.xsd XML Schema] that provides one representation for the data model. | ||
# [[DAP4: Requests | Requests ]] | # [[DAP4: Requests | Requests ]] | ||
# [[DAP4: Responses | Responses]] | # [[DAP4: Responses | Responses]] | ||
Revision as of 22:02, 5 March 2012
OPULS Process
DAP4 Features
This is a straw man design, broken down into sections. It is incomplete and its content is subject to revision.
- Versions
- Checksum
- DAP Service Terminus
- Data Model and a XML Schema that provides one representation for the data model.
- Requests
- Responses
- Web Services
Proposals
These proposals have been put forth by Dennis:
- XML Use in DAP4 New (Modified: 2/25/2012)
- Grids Delenda Est Under Consideration
- Constraints and Shared Dimensions New, closely related to Grids Delenda Est (New 02/26/2012)
- Ideas for the On-The-Wire Format New
- Characterization of URL Annotations New (Modified: 2/26/2012)
- DAP4 DDX Grammar New
- DAP4: DDX Lexical Elements New
- Ideas for Defining VLens (and Sequences) New (New 02/25/2012)
- Possible Notation for Server Commands New (New 02/26/2012)
OPULS references
Old DAP4 Design and Implementation
- DAP3/4
- DAP 4.0 Design and DAP 4.0 Essential Features The design is meant to be a complete document while essential features are the minimal see we want to release. Since this task has been stalled for nearly a year, doing the latter seems like a noble goal.
