Re: RSS Profile Character Data Advice

rcade wrote:
> I'm not sure I like the new sections we've added here, on several
> grounds.

I've been thinking about this some more and I like Randy's compromise 
suggestion from a little while ago:

>I think we have room for agreement then. Let's say in the profile
> that some vendors incorrectly treat elements other than
> item/description as html (double encoded), but that it's actually
> text (single encoded).

However, I think it's important that the examples we include should actually 
work in most aggregators. The "nice <gorillia>" and "the &amp; entity" 
examples definitely have to go - "A<B" should probably go too. Including 
those as examples of how people should escape when we know they won't work 
in most aggregators is misleading.

> simply tell
> publishers that other encodings are discouraged because they are
> unlikely to work properly in most aggregators.

That wouldn't be true though. We can tell publishers that other forms of 
encoding/escaping are discouraged because they won't work in IE, or because 
the spec doesn't explicitly allow HTML in titles. We can't say that they 
won't work in most aggregators when we know that they will (some of them). 
If we want people to find this profile useful we shouldn't lie to them.

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/