W3C

- DRAFT -

XML Processing Model WG

Meeting 270, 29 Apr 2015

Agenda

See also: IRC log

Attendees

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

Contents


Accept this agenda?

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

Accepted.

Accept minutes from the previous meetings?

-> http://www.w3.org/XML/XProc/2015/04/01-minutes

-> http://www.w3.org/XML/XProc/2015/04/08-minutes

Accepted.

Next meeting

Any regrets for 6 May?

None heard.

Review of open action items

<scribe> No progress reported

TPAC

Norm, Alex are maybes. No one else appears able to go.

<jfuller> yes, its unlikely I could swing it

<jfuller> xmllondon/Edinburgh has used up that slot

Proposal for a p:sort step

-> https://github.com/xproc/extensions/blob/master/steps/sort.md

Norm attempts to summarize.

<ht> +1

<jfuller> +1

<jfuller> https://lists.w3.org/Archives/Public/public-xml-processing-model-wg/2010Nov/0050.html

<ht> I keep being surprised it's not there already

<ht> There must be a reason why not?

Norm: Ok, I hear approval and no objections. We'll stick this in the steps book.

<scribe> ACTION: A-270-01 Norm to move it into the steps document [recorded in http://www.w3.org/2015/04/29-xproc-minutes.html#action01]

Proposal for importing functions

-> https://github.com/xproc/extensions/blob/master/steps/sort.md

Norm attempts once again to summarize

<jfuller> https://github.com/xproc/specification/issues/49

<ht> And where can you use them?

<jfuller> saxon-ee though right ?

<Norm> yes, saxon-ee only in my impl.

Norm: You can use them in the XProc XPath Context (but not the XProc Step XPath context). So on p:with-option but not inside a stylesheet.

<ht> Cool

<jfuller> why not add attribs to existing p:import instead of a whole new p:import-function element

Norm: I suppose we could.

<jfuller> happier for me

Norm: I guess we could add a type attribute (and others) to p:import

Alex: We have a media type?

Norm: Yes, appendix I

Alex: So we'd default to that?

Norm: Yes.

Alex: And namespace is optional and an error for XProc imports?

Norm: Yep.

Alex: Error or ignored?

Norm: Error, I think, it's resolved statically and if you've used it incorrectly, you're probably confused.

<jfuller> +1

Proposal: Ask the editor to incorporate this into the draft as an overload on p:import?

No objections heard

<jfuller> (apologies telcoms issues at the moment)

<scribe> ACTION: A-270-02 Norm to add function import to the language spec [recorded in http://www.w3.org/2015/04/29-xproc-minutes.html#action02]

Any other business?

Alex: Have we attempted to reconcile progress against the requirements document?

<jfuller> related - I am confident we can close https://github.com/xproc/specification/issues/158

<jfuller> (I think we get this with combo of depends-on and enhancements for logging)

Norm: Not yet
... roughly, we're using github issues to track things

Jim: I think we can close 158

Norm: You opened it, so if you want to close it, I won't object.

Jim: Yes, I think we can.

Adjourned.

Summary of Action Items

[NEW] ACTION: A-270-01 Norm to move it into the steps document [recorded in http://www.w3.org/2015/04/29-xproc-minutes.html#action01]
[NEW] ACTION: A-270-02 Norm to add function import to the language spec [recorded in http://www.w3.org/2015/04/29-xproc-minutes.html#action02]
 
[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.140 (CVS log)
$Date: 2015/04/29 14:43:44 $