Difference between revisions of "Discovery Telecon 2012-02-14"
From Earth Science Information Partners (ESIP)
(→Notes) |
|||
Line 29: | Line 29: | ||
* 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? | * 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 | * Brian suggests a separate DCP for the general case (e.g., using "arcrole"), this will be coming in DCP-5 | ||
− | * Returning a collection cast is | + | ** 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 === |
Revision as of 15:11, February 14, 2012
<< Back to the Discovery Telecons page
- Tuesday, February 14, 2011. 4:00pm ET / 1:00pm PT
- WebEx Info:
- Call-in toll-free number (US/Canada): 1-877-668-4493
- Attendee access code: 231 407 50
- To start the online portion of the Personal Conference meeting , go to https://esipfed.webex.com/mw0306ld/mywebex/default.do?siteurl=esipfed&service=1 and select the Discovery Cluster meeting.
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
- 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-6: Adopt Dublin Core Date Specification in Atom Response
Current version: DCP-6: Adopt Dublin Core Date Specification in Atom Response