Re: AtomPubIssuesList for 2005/02/22

[Ezra Cooper <ezra@xxxxxxxxxxxx>]

I've just posted PaceSliceAndDice. This describes a way for clients and
servers to break large collections into small pieces.

The basic ideas here are not new to the group, but the language is more
precise and I've thrown in a mechanism that helps to compose
"subcollections" with "time-interval queries." I'm assuming that we'll use
the same syntax to collect entries, templates, "resources", etc.

In this proposal, none of the item-specific data is included in the
collection document (you have to dereference the individual URLs), but we
should probably address that in an independent proposal.

Suggestions on how to make this more clear are heartily welcomed. Also,
there are lots of details that could be changed without damaging the
proposal, so I'll be interested in your criticisms.

It should now be safe to close these, which I originally authored:
    PaceDateRangeCollections
    PaceRangesAndSubsets
    PaceReturnCollNewestToOldest
    PaceServerCollectionSubsets

Thanks,
Ezra
 


On 2/22/05 10:52 AM, "Sam Ruby" <rubys@xxxxxxxxxxxxxxxx> wrote:

> Ezra Cooper wrote:
>> 
>> I don't object to these being closed, but I'd like to have the chance to
>> make a new proposal which would be an alternative to PaceEntryQuery.
>> 
>> My proposal will:
>> 
>>   * provide for collections, obeying the "slash semantics"
>>   * allow for date-range queries over any (top-level) collection or
>> sub-collection
>>   * not provide for index-based ranges, or other kinds of searches.
>> 
>> If I can have this done by the end of the day, could we discuss it in this
>> round?
> 
> Yes.
> 
> - Sam Ruby
>