Re: RFC: myPublicFeeds.opml

The majority of responses seems to indicate the fixed URL idea, on it's face, is
a bad one.  Thus forcing use of 8.3 naming conventions doesn't really matter at
all.  If it's a bad idea how it's named is irrelevant.  Not to mention the
arrogance of dictating that it be english-centric.  Isn't it bad enough already?
Granted, a URI or MIME type specifying the type is going to end up having the
same bias, it'll free the site authors to use URLs that are identifiable in
their native tongue.

<link rel='subscriptions' type='application/adx+xml'
href='http://example.com/blog/feeds.xml'/>
<link rel='subscriptions' type='text/opmll'
href='http://example.com.de/tagebuch/zufuhren.opml'/>
<link rel='subscriptions' type='application/rdf'
href='http://example.com.jp/供給.rdf'/>

Thus a site author is free to use pathnames that won't offend or otherwise
confuse their audience.  Why force the 4 billion people that don't speak english
to suffer using english wording for a URL their audience might see?

The link rel and type attributes are bad enough but internationalizing them
would, at this point, be going overboard.  There's simple, there's complex and
then there's just crazy.

Honestly, use of a fixed URL is needlessly biased and generally a harmful idea.
Can we not agree to abandon the idea?

-Bill Kearney
Syndic8.com

----- Original Message -----
From: "Dave Winer" <dave-rH/ioLL7x7RWk0Htik3J/[email protected]>


> It's been recommended that the file name be 8.3, meaning eight characters in
> the name, followed by a three-character extension on the theory that this
> would increase the number of places it could be deployed. Comments? Dave


 

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