Difference between revisions of "Discovery Change Proposals"

From Earth Science Information Partners (ESIP)
 
(29 intermediate revisions by 8 users not shown)
Line 1: Line 1:
 
[[Discovery_Governance|<< Back to the Discovery Cluster Governance page]]
 
[[Discovery_Governance|<< Back to the Discovery Cluster Governance page]]
  
 +
== Current Change Proposals ==
  
== DCP-1 ==
+
=== [[Discovery Change Proposal-1 | DCP-1: ESIP Discovery Cast Atom Response Format v1.1]] ===
* '''Title''': ESIP Discovery Cast Atom Response Format v1.1
+
* '''Submitted on''': 2011-02-08T13:00 PST
* '''Submitted''': 2011-02-08T13:00 PST
+
* '''Ratified on''': 2011-03-22T12:30 PST
* '''Review period deadline''': 2011-02-28T00:00 PST
+
=== [[Discovery Change Proposal-2 | DCP-2: Canonicalizing Granule-level OPeNDAP Links]] (Withdrawn) ===
* '''Current governance step''': submitted
+
* '''Submitted on''': 2011-06-15
* '''Background''': At the NASA Earth Science Data System Working Group meeting in New Orleans on October 21, 2010, a proposal was made to expand the scope of Federated Open Search to cover Discovery more generally, thus bringing into the fold datacasting and servicecasting. Therefore a common Atom response format is needed that extends the [http://www.ietf.org/rfc/rfc4287.txt Atom  Syndication Format (RFC 4287)] with extensions specific for Earth science data usage.
+
* Withdrawn due to lack of consensus. See [[DCP-4]] for replacement.
* '''Problem addressed''': Currently OpenSearch, datacasting and servicecasting all return very similar granule-level information. But there is no consistent format used. This proposal will provide a specification for a set of Earth science-specific extensions to the Atom response format.
 
* '''Proposed solution''': See [[Discovery_Cast_Atom_Response_Format]]. Note that this link will be changed to include a version.
 
* '''Rationale for the solution''': Reuse as much of existing standards as possible. Fold in Geo and Time extensions. Define a set of commonly used rel link types for OpenSearch, datacasting and servicecasting.
 
  
 +
=== [[Discovery Change Proposal-3 | DCP-3: Standardized Linking from one cast to another or to additional metadata]] ===
 +
* '''Submitted on''': 2011-10-10
 +
* Expected to be replaced by an upcoming DCP to generalize the approach in [[DCP-4]].
  
== Template for new DCPs ==
+
=== [[DCP-4 | DCP-4: OPeNDAP Links in the Atom <link/> element]] ===
 +
* '''Submitted on''': 2012-02-14
 +
* '''Ratified on''': 2012-04-30
  
All changes to the Discovery specifications must go through the governance process starting with a Discovery Change Proposal (DCP). Each DCP must include the following context for reference:
+
=== [[DCP-5 | DCP-5:  Valids and restrictions for query elements]] ===
* A unique identifier. For example, DCP-i, where i is a unique id. It is common to see an incrementing number used in these types of community based processes.
+
* '''Submitted on''': 2012-04-24
* '''Title''': Title of proposal.
+
 
* '''Facilitator''': The primary editor to help the DCP move along the process.
+
=== [[Discovery_Change_Proposal-6 | DCP-6: Adopt Dublin Core Date Specification in Atom Response]] ===
* '''Submitted''': Timestamp of when proposal was submitted.
+
* '''Submitted on''': 2012-02-13
* '''Review period deadline''':  
+
 
* '''Current governance step''': choose from: submitted, proposal review, vote, revising, final review, & ratified.
+
===[[Discovery_Change_Proposal-7 | DCP-7: Error Handling Best Practices for Discovery Repsonse]]===
* '''Background''':  
+
* '''Submitted on''': 2012-02-13
* '''Problem addressed''':  
+
===[[Discovery_Change_Proposal-8 | DCP-8: Standardized Linking from one cast to another or to additional metadata]]===
* '''Proposed solution''':  
+
 
* '''Rationale for the solution''':
+
===[[Discovery_Change_Proposal-9 | DCP-9: Identifying Version of ESIP Discovery Conformance]]===
 +
* '''Submitted on''': 2012-08-21
 +
 
 +
== How to add new change proposal? ==
 +
 
 +
* Editors, please use this [[Discovery Change Proposal Template]].
 +
 
 +
== Incubation Ideas ==
 +
 
 +
* Specific extensions to Discovery Atom Response format for Granule-level, Collection-level, and Service responses. Simply builds upon DCP-1.
 +
* Discovery RSS Response Format?
 +
* OpenSearch Request Format. adopt OGC OpenSearch spec?
 +
* ServiceCasting Request Format?
 +
* DataCasting Request Format?
 +
* Mashup conventions?
 +
* [http://wiki.apache.org/solr/CommonQueryParameters Apache SOLR Request format]
 +
* [http://wiki.apache.org/solr/QueryResponseWriter Apache SOLR Response format]
 +
* [http://wiki.apache.org/nutch/FAQ#What_is_the_RSS_symbol_in_search_results_all_about.3F Apache Nutch Opensearch RSS response format]
 +
* [[Custom Elements]]

Latest revision as of 07:46, August 23, 2012

<< Back to the Discovery Cluster Governance page

Current Change Proposals

DCP-1: ESIP Discovery Cast Atom Response Format v1.1

  • Submitted on: 2011-02-08T13:00 PST
  • Ratified on: 2011-03-22T12:30 PST

DCP-2: Canonicalizing Granule-level OPeNDAP Links (Withdrawn)

  • Submitted on: 2011-06-15
  • Withdrawn due to lack of consensus. See DCP-4 for replacement.

DCP-3: Standardized Linking from one cast to another or to additional metadata

  • Submitted on: 2011-10-10
  • Expected to be replaced by an upcoming DCP to generalize the approach in DCP-4.

DCP-4: OPeNDAP Links in the Atom <link/> element

  • Submitted on: 2012-02-14
  • Ratified on: 2012-04-30

DCP-5: Valids and restrictions for query elements

  • Submitted on: 2012-04-24

DCP-6: Adopt Dublin Core Date Specification in Atom Response

  • Submitted on: 2012-02-13

DCP-7: Error Handling Best Practices for Discovery Repsonse

  • Submitted on: 2012-02-13

DCP-8: Standardized Linking from one cast to another or to additional metadata

DCP-9: Identifying Version of ESIP Discovery Conformance

  • Submitted on: 2012-08-21

How to add new change proposal?

Incubation Ideas