Re: Unwrapping urn:public:...

[dcpleland@ftnetwork.com]

John Cowan wrote:

>It%27s%20visually%20very%20cluttered,%20and%20spaces%20are%20extremely%20common.

Not in the sorts of examples that have been shown in the discussion, to wit:

"-//Acme//DTD Book//EN" 

Sure, you can overstate anything.

What has not been stated is that we are now proposing to rewrite the internet convention for representing a white space, and I think that's beyond the scope of this TC.

Regards,
David Leland

************************************************************
jcowan@reutershealth.com wrote on 5/8/01 4:37:55 PM
************************************************************
dcpleland@ftnetwork.com wrote:

> Norm Walsh wrote;
> 
>> I think going the last step and allowing
> 
> 
>   -//* to match "urn:publicid:-:*"
> 
>> adding unnecessary confusion for users and burden for implementors.
> 
> 
> I have been thinking this all along.

Hmm, okay.  I'm not used to thinking of "match" as irreflexive, but in
this case it may make sense for it to be.

> I cannot truly understand why we have reinvented the nomenclature for
> the white space in the url either.  Is not '%20' good enough?

It%27s%20visually%20very%20cluttered,%20and%20spaces%20are%20extremely%20common.


-- 
There is / one art             || John Cowan <jcowan@reutershealth.com>
no more / no less              || http://www.reutershealth.com
to do / all things             || http://www.ccil.org/~cowan
with art- / lessness           \\ -- Piet Hein


___________________________________________________________________________________________________
Get your free e-mail account with *unlimited* storage at  http://www.ftnetwork.com

Visit the web site of the Financial Times at  http://www.ft.com