Difference between revisions of "OpenSearch Response Conventions"

From Federation of Earth Science Information Partners
(Reverted edits by Clynnes (talk) to last revision by Rduerr)
 
(3 intermediate revisions by 2 users not shown)
Line 11: Line 11:
 
* [[GHRC OpenSearch Response]]
 
* [[GHRC OpenSearch Response]]
 
* [[Mirador OpenSearch Response]]
 
* [[Mirador OpenSearch Response]]
 +
* [[GHRC to Mirador Difference Summary]]
 +
 
=Recommendations=
 
=Recommendations=
 
==Data Links==
 
==Data Links==
 
TBS.
 
TBS.
  
=Metadata Links=
+
==Metadata Links==
 
TBS.
 
TBS.
=Browse/Preview Links=
+
==Browse/Preview Links==
 
TBS.
 
TBS.
=OPeNDAP Links=
+
==OPeNDAP Links==
 
TBS.
 
TBS.
=Other Links=
+
==Other Links==
 
TBS.
 
TBS.
=Semantic Markup=
+
==Semantic Markup==
 
TBS.
 
TBS.

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

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

Background

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

Recommendations

Data Links

TBS.

Metadata Links

TBS.

Browse/Preview Links

TBS.

OPeNDAP Links

TBS.

Other Links

TBS.

Semantic Markup

TBS.