Slashdot Mirror
RSS Version 3 Specs Up for Review
Jonathan Avidan writes "The RSS 3 Homepage now offers its first publicly available specification, the RSS 3 Lite-type Specification First Draft, intended for review and commenting for revision. RSS 3 is a reworking of RSS 2.0, filling the gaps and removing unnecessary features and is fully backwards-compatible, rather than a new format."
They removed
:)
<clouds>
<skipHours>
<skipDays>
<textInput>
<source> element
<pics> element
<guid> element's optional "isPemraLink" attribute
And added
The <comments> element's optional "type" attribute
The <pubDate> element's optional "type" attribute
The <ttl> element's optional "span" attribute
Looks like good news for bloggers and God knows what for stuff like GeoRSS or BlogTorrents
I've been waiting for that a long time now
Quidquid latine dictum sit, altum videtur
... plans are afoot for Microsoft to co-opt RSS and rename it "web feeds".
Huh?
They're choosing "web feeds" as the user interface text to mean RSS, Atom et al. The article says nothing about them modifying the feed schema.
Five? There are nine different versions of RSS. Not counting this new RSS 3.0, or the previous RSS 3.0 that has been around for years.
Bogtha Bogtha Bogtha
The RSS 3 Requirements Page: General RSS 3 Requirements:
6. The Standard should strive to remain as backwards compatible as possible with the RSS 2.0 standard
If you don't fail at least 90 percent of the time, you're not aiming high enough. (Alan Kay)
It's explained in the terminology page and the terminology section in the spec. In short - normative equals "for implementation", "non-normative" means "of recommendation or suggestion nature" and "informative" means, well, "for further details only".
Yrs John XXX
So I basically have to link this from here, maybe people will learn eventually.
7
This whole mess is just not funny anymore.
http://www.kuro5hin.org/story/2002/11/10/122820/9
You're looking at the wrong specification. RSS is transmitted over HTTP. HTTP provides authentication.
The thing preventing this is that common feed readers do not support enough of HTTP's features to be able to supply a username and password in a standard HTTP way.
Like gzip compression, above, this isn't a problem that needs to be solved on a format-by-format basis. The transfer protocol handles it for all formats.
Bogtha Bogtha Bogtha
1. The term "normative" describes sections (or comments/notes) which describes behaviors and feature to which implementors must adhere
2. The term "informative" describes sections (or comments/notes) which give certain details for further knowledge and do not describe behavior to which implementors must adhere
3. The term "non-normative" describes sections (or comments/notes) which describe behaviors or features of recommendation nature or changing nature
4. The words "must", "must not", "required", "shall", "shall not", "should", "should not", "recommended", "may", "may not" and "optional" are to be interpreted as described in RFC 2119
"A language that doesn't affect the way you think about programming, is not worth knowing" - Alan Perlis
It can read the whole document and notice
that occurs alot and replace it with one bit.
Uh, no it can't. bzip2 uses
- run length encoding
- move-to-front buffering
- the Burrows-Wheeler block transform (sorts the data in a reversible way; the output is usually more compressible)
- run length encoding (again)
- huffman encoding
There's no searching for repeated sequences beyond the BW transform. You're not going to replace a common sequence with a single bit.