[
Lists Home |
Date Index |
Thread Index
]
>>Surely both 1 & 2 are caused by misinterpretation of the specs, not by
>>anything being fundamentally wrong (machine-wise) with treating URL-syntax
>>strings as URIs. 3 may add to confusion, but isn't such a danger
>in itself -
>>there's plenty of other strange stuff on the web.
>
>[beating myself bloody for jumping into a thread a swore I would
>ignore :~) ]
>
>People don't RTFM, much less the F****** Spec. Architectures that don't
>support the "principle of least surprise" are going to be fragile,
>no matter how logical and consistent their other principles might be.
>
>Confusion IS a danger in itself, as various spacecraft lost for want of a
>comma, or misunderstandings of units of measurement, can attest.
I agree with you 100%. But is the path of least surprise to invalidate a
very large quantity of material that's out there, and to introduce (and
explain) a significant revision? Or to explain the status quo a little
better?
A soft deprecation would I suppose be the middle path.
|