OPULS Development

OPULS Process

Design Proposal Process

DAP4 Features

This is a straw man design, broken down into sections. It is incomplete and its content is subject to revision.

1. Versions
2. Checksum
3. DAP Service Terminus
4. Data Model and a XML Schema that provides one representation for the data model.
5. Requests
6. Responses
7. 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):

1. Grids Delenda Est Under Review
2. Constraints and Shared Dimensions Under Review, closely related to Grids Delenda Est (New 02/26/2012)
3. Ideas for Defining VLens (and Sequences) Under Consideration (New 02/25/2012)
4. 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:

1. Ideas for the On-The-Wire Format New
2. Possible Notation for Server Commands New (New 02/26/2012)

These ideas have to do with formal notations for the specification:

1. DAP4 DDX Grammar New
2. 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.

1. Characterization of URL Annotations (Modified: 2/26/2012)

OPULS references

• http://www.mnot.net/blog/2011/10/25/web_api_versioning_smackdown

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.