Difference between revisions of "Discovery Telecon 2012-03-13"
From Earth Science Information Partners (ESIP)
| Line 15: | Line 15: | ||
* Brian Wilson (6) | * Brian Wilson (6) | ||
* Pedro Goncalves | * Pedro Goncalves | ||
| + | * James Gallagher (7) | ||
== Action Items == | == Action Items == | ||
| + | |||
| + | * Chris or Hook will deprecate DCP-2 and DCP-3 on DCP page | ||
| + | * Brian will work on generalized version of DCP-4 (Pedro will contribute examples for WxS) | ||
| + | * Chris will send out Doodle poll for DCP-4 | ||
| + | * James will update examples for DCP-4 with details and additional examples (also include all the different OPeNDAP MIME types) (also, try to use real links) | ||
== Agenda == | == Agenda == | ||
| Line 34: | Line 40: | ||
=== DCP Updates === | === DCP Updates === | ||
| + | |||
| + | * DCP-2 | ||
| + | ** deprecated (withdrawn) | ||
| + | ** replaced by DCP-3 | ||
| + | * DCP-3 | ||
| + | ** deprecated (withdrawn) | ||
| + | ** replaced by DCP-4 | ||
| + | * DCP-4 | ||
| + | ** is this ready for voting? | ||
| + | ** currently just about OPeNDAP links | ||
| + | ** vote on DCP-4 as a move forward, then generalize | ||
| + | ** we needed an extra attribute to express that the service was OPeNDAP | ||
| + | ** Brian will write the generalized version | ||
| + | ** Chris will set up Doodle poll | ||
| + | ** Has James updated the examples per Pedro's request? | ||
| + | *** Yes | ||
| + | *** The server might be configured to give you an error message or an HDF file, so it could be type="text/plain" | ||
| + | *** The default case is an error message | ||
| + | *** James should right up more justifying why the example has the attributes it does, and maybe add more examples | ||
| + | ** Is there any need to have a dereferenceable xlink:role? | ||
| + | *** Yes, but it should not be required | ||
| + | *** An XSD is as good of a URI as any | ||
=== Planning for ESIP Summer Meeting === | === Planning for ESIP Summer Meeting === | ||
Revision as of 14:27, March 13, 2012
<< Back to the Discovery Telecons page
- Tuesday, March 13, 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
- Christine White (3)
- Eric Rozell
- Erin Robinson
- Brian Wilson (6)
- Pedro Goncalves
- James Gallagher (7)
Action Items
- Chris or Hook will deprecate DCP-2 and DCP-3 on DCP page
- Brian will work on generalized version of DCP-4 (Pedro will contribute examples for WxS)
- Chris will send out Doodle poll for DCP-4
- James will update examples for DCP-4 with details and additional examples (also include all the different OPeNDAP MIME types) (also, try to use real links)
Agenda
- DCP updates
- 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: Error Handling Best Practices for Discovery Repsonse
- Planning for ESIP summer meeting
- Discovery Testbed
- Discovery_Testbed_Work_Plan contains Use Cases and Functional Requirements
- Brian's service cast "Relax NG" validator service
Notes
DCP Updates
- DCP-2
- deprecated (withdrawn)
- replaced by DCP-3
- DCP-3
- deprecated (withdrawn)
- replaced by DCP-4
- DCP-4
- is this ready for voting?
- currently just about OPeNDAP links
- vote on DCP-4 as a move forward, then generalize
- we needed an extra attribute to express that the service was OPeNDAP
- Brian will write the generalized version
- Chris will set up Doodle poll
- Has James updated the examples per Pedro's request?
- Yes
- The server might be configured to give you an error message or an HDF file, so it could be type="text/plain"
- The default case is an error message
- James should right up more justifying why the example has the attributes it does, and maybe add more examples
- Is there any need to have a dereferenceable xlink:role?
- Yes, but it should not be required
- An XSD is as good of a URI as any
