Use cases/requirements/chartering for
V.next

Henry: Unless I'm mistaken, Liam
will be contacting the chair about the rechartering.
... He'll tell us what he wants.
... I'm not disagreeing, that's part of the reason that we
started the wiki.

Norm: Ok, using the wiki is fine
by me.

Henry: We're still in an
expansive phase. No bar is required to make an entry in the
wiki. We're in a gathering phase.
... At some point the chair should declare we have enough and
start pruning.

Norm rambles a bit.

Alex: There were a couple of
themes: improving usability and looking at steps that should be
standardized.
... there's also an aspect of integration that we touched
one.

Henry: Another question at that
level, is "is this 1.1 or 2.0?"
... How much do we care about backward compatibility.
... How much is this fixing the problems we know about and how
much is it we know better and are going to start again
... One area is simplifying parameters. We might just get rid
of some things that no one has used.

Any other business?

Jim: I don't know if it was clear
from the minutes, but we did sit down for a while with the
XQuery WG. Henry, maybe it would be good to describe that
meeting.

Henry: Here's my spin: over the
last 6 months, I've had occasion to look at three or more XRX
implementations. They're all lousy pipeline languages. They all
would be much better if they were XProc. I think Liam's
question is, what would XProc need to do to be better at
choreographic between the web and XML databases.
... In particular choreographing XSLT and XQuery to build
"lower case 'w'" web services.
... This comes under the integration heading.

Jim: Did we get any requests over
email for things we have to go through?