OPULS Development: Difference between revisions
From OPeNDAP Documentation
⧼opendap2-jumptonavigation⧽
No edit summary |
|||
Line 1: | Line 1: | ||
== OPULS Process == | == OPULS Process == | ||
[[DAP4: Design Proposal Process| Design Proposal Process]] | [[DAP4: Design Proposal Process| Design Proposal Process]] | ||
Line 23: | Line 22: | ||
These ideas are orthogonal to the ones above (which cover different aspects of the data model). They are about aspects of the server/service software requests and responses: | These ideas are orthogonal to the ones above (which cover different aspects of the data model). They are about aspects of the server/service software requests and responses: | ||
# [[DAP4: DAP4 On the Wire Format | Ideas for the On-The-Wire Format]] '''New''' | # [[DAP4: DAP4 On the Wire Format | Ideas for the On-The-Wire Format]] '''New''' | ||
# [[DAP4: Possible Notation for Server Commands | Possible Notation for Server Commands]] '''New''' (New 02/26/2012) | # [[DAP4: Possible Notation for Server Commands | Possible Notation for Server Commands]] '''New''' (New 02/26/2012) | ||
These ideas have to do with formal notations for the specification: | These ideas have to do with formal notations for the specification: | ||
# [[DAP4: DDX Grammar | DAP4 DDX Grammar]] '''New''' | # [[DAP4: DDX Grammar | DAP4 DDX Grammar]] '''New''' | ||
# [[DAP4: DDX Lexical Elements]] ''' | # [[DAP4: DDX Lexical Elements]] '''New''' (Modified 2/28/2012) | ||
== Commentary on DAP4 Related Topics == | |||
These are not intended as specific proposal, but rather | |||
as commentary on some issues with DAP4 that need addressing | |||
with specific proposals. | |||
# [[DAP4: URL Annotations | Characterization of URL Annotations]] (Modified: 2/26/2012) | |||
== OPULS references == | == OPULS references == |
Revision as of 17:38, 28 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 (Jimg 15:18, 27 March 2012 (PDT) Ordered by priority at the 3/27/12 meeting):
- Grids Delenda Est Under Review
- Constraints and Shared Dimensions Under Review, closely related to Grids Delenda Est (New 02/26/2012)
- Ideas for Defining VLens (and Sequences) Under Consideration (New 02/25/2012)
- XML Use in DAP4 Accepted (Modified: 2/25/2012)
These ideas are orthogonal to the ones above (which cover different aspects of the data model). They are about aspects of the server/service software requests and responses:
- Ideas for the On-The-Wire Format New
- Possible Notation for Server Commands New (New 02/26/2012)
These ideas have to do with formal notations for the specification:
- DAP4 DDX Grammar New
- DAP4: DDX Lexical Elements New (Modified 2/28/2012)
Commentary on DAP4 Related Topics
These are not intended as specific proposal, but rather as commentary on some issues with DAP4 that need addressing with specific proposals.
- Characterization of URL Annotations (Modified: 2/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.