Difference between revisions of "Talk:Discovery Change Proposal-2"

From Earth Science Information Partners (ESIP)
(Combined with incubator DCP from Matt Cechini -- ~~~~)
 
Line 4: Line 4:
  
 
However, the namespace remains in opendap.org.  This is chosen as a namespace because it is more authoritative than ESIP, i.e., the keepers of the DAP standard.
 
However, the namespace remains in opendap.org.  This is chosen as a namespace because it is more authoritative than ESIP, i.e., the keepers of the DAP standard.
 +
 +
== From telecon discussion of handling alternate service/data links in granule-level Discovery responses -- [[User:Hook|Hook]] 15:12, 9 August 2011 (MDT) ==
 +
 +
* See [[Discovery Telecon 2011-08-09]] for meeting minutes on discussion.
 +
* To continue discussion here and vote on the preferred approach.
 +
* Possible ideas so far:
 +
# Original DCP-2 idea: ''rel'' attribute value of '''http://xml.opendap.org/ns/DAP/3.3#'''.
 +
# "rel" could be dereferencible URI. but is fragile.
 +
# Could leverage the ''fragment'' part of the [http://en.wikipedia.org/wiki/Uniform_Resource_Identifier URI]
 +
## e.g. http://esipfed.org/ns/discovery/1.1/data#DAP/3.3/
 +
# Use space-delimitation in "rel" URI
 +
# Define third attribute, with appropriate namespace.
 +
## As long as using namespaced attribute, it does not break in the [http://validator.w3.org/feed/ W3C Feed Validation Service].

Revision as of 15:12, August 9, 2011

Combined with incubator DCP from Matt Cechini -- Clynnes 10:22, 17 June 2011 (MDT)

We grafted the description from Matt Cechini's incubator DCP on OPeNDAP link_type with this DCP.

However, the namespace remains in opendap.org. This is chosen as a namespace because it is more authoritative than ESIP, i.e., the keepers of the DAP standard.

From telecon discussion of handling alternate service/data links in granule-level Discovery responses -- Hook 15:12, 9 August 2011 (MDT)

  • See Discovery Telecon 2011-08-09 for meeting minutes on discussion.
  • To continue discussion here and vote on the preferred approach.
  • Possible ideas so far:
  1. Original DCP-2 idea: rel attribute value of http://xml.opendap.org/ns/DAP/3.3#.
  2. "rel" could be dereferencible URI. but is fragile.
  3. Could leverage the fragment part of the URI
    1. e.g. http://esipfed.org/ns/discovery/1.1/data#DAP/3.3/
  4. Use space-delimitation in "rel" URI
  5. Define third attribute, with appropriate namespace.
    1. As long as using namespaced attribute, it does not break in the W3C Feed Validation Service.