- From: John Lumley <john@saxonica.com>
- Date: Mon, 05 Aug 2013 09:18:11 +0100
- To: EXPath <public-expath@w3.org>
- CC: Christian Grün <christian.gruen@gmail.com>, Florent Georges <fgeorges@fgeorges.org>
Received on Monday, 5 August 2013 08:18:34 UTC
On 02/08/2013 23:53, Christian Grün wrote: > – the name of the bin:subsequence() function may be irritating as it > returns no sequence, but zero or one xs:base64Binary item. Possible > alternative could be: bin:sub(), bin:range() or bin:split(). On 03/08/2013 15:42, Florent Georges wrote: > I agree. What about bin:slice()? I agree in retrospect that subsequence isn't the right term. What we're really after is a binary equivalent of fn:substring(), but of course it isn't a string. bin:split() and perhaps even bin:slice() have connotations of cutting into several parts (c.f. java String.split()), which is what this function doesn't do. bin:sub() may be just too short. bin:range() may be confused with something about identifying the 'range' of some data. bin:subsection() might be confused with some sort of implicit structuring. What about bin:subpart() ? John -- *John Lumley* MA PhD CEng FIEE john@saxonica.com <mailto:john@saxonica.com> on behalf of Saxonica Ltd
Received on Monday, 5 August 2013 08:18:34 UTC