Sorry Tim, one more concern and I'm done.
I think mU introduces scenarios where content cannot be safely or
properly processed without looking to the metadata for control codes, ie
metadata no longer is advisory or supplementary information. I suspect
this is a significant innovation in feed
Tim Bray wrote:
+1.
The objections to this fall into two forms:
1. We don't have prior art in the syndication space that proves this is
needed.
2. This is someone else's problem, e.g. SOAP
I can see both those arguments, but when I re-visit and re-read this,
the implementation is so
Tim Bray wrote:
-0
I could live with this, but I think PaceMustUnderstandElement buys 80%
of the benefit with 20% of the cost/apparatus. -Tim
-1. I suspect everyone else giving PaceMustUnderstand -1s will feel the
same.
Robert Sayre
Tim Bray wrote:
-1
I think this issue has been discussed to death and the current
consensus around atom:id and atom:updated will meet users' needs
simply and elegantly. Trying to achieve consensus on a generalized
abstract model of versioning is doomed to failure. -Tim
-1 as well.
Robert
I was just in the middle of putting the world to rights regarding feed
discovery/subscription from browsers [1] when something occurred to
me. Correct me if I'm wrong, but isn't one of the solutions for this
to serve the feed with the Atom mime type, which will trigger an
appropriate handler in
The semantics of atom:contributor weren't obvious to me. Is this
correct:
atom:feed/atom:head/atom:author is a syntactic default for all entries
that are missing an author.
atom:feed/atom:head/atom:contributor is a set of regular contributors
and authors of a feed, which may or may not have
Danny Ayers wrote:
Thing is, with the spec as it currently stands, we don't have a link
from the feed that can be guarenteed to point to the feed URI itself.
That's not a very robust way to accomplish the goal. People tend to use
cp without thinking about these things. The browser vendors will
Hmmm. Not looking at the spec, but at the feeds we're currently
producting for AOL Journals, our feeds have link rel=service.feed
... essentially pointing to themselves, which I yesterday thought was
redundant but perhaps is actually useful. Useful enough to be
mandatory, perhaps?
-John
Danny
On 15/1/05 7:37 AM, Danny Ayers [EMAIL PROTECTED] wrote:
If I remember correctly from previous discussions, there is a little
snag with most browsers only passing the data, not the source URI.
Thing is, with the spec as it currently stands, we don't have a link
from the feed that can be
