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

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.