- From: Florent Georges <fgeorges@fgeorges.org>
- Date: Thu, 4 Jul 2013 10:04:12 +0200
- To: Michael Kay <mike@saxonica.com>
- Cc: Christian Grün <christian.gruen@gmail.com>, Jirka Kosek <jirka@kosek.cz>, EXPath CG <public-expath@w3.org>
On 3 July 2013 22:41, Michael Kay wrote: > On 3 Jul 2013, at 21:23, Christian Grün wrote: >>> I thought that we can formally use untypedAtomic in signature, but raise >>> dynamic error when passed parameter is not hexBinary or base64Binary >>> value. >> This would also be my favorite approach (as I believe I have mentioned >> in the thread from March). > I'm sure you mean xs:anyAtomicType rather than xs:untypedAtomic. > I think this is probably the best we'll manage. Just to be sure... So if an untyped atomic or an untyped node is passed, it is an error unless the user explicitly convert it to, say, xs:base64Binary? Regards, -- Florent Georges http://fgeorges.org/ http://h2oconsulting.be/
Received on Thursday, 4 July 2013 08:04:59 UTC