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: : <code><nowiki>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: ...on of this document is available [[Specifications/OpenSearch/Extensions/Geo/1.0/Draft_2|here]]9: ...re ubiquitous and easy to use. The purpose of the OpenSearch-Geo extensions is to provide a standard mechanism...13: ...te''' : New draft available (see [[Specifications/OpenSearch/Extensions/Geo/1.0/Draft_2|here]])19: ...namespace was shortened to just "geo" instead of "opensearchgeo". This was to make the namespace more succinct...23: Example of a detailed OpenSearch description document that describes a search engi...

Specifications/OpenSearch/Extensions/Time/1.0/Draft 1 (3,610 bytes)7: ...y based on time and timespans. The purpose of the OpenSearch-Time extensions is to provide a standard mechanis...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...23: ...chDescription xmlns="<nowiki>http://a9.com/-/spec/opensearch/1.1/</nowiki>"24: ... xmlns:time="<nowiki>http://a9.com/-/opensearch/extensions/time/1.0/</nowiki>">

Specifications/OpenSearch/1.1/Draft 4 (52,029 bytes)7: ...may be referred to as "OpenSearch 1.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 ...

Specifications/OpenSearch/Extensions/Suggestions/1.1/Draft 1 (9,097 bytes)7: The OpenSearch Suggestions extension offers a convention by whic...15: ...iption document]] containing two [[Specifications/OpenSearch/1.1/Draft_3#The_.22Url.22_element|Url elements]]....25: The XML namespace of the OpenSearch Suggestions Extension is:27: ...><nowiki>http://www.opensearch.org/specifications/opensearch/extensions/suggestions/1.1</nowiki></code>29: ...must be included when the extension is used in an OpenSearch Description document.

Specifications/OpenSearch/Extensions/Geo/1.0/Draft 2 (13,066 bytes)7: ...re ubiquitous and easy to use. The purpose of the OpenSearch-Geo extensions is to provide a standard mechanism...13: ...namespace was shortened to just "geo" instead of "opensearchgeo". This was to make the namespace more succinct...17: Example of a detailed OpenSearch description document that describes a search engi...20: ...chDescription xmlns="<nowiki>http://a9.com/-/spec/opensearch/1.1/</nowiki>"21: ... xmlns:geo="<nowiki>http://a9.com/-/opensearch/extensions/geo/1.0/</nowiki>">

Community/Proposal/Specifications/OpenSearch/Extensions/SRU/1.0/Draft 1 (17,408 bytes)7: ...s the full SRU request parameter set available to OpenSearch implementations. This SRU Extension is aligned wi...17: The XML namespace of the OpenSearch SRU Extension is:19: <nowiki>http://a9.com/-/opensearch/extensions/sru/2.0/</nowiki>21: ... be included when the SRU Extension is used in an OpenSearch Description document.25: Example of a detailed OpenSearch description document that describes a search engi...

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: : <code><nowiki>http://a9.com/-/opensearch/extensions/semantic/1.0/</nowiki></code>32: ...must be included when the extension is used in an OpenSearch Description document.

Specifications/OpenSearch/1.1/Draft 5 (55,362 bytes)7: ...may be referred to as "OpenSearch 1.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 ...

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/Frequently asked questions (2,452 bytes)1: === What is OpenSearch? ===3: OpenSearch is a collection of simple formats for the sharing...5: You can use [[Specifications/OpenSearch/1.1|OpenSearch formats]] to help people discover and use your se...7: === Why use OpenSearch? ===13: OpenSearch helps search engines and search clients communica...

Documentation/Developer how to guide (3,720 bytes)1: === How to return OpenSearch results from your search engine ===5: ...e]] contains a list of libraries that can produce OpenSearch results within popular software packages and prog...7: ...basic steps for publishing your search results as OpenSearch:9: ...tions/OpenSearch/1.1#OpenSearch response elements|OpenSearch response elements]].10: #* Check to see if there is [[Community/OpenSearch client libraries|already software]] to do this fo...

Documentation/Recommendations/OpenSearch and microformats (8,317 bytes)9: In the same way, OpenSearch is a set of simple, open data formats built upon ...11: ...ies of the two initiatives are highly compatible; OpenSearch and microformats can work together in bringing ri...13: ...s particularly well within the context of search. OpenSearch search engines can return search results in a hum...17: ...le search results. The use of microformats in an OpenSearch context does not preclude the use of alternate te...21: All elements, attributes, and parameters in an OpenSearch context must be associated with an XML namespace....

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 ===

Documentation/OpenSearch 1.0 to 1.1 upgrade guide (3,524 bytes)3: ...t came about from comments on the first version. OpenSearch 1.1 is more powerful, flexible, and extensible.5: ...ionally, most software that produces and consumes OpenSearch will make use of the new format, so it is a good ...9: ... made to keep OpenSearch 1.1 back-compatible with OpenSearch 1.0, though there are a small number of changes t...15: ...log|the full changelog between OpenSearch 1.0 and OpenSearch 1.1]].21: ...your OpenSearch description documents|Update your OpenSearch description documents]]

Community/Proposal guidelines (972 bytes)1: ... for a new [[Specifications/OpenSearch/Extensions|OpenSearch extension specification]], then please create a n...5: : <code>Community/Proposal/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: ...on of this document is available [[Specifications/OpenSearch/Extensions/Geo/1.0/Draft_2|here]]9: ...re ubiquitous and easy to use. The purpose of the OpenSearch-Geo extensions is to provide a standard mechanism...13: ...te''' : New draft available (see [[Specifications/OpenSearch/Extensions/Geo/1.0/Draft_2|here]])19: ...namespace was shortened to just "geo" instead of "opensearchgeo". This was to make the namespace more succinct...23: Example of a detailed OpenSearch description document that describes a search engi...

Specifications/OpenSearch/1.1/Draft 4 (52,029 bytes)7: ...may be referred to as "OpenSearch 1.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 ...

Specifications/OpenSearch/Extensions/Suggestions/1.1/Draft 1 (9,097 bytes)7: The OpenSearch Suggestions extension offers a convention by whic...15: ...iption document]] containing two [[Specifications/OpenSearch/1.1/Draft_3#The_.22Url.22_element|Url elements]]....25: The XML namespace of the OpenSearch Suggestions Extension is:27: ...><nowiki>http://www.opensearch.org/specifications/opensearch/extensions/suggestions/1.1</nowiki></code>29: ...must be included when the extension is used in an OpenSearch Description document.

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: : <code><nowiki>http://a9.com/-/opensearch/extensions/semantic/1.0/</nowiki></code>32: ...must be included when the extension is used in an OpenSearch Description document.