- From: John Boyer <boyerj@ca.ibm.com>
- Date: Tue, 23 Mar 2010 14:35:17 -0700
- To: public-forms@w3.org
- Message-ID: <OF73C9AFC1.183C3ADD-ON882576EF.0075A31E-882576EF.007698FD@ca.ibm.com>
It may seem obvious that all XForms attributes of type xsd:anyURI should have a URL encoding applied to them, a la XLink 1.0 Section 5.4, before proceeding to URL resolution. But I think we don't come out and say it in places like Section 11.6 on the XForms submission resource and Section 3.3.2 for instance @src and @resource. This means we don't end up testing it. And it makes me wonder how many implementations don't do it. Can any implementers confirm whether or not they do this encoding? Can anyone comment on whether they think I am wrong about the obviousness of needing to do this encoding? I know it is pretty clear that we do urlencoded *parameters* just due to the serialization type name, but I am talking esp. about the domain name and path in the URL, not just the parameters. One way that this is going to hit us, post XForms 1.1, is in the attempt to scale up to IRIs. My understanding from the I18N group is that xsd:anyURI was meant to be "compatible" with IRIs. My current understanding of IRIs is that there is a similar encoding step. John M. Boyer, Ph.D. STSM, Lotus Forms Workplace, Portal and Collaboration Software IBM Victoria Software Lab E-Mail: boyerj@ca.ibm.com Blog: http://www.ibm.com/developerworks/blogs/page/JohnBoyer Blog RSS feed: http://www.ibm.com/developerworks/blogs/rss/JohnBoyer?flavor=rssdw
Received on Tuesday, 23 March 2010 21:35:57 UTC