I second my future second of your proposal ;-)
--- In rss-board@yahoogroups.com, "rcade" <cadenhead@...> wrote:
>
> Randy Charles Morin and I are going to propose the RSS Profile to a
> vote of the RSS Advisory Board next Monday. The effort to draft a set
> of best practices guidelines for RSS 2.0 has been 18 months in the
making:
>
> http://www.rssboard.org/rss-profile
>
> If you see any issues that should be addressed before the vote, or
> there are changes you'd like us to consider, let us know on RSS-
Public.
>
The following RSS Advisory Board proposal has been made by Rogers
Cadenhead and seconded by Randy Charles Morin.
Under the advisory board charter, the board has seven days to discuss
the proposal followed by seven days to vote on it. Interested parties
can comment on the proposal on the mailing list RSS-Public [1].
Proposal
For the last 18 months, the RSS Advisory Board has been drafting a set
of best-practice recommendations for RSS [2]. Working with the
developers of browsers such as Microsoft Internet Explorer and Mozilla
Firefox, aggregators such as Bloglines and Google Reader, and blogging
tools including Movable Type, we've looked for areas where questions
about the RSS format have led to differences in how software has been
implemented to produce and consume RSS feeds.
The result of our work is the RSS Profile:
http://www.rssboard.org/rss-profile
The lead authors are James Holderness, Morin, Geoffrey Sneddon and
myself. The profile isn't a set of rules; it's a set of suggestions
drafted by programmers and web publishers who've been working with RSS
since the format's first release in 1999. Our goal is for the profile
to be the second document programmers consult when they're learning
how to implement RSS.
The profile tackles some long-standing issues in RSS implementation,
including the proper number of enclosures per item, the meaning of the
TTL element and the use of HTML markup in character data.
In addition to recommendations for the RSS elements documented in the
specification, the profile includes advice for four common namespace
elements: atom:link, content:encoded, dc:creator and slash:comments.
We propose that the board endorse and publish the RSS Profile, making
it available under a Creative Commons Attribution-ShareAlike 2.0
license [3] so that others can build upon and extend it with their own
recommendations.
Additionally, we propose that the following sentence be added to the
About this document section [4] of the specification, as a new fifth
paragraph:
"The RSS Profile [5] contains a set of recommendations for how to
create RSS documents that work best in the wide and diverse audience
of client software that supports the format."
1: http://groups.yahoo.com/group/rss-public
2: http://www.rssboard.org/rss-specification
3: http://www.rssboard.org/rss-profile#license
4: http://www.rssboard.org/rss-specification#aboutThisDocument
5: http://www.rssboard.org/rss-profile
The vote has begun on the proposal to adopt the RSS Profile. As one of
the proponents, I'm voting yes, and I'd like to encourage the board
members to do the same.
When I joined the board back in the Pleistocene epoch, we used to hear
over and over from developers about three issues that were making RSS
2.0 harder to implement:
1. How many enclosures can an item contain?
2. Are relative URLs OK in item descriptions?
3. Is it OK to use HTML in elements other than an item's description?
With the RSS Profile, we can now answer these questions.
1. One, if you want your feed to work in the widest number of clients.
http://www.rssboard.org/rss-profile#element-channel-item-enclosure
2. No, because there's no way in RSS to identify the base URL to
resolve them to.
http://www.rssboard.org/rss-profile#element-channel-item-description
3. No, but many aggregators expect HTML in other elements, so we're
offering some tips on how to encode text properly.
http://www.rssboard.org/rss-profile#data-types-characterdata
If we pass the profile, we can start evangelizing its full adoption in
RSS software that produces and consumes RSS and seek translations into
other languages.
I vote yes for a greater tomorrow in RSS-land ;-)
Randy
--- In rss-board@yahoogroups.com, "rcade" <cadenhead@...> wrote:
>
> The vote has begun on the proposal to adopt the RSS Profile. As one of
> the proponents, I'm voting yes, and I'd like to encourage the board
> members to do the same.
>
No. Why is this best practices and not just a formal declaration/spec?
Guidelines will add no value.
--- In rss-board@yahoogroups.com, "rcade" <cadenhead@...> wrote:
>
> The following RSS Advisory Board proposal has been made by Rogers
> Cadenhead and seconded by Randy Charles Morin.
>
> Under the advisory board charter, the board has seven days to discuss
> the proposal followed by seven days to vote on it. Interested parties
> can comment on the proposal on the mailing list RSS-Public [1].
>
> Proposal
>
> For the last 18 months, the RSS Advisory Board has been drafting a set
> of best-practice recommendations for RSS [2]. Working with the
> developers of browsers such as Microsoft Internet Explorer and Mozilla
> Firefox, aggregators such as Bloglines and Google Reader, and blogging
> tools including Movable Type, we've looked for areas where questions
> about the RSS format have led to differences in how software has been
> implemented to produce and consume RSS feeds.
>
> The result of our work is the RSS Profile:
>
> http://www.rssboard.org/rss-profile
>
> The lead authors are James Holderness, Morin, Geoffrey Sneddon and
> myself. The profile isn't a set of rules; it's a set of suggestions
> drafted by programmers and web publishers who've been working with RSS
> since the format's first release in 1999. Our goal is for the profile
> to be the second document programmers consult when they're learning
> how to implement RSS.
>
> The profile tackles some long-standing issues in RSS implementation,
> including the proper number of enclosures per item, the meaning of the
> TTL element and the use of HTML markup in character data.
>
> In addition to recommendations for the RSS elements documented in the
> specification, the profile includes advice for four common namespace
> elements: atom:link, content:encoded, dc:creator and slash:comments.
>
> We propose that the board endorse and publish the RSS Profile, making
> it available under a Creative Commons Attribution-ShareAlike 2.0
> license [3] so that others can build upon and extend it with their own
> recommendations.
>
> Additionally, we propose that the following sentence be added to the
> About this document section [4] of the specification, as a new fifth
> paragraph:
>
> "The RSS Profile [5] contains a set of recommendations for how to
> create RSS documents that work best in the wide and diverse audience
> of client software that supports the format."
>
> 1: http://groups.yahoo.com/group/rss-public
> 2: http://www.rssboard.org/rss-specification
> 3: http://www.rssboard.org/rss-profile#license
> 4: http://www.rssboard.org/rss-specification#aboutThisDocument
> 5: http://www.rssboard.org/rss-profile
>
On 10/8/07, mdbookspan <mbookspan@...> wrote:
> No. Why is this best practices and not just a formal declaration/spec?
> Guidelines will add no value.
I tried this approach in October 2006, proposing to clarify the spec
on the issues of enclosures, relative URLs, HTML markup and other
questions with a clean rewrite of the RSS 2.0 spec:
http://tech.groups.yahoo.com/group/rss-board/message/143
The proposal died for lack of a second. If there's interest now in
clarifying the spec, either by revising the existing document or
taking my proposal off the table, let me know.
But even if we revise the spec, there are things the RSS Profile can
accomplish that can't be done in the spec -- such as telling people
that ttl, skipDays, ratings and textInput are implemented by less than
one percent of surveyed feeds; recommending atom:link to identify a
feed's URL; recommending dc:creator as an alternative to
channel-managingEditor; and documenting test results for several dozen
RSS clients and feed publishing tools.
rcade wrote:
> The vote has begun on the proposal to adopt the RSS Profile. As one of
> the proponents, I'm voting yes, and I'd like to encourage the board
> members to do the same.
I vote yes. The profile may not be perfect, but I still believe it will be a
valuable resource to both feed publishers and aggregator developers.
Regards
James
Yes on the proposal.
On Oct 9, 2007 12:38 AM, James Holderness <j4_james@...> wrote:
> rcade wrote:
> > The vote has begun on the proposal to adopt the RSS Profile. As one of
> > the proponents, I'm voting yes, and I'd like to encourage the board
> > members to do the same.
>
> I vote yes. The profile may not be perfect, but I still believe it will be a
> valuable resource to both feed publishers and aggregator developers.
>
> Regards
> James
>
>
>
>
>
> Yahoo! Groups Links
>
>
>
>
--
Cheers,
Jason Shellen
I vote yes ... good job. In a future version, I'd like a little
section on best practices if an item has both <link> and <guid
isPermaLink="true"> elements, which I'd be happy to help with.
Eric Lunt
The following RSS Advisory Board proposal has been made by Rogers
Cadenhead and seconded by Randy Charles Morin.
Under the advisory board charter, the board has seven days to discuss
the proposal followed by seven days to vote on it. Interested parties
can comment on the proposal on the mailing list RSS-Public [1].
Proposal
For the last 18 months, the RSS Advisory Board has been drafting a set
of best-practice recommendations for RSS [2]. Working with the
developers of browsers such as Microsoft Internet Explorer and Mozilla
Firefox, aggregators such as Bloglines and Google Reader, and blogging
tools including Movable Type, we've looked for areas where questions
about the RSS format have led to differences in how software has been
implemented to produce and consume RSS feeds.
The lead authors are James Holderness, Morin, Geoffrey Sneddon and
myself. The profile isn't a set of rules; it's a set of suggestions
drafted by programmers and web publishers who've been working with RSS
since the format's first release in 1999. Our goal is for the profile
to be the second document programmers consult when they're learning
how to implement RSS.
The profile tackles some long-standing issues in RSS implementation,
including the proper number of enclosures per item, the meaning of the
TTL element and the use of HTML markup in character data.
In addition to recommendations for the RSS elements documented in the
specification, the profile includes advice for four common namespace
elements: atom:link, content:encoded, dc:creator and slash:comments.
We propose that the board endorse and publish the RSS Profile, making
it available under a Creative Commons Attribution-ShareAlike 2.0
license [3] so that others can build upon and extend it with their own
recommendations.
Additionally, we propose that the following sentence be added to the
About this document section [4] of the specification, as a new fifth
paragraph:
"The RSS Profile [5] contains a set of recommendations for how to
create RSS documents that work best in the wide and diverse audience
of client software that supports the format."
I vote yes.
-Paul
rcade wrote:
> The vote has begun on the proposal to adopt the RSS Profile. As one of
> the proponents, I'm voting yes, and I'd like to encourage the board
> members to do the same.
>
> When I joined the board back in the Pleistocene epoch, we used to hear
> over and over from developers about three issues that were making RSS
> 2.0 harder to implement:
>
> 1. How many enclosures can an item contain?
>
> 2. Are relative URLs OK in item descriptions?
>
> 3. Is it OK to use HTML in elements other than an item's description?
>
> With the RSS Profile, we can now answer these questions.
>
> 1. One, if you want your feed to work in the widest number of clients.
>
> http://www.rssboard.org/rss-profile#element-channel-item-enclosure
>
> 2. No, because there's no way in RSS to identify the base URL to
> resolve them to.
>
> http://www.rssboard.org/rss-profile#element-channel-item-description
>
> 3. No, but many aggregators expect HTML in other elements, so we're
> offering some tips on how to encode text properly.
>
> http://www.rssboard.org/rss-profile#data-types-characterdata
>
> If we pass the profile, we can start evangelizing its full adoption in
> RSS software that produces and consumes RSS and seek translations into
> other languages.
>
>
>
>
> Yahoo! Groups Links
>
>
>
From: rcade <cadenhead@...> Sent: Monday, October 08, 2007 06:05 AM To: rss-board@yahoogroups.com Subject: [rss-board] Vote: Publish the RSS Best-Practices Profile
The vote has begun on the proposal to adopt the RSS Profile. As one of the proponents, I'm voting yes, and I'd like to encourage the board members to do the same.
When I joined the board back in the Pleistocene epoch, we used to hear over and over from developers about three issues that were making RSS 2.0 harder to implement:
1. How many enclosures can an item contain?
2. Are relative URLs OK in item descriptions?
3. Is it OK to use HTML in elements other than an item's description?
With the RSS Profile, we can now answer these questions.
1. One, if you want your feed to work in the widest number of clients.
If we pass the profile, we can start evangelizing its full adoption in RSS software that produces and consumes RSS and seek translations into other languages.
The proposal to endorse and publish the RSS Profile has passed 8-1
with RSS Advisory Board members Rogers Cadenhead, Christopher Finke,
James Holderness, Eric Lunt, Randy Charles Morin, Paul Querna, Jake
Savin and Jason Shellen voting in favor and Matthew Bookspan voting
against.
Full details here:
http://www.rssboard.org/news/178
Loic Le Meur and Jason Douglas have left the board. Loic's outside
commitments prevent him from continuing and Jason has joined a startup
outside the RSS space, so he didn't think he should remain a member.
Also, I'm exercising my discretion as chair and removing Greg Smith
from the board for inactivity. He's missed four successive votes going
back to Nov. 2006. If he has time later to rejoin, I'd love to see him
do so because he's a great resource on mobile feedreading.
Thanks for your efforts, Loic, Jason and Greg! These departures leave
four spots open, so if you'd like to propose a member, please do so on
the board's private mailing list for member deliberations.
WordPress and WordPress MU now support atom:link in their RSS feeds,
one of the recommendations in the RSS Profile:
http://www.rssboard.org/news/179
If you work on any software that produces RSS feeds, I'd like to work
with you to add atom:link and other recommendations in the profile.
I've made the announcement about Sterling "Chip" Camden and Simone
Carletti joining the board:
http://www.rssboard.org/news/180
Matthew Bookspan and Christopher Finke have left the board due to time
considerations and a job change, respectively. I'd like to thank them
for lending their time to this effort.
So hello, hello, goodbye, goodbye and thanks^4!
A year ago, Netscape moved My.Netscape.Com to new servers as part of a
relaunch and temporarily hosed the RSS 0.91 DTD. Because RSS 0.91
requires the DTD, there's software out there that was hitting their
servers as it parsed RSS feeds. They were getting four million
requests a day for the DTD.
I told Chris Finke and Tom Drapeau at Netscape that if they ever
needed a permanent home for the specs and other docs, we'd be happy to
help. The board's already providing the same services for the current
RSS. We can serve the older specs, answer questions on RSS-Public and
encourage people to upgrade from RSS 0.90 or 09.1 to RSS 2.0.
Here are the dueling announcements:
http://tinyurl.com/2rng4bhttp://www.rssboard.org/news/181
Here's the first version of a conversion guide for people who want to
move from RSS 0.91 to RSS 2.0:
http://www.rssboard.org/convert-rss-0-91-to-rss-2-0
If you have any suggestions, let me know.
rcade wrote:
> Here are the dueling announcements:
>
> http://tinyurl.com/2rng4b
> http://www.rssboard.org/news/181
That's great news.
> Here's the first version of a conversion guide for people who want to
> move from RSS 0.91 to RSS 2.0:
>
> http://www.rssboard.org/convert-rss-0-91-to-rss-2-0
Nicely done. I think there should be some mention of named entities though -
the DTD in 0.91 defined a bunch of Latin entities which won't be valid in
RSS 2.0 once the DTD has been removed.
Also, I'm not sure the section about HTML in RSS 2.0 is quite right. In
item/description elements, representing &, < and > as hex character
references, while legal, is probably not ideal.
Regards
James
--- In rss-board@yahoogroups.com, "rcade" <cadenhead@...> wrote:
>
> I've made the announcement about Sterling "Chip" Camden and Simone
> Carletti joining the board:
>
> http://www.rssboard.org/news/180
>
> Matthew Bookspan and Christopher Finke have left the board due to time
> considerations and a job change, respectively. I'd like to thank them
> for lending their time to this effort.
>
> So hello, hello, goodbye, goodbye and thanks^4!
>
Hi Rogers,
due to a few personal problems I've just joined the list today.
Thanks to you and all board members for giving me this great
opportunity! :)
-- Simone
Hello everybody,
I just completed the translation for the document "Convert from RSS
0.91 to RSS 2.0" that Rogers created a few weeks ago.
http://rss.specifiche.it/2.0/convert-rss-0-91-to-rss-2-0.htm
I will post to the public mailing-list in a few days, just the time to
check it again before announcing it.
Any feedback or suggestion is appreciated. :)
-- Simone
--- In rss-board@yahoogroups.com, "Simone Carletti" <weppos@...> wrote:
> I just completed the translation for the document "Convert from RSS
> 0.91 to RSS 2.0" that Rogers created a few weeks ago.
> http://rss.specifiche.it/2.0/convert-rss-0-91-to-rss-2-0.htm
Cool. Thanks!
I'd like to see the RSS Profile translated into Italian and other
languages. If there's anything we can do to help with this, such as
issuing a call for translators, let me know.
I already planned to translate the RSS Profile but I need a small architecture upgrade before. I'm moving all sites from *.specifiche.it to a single wiki installation under specifiche.it. Wiki is a better way to manage these files that at the moment are all stored as static files.
I hope to have a first RSS Profile draft ready soon!
> such as issuing a call for translators, let me know.
Talking from my side, once the wiki will be installed that would be a great help! Wiki allows collaborative translation while current architecture doesn't.
-- Simone
On Mon, Mar 3, 2008 at 4:31 PM, rcade <cadenhead@...> wrote:
I'd like to see the RSS Profile translated into Italian and other
languages. If there's anything we can do to help with this, such as
issuing a call for translators, let me know.
Nat Lanza recently wrote on Twitter, "Dear weblog authors: I pretty
much never want to have to figure out *which* of your feeds to
subscribe to. Pick a format and stick with it."
http://twitter.com/nlanza/statuses/776809841
I have the same thought every time I find a site that offers a choice
of its feed in RSS 1.0, RSS 2.0 or Atom formats. This approach
actively deters subscribers, because most web users have no idea how
to make this choice and it scares them off.
Should the RSS Advisory Board recommend that feed publishers offer
their feeds in one format only, whether they choose Atom, RSS 1.0 or
RSS 2.0 as that format?
+1 adding this to the profile
--- In rss-board@yahoogroups.com, "rcade" <cadenhead@...> wrote:
>
> Nat Lanza recently wrote on Twitter, "Dear weblog authors: I pretty
> much never want to have to figure out *which* of your feeds to
> subscribe to. Pick a format and stick with it."
>
> http://twitter.com/nlanza/statuses/776809841
>
> I have the same thought every time I find a site that offers a choice
> of its feed in RSS 1.0, RSS 2.0 or Atom formats. This approach
> actively deters subscribers, because most web users have no idea how
> to make this choice and it scares them off.
>
> Should the RSS Advisory Board recommend that feed publishers offer
> their feeds in one format only, whether they choose Atom, RSS 1.0 or
> RSS 2.0 as that format?
>
--- In rss-board@yahoogroups.com, "rcade" <cadenhead@...> wrote:
>
> Nat Lanza recently wrote on Twitter, "Dear weblog authors: I pretty
> much never want to have to figure out *which* of your feeds to
> subscribe to. Pick a format and stick with it."
>
> http://twitter.com/nlanza/statuses/776809841
>
> I have the same thought every time I find a site that offers a choice
> of its feed in RSS 1.0, RSS 2.0 or Atom formats. This approach
> actively deters subscribers, because most web users have no idea how
> to make this choice and it scares them off.
>
> Should the RSS Advisory Board recommend that feed publishers offer
> their feeds in one format only, whether they choose Atom, RSS 1.0 or
> RSS 2.0 as that format?
>
+1
There was an excellent article I read on 2004 about choosing a single
feed flavor instead of duplicating the same content across multiple feeds.
I tried to find this but I didn't remember who was the autor. Niall
Kennedy, Nick Bradbury, Mark Nottingham...
The only article concerning feed confusion I have been able to pick up
from my delicious archive is
http://www.simplebits.com/notebook/2005/04/14/feeds.html
Simone
--- In rss-board@yahoogroups.com, "Randy Morin" <randy@...> wrote:
> +1 adding this to the profile
Would you support a resolution as well, like the ones we've done
endorsing the common feed icon and Feed Validator?
--- In rss-board@yahoogroups.com, "rcade" <cadenhead@...> wrote:
>
> --- In rss-board@yahoogroups.com, "Randy Morin" <randy@> wrote:
> > +1 adding this to the profile
>
> Would you support a resolution as well, like the ones we've done
> endorsing the common feed icon and Feed Validator?
>
I believe it's hard to talk about a "resolution" in this situation.
I would talk about suggestions instead.
The suggestion I usually provide is the following:
1. always use the latest feed version
For instance, if you are syndicating a feed as a RSS 0.91, RSS 0.92
and RSS 2.0 you are simply wasting your time.
Because RSS 2.0 is the natural evolution of the other releases, simply
use RSS 2.0 and you will obtain the same result with the bonus you are
not spreading confusion.
The same applies to Atom: be sure you are not using Atom 0.3 and Atom
1.0 for the same content.
2. choose between RSS 1.0, RSS 2.0 and Atom 1.0
At the end of the story, at least you should have to decide among 3
major formats: RSS 1.0, RSS 2.0 and Atom 1.0.
Each format has special features and unique specification thus you
"simply" need to use the one that better suit your needs.
Don't be scared about feed readers.
The 90% of them is compatibile with these 3 formats thus syndicate the
one you are more comfortable with, you better understand or offers the
features your feed really needs.
About the last sentence, I wrote a full article (in Italian) a couple
of years ago.
http://xml.html.it/articoli/leggi/263/a-ciascuno-il-suo-rss/
Probably it's outdated now, but I suppose it could be useful to
provide a short list of common choices for feed publisher, if applicable.
For example, would you syndicate a podcast? Format RSS 2.0 it's better
to use because... and so on.
Simone
For those that don't know, I beat Rogers Cadenhead at Wii Golf and thus
assumed leadership of the RSS advisory board. Big thanks to Rogers for
all his great work in the last two years and his crappy golf skills as
well. I hope we can do something special in the next year.
Randy
http://www.therssweblog.com
I ask all board members to please vote on the following matter. Failure to vote
on successive appeals to vote may lead to removal from the board. We ask that
you vote for either of the two namespaces or to vote to abstain in the next 7
days.
This vote is not binding in any form and absolutely nothing should be
interpreted from the results. This vote is solely to determine which namespace
should be used for RSS elements, if ever that happens. A secondary vote to
modify the RSS spec is required before this board approves any use of namespaces
with RSS elements.
Board members may vote for either of the two following namespaces or they may
vote to abstain.
http://backend.userland.com/rss2http://www.rssboard.org/rss-specification
Please review the following thread on the RSS-public mailing list to review
arguments for either namespace.
http://tech.groups.yahoo.com/group/rss-public/message/1874
I vote for http://www.rssboard.org/rss-specification.
--
Ryan Parman
<http://ryanparman.com>
On Feb 18, 2009, at 11:46 AM, Randy Morin wrote:
> I ask all board members to please vote on the following matter.
> Failure to vote on successive appeals to vote may lead to removal
> from the board. We ask that you vote for either of the two
> namespaces or to vote to abstain in the next 7 days.
>
> This vote is not binding in any form and absolutely nothing should
> be interpreted from the results. This vote is solely to determine
> which namespace should be used for RSS elements, if ever that
> happens. A secondary vote to modify the RSS spec is required before
> this board approves any use of namespaces with RSS elements.
>
> Board members may vote for either of the two following namespaces or
> they may vote to abstain.
>
> http://backend.userland.com/rss2
> http://www.rssboard.org/rss-specification
>
> Please review the following thread on the RSS-public mailing list to
> review arguments for either namespace.
>
> http://tech.groups.yahoo.com/group/rss-public/message/1874
>
>
>
>
>
> ------------------------------------
>
> Yahoo! Groups Links
>
>
>
Send Email
