RE: OT: XML-RPC [was: site-wide metadata [was: RFC: myPublicFeeds.opml]]

> > Sure, like the myopic limitations of XML-RPC?  Replete with
> it's arrogance of
> > being anglo-centric?
>
> Bill, you're out of date here.  XML-RPC started off only understanding
> Latin-1 but any decent implementation ('decent' == 'built on a working
> XML parser that understands character encodings') looks at the
> encoding given in the <?xml?> tag and works off that.
>
> An app running on my server receives blog posts over XML-RPC and it
> was successfully rendering them in UTF-8 last time I looked ...

Surely that means the app had to work around the spec, hardly a stunning
endorsement. However, I believe the  XML-RPC spec is now fixed in this
regard, after very few years - all it took was the hint that Atom might not
use it.

A little more on topic : I note that Dave's sample myPublicFeeds.opml file
[1] has <opml version="1.1">, yet there doesn't appear to be an OPML 1.1
spec. However it was "coming soon" in 2001 [2].

Off topic again : 2001 was also the year RFC 2822 obsoleted RFC 822, the
date format still used in RSS 2.0, which was rebranded and had its control
handed to the "advisory board" 3 months ago. The spelling of propogate in
that spec has since been changed to propagate [3]. Eee, the winds of
change...

Cheers,
Danny.

[1] http://blogs.law.harvard.edu/myPublicFeeds.opml

[2] http://www.opml.org/discuss/msgReader$11?mode=day

[3] http://blogs.law.harvard.edu/tech/rssChangeNotes


 

Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/