- From: Norman Walsh <ndw@nwalsh.com>
- Date: Tue, 02 Sep 2014 12:05:16 -0500
- To: public-xml-processing-model-wg@w3.org
- Message-ID: <87a96ineb7.fsf@nwalsh.com>
See http://www.w3.org/XML/XProc/2014/08/27-minutes
[1]W3C
- DRAFT -
XML Processing Model WG
Meeting 249, 27 Aug 2014
[2]Agenda
See also: [3]IRC log
Attendees
Present
Norm, Loren, Alex, Henry
Regrets
Jim
Chair
Norm
Scribe
Norm
Contents
* [4]Topics
1. [5]Accept this agenda?
2. [6]Accept minutes from the previous meeting?
3. [7]Specification issues
4. [8]Test suite issues
5. [9]Any other business?
* [10]Summary of Action Items
--------------------------------------------------------------------------
Accept this agenda?
-> [11]http://www.w3.org/XML/XProc/2014/08/27-agenda
Accepted.
Accept minutes from the previous meeting?
-> [12]http://www.w3.org/XML/XProc/2014/08/20-minutes
Accepted.
Next meeting: 3 Sep 2014
<ht> Regrets for 3 Sept
Norm gives probable regrets for 10, 17, and possibly 24 Sep
Specification issues
-> [13]https://github.com/xproc/specification/issues
Norm describes the move to GitHub issues for the spec
Alex: Did you merge my XInclude stuff?
Norm: Yes, in the xproc20 branch.
... I want everyone to use pull requests to change the spec.
Test suite issues
-> [14]https://github.com/xproc/test-suite/issues
Norm describes the test-suite repo
-> [15]https://github.com/xproc/test-suite/pull/13
Norm describes his pull request.
->
[16]https://github.com/ndw/test-suite/commit/018adf51bb43edea7c00883818507bea6ddbbf6b
Alex: Alternatively, we could have multiple expected results and the test
passes if you match any one of them.
Norm: I agree, but that'd be a bigger change in the test suite.
Alex: I'm fine with this change, but we should consider multiple outputs
for the future
-> [17]https://github.com/xproc/test-suite/issues/15
Norm: I propose that we accept the change offered in
[18]https://github.com/xproc/test-suite/pull/13
[19]http://tests.xproc.org/tests/required/data-002.xml
Alex: How far are we going to go, are we going to try to produce tests
that test every conceivable variation.
Norm: We're going to go as far as we can.
Henry: I hear Norm saying "it would be a bug if our core processing didn't
accept quoted content type parameters", but that doesn't appear to be the
problem.
... Alex is suggesting we should normalize these things. If we find places
where there was a bug in somebody's step implementation then we should try
to make sure that we test that.
... But we can't go and look for all possible bugs.
... What I heard Alex say was that we should actually normalize this.
Alex: I think you misheard me. I think there is an open issue of how we
deal with this in general in our test suite for 2.0.
... I think we should consider this carefully so that we have a good test
suite without combinatorial issues.
... My question was "should we be trying to be that complete". Norm says
"best effort" and I think that's a fine answer.
Norm: I'm happy to have tests for all the cases we think of.
Alex: I've run into this with other test suites.
Norm: I think experience with the 1.0 test suite will improve the 2.0 test
suite.
... Coming back around to my question, does anyone object to the proposed
change to those two tests?
None heard. Accepted.
-> Requirement “2.3 Align with XPath 3.0 technlogies”
-> [20]https://github.com/xproc/specification/issues/30
Norm: I attempted to address part of the 2.3 requirement, removing XPath
1.0
-> [21]https://ndw.github.io/specification/langspec/remove-xpath-10/head/
Norm waffles on a bit about XPath versions...
Alex: How are we going to track the changes? For example, if I wanted to
write an upgrade tool, how would I know that two p: functions had been
removed.
Norm: I guess there should be a changelog.
Alex: It doesn't have to be in the document.
Any other business?
None heard.
Adjourned.
rrsangent, draft minutes
Summary of Action Items
[End of minutes]
--------------------------------------------------------------------------
Minutes formatted by David Booth's [22]scribe.perl version 1.138 ([23]CVS
log)
$Date: 2014-09-02 17:04:35 $
References
1. http://www.w3.org/
2. http://www.w3.org/XML/XProc/2014/08/27-agenda
3. http://www.w3.org/2014/08/27-xproc-irc
4. http://www.w3.org/XML/XProc/2014/08/27-minutes#agenda
5. http://www.w3.org/XML/XProc/2014/08/27-minutes#item01
6. http://www.w3.org/XML/XProc/2014/08/27-minutes#item02
7. http://www.w3.org/XML/XProc/2014/08/27-minutes#item03
8. http://www.w3.org/XML/XProc/2014/08/27-minutes#item04
9. http://www.w3.org/XML/XProc/2014/08/27-minutes#item05
10. http://www.w3.org/XML/XProc/2014/08/27-minutes#ActionSummary
11. http://www.w3.org/XML/XProc/2014/08/27-agenda
12. http://www.w3.org/XML/XProc/2014/08/20-minutes
13. https://github.com/xproc/specification/issues
14. https://github.com/xproc/test-suite/issues
15. https://github.com/xproc/test-suite/pull/13
16. https://github.com/ndw/test-suite/commit/018adf51bb43edea7c00883818507bea6ddbbf6b
17. https://github.com/xproc/test-suite/issues/15
18. https://github.com/xproc/test-suite/pull/13
19. http://tests.xproc.org/tests/required/data-002.xml
20. https://github.com/xproc/specification/issues/30
21. https://ndw.github.io/specification/langspec/remove-xpath-10/head/
22. http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm
23. http://dev.w3.org/cvsweb/2002/scribe/
Received on Tuesday, 2 September 2014 17:05:45 UTC