Difference between revisions of "Discovery Telecon 2012-02-14"

From Earth Science Information Partners (ESIP)
(Reverted edits by Rozele (talk) to last revision by Clynnes)
 
(11 intermediate revisions by one other user not shown)
Line 25: Line 25:
  
 
=== DCP-4: Use of xlink attributes in Atom <link> tags ===
 
=== DCP-4: Use of xlink attributes in Atom <link> tags ===
* Current Version: [[DCP-4|DCP-4: OPeNDAP Links in the Atom <link/> element]]
+
Current Version: [[DCP-4|DCP-4: OPeNDAP Links in the Atom <link/> element]]
* Potentially use "role" and "arcrole" from xlink to capture all the semantics of DCP-3.
 
* Should we change DCP-4 to the current OPeNDAP suggestion, or should there be a separate DCP for the more general case of DCP-4?
 
* Brian suggests a separate DCP for the general case (e.g., using "arcrole"), this will be coming in DCP-5
 
** Basically, covering the case where servicecasts refer to collections, or collectioncasts referring to services
 
* Returning a collection cast is a different use case from returning OPeNDAP response
 
  
 
=== DCP-5: Use of OpenSearch <Query> tags for valid parameter values ===
 
=== DCP-5: Use of OpenSearch <Query> tags for valid parameter values ===

Latest revision as of 11:56, July 22, 2012

<< Back to the Discovery Telecons page

Attendees

Action Items

Agenda

  • Recap of Winter Meeting (if needed)
  • Status of new DCPs
    • DCP-4: Use of xlink attributes in Atom <link> tags
    • DCP-5: Use of OpenSearch <Query> tags for valid parameter values
    • DCP-6: Replace overloaded time:start and time:end tags with dc:date
    • DCP-7: define error handling best practices

Notes

Recap of Winter Meeting (if needed)

DCP-4: Use of xlink attributes in Atom <link> tags

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

DCP-5: Use of OpenSearch <Query> tags for valid parameter values

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

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

DCP-7: define error handling best practices