As suggested by someone else in this newsgroup, why not have a set of methods that localize the conversion of file names, mis-formed URLs etc to well-formed URIs. All the 'laxity' or 'complexity' can be hidden in these methods.
> What do people think? Is it too much to ask of applications to provide > URI's rather than platform-dependent filenames? Do people think increasing > the complexity of our stream-processing code is worth whatever convenience > is gained? Is it acceptable that, by allowing filenames, we're violating > the letter of many specifications and probably not aiding the cause of > platform/parser independence, since we're being more permissive than other > products are likely to be? The parser will then accept *only* well-formed URIs, it is the responsibility of the programmer to use one of the above mentioned methods to convert filenames etc to well-formed URIs - *before* calling any parser methods. Regards... Milind Gadre ecPlatforms, Inc 901 Mariner's Island Blvd, Suite 565 San Mateo, CA 94404 C: 510-919-0596 F: 815-352-0779 [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
