- From: James Fuller <jim@webcomposite.com>
- Date: Thu, 9 Apr 2015 21:38:21 +0200
- To: Norman Walsh <ndw@nwalsh.com>
- Cc: XProc WG <public-xml-processing-model-wg@w3.org>
FWIW I think the problem p:filter was addressing is an important one ... but yes there is overlap with @select attribute and it was unclear to me if the proposal addressed an 80% type use case. I wonder if there anything we could do to reduce complexity within the @select itself ? J On 9 April 2015 at 20:30, Norman Walsh <ndw@nwalsh.com> wrote: > Hello world, > > In the course of investigating the consequences of our decisions at > the 1 Apr 2015 telcon wrt the p:filter element, I've come to the > conclusion that we don't need it. > > The places where you could do a filter operation already have a select > attribute. You can use that to do both. You might, perhaps, have to > write a fairly hairy select expression but so be it. > > We can revisit if we encounter common cases where it's a problem. > > Be seeing you, > norm > > -- > Norman Walsh > Lead Engineer > MarkLogic Corporation > Phone: +1 512 761 6676 > www.marklogic.com
Received on Thursday, 9 April 2015 19:38:50 UTC