Difference between revisions of "OpenSearch Response Conventions"

From Earth Science Information Partners (ESIP)
(Reverted edits by Clynnes (talk) to last revision by Rduerr)
 
Line 13: Line 13:
 
* [[GHRC to Mirador Difference Summary]]
 
* [[GHRC to Mirador Difference Summary]]
  
=[[FederatedSearchConvention|Recommendations]]=
+
=Recommendations=
 +
==Data Links==
 +
TBS.
 +
 
 +
==Metadata Links==
 +
TBS.
 +
==Browse/Preview Links==
 +
TBS.
 +
==OPeNDAP Links==
 +
TBS.
 +
==Other Links==
 +
TBS.
 +
==Semantic Markup==
 +
TBS.

Latest revision as of 16:28, July 27, 2012

This describes where the various links are located in the response, and how they are identified.

Background[edit | edit source]

Within Atom, there is nonetheless a lot of room for variation in how responses are formatted. For integration purposes, we would like to specify conventions that address:

  1. How the "main" data link is identified
  2. How different access points to the data are described (e.g., FTP, HTTP, OPeNDAP)
  3. How browse is identified
  4. How additional metadata is enclosed: machine tags in the summary? Or an RDFa-like approach? Or something similar to the georss extension to OpenSearch?
  5. etc.

Current Examples[edit | edit source]

Recommendations[edit | edit source]

Data Links[edit | edit source]

TBS.

Metadata Links[edit | edit source]

TBS.

Browse/Preview Links[edit | edit source]

TBS.

OPeNDAP Links[edit | edit source]

TBS.

Other Links[edit | edit source]

TBS.

Semantic Markup[edit | edit source]

TBS.