Search results
From OPeNDAP Documentation
⧼opendap2-jumptonavigation⧽
Page title matches
- We need a formal process for presenting and discussing proposals for the DAP4 design. It should be easy to use and accommodate the ideas/proposals we already ha For Design Proposals, I propose these steps:2 KB (409 words) - 22:48, 2 March 2012
Page text matches
- We need a formal process for presenting and discussing proposals for the DAP4 design. It should be easy to use and accommodate the ideas/proposals we already ha For Design Proposals, I propose these steps:2 KB (409 words) - 22:48, 2 March 2012
- * [[Template:DAP4 Design Proposal]]901 bytes (136 words) - 20:45, 27 January 2015
- [[DAP4: Design Proposal Process| Design Proposal Process]] Short version: Each proposal is in one of the following categories:13 KB (1,672 words) - 17:53, 4 January 2016
- [[Category:Development|Development]] [[Category:DAP4|DAP4]] ...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 the13 KB (1,925 words) - 21:12, 6 November 2013
- ...HTTP headers or URL keywords is described in [[DAP4:_DAP_Versions|DAP 4.0 Design doc]]. Advertising DAP protocol services is described in the [[DAP_Service_ The proposal attempts to address the following requirements:18 KB (2,567 words) - 20:48, 10 May 2012
- [[Category:Development|Development]][[Category:DAP4|DAP4]] (1) above. In any case, this proposal below would obviate the18 KB (3,082 words) - 16:00, 23 October 2012
- [[Category:Development|Development]] [[Category:DAP4|DAP4]] ...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 the18 KB (2,933 words) - 19:15, 31 August 2012
- ...ich are not readily available, and it builds on some of the ideas in the [[DAP4: Capabilities and Versioning]] document. * When a client, that does not understand DAP4 asynchronous responses, makes a request that will return an asynchronous re28 KB (4,197 words) - 17:09, 1 October 2013
- [[Category:Development|Development]] [[Category:DAP4|DAP4]] ...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 the38 KB (5,326 words) - 19:13, 31 August 2012
- [[Category:Development|Development]][[Category:DAP4|DAP4]] NB: This proposal covers only the DAP4 data response; it does not apply to the other responses including, e.g., an24 KB (4,073 words) - 23:22, 13 September 2012
- [[Category:Development|Development]][[Category:DAP4|DAP4]] ...he work. It has been superseded by the ''[[DAP4: Specification Volume 2 | DAP4 Specification Volume 2: Web Services Specification]]'' </font>70 KB (10,599 words) - 21:47, 13 November 2013
- [[Category:Development|Development]][[Category:DAP4|DAP4]] ...DAP4's data model and to fix problems with the DAP2 syntax and semantics. DAP4 constraint expressions (CEs) will support ''projection'' in much the same w65 KB (10,249 words) - 20:13, 6 January 2014
- [[Category:Development|Development]][[Category:DAP4|DAP4]] <div style="font-size: 24pt;line-height: 100%">'''Volume 2: DAP4 Web Services</div>84 KB (12,789 words) - 15:35, 28 July 2022
- [[Category:Development|Development]][[Category:DAP4|DAP4]] 4.0 (referred to also as DAP4). This data transmission145 KB (22,480 words) - 22:53, 5 November 2021