Robert Sayre wrote:
.. Are there any
WG members left who were around at that phase? I joined right around
then...
*Holds up hand. Shrugs. Goes back to work.*
Monday, May 1, 2006, 8:40:57 PM, James Snell wrote:
I'm wondering if it would make sense to have a single common type
scheme that could be used consistently across implementations.
random thoughts
Type seems a bit vague, this seems to be mainly about describing how
an entry should be
Type seems a bit vague, this seems to be mainly about describing how
an entry should be processed. A few possible ways to do that:
a) Using categories and a known categorisation scheme
b) Using an ex:processAs extension
c) Using domain specific extensions, eg contact:VCard /
d)
* James M Snell [EMAIL PROTECTED] [2006-05-02 07:15]:
As you can see from the example, the thr:replies/@ref attribute
points to an atom:id value, and not the URI used by the link.
So fetching and parsing all relevant links is the only way to
know which `thr:replies` element applies to which
Aristotle,
I'm not 100% happy with it yet so it may change at least one more time.
But I did want to get this out and in front of y'all to get initial
reactions.
I'll go ahead and make the ref attribute optional. Regarding the ref
vs. href, issue, I really want to discourage client
Hey David,
Just some responses to your random thoughts. My goal is not to argue
that the category approach is best, but only to state the rationale
behind what we've done to this point.
David Powell wrote:
Monday, May 1, 2006, 8:40:57 PM, James Snell wrote:
I'm wondering if it would make
* Robert Sayre [EMAIL PROTECTED] [2006-05-02 05:25]:
On 5/1/06, A. Pagaltzis [EMAIL PROTECTED] wrote:
* Robert Sayre [EMAIL PROTECTED] [2006-05-02 03:50]:
especially when changes requested by the community are met
with hostility and channel flooding.
Did this happen in more cases than
* James M Snell [EMAIL PROTECTED] [2006-05-02 17:00]:
I'll go ahead and make the ref attribute optional.
I think that still needs to be accompanied with verbiage about
global vs local reply count though. There should be guidance on
what it means when elements both with and without `ref`
On 5/2/06, A. Pagaltzis [EMAIL PROTECTED] wrote:
Such as?
Not appropriate for on-list discussion, sorry.
When I read terms like more standard wrt the feed thread
extension, it makes me cringe.
There are obvious reasons why that one is better than the rag-tag
group of RSS
A. Pagaltzis wrote:
* Robert Sayre [EMAIL PROTECTED] [2006-05-02 05:25]:
On 5/1/06, A. Pagaltzis [EMAIL PROTECTED] wrote:
* Robert Sayre [EMAIL PROTECTED] [2006-05-02 03:50]:
especially when changes requested by the community are met
with hostility and channel flooding.
Did this happen in
I can only assume that someone from Opera is on this list, and I'm not
even sure this is that big of a deal, but then again
From: http://my.opera.com/community/customize/widgets/info/?id=4021
This feed allows subscribing to an unlimited number of news feeds.
Supported formats: RSS 2 and
On 5/2/06, James M Snell [EMAIL PROTECTED] wrote:
Aristotle, I appreciate the intention, but please don't bother. It is
painfully clear that Robert has no intention of adding anything of any
real value to the discussion.
???
--
Robert Sayre
* James M Snell [EMAIL PROTECTED] [2006-05-02 19:45]:
A. Pagaltzis wrote:
Such as?
Aristotle, I appreciate the intention, but please don't bother.
It is painfully clear that Robert has no intention of adding
anything of any real value to the discussion.
I know. However, I despise
On 5/2/06, A. Pagaltzis [EMAIL PROTECTED] wrote:
* James M Snell [EMAIL PROTECTED] [2006-05-02 19:45]:
A. Pagaltzis wrote:
Such as?
Aristotle, I appreciate the intention, but please don't bother.
It is painfully clear that Robert has no intention of adding
anything of any real value to
A. Pagaltzis wrote:
[snip]
With the thr:replies element, to do it properly, I have to
create a new extension element, create a factory, register the
extension with the parser, etc. Adding in the difficulties
inherent in matching equivalent href values between the
atom:link and thr:replies
Just a quick heads up. To illustrate a simple example of feed rank bein
used, I put together an xslt that renders my Netflix Queue as an Atom
feed using the feed rank, feed history and MSFT simple list extensions.
http://tinyurl.com/nxzgh
Please excuse the tinyurl, the real URL for the feed is
Le Tue, 02 May 2006 20:51:41 +0300, M. David Peterson
[EMAIL PROTECTED] a écrit:
I can only assume that someone from Opera is on this list, and I'm not
even sure this is that big of a deal, but then again
From: http://my.opera.com/community/customize/widgets/info/?id=4021
This feed
Very cool! Thanks for the prompt reply :)
re: I must make myself very clear, it was *not* my intention to use improperversion number and to falsely promote Atom 2 support.
My apologies if I came across the wrong way... I wasn't meaning to call you out and suggest something evil had taken
* Robert Sayre [EMAIL PROTECTED] [2006-05-02 22:00]:
I've been saying the same thing for weeks. I suppose it's par
for the course to handwave about them being strictly
advisory, supply circular definitions for the feature in the
first place, claim no one will be implementing the feature,
* James M Snell [EMAIL PROTECTED] [2006-05-02 22:25]:
A. Pagaltzis wrote:
I have to say that your architecture sounds rather
heavyweight,
Heavyweight? It's Java. need I say more?
Hehe. I stopped just short of asking “is that in Java?” :-)
Does your implementation properly handle the
James Holderness wrote:
Just looking at that example, it seems to me that an aggregator that
implements Microsoft's simple list extensions would get a full-featured
representation of that feed without having to know anything at all about
feed rank and feed history.
That's part of the
Tuesday, May 2, 2006, 9:12:56 PM, James Snell wrote:
Does your implementation properly handle the following (contrived) example:
entry xml:base=http://example.org/foo/bar;
...
link href=../comments.xml rel=replies /
thr:replies href=http://EXAMPLE.org:80/foo/bar/../comments.xml; ... /
On 5/2/06, James M Snell [EMAIL PROTECTED] wrote:
Again, however, Feed Rank is not intended to compete with the simple
list extensions. They serve different purposes. SLE defines a
processing model for individual feed documents whose entries represent a
sorted list; Feed Rank defines a way
Hi David,
* David Powell [EMAIL PROTECTED] [2006-05-03 01:15]:
I don't think you should do URI normalisation. The ref is being
used as an identifier, you don't do protocol level
normalisation on namespace URIs or Atom ids why do it here?
That’s a good point; though there’s a slight
Ok, so how's this (not word-for-word as I would write it in the spec,
but you should get the idea)
The ref attribute MUST be an absolute URI that matches a the resolved
href URI of a replies link character-for-character (case sensitive)
In other words;
link rel=replies href=comments.xml
On 2006/05/01, at 12:55 AM, James M Snell wrote:
Eric Scheid wrote:
I thought OpenSearch results are not sorted by chronological age
at all, but
instead by relevance? Using next with OpenSearch makes sense in
that
context. Using previous for stepping back thru time in a data store
Peter,
Can you expand upon being more precise about exactly what is needed?
On 2006/05/01, at 3:16 AM, Peter Robinson wrote:
Mark Nottingham [EMAIL PROTECTED] wrote:
One thing I did notice -- you're using URLs like this for your
archives:
Messages | Bytes| Who
+--++--+
29.09% | 16 | 36.32% |83142 | [EMAIL PROTECTED]
16.36% |9 | 14.13% |32346 | [EMAIL PROTECTED]
12.73% |7 | 11.57% |26492 | [EMAIL PROTECTED]
7.27% |4 | 6.01% |13765
* Robert Sayre [EMAIL PROTECTED] [2006-05-03 03:15]:
You know, stuffing an idea because of who proposed it.
No, not just because of who proposed it, but also because of
how.
Sorry Aristotle, you're not qualified to make that statement.
I've proposed things every which way, so I know the
Mark Nottingham wrote:
[snip]
As it stands now, a single feed
cannot implement APP, OpenSearch AND Feed History.
Please describe the scenario where you'd want that to happen -- show the
feed.
The feed(s) are part of our open activities implementation and are
available via our APP interop
30 matches
Mail list logo
