W3C

- DRAFT -

XML Processing Model WG

Meeting 277, 09 Sep 2015

Agenda

See also: IRC log

Attendees

Present
Norm, Henry, Alex
Regrets
Jim
Chair
Norm
Scribe
Norm

Contents


Accept this agenda?

-> http://www.w3.org/XML/XProc/2015/09/09-agenda

Accepted.

Accept minutes from the previous meeting?

-> http://www.w3.org/XML/XProc/2015/09/02-minutes

Accepted.

Next meeting, 23 September 2015

Henry gives possible regrets

The latest “flowchart” branch (section 5.10, p:inline “flowchart”).

-> https://ndw.github.io/specification/langspec/flowchart/head/xproc20/

Henry: I think this looks better.
... What about the text/* story? Isn't that missing?

Norm: Right. Yes it is.
... Back to the editor it goes.

Some discussion of non-text/* media types that are in fact text.

Consensus: Maybe but we're not going to try to handle those.

Alex: What about application/json?

Norm: You have to mislabel that or encode it, I think.

More discussion leads to the conclusion that it's just characters.

scribe: You lose if it's not just a sequence of characters.

Henry: If it's an XML media type, we're done.
... If it's not XML, it must a single text node.
... anything else is an error.
... The characters in that text node are then available as the data in the specified content type.

The “variables” anywhere branch. (Completes ACTION A-273-01 on Norm.)

-> https://ndw.github.io/specification/langspec/variables/head/xproc20/

Henry: In 2.6, there's nothing that says where the scope ends.
... I think I want a link to "lexically scoped."
... I'd remove in-scope bindings from the environment alltogether. The environment is just the readable ports story.
... Remove (3) from the first list in 2.6.
... Maybe call it the 'port environment'. And then you don't say anything about variables and options in this section at all.

Norm muses about the boundary of nested p:declare-steps.

Henry: Something like p:pipeline/p:declare-step define a scope and inherit nothing.
... I would hope that In-scope variables in 2.7.1, could read "because V & O are lexically scoped, the in-scope variables are the union of the in-scope specified options and the in-scope variable bindings.
... I wonder if 2.11 needs to be Variables & Options and have subsections for each.

Norm: Ok, that's plenty to work on for a new draft.

Any other business?

Alex: We should try to work on getting a new public working draft out after Sapporo.

Norm: I think that makes sense.
... I'll try to get something ready to talk about in two weeks.

Summary of Action Items

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.140 (CVS log)
$Date: 2015/09/09 14:55:12 $