- From: Michael Kay <mike@saxonica.com>
- Date: Thu, 4 Jul 2013 15:27:54 +0100
- To: Florent Georges <fgeorges@fgeorges.org>
- Cc: Jirka Kosek <jirka@kosek.cz>, Christian Grün <christian.gruen@gmail.com>, EXPath CG <public-expath@w3.org>
> > That's one of the reasons why I like the solution with a new item > type, because we can define that any (direct) serialization or copy to > a tree is an error (like for function items) :-) > But it's difficult to know how to name such an item type. Users will want to use this type name in "as" attributes. Although the specs sort-of-allow new item types to be introduced (XSLT is clearer on this than XQuery), they don't require implementations to provide the facility, and they don't provide any standards for naming such types. So it doesn't feel portable enough for a cross-product library, especially one that people will want to implement on XQ 1.0 or XSLT 2.0 processors. How about having two different libraries one for hexB and one for b64B, having the same functions but in two different namespaces? Michael Kay Saxonica
Received on Thursday, 4 July 2013 14:28:18 UTC