Difference between revisions of "Discovery Telecon 2012-08-14"
From Earth Science Information Partners (ESIP)
Line 48: | Line 48: | ||
=== Updates for SPG Specification === | === Updates for SPG Specification === | ||
+ | * None, Chris has been looking into the format for these specs | ||
=== Plan for Winter Meeting Participatory Workshop === | === Plan for Winter Meeting Participatory Workshop === |
Revision as of 14:54, August 14, 2012
<< Back to the Discovery Telecons page
- Tuesday, August 14, 2012. 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
- Chris Lynnes
- Hook Hua
- Ken Keiser
- Eric Rozell
- Christine White
Past Action Items
- Eric, Hook, Nga, Chris, Christine, Ruth - prep slides for Hack-a-thon session
- Chris - prep OpenSearch Intro for hack-a-thon session
- Ruth - prep Casting Intro for hack-a-thon session
- Chris - market the Hack-a-thon
Agenda
- DCP business
- Handling specification versions
- others..
- updates for SPG specification
- Plan for Winter meeting's participatory workshop
- feedback
- collect ideas on what we can ask Carol/Erin for help in getting Winter meeting attendance demographics
- topics. noting that Winter meetings tend to be more a little moreprogrammatic.
Notes
DCP Business
- Versioning
- Should the "esip" prefix convention be included in the spec?
- W3C does this (e.g., dc == Dublin Core)
- this spec aligns with the W3C conventions for including namespaces in
- do we need to limit
- how do versions fit within OSDDs or feed elements? Can you have multiple versions in an individual request or response?
- examples will be good here
- Should the "esip" prefix convention be included in the spec?
- Error handling
Updates for SPG Specification
- None, Chris has been looking into the format for these specs