http:urlEncoded, http:urlReplacement issues
- View SourceThe spec does not say much about how values of abstract types are to
be stringified when the type is something else xsd:string. Should it
just be stringified as XML (and then URLencoded)?
If it is xsd:string, then it is unclear how chars outside the ASCII
range are to be handled. UTLencoded UTF8 perhaps?
Is it legal for the part referenced to reference a schema element
instead of a type?
For http:urlReplacement it not not clear what URL escaping should be
done on the replacement text.
- Is an embedded "?" to be expanded into "?" or "%3f".
- Is an embedded "%3f" to be expanded into "%3f" or "%253f"
For http:urlReplacement it is not clear what should happen for "search
patterns" where there is no correspondingly named part in the message.