Sapna, et al:
Several months back, there was discussion about placing the
custodianship of the Media RSS spec with the RSS Advisory Board. The
folks at Yahoo! at the time had consented that it was a good idea (I
believe this was Jeremy Zawdony, IIRC), but there never seemed to be
any forward progress on that initiative.
My concern stems from the fact that the Media RSS spec has been broken/
incorrect multiple times now under Yahoo!'s custodianship. This is a
spec that many people depend on, and speaking as the developer of the
SimplePie RSS parser, arbitrarily changing the namespace URL
substantially affects our ability to handle Media RSS feeds. (We
already have to normalize the two different Media RSS namespace URLs
that are floating around: one with, and one without the trailing slash
-- which was broken for over a year.)
I would really like to see the RSS Advisory Board pass a resolution to
publish the namespace documentation on its site with the proper
longtime namespace URI. Netscape trusted the board to oversee RSS 0.90
and RSS 0.91, and I would hope that Yahoo! would be able to see that
this transfer of custodianship would be a Good Thing™ for the Media
RSS community.
Future changes to the spec could be handled by the Media RSS
community, of which Yahoo! and others could be a part.
Thoughts?
On Jul 28, 2009, at 12:52 AM, Sapna Chandiramani wrote:
> Folks,
>
> I apologize for the issues on behalf of Yahoo.
> There were indeed some problems with the spec. This happened when we
> were moving the spec to the Video Search servers so it would be
> easier to respond to issues and requests henceforth.
>
> In any case, we have reverted back the spec. We are also working on
> a newer version of the spec that addresses some concerns this group
> had pointed out earlier, as well as some enhancements that we felt
> would be good to have.
>
> We will send that out for review to you soon.
>
> Thanks,
> Sapna
>
> -------- Original Message --------
> Subject: Re: [rss-media] Specification currently lists the wrong
> namespace
> Date: Tue, 21 Jul 2009 01:17:48 +0530
> From: Joly MacFie <joly@...>
> Reply-To: rss-media@yahoogroups.com <rss-media@yahoogroups.com>
> To: rss-media@yahoogroups.com <rss-media@yahoogroups.com>
> References: <h421vv+3t1f@eGroups.com>
> <2A6EB872-D3DE-4B36-9206-67902504C3A1@...>
>
> Earlier discussion:
>
http://tech.groups.yahoo.com/group/rss-media/msearch?query=slash&submit=Search&c\
harset=ISO-8859-1
>
<http://tech.groups.yahoo.com/group/rss-media/msearch?query=slash&submit=Search&\
charset=ISO-8859-1
> >
>
> Yahoo's neglect is a shame. Wasn't there some talk of moving it out of
> their control?
>
> joly
>
> On Mon, Jul 20, 2009 at 1:52 PM, Ryan Parman
> <ryan.lists.warpshare@...
> <mailto:ryan.lists.warpshare@...>>
> wrote:
>
> It looks like Yahoo once again arbitrarily changed the spec without
> telling anybody.
>
> As of the last update that anybody was aware of, we had:
>
> 03/12/2008 - Namespace corrections: [1.1.2]
>
> * Added trailing slash to namespace
>
> The correct namespace *should* be exactly what you posted.
> Apparently, Yahoo thought it'd be a good idea to change the
> namespace again and break all sorts of parsing software. It is
> embarrassing how badly they've bungled this spec.
>
> Once upon a time it fell to Jeremy Zawdony, but he's left Yahoo
> since then. From what I can tell, nobody at Yahoo is paying
> attention to this spec.
>
> On Jul 20, 2009, at 8:20 AM, James Abley wrote:
>
> > Hi,
> >
> > I'm putting http://search.yahoo.com/mrss/
> > <http://search.yahoo.com/mrss/> into my browser, which used to
> > display the spec and have the correct namespace on the page. At
> > the moment, I'm getting a 302 back to
> >
> > Location: http://video.search.yahoo.com/mrss
> > <http://video.search.yahoo.com/mrss>
> >
> > and that URL is used as the namespace URI in the rendered
> > specification.
> >
> > Anyone else noticed this and know who to raise it with? I don't
> > want any more ambiguity in the world as to the correct namespace
> > URI for this extension!
> >
> > Cheers,
> >
> > James
> >
>
> --
> ----------------------------------------------------------
> Joly MacFie 917 442 8665 Skype:punkcast
> WWWhatsup NYC - http://wwwhatsup.com <http://wwwhatsup.com>
> http://pinstand.com <http://pinstand.com> - http://punkcast.com
> <http://punkcast.com>
> ----------------------------------------------------------
>
>
>
[Non-text portions of this message have been removed]
--- In rss-public@yahoogroups.com, Ryan Parman <ryan.lists.warpshare@...> wrote:
> I would really like to see the RSS Advisory Board pass a resolution to
> publish the namespace documentation on its site with the proper
> longtime namespace URI. Netscape trusted the board to oversee RSS 0.90
> and RSS 0.91, and I would hope that Yahoo! would be able to see that
> this transfer of custodianship would be a Good Thing™ for the Media
> RSS community.
I favor this proposal and will work up a draft for consideration by the board.
The RSS Advisory Board has been around for years and has proven to be a useful
place for specs and other documentation related to RSS. We've recently moved the
site to its own server -- taking it off my own -- to ensure its continued
availability. We could publish the spec under any terms desired by Yahoo and the
Media RSS community.
Hello everyone,Im a newbie at this stuff.I have a valid rss v2.0 feed but it
says its missing atom.Have no clue how to do this.Here is the feed.
http://groups.google.com/group/rec.games.pinball/feed/rss_v2_0_msgs.xml If
anyone could show me what this feed should look like with the atom added i would
be greatfull.Thanks
[Non-text portions of this message have been removed]
Hello all.This is probably simple but as i am new to this stuff i can't figure
it out.I have a valid rss v2.0 feed but it tells me im missing an atom link.So
this is the
feed.http://www.groups.google.com/group/rec.games.pinball/feed/rss_v2_0_topics.x\
ml If someone could tell me where an how to put this atom link in i would be
thankful.LOL i don't know what an atom link looks like.Thanks
WordPress and Dave Winer are working on reviving RSSCloud as a means of RSS
update notification. It's an interesting project, and I'm glad to see the
attempt, but there's a reason cloud didn't catch on:
http://workbench.cadenhead.org/news/3555
Rogers,
Spent a lot of time thinking this one over. I think there are some best
practices in the Ajax world that can make rssCloud work, but it would mean
evolving the approach somewhat beyond what it is now.
My reply was getting too long to put in a message board email, so I blogged it
instead:
http://techbrew.net/articles/200909/rsscloud-all-wet/
- Mark
--- In rss-public@yahoogroups.com, "rcade" <cadenhead@...> wrote:
>
> WordPress and Dave Winer are working on reviving RSSCloud as a means of RSS
update notification. It's an interesting project, and I'm glad to see the
attempt, but there's a reason cloud didn't catch on:
>
> http://workbench.cadenhead.org/news/3555
>
Dave's response to Rogers and Mark.
http://www.scripting.com/stories/2009/09/08/20022009.html
IMHO, he didn't actually mention how he has overcome the limitations that Rogers
and Mark have raised.
http://www.therssweblog.com/?guid=20090908183007
And there's more. I'll write more in the morning.
Randy
--- In rss-public@yahoogroups.com, "mark.woodman" <mark@...> wrote:
>
> Rogers,
>
> Spent a lot of time thinking this one over. I think there are some best
practices in the Ajax world that can make rssCloud work, but it would mean
evolving the approach somewhat beyond what it is now.
>
> My reply was getting too long to put in a message board email, so I blogged it
instead:
>
> http://techbrew.net/articles/200909/rsscloud-all-wet/
>
> - Mark
>
>
> --- In rss-public@yahoogroups.com, "rcade" <cadenhead@> wrote:
> >
> > WordPress and Dave Winer are working on reviving RSSCloud as a means of RSS
update notification. It's an interesting project, and I'm glad to see the
attempt, but there's a reason cloud didn't catch on:
> >
> > http://workbench.cadenhead.org/news/3555
> >
>
Hi,
I'd like to use a variation of the sitemaps protocol
(http://www.sitemaps.org/protocol.php
<http://www.sitemaps.org/protocol.php> ) to enable client RSS readers to
discover all the available feeds in a domain just by referencing the
domain name.
I was going to post this to the Google Webmaster Central sitemaps group
but it appears to be a more of a products support group. I figured that
as I specifically want to enable access to RSS feeds this RSS group
would be a better place to discuss.
So, for the RSS reader example, the user would:
1) enter a domain
2) be presented with a list of all available feeds for the domain
3) select feeds to subscribe to
The RSS reader would:
1) download domain.com/robots.txt
2) discover and download the Sitemap: URL containing an index of indexes
into available site data, eg. feeds index, TV listings index
3) download the feeds index containing actual feeds and further feed
indexes
4) present the list of available feeds to the user
The web site owner would have:
1) published a sitemap-feeds index or a set of indexes in a variant
sitemap-feeds format
2) published a sitemap-index containing a link to the sitemap-feeds
index
3) linked through to the sitemap-index using Sitemap: in the robots.txt
file (see for example http://www.bbc.co.uk/robots.txt
<http://www.bbc.co.uk/robots.txt> )
I have created the following examples to illustrate how I think this
could work:
1) sitemap-index
I see there is a siteindex.xsd here:
http://www.sitemaps.org/schemas/sitemap/0.9/siteindex.xsd
<http://www.sitemaps.org/schemas/sitemap/0.9/siteindex.xsd>
...and an example here:
http://www.bbc.co.uk/sitemap.xml <http://www.bbc.co.uk/sitemap.xml>
However, in the RSS reader example, the client app would have to
download and parse each document to find out if the referenced data
relates to RSS feeds. Therefore maybe the sitemap-index format could
contain a namespace element for each entry. The RSS reader could then
understand that a standard sitemap namespace such as
http://www.sitemaps.org/schemas/sitemap/0.9/site-feeds means the
referenced URL contains information about feeds and so download the
correct index rather than having to download all files:
<sitemap-index>
<sitemap>
<loc>http://www.bbc.co.uk/sitefeeds.xml</loc>
<lastmod>20090914000000</lastmod>
<namespace>http://www.sitemaps.org/schemas/sitemap/0.9/site-feeds</names\
pace>
</sitemap>
<sitemap>
<loc>http://www.bbc.co.uk/tvlistings.xml</loc>
<lastmod>20090914000000</lastmod>
<namespace>http://www.sitemaps.org/schemas/sitemap/0.9/tvtimes</namespac\
e>
</sitemap>
</sitemap-index>
2) sitemap-feeds
In the following example there are two actual feeds and two further
indexes.
The namespace and mimetype elements could be optional here except for
further indexes which need the namespace data to instruct the client to
download the additional index list:
<sitemap-feeds>
<url>
<loc>http://newsrss.bbc.co.uk/rss/newsonline_uk_edition/front_page/rss.x\
ml</loc>
<lastmod>20090914212800</lastmod>
<title>BBC News | News Front Page | UK Edition</title>
<description>Visit BBC News for up-to-the-minute news...</description>
<namespace>http://search.yahoo.com/mrss</namespace>
<mimetype>application/rss+xml</mimetype>
</url>
<url>
<loc>http://newsrss.bbc.co.uk/rss/newsonline_uk_edition/latest_published\
_stories/rss.xml</loc>
<lastmod>20090914212800</lastmod>
<title>BBC News | Latest Published Stories | UK Edition</title>
<description>Updated every minute of every day</description>
<namespace>http://search.yahoo.com/mrss</namespace>
<mimetype>application/rss+xml</mimetype>
</url>
<url>
<loc>http://newsrss.bbc.co.uk/rss/news/newsmap.xml</loc>
<lastmod>20090914210000</lastmod>
<namespace>http://www.sitemaps.org/schemas/sitemap/0.9/site-feeds</names\
pace>
</url>
<url>
<loc>http://newsrss.bbc.co.uk/rss/sport/sportmap.xml</loc>
<lastmod>20090914210000</lastmod>
<namespace>http://www.sitemaps.org/schemas/sitemap/0.9/site-feeds</names\
pace>
</url>
</sitemap-feeds>
Does this make sense?
chris
[Non-text portions of this message have been removed]
As you probably know, Dave Winer's been working to revive the cloud element in
RSS and the RSSCloud Interface that defines how it is used. These date back to
RSS 0.92. The work's described on a web site he has launched:
http://www.rsscloud.org/
For this effort, Winer is unilaterally making changes to the RSSCloud Interface.
He has added multiple url# arguments (url1, url2, url3 and so on) to the REST
interface:
http://rsscloud.org/walkthrough.html#requestingNotificationUsingRest
He also has added a REST ping method:
http://rsscloud.org/walkthrough.html#pingingViaRestaNamepingresta
WordPress has implemented RSSCloud with Winer's participation for all seven
million of its hosted blogs on wordpress.com.
I'd like to know what the readers here think that the RSS Advisory Board should
do, if anything, in regard to this effort.
Offering autodiscovery for RSS reading lists is a good idea. Why did you look to
implement it in Google's sitemaps format rather than in OPML, the most popular
format for reading lists?
I can't find the link, but Winer's also proposed adding an optional domain
element to the REST interface of the cloud notification. This element when
present identifies a domain to call back with notifications instead of using the
requester's IP address.
I believe it has been discussed on this list whether there should be a namespace
for RSS:
http://tech.groups.yahoo.com/group/rss-public/message/1874http://tech.groups.yahoo.com/group/rss-public/message/1831
Presumably this would be for reusing RSS elements in XML other than RSS, rather
than redefining existing RSS feeds or changing RSS 2.0, which would break
backwards compatibility.
I think I have another good use case for there being a "recognized" namespace to
use when reusing the RSS schema elements out of RSS context:
http://masonlee.org/2009/09/11/rsscloud-atom-extension/
Does rssboard have a general namespace in mind? Would it be suitable for my
purposes outlined in the above blog post? Would RSS Board like to host an xsd
at the namespace URL?
Thanks in advance for your consideration.
Mason Lee
http://masonlee.org
Rogers,
I think the RSS board should be forking the RSS cloud spec as it stands right
now and fixing the glaring issues in it (ie: the DDoS vulnerability
http://grack.com/blog/2009/09/10/serious-rsscloud-ddos-vulnerability/) before it
becomes too widespread.
I'd start by formalizing the http-post protocol part of RSSCloud, adding in the
necessary challenge parameter to prevent rogue subscriptions.
I would certainly be willing to take a crack at specifying the protocol or
working with whoever decides to take this on.
--- In rss-public@yahoogroups.com, "rcade" <cadenhead@...> wrote:
>
> As you probably know, Dave Winer's been working to revive the cloud element in
RSS and the RSSCloud Interface that defines how it is used. These date back to
RSS 0.92. The work's described on a web site he has launched:
>
> http://www.rsscloud.org/
>
> For this effort, Winer is unilaterally making changes to the RSSCloud
Interface. He has added multiple url# arguments (url1, url2, url3 and so on) to
the REST interface:
>
> http://rsscloud.org/walkthrough.html#requestingNotificationUsingRest
>
> He also has added a REST ping method:
>
> http://rsscloud.org/walkthrough.html#pingingViaRestaNamepingresta
>
> WordPress has implemented RSSCloud with Winer's participation for all seven
million of its hosted blogs on wordpress.com.
>
> I'd like to know what the readers here think that the RSS Advisory Board
should do, if anything, in regard to this effort.
>
I've written my thoughts on the subject on my blog.
http://workbench.cadenhead.org/news/3559
The short version is that one person should not be allowed to control the
revision of the RSSCloud Interface.
On Tue, Sep 15, 2009 at 1:53 PM, rcade <cadenhead@...> wrote:
> I've written my thoughts on the subject on my blog.
>
> http://workbench.cadenhead.org/news/3559
>
> The short version is that one person should not be allowed to control the
revision of the RSSCloud Interface.
I agree that the process of creating a spec unilaterally by a single
(or even small group of people!) is not a good thing.
I don't believe 'we' as the RSS Board should 'take over' anything though.
I personally believe the only thing the RSS Board should perhaps do,
is promote PubSubHubBub, it is being developed in the open, by people
who get it. (once they are approaching a finalized specification of
course)
That should be our response, not diving into political games that
poison communities.
As Brad mentioned in his blog post, It is unfortunate that there was
some belief that PubSubHubBub is specific to Atom -- but that has been
corrected, and was just an oversight.
--- In rss-public@yahoogroups.com, "rcade" <cadenhead@...> wrote:
>
> Offering autodiscovery for RSS reading lists is a good idea. Why did you look
to implement it in Google's sitemaps format rather than in OPML, the most
popular format for reading lists?
>
I'd like to create a data format based on the concept of the sitemaps protocol
rather than use the Google News format variation itself. I like the idea of
using the robots.txt file to embed a link to a sitemap index for data exchange
and given that there is some awareness of sitemaps I figured it could be a good
place to start.
Using OPML for the RSS index does make sense so I agree this could be used
instead of the sitemap-feeds doc but the sitemap-index doc would still be needed
so that other types of data can be discovered. The namespace tag per entry in
the sitemap-index doc could hint to the client what type of data is contained
within the referenced index.
OPML indexes for other types of data could work, eg. to reference TV listings
docs in XMLTVFormat, but maybe some types of data could use new index formats.
The RSS reader would need a better hint from the sitemap-index doc than just the
OPML namespace though if other types of data also used OPML otherwise it could
download unnecessary data.
For the record, my thoughts on this subject are similar to Anil Dash's
comments on your blog. [1]
Let's leave Dave to do his thing for now. Offer feedback if you think it
might help (some of his changes do seem to be in response to comments others
have made), and once the technology has matured and is more widely used, we
can consider whether further action from the board would helpful.
Personally, at least from the client side, I prefer RSS cloud to PuSH, but
I'm not sure we should be picking sides. At least not this early in the
process, when both specs are still evolving.
Further down the line we may want to add some guidance in the BPP on how
best to use these technologies (both of them if they both gain significant
traction). However, I think it's a little too early to be thinking about
that now.
Regards
James
[1]
http://workbench.cadenhead.org/news/3559/rsscloud-should-not-controlled-one#2856\
89
masonglee wrote:
> I think I have another good use case for there being a "recognized"
> namespace to use when reusing the RSS schema elements out of RSS context:
>
> http://masonlee.org/2009/09/11/rsscloud-atom-extension/
From the rsscloud.org website:
"Just define a namespace to have a single element in it, the <cloud> element
from RSS 2.0.
If you need a URL for the namespace, please consider using the URL for this
site. "
That implies a one-off namespace for just the cloud element, which I'm not
sure is a great idea, but it appears to be Dave's current recommendation. We
shall see whether that gains traction or not. AFAICT Wordpress doesn't yet
support RSS cloud in their Atom feeds.
Regards
James
--- In rss-public@yahoogroups.com, "James Holderness" <j4_james@...> wrote:
> Let's leave Dave to do his thing for now. Offer feedback if you
> think it might help (some of his changes do seem to be in response
> to comments others have made), and once the technology has matured
> and is more widely used, we can consider whether further action
> from the board would helpful.
If we defer to Dave, he will control RSSCloud and the most likely outcome is
that the spec will be imprecise, he will declare it frozen and we won't be in
any position to do anything afterward other than live with it. RSS includes
RSSCloud, so the RSS Advisory Board will be tasked with helping people support
it.
If we are letting him take over a component of the RSS specification and make
changes to it, I think the board members who favor this course should get
involved with his development of RSSCloud before he declares it frozen. The
window of opportunity to improve it is probably short.
Also, I think the new RSSCloud needs a version number to distinguish it from the
original interface.
Dave has made a request to me that could be directed to the board as well:
"A couple of requests.
"1. Work through the rsscloud.org doc with the same approach you used here. An
open mind, don't prejudge. I'd be interested to hear how your experience
compares.
"2. Review the docs and report any problems you see. There's a mail list or use
the comments section on the walkthrough. As you've said, now is the time to fix
problems. If you find them later it will be more difficult.
"3. Also if possible review the Wordpress implementation and my rsscloud.root. I
shipped source and it's in a Frontier tool, an environment you know well."
I appreciate the gesture he's made here, but speaking for myself personally, I
won't participate in a project that puts part of RSS in a single developer's
control. We fought hard to establish a public process and community
decision-making on matters related to RSS, and supporting his project is counter
to that.
--- In rss-public@yahoogroups.com, "James Holderness" <j4_james@...> wrote:
> That implies a one-off namespace for just the cloud element, which I'm not
> sure is a great idea, but it appears to be Dave's current recommendation. We
> shall see whether that gains traction or not. AFAICT Wordpress doesn't yet
> support RSS cloud in their Atom feeds.
A better way to handle the use of RSS elements in other XML dialects would be
the proposal we've been batting around. Revise the RSS spec to declare that when
RSS elements are used in other formats, the namespace URI should be
"http://www.rssboard.org/rss-namespace", but that RSS itself does not have a
namespace.
Dave's RSSCloud proposal is another use case for the need to have a namespace
for RSS used elsewhere.
I agree. We need to get the embedded namespace going. My bad.
Randy
http://www.therssweblog.com/
--- In rss-public@yahoogroups.com, "Rogers" <cadenhead@...> wrote:
> A better way to handle the use of RSS elements in other XML dialects would be
the proposal we've been batting around. Revise the RSS spec to declare that when
RSS elements are used in other formats, the namespace URI should be
"http://www.rssboard.org/rss-namespace", but that RSS itself does not have a
namespace.
>
> Dave's RSSCloud proposal is another use case for the need to have a namespace
for RSS used elsewhere.
>
* Rogers <cadenhead@...> [2009-09-19 19:25]:
> If we defer to Dave, he will control RSSCloud and the most
> likely outcome is that the spec will be imprecise, he will
> declare it frozen and we won't be in any position to do
> anything afterward other than live with it.
That’s what the RSS Board *does*. You thought you were signing
up for something else?
Regards,
--
Aristotle Pagaltzis // <http://plasmasturm.org/>
On Sat, Sep 19, 2009 at 2:11 PM, Aristotle Pagaltzis <pagaltzis@...> wrote:
> That’s what the RSS Board *does*. You thought you were signing
> up for something else?
The board decided to be conservative about touching the spec, so we
ended up writing the RSS Best Practices Profile instead.
That doesn't mean the same approach would be taken on new RSS-related
specs. If we had decided to revise RSSCloud, the board would have been
as rigorous as it was on the profile.
Yep, we've already agreed on a namespace.
http://www.rssboard.org/rss-namespace
We just haven't modified the spec to include it, but will shortly
Thanks,
Randy
--- In rss-public@yahoogroups.com, "masonglee" <mason.lee@...> wrote:
>
> I believe it has been discussed on this list whether there should be a
namespace for RSS:
>
> http://tech.groups.yahoo.com/group/rss-public/message/1874
> http://tech.groups.yahoo.com/group/rss-public/message/1831
>
> Presumably this would be for reusing RSS elements in XML other than RSS,
rather than redefining existing RSS feeds or changing RSS 2.0, which would break
backwards compatibility.
>
> I think I have another good use case for there being a "recognized" namespace
to use when reusing the RSS schema elements out of RSS context:
>
> http://masonlee.org/2009/09/11/rsscloud-atom-extension/
>
> Does rssboard have a general namespace in mind? Would it be suitable for my
purposes outlined in the above blog post? Would RSS Board like to host an xsd
at the namespace URL?
>
> Thanks in advance for your consideration.
>
> Mason Lee
> http://masonlee.org
>
* Rogers Cadenhead <cadenhead@...> [2009-09-19 20:45]:
> On Sat, Sep 19, 2009 at 2:11 PM, Aristotle Pagaltzis <pagaltzis@...> wrote:
> >That’s what the RSS Board *does*. You thought you were signing
> >up for something else?
>
> The board decided to be conservative about touching the spec,
> so we ended up writing the RSS Best Practices Profile instead.
And you’ll end up writing an RSSCloud Best Practices Profile.
> That doesn't mean the same approach would be taken on new
> RSS-related specs. If we had decided to revise RSSCloud, the
> board would have been as rigorous as it was on the profile.
Do you honestly believe what you are saying? That the RSSÂ Board
carries even an ounce of weight with Winer? “Decided to revise
RSSCloud”, really?
Regards,
--
Aristotle Pagaltzis // <http://plasmasturm.org/>
--- In rss-public@yahoogroups.com, Aristotle Pagaltzis <pagaltzis@...> wrote:
> And you'll end up writing an RSSCloud Best Practices Profile.
I would not vote for doing that or work on it.
> Do you honestly believe what you are saying? That the RSSÂ Board
> carries even an ounce of weight with Winer? "Decided to revise
> RSSCloud", really?
The RSS Advisory Board has been around for six years. I don't see the point of
diving back into the argument over whether we have authority to do anything in
this space.
Hi -- I've been following the discussion here and elsewhere, and encourage you
all to help out in the bootstrap that's going on now to make RSS realtime. It's
something I've wanted to see happen since 2001, and now seems to be the time. It
seems the same as when podcasting was booting up in 2004. We were ready much
earlier, but the time wasn't right.
Anyway, after seeing Rogers' review of PSHB, I saw that we were missing a
document that showed the easy path into rssCloud for people who just have a
feed. Of course it's much easier to get started for publishers.
http://rsscloud.org/walkthrough/publisher.html
You'll see there's a place to comment, if you have any problems getting started,
please post a question there. Please try to avoid questions like "Who do you
think you are?" -- that's not so helpful. :-)
Dave
May 18, 2004
http://cyber.law.harvard.edu/rss/2004/05/18/#a540
There's been some confusion about the role of the advisory board. The purpose of
this post to try to clear it up.
1. It's got a very conservative mission, to answer questions about RSS, to help
people use it, to promote its use. It's basically a support function.
2. Anyone can extend RSS through namespaces. We suggest that people look first
to see if there is a core element that already does what they need to do, and if
so, use that instead of inventing a new one. That will keep the work of
aggregator developers to a minimum, keep the barriers to entry low, help keep
the market competitive. Competition should be based on features, performance and
price, not compatibility. Compatibility should be easy.
3. Emphatically, this group is not a standards organization. It does not own
RSS, or the spec, it has no more or less authority than any other group of
people who wish to promote RSS.
# Posted on 5/18/04; 3:59:18 PM -
Send Email
