Specifications/OpenSearch/Extensions/Referrer/1.0/Draft 1 (2,772 bytes)7: The OpenSearch Referrer extension allows search engines to reque...11: The XML namespace of the OpenSearch Referrer Extension is:13: ...>http://a9.com/-/opensearch/extensions/referrer/1.0/</nowiki></code>15: ...must be included when the extension is used in an OpenSearch Description document.19: ... introduces the following parameter to be used in OpenSearch URL templates.

Specifications/OpenSearch/Extensions/Geo/1.0/Draft 1 (12,292 bytes)5: ...able [[Specifications/OpenSearch/Extensions/Geo/1.0/Draft_2|here]]9: ...a standard mechanism to query a resource based on geographic extents, or location name. 11: The geospatial results are based on the GeoRSS standards. Therefore, latitude/longitude order...13: ...(see [[Specifications/OpenSearch/Extensions/Geo/1.0/Draft_2|here]])19: ...was shortened to just "geo" instead of "opensearchgeo". This was to make the namespace more succinct.

Specifications/OpenSearch/Extensions/Time/1.0/Draft 1 (3,610 bytes)7: ...and timespans. The purpose of the OpenSearch-Time extensions is to provide a standard mechanism to query a res...16: ...amespace was shortened to just "time" instead of "opensearchtime". This was to make the namespace more succint...20: Example of a detailed OpenSearch description document that describes a search engi...22: <?xml version="1.0" encoding="UTF-8"?>23: ... xmlns="<nowiki>http://a9.com/-/spec/opensearch/1.1/</nowiki>"

Specifications/OpenSearch/Extensions/Geo/1.0/Draft 2 (13,066 bytes)7: ...a standard mechanism to query a resource based on geographic extents, or location name. 9: The geospatial results are based on the GeoRSS standard. Therefore, latitude/longitude order,...13: ...was shortened to just "geo" instead of "opensearchgeo". This was to make the namespace more succinct.17: ...cument that describes a search engine that accept geospatial search parameters.19: <?xml version="1.0" encoding="UTF-8"?>

Community/Proposal/Specifications/OpenSearch/Extensions/Semantic/1.0/Draft 1 (11,290 bytes)9: The OpenSearch Semantic extension offers a standard way to query...13: ...lements are the regular <code>Url</code> from the OpenSearch core specification, where the semantic operators ...28: The XML namespace of the OpenSearch Semantic Extension is:30: ...>http://a9.com/-/opensearch/extensions/semantic/1.0/</nowiki></code>32: ...must be included when the extension is used in an OpenSearch Description document.

Page text matches

Home (3,635 bytes)5: OpenSearch is a collection of simple formats for the sharing...7: ...arch engine so that it can be used by [[Community/OpenSearch search clients|search client applications]].9: ...om, with the extra metadata needed to [[Community/OpenSearch search engine directories|return search results]]...14: ...Search search clients|Search clients that support OpenSearch]]15: ...tories|Directories of search engines that support OpenSearch]]

Specifications/License (388 bytes)1: ... specifications]], and the [[About OpenSearch.org|OpenSearch.org website]] are made available by [http://a9.co...

Documentation/Stylesheet (5,967 bytes)3: ...is a good idea to use this stylesheet on your own OpenSearch feeds, so that users can see actual search result...9: ...://69.55.232.189/downloads/opensearch_to_html.xsl opensearch_to_html.xsl] - the XSLT (primary file)10: ...://69.55.232.189/downloads/opensearch_to_html.css opensearch_to_html.css]- the CSS stylesheet11: ...p://69.55.232.189/downloads/opensearch_to_html.js opensearch_to_html.js] - the Javascript file (see [[#Technic...15: === Step 1: Find an OpenSearch feed that you want to display ===

Community/Proposal guidelines (972 bytes)1: ... for a new [[Specifications/OpenSearch/Extensions|OpenSearch extension specification]], then please create a n...5: ...osal/Specifications/OpenSearch/Extensions/Color/1.0</code>9: Please do not place your page directly in the Specifications tree, as it will be moved the Community tree for ...

Specifications/OpenSearch/Extensions/Geo/1.0/Draft 1 (12,292 bytes)5: ...able [[Specifications/OpenSearch/Extensions/Geo/1.0/Draft_2|here]]9: ...a standard mechanism to query a resource based on geographic extents, or location name. 11: The geospatial results are based on the GeoRSS standards. Therefore, latitude/longitude order...13: ...(see [[Specifications/OpenSearch/Extensions/Geo/1.0/Draft_2|here]])19: ...was shortened to just "geo" instead of "opensearchgeo". This was to make the namespace more succinct.

Specifications/OpenSearch/1.1/Draft 4 (52,029 bytes)7: ...may be referred to as "OpenSearch1.1" or simply "OpenSearch".9: ...make search requests. Search engines can use the OpenSearch response elements to add search metadata to resul...15: : <code><nowiki>http://a9.com/-/spec/opensearch/1.1/</nowiki></code>17: == OpenSearch description document ==21: An OpenSearch description document can be used to describe the ...