Also, the MediaRSS module references it as a best practice.
When I started working on it, there was interest from server-side
folks as well (e.g., Six Apart); AFAIK they're just waiting for it to
be finalised (it's taken a while).
Cheers,
On 2006/11/27, at 11:18 AM, Mark Nottingham wrote:
Well, since you ask a leading question...
I have a demo implementation of a client at:
http://www.mnot.net/rss/history/
and my blog does the server side:
http://www.mnot.net/blog/index.atom
James Holderness has mentioned an implementation, and the Apache
abdera people seem to be planning something, based on their
repository. I know of other folks who are planning to integrate
into products and services, but I can't disclose anything more (I'd
encourage them to, of course). Anybody else?
The issue we're discussing here, though, isn't about ambiguities in
*this* spec, but rather in Atom itself; i.e., what does a feed ID
really identify?
Cheers,
On 2006/11/27, at 11:06 AM, Ernest Prabhakar wrote:
Hi Mark,
Given all the ambiguities, are there any implementations available
to test against in practice? Or even implementors planning to
make the attempt?
- Ernie P.
On Nov 26, 2006, at 1:25 PM, Mark Nottingham wrote:
Sorry, this got lost in my inbox...
I think they do, although the draft is silent on it. This is one
of those areas where it would have been really nice if the WG had
agreed to take on FH as part of the core, rather than extension;
there are lots of little ambiguities like this as a result.
Cheers,
On 2006/11/03, at 1:37 PM, James M Snell wrote:
Mark,
I cannot recall if I've asked you this in the past but... if I
have a
set of paged/archive feed documents all of which make up a single
logical feed, do the atom:id's for each feed document have be
the same?
If not, how do I determine the atom:id of the logical feed?
- James
--
Mark Nottingham http://www.mnot.net/
--
Mark Nottingham http://www.mnot.net/
--
Mark Nottingham http://www.mnot.net/
