00:00:03 <ht> RRSAgent, make logs world-visible
16:16:53 <RRSAgent> RRSAgent has joined #xproc
16:16:53 <RRSAgent> logging to http://www.w3.org/2011/11/01-xproc-irc
16:16:58 <PGrosso> PGrosso has joined #xproc
16:17:03 <ht> Yesterday's logs are now visible at http://www.w3.org/2011/10/31-xproc-irc.html
16:17:21 <Cornelia> Cornelia has joined #xproc
16:23:49 <jfuller> Jim will be scribe
16:23:53 <alexmilowski> alexmilowski has joined #xproc
16:24:19 <jfuller> Henry overviews the scribe process to Jim
16:25:33 <jfuller> Cornelia 'were all those requirements met ?' 
16:25:34 <jfuller> Henry responded and Jim said perhaps we need to dig into the reasons why
16:26:44 <jfuller> as it relates to original use cases
16:26:45 <jfuller> Henry ' Most of the use cases pulled from common pipeline experience, pretty concrete and simple'
16:26:46 <jfuller> Cornelia asked about v.next and should we do v.next, based on what
16:26:53 <jfuller> Mohammed responds 'one of them was GRDDL and was not fulfilled'
16:27:06 <PGrosso> s/Mohammed/Mohamed/
16:28:02 <jfuller> Everyone having a chat about use cases ... Cornelia 'speak to Vojtech about xproc in the browser'
16:29:05 <jfuller> Alex demonstrating that current use cases maybe defined too broadly ...
16:31:33 <jfuller> Henry saying 'its important to the browser vendors to have a live unified API, much wider range of behaviors more tightly defined' ... xproc might be able to take advantage of this
16:34:20 <jfuller> Henry 'Most of the browsers you can register a handler and link up with a media type hook', can we use as an extensibility point for xproc
16:34:40 <PGrosso> The V1 requirements doc is at http://www.w3.org/TR/xproc-requirements/
16:36:49 <ht> RESOLUTION: Those present agree that we should request rechartering to do a Vnext, subject to Norm's agreement
16:37:44 <jfuller> Paul 'should we go through v1 requirements doc ?'
16:37:51 <jfuller> Paul summarising 'the group here is interested in v.next, perhaps we should create a requirements doc for v.next ... start with v1 and capture the delta'
16:37:58 <jfuller> Henry clarifies 'we should be collecting candidate requirements for v.next'
16:39:32 <jfuller> Henry highlights that v.next may have another dimension in terms of dealing with a broader set of data types (serialized xml)
16:40:55 <alexmilowski> http://www.w3.org/TR/xproc-requirements/#use-case-rw-non-xml
16:41:06 <alexmilowski> That's the read/write non-XML use case.
16:41:08 <jfuller> Mohamed says we have p:data, Henry reminds us if this is not enough
16:41:30 <PGrosso> s/if/that/
16:42:21 <ht> AM: General topics:
16:42:40 <ht> ... 1) What flows: XDM more generally, text, JSON
16:42:44 <ht> ... 2) Usability
16:43:06 <ht> ... 3) New steps and control primitives
16:43:44 <ht> ... 4) Storage
16:43:59 <MoZ> MoZ has joined #xproc
16:44:03 <ht> JF: What are the major sources of cognitive dissonance
16:45:41 <jfuller> Henry 'the problems at the margins were known'
16:47:02 <jfuller> Henry 'maybe we put up a wiki for dumping thoughts for v.next use cases'
16:47:43 <ht> s/use cases/use cases, pain points, good experiences/