Hi Mike,

>  1. str:encode-uri() changes as follows:
>     - intended usage: cleaning up sloppily assembled URIs/IRIs
>     - reference RFC 2396, RFC 2732
>     - does not escape reserved or unreserved characters
>     - optional second argument: encoding used as basis for escaping
>     - unknown encoding = return empty string
>     - empty string for second argument = non-ASCII characters not escaped
>     - unencodable characters escaped as %3F (question mark)

Can you describe the use cases for having control over the encoding
that gets used rather than just using UTF-8? I ask partly because the
current draft of xf:escape-uri() in XPath 2.0 [1] doesn't give that
level of control, and I'm wondering whether it's something that it
should support. Also, it seems to be adding a fair amount of
complexity to the definition and feels pretty fragile to me (since
there's no way of saying what encoding's been used to escape a
particular URI). Can you go into your requirement for it?

Thanks,

Jeni

[1] http://www.w3.org/TR/xquery-operators/#func-escape-uri

---
Jeni Tennison
http://www.jenitennison.com/

_______________________________________________
exslt mailing list
list@[...].org
http://www.exslt.org/list