At 10:31 AM -0500 2/22/05, Sam Ruby wrote:
So, currently under discussion:
PaceCollectionIdiom
PaceCollectionSyntax
PaceEntryQuery
And, recommended for closure:
PaceDateRangeCollections
PaceRangesAndSubsets
PaceReturnCollNewestToOldest
PaceServerCollectionSubsets
Right. Because these
At 12:25 PM + 2/20/05, Bill de hÓra wrote:
Chairs/Editors,
- I think that this discussion (repeat ids) is architecturally
significant in terms of how Atom layers onto the Web and is best
taken forward under feed state,
- Feed state discussion ought to deal explicitly with entry state,
as
On 2/22/05 7:31 AM, Sam Ruby [EMAIL PROTECTED] wrote:
As Tim noted[1], the collection paces appear to be in a bit of a
disarray. His suggestion that the authors address this over the past
few days did not achieve the desired result. Given this, I am going to
tentatively declare all
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)
Bob Wyman wrote:
However, atom requires that a link element have a mime-type. Given that we
have no idea what the mime-type for the URI is, what mime-type should we
use?
It type attributes are optional in the current draft.
http://www.ietf.org/internet-drafts/draft-ietf-atompub-format-05.txt
4.6.3
On 23/2/05 6:31 AM, Bob Wyman [EMAIL PROTECTED] wrote:
However, atom requires that a link element have a mime-type. Given that we
have no idea what the mime-type for the URI is, what mime-type should we use?
@type is optional.
Link elements MAY have a type attribute, whose value
MUST
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
At 01:44 05/02/23, Paul Hoffman wrote:
This list should still be focused on the format draft. As our document
editors toil away diligently, we can still offer editorial suggestions.
This is also a reasonable time to start creating format extensions and
talking about them here.
Hello Paul,
(BAt 04:31 05/02/23, Bob Wyman wrote:
(BAt PubSub, we allow users to subscribe to RSS/Atom entries that contain
(Buser-specified URIs. (Using a query like: URI:nytimes.com) Users of this
(Bfeature have often asked us to augment the entries we publish by attaching
(Bthe URIs we discover to
Martin Duerst wrote:
Are you talking about the type attribute (as Sam and others have
pointed out, that's no longer required) or the rel attribute.
I was primarily concerned about the type attribute since I hadn't
realized it was now optional. Thanks to Sam, etc. for pointing out that
The following message was on the RSS-Media
group at:
http://groups.yahoo.com/group/rss-media/
It seems reasonable to expect that users
will expect that Atom and RSS-Media will, in fact, be used in concert in the
future.
From: ecomputerd
[mailto:[EMAIL PROTECTED]
Sent: Tuesday,
Paul Hoffman wrote:
This is also a reasonable time to start creating format extensions and
talking about them here.
Here's one that's sort of done:
http://fotonotes.net/spec/index.cgi?FotoNotesSpecification
This is what will carry Flickr annotations, and they do it with Atom and
RDF. They made
12 matches
Mail list logo
