Ned Konz wrote:

...a lot of great analysis (as always :-)...


Let me suggest something going into another direction: simplicity.

if you want to have portable filenames, you have to use portable 
filenames (modulo some character encoding/escaping magic).

If you want to be compatible to MacOS 8 or such, you are restricted to 
31 chars (IRC).

IMO everything else leads to a hugely complicated framework that will 
still not solve all cases.

And again, IMO, filenames within the URI spec should be flexible enough 
to do about everything.
And URIs would give a Universal Resource Identification to handle local 
and remote streams transparently.

I've rewritten my URI implementation inspired by Craig's and Brenda's(?) 
implementation and am adapting it to the upcoming m17n changes. The 
changes mainly involve more compliance with the spec and character 
encoding/escaping mechanisms.

Just MTC (current exchange rate 1.19 ;-)

Michael