<scribe> Scribe: Henry S. Thompson

<scribe> ScribeNick: ht

Hey Paul -- good holiday?

France?

<PGrosso> yes and yes

<PGrosso> [weather could have been better, but the wine and food could not have been.]

Good good

Ah, good Morning Norm

<Norm> Morning ht

<Norm> Alas, I'm not going to be able to call in

<Norm> Welcome home, PGrosso

<Norm> Make what progress you can. It might be worth talking about the PSVI stuff in the editor's draft of a few days ago, if anyone has read it

Not me, alas -- I am neck-deep in boxes, recycling bags, burn bags, etc.

We're moving office, and I've been in this building for about 15 years

<Norm> Ah.

<Norm> No worries

Apologies: Rui Lopes, Richard Tobin, Norm Walsh

Last week's minutes: http://www.w3.org/XML/XProc/2008/06/05-minutes.html

Accepted.

Next meeting: 19 June 2008, regrets from Andrew only ones known as yet

<alexmilowski> grrr... phone lost its mind...

MoZ, are you planning on dialing in?

<alexmilowski> time for a new office phone...

http://lists.w3.org/Archives/Public/public-xml-processing-model-wg/2008May/0040.html

MZ: Features suggested by Alessandro's suggestions based on Haskell:
... p:is-empty is covered by limit attr on p:count
... p:pack has been added
... split a sequence up until the first match of some pattern

http://www.w3.org/TR/xproc/#c.split-sequence

HT: Sounds straightforward
... anyone see any difficulties?

MZ: This gives us functionality for dealing with sequences which it's difficult, if not impossible, to get any other way

HT: Better name than 'stop-test-after-first-false' ?
... We get the initial subsequence which matches

AM: I get it

HT: How about 'initial-only'

AM: It's going to be opaque, people will have to look it up to understand it

RESOLUTION: Add an 'initial-only' attribute to p:split-sequence, a boolean

<scribe> ACTION: Alex Milowski to add an 'initial-only' attribute to p:split-sequence, a boolean [recorded in http://www.w3.org/2008/06/12-xproc-minutes.html#action01]

Serialization question

http://lists.w3.org/Archives/Public/public-xml-processing-model-wg/2008Jun/0008.html

AM: The origin of the impl-defined for the defaults for unspec'd serialization options comes from the QT Serialization spec.

MZ: That's not what I was concerned about, rather that I read the spec. in 5.6 as allowing _other_ attributes which are not specified in the spec.

HT: Oops, this section needs to be cross-referenced from 7.3

AM, MZ: Discuss what 'unspecified' means here

HT: I think that the intent was that 'unspecified' refers to _options_ which are missing for a particular step

AM: Right

MZ: Yes

HT: But, alas, the Serialization step does not say that defaults are impl-defined
... Propose to delete the "default value" sentence from 5.6

RESOLUTION: delete the "default value" sentence from 5.6

HT: Propose to amend the reference to 7.3 in 5.6 to read as follows:

The semantics and defaulting behaviour of the attributes on a p:serialization are as described for the corresponding options Section 7.3, �Serialization Options�.

<alexmilowski> phone lost its mind

<alexmilowski> ...again

RESOLUTION: Amend the reference to 7.3 in 5.6 to read as follows: "The semantics and defaulting behaviour of the attributes on a p:serialization are as described for the corresponding options in Section 7.3, �Serialization Options�."

<scribe> ACTION: Alex Milowski to draft a Note to add to 7.3 explaining that we don't give simple defaults, behaviour wrt missing options is complex and you have to read [Serialization] to find out. [recorded in http://www.w3.org/2008/06/12-xproc-minutes.html#action02]

<scribe> ACTION: Alex Milowski to add an error to 7.3 to cover all other parameter-related Serialization errors [recorded in http://www.w3.org/2008/06/12-xproc-minutes.html#action03]

HT: I am opposed, it's a new feature, and it can be easily fitted into the existing spec. as an impl-defined serialization method

AM: I'm opposed also, we should wait for Serialization spec. to provide for this, so we don't find ourselves isolated when they do

[Oops, Scribe needs to add, before HT above, MZ: My email also proposes adding support for c14n to serialisation]

MZ: So, do you mean there would have to be two new methods, x:c14n-with-comments and x:c14n-without-comments

HT: No, I think you would have new options to go with impl-defined x:c14n method

AM: What happens when Serialization _does_ add support for c14n -- do those attributes/options move from prefixed to unprefixed?

HT: MSM would say "we should say 'Serialization or its successors'"

AM: The problem is that it's not hard to allow for new serialization _options_, when there's a new Serialization spec., but adding _attributes_ in no namespace to p:serialization is not allowed
... Maybe we should provide for this ahead of time, with a specific namespace.

HT: We're out of time, AM please start an email thread on your idea, we'll pick it up next week

Adjourned

This is scribe.perl Revision: 1.133  of Date: 2008/01/18 18:48:51  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Succeeded: s/no regrets/regrets from Andrew only ones/
Succeeded: s/Richard/Rui Lopes, Richard/
Succeeded: s/and 7.3 need to be cross-referenced/needs to be cross-referenced from 7.3/
Succeeded: s/5.3/5.6/
Succeeded: s/5.3/5.6/
Succeeded: s/as described in//
Found Scribe: Henry S. Thompson
Found ScribeNick: ht
Default Present: Ht, PGrosso, Vojtech, alexmilowski, MoZ
Present: Paul Henry Vojtech
Agenda: http://www.w3.org/XML/XProc/2008/06/12-agenda.html
Got date from IRC log name: 12 Jun 2008
Guessing minutes URL: http://www.w3.org/2008/06/12-xproc-minutes.html
People with action items: alex milowski