Difference between revisions of "OpenSearch Response Conventions"
From Earth Science Information Partners (ESIP)
| Line 15: | Line 15: | ||
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. | ||
Revision as of 05:11, July 24, 2009
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:
- 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
Recommendations
Data Links
TBS.
Metadata Links
TBS.
Browse/Preview Links
TBS.
OPeNDAP Links
TBS.
Other Links
TBS.
Semantic Markup
TBS.
