[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: PaceSimplifyCollections2 update




James M Snell wrote:


Btw, it's a bit of a nit but can we *please* use some other term than "search"? It implies entirely the wrong thing. What we're doing is filtering the collection set, not searching it. Perhaps "Filter resources" would be better?

i think both searching and filtering are very closely related especially if more of OpenSearch approach is used (consider full text search).


in my experience it makes sense to call it "Search and Filter API" but that may be overkill
http://fluency.xspaces.org/2005/03/27/search-and-filter


best,

alek


Joe Gregorio wrote:


Updated wording:

"""Search resources are resources that are identified by URI Templates.
They MUST return Atom Feed Documents as their representation, and unless
otherwise stated the entries in the document must be ordered by
their atom:updated
property, with the most recently updated entries coming first in the
document. Clients
MUST NOT assume that the entry returned in the feed is a full representation
of a member resource. If the entry is an Editable Resource then the
client should
perform a GET on the member resource before editing.
"""


-joe

On 9/27/05, Luke Arno <luke.arno@xxxxxxxxx> wrote:


On 9/27/05, James M Snell <jasnell@xxxxxxxxx> wrote:


Rather than "Full Entry", let's say "clients MUST NOT assume that the
feed returned in search responses contain complete representations of
the contained entries"...

a bit more wordy, but a whole lot clearer.

+1






-- Joe Gregorio http://bitworking.org







--
---         Memorable Quote from Firefly (105. Out Of Gas)
-Ship like this, be with you until you die -That's because it's a deathtrap