- From: Innovimax W3C <innovimax+w3c@gmail.com>
- Date: Thu, 2 Feb 2012 11:09:04 +0100
- To: Norman Walsh <ndw@nwalsh.com>
- Cc: public-xml-processing-model-wg@w3.org
I have certainly and the change I'd like to propose are not so huge On the top of my head, here are two types of modifications : 1) One is to remove the necessity to use p:try/p:catch to capture validation errors (because p:try/p:catch mandates buffering) 2) Another is to allow p:for-each to generate the result of each step in an unordered way (with a simple attribute ordered="true|false", the default being true) Mohamed On Wed, Feb 1, 2012 at 7:15 PM, Norman Walsh <ndw@nwalsh.com> wrote: > Innovimax W3C <innovimax+w3c@gmail.com> writes: >> I would also add, improving relationship with Streaming and Parallel processing > > If you look back at the minutes of the last couple of meetings, you'll > see that we have at least a rough consensus to focus v.next efforts on > simple, low-hanging fruit items that will improve usability. > > I'm not sure that language design changes to better support streaming > or parallel processing fit into that plan. But if you have specific > proposals... > > Be seeing you, > norm > > -- > Norman Walsh > Lead Engineer > MarkLogic Corporation > Phone: +1 413 624 6676 > www.marklogic.com -- Innovimax SARL Consulting, Training & XML Development 9, impasse des Orteaux 75020 Paris Tel : +33 9 52 475787 Fax : +33 1 4356 1746 http://www.innovimax.fr RCS Paris 488.018.631 SARL au capital de 10.000 €
Received on Thursday, 2 February 2012 10:09:41 UTC