Re: RSS Profile Character Data Advice

"James Holderness" <[email protected]>
Newsgroups gmane.network.syndication.rss.support
Message-ID <BAY141-DAV7D722FEB3F5A238EEFBD0BE120__45689.6265889101$1182246658$gmane$org@phx.gbl>
Bill Kearney wrote:
> If people want fancy formatting, get a web page.  These feeds are not ones
> you're looking for... (waves hand...)

This has got nothing to do with fancy formatting. The issue we're trying to 
resolve here is how to let people include ampersands and angle brackets in 
their titles.

>> tell people they should encode <, >
>> and & with hexadecimal character references
>
> Why?  XML itself allows for the five references amp, apos, quot, lt and 
> gt.
> To numerically encode them isn't ever necessary.  If a reader can't handle
> these basic five, well, then it has much bigger problems.

The reason for that suggestion was to ensure that our recommended encoding 
format would work in Bloglines. It actually relies on the *existence* of a 
bug in Bloglines rather than avoiding a bug. Since Bloglines is still one of 
the most popular aggregators today, I believe it's important to tell people 
how to get their feeds to work with it.

>> and simply tell
>> publishers that other encodings are discouraged because they are
>> unlikely to work properly in most aggregators.
>
> It would seem you're mixing terms here.  Plenty of character encodings 
> work
> quite well for RSS, thank you.

I guess that is a little confusing - "escaping" might be a better term to 
use. The HTML spec use the term "encode" for all sorts of things. I believe 
the XML spec consistently uses the term "escape" when talking about entity 
reference conversions.

> I'm not sure using a bad tool as a reference is a good idea.  God help you
> when the other limitations of a tool start being offered as excuses to
> further bastardize a spec.  Just because the tools suck doesn't mean the
> spec has to bend to tyranny.

We're not writing a spec here. The reason for the profile (IMO) is to help 
people get their feeds to work with the popular RSS implementations that 
exist today. We aren't bending the spec to deal with sucky tools, but we are 
telling people in what way those tools suck. That way they at least have the 
knowledge to bend their feeds to work with those tools, if they so choose.

Regards
James



 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/rss-public/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/rss-public/join
    (Yahoo! ID required)

<*> To change settings via email:
    mailto:[email protected] 
    mailto:[email protected]

<*> To unsubscribe from this group, send an email to:
    [email protected]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.