Unification and syntax

One argument against unification that I have heard is that XSL uses many
URI-incompatible characters. I don't follow that argument.

Why must we encode URIs in our documents in the exact syntax that will be
sent across the wire? There is a well-defined encoding algorithm:
computers can handle it instead of computers. It seems to me that I should
be able to make URIs that include any character that can be represented in
the encoding. In traversing the URI, the *software* can do the encoding
before fetching the resource. Maybe I'm missing something.

-- 
 Paul Prescod  - ISOGEN Consulting Engineer speaking for only himself
 http://itrc.uwaterloo.ca/~papresco

By lumping computers and televisions together, as if they exerted a 
single malign influence, pessimists have tried to argue that the 
electronic revolution spells the end of the sort of literate culture 
that began with Gutenberg?s press. On several counts, that now seems 
the reverse of the truth.

http://www.economist.com/editorial/freeforall/19-12-98/index_xm0015.html


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list