In order for your system to be RESTful, one of the requirements is that the client knows nothing about how your URIs are structured. This means that you cannot write code that builds URIs in the way most Twitter clients do. The usual wisdom is that in order for the resource to be located, you need to open its URI in another place.
, , . . , URI, .
OpenSearch - RESTful , , . OpenSearch HTML, (, ) :
<Url type="application/atom+xml"
template="...search/?q={searchTerms}"/>
, , . ? OpenSearch . OpenSearch , URL-, , ( , xmlns:time :
<Url type="application/atom+xml"
template="...search/?after={time:start}&before={time:end}"/>
, , . .
OpenSearch, , - . -, . , ; - , , . , , name OpenSearch :
<Url type="application/atom+xml"
template="...search?lastName={name:last}"/>
, name, , .
, ; . , OpenSearch , :
<Url type="application/atom+xml"
template="...search/?latitude={geo:lat?}&
longitude={geo:lon?}&
metres={geo:radius?}"/>
, .
, (). , ? , , , :
. tha ( ):
<Url type="application/atom+xml"
template="combo-find?customerLastName={name:last}&
lat={geo:lat?}&
lon={geo:lon?}&
radius={geo:radius?}"/>
, ( OpenSearch Time , ):
<Url type="application/atom+xml"
template="...search/?lastName={name:last}&
lat={geo:lat?}&
lon={geo:lon?}&
r={geo:radius?}&
after={time:start}&
before={time:end}"/>
URI, , URI . , , URI, , URI .
RESTfulness , REST ; , - , .. OpenSearch - , !