While the current limitations of existing readers is important to
consider, it's also important to note that the standard supports
capabilities that go well beyond what those current readers have chosen
to implement, especially given that most of those readers began life as
RSS readers.
- James
James Holderness wrote:
Aristotle Pagaltzis wrote:
Besides the content model, there is also the fact that RSS has no
summary/content dichotomy, which allows Atom to transport non-
human-readable data (as the content) along with a human-readable
alternative form (in the summary).
That sounds great in theory, but in practice you're usually way better
off with something like this:
<content type="html">
<img src="boat.jpg" alt="picture of a boat" />
</content>
Than you are with something like this:
<summary>picture of a boat</summary>
<content type="image/jpeg" src="boat.jpg"/>
That doesn't apply to all forms of content of course, but if there's an
accessible way to represent your data in HTML, then an HTML content
element is probably the most interoperable way to syndicate it.
Furthermore, several RSS elements, such as title, may not contain
markup per the spec, and therefore cannot contain such things as
ruby annotations.
Out of curiosity, do you know of any Atom feed readers that support ruby
annotations in titles?
Regards
James
