Difference between revisions of "OpenSearch Response Conventions"

From Earth Science Information Partners (ESIP)
(New page: This describes where the various links are located in the response, and how they are identified. =Data Links= =Metadata Links= =Browse/Preview Links= =OPeNDAP Links= =Other Links=)
 
(Reverted edits by Clynnes (talk) to last revision by Rduerr)
 
(6 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 
This describes where the various links are located in the response, and how they are identified.
 
This describes where the various links are located in the response, and how they are identified.
  
=Data Links=
+
=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:
 +
# How the "main" data link is identified
 +
# How different access points to the data are described  (e.g., FTP, HTTP, OPeNDAP)
 +
# How browse is identified
 +
# How additional metadata is enclosed:  machine tags in the summary?  Or an RDFa-like approach?  Or something similar to the georss extension to OpenSearch?
 +
# etc.
 +
=Current Examples=
 +
* [[GHRC OpenSearch Response]]
 +
* [[Mirador OpenSearch Response]]
 +
* [[GHRC to Mirador Difference Summary]]
  
=Metadata Links=
+
=Recommendations=
 +
==Data Links==
 +
TBS.
  
=Browse/Preview Links=
+
==Metadata Links==
 
+
TBS.
=OPeNDAP Links=
+
==Browse/Preview Links==
 
+
TBS.
=Other Links=
+
==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

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.