- From: Norman Walsh <ndw@nwalsh.com>
- Date: Thu, 11 Feb 2010 11:48:50 -0500
- To: public-xml-processing-model-wg@w3.org
- Message-ID: <m28wazbtvx.fsf@nwalsh.com>
See http://www.w3.org/XML/XProc/2010/02/11-minutes
[1]W3C
- DRAFT -
XML Processing Model WG
Meeting 167, 11 Feb 2010
[2]Agenda
See also: [3]IRC log
Attendees
Present
Norm, Alex, Mohamed, Vojtech, Henry
Regrets
Paul
Chair
Norm
Scribe
Norm
Contents
* [4]Topics
1. [5]Accept this agenda?
2. [6]Accept minutes from the previous meeting?
3. [7]Next meeting: telcon, 18 Feb 2010
4. [8]LC003: XSLT match pattern
5. [9]010 Scoping of options and variables
6. [10]013: multiple inputs in test expression
7. [11]016: pipelines with infinite recursion
8. [12]Change the type of prefix value to NCName
9. [13]More string changes
10. [14]Any other business?
* [15]Summary of Action Items
--------------------------------------------------------------------------
Accept this agenda?
-> [16]http://www.w3.org/XML/XProc/2010/02/11-agenda
Accepted.
Accept minutes from the previous meeting?
-> [17]http://www.w3.org/XML/XProc/2010/01/21-minutes
Accepted.
Next meeting: telcon, 18 Feb 2010
Mohamed gives regrets for 18 Feb
LC003: XSLT match pattern
Vojtech: We discussed this.
Norm: Ok, I'll dig back further to see what I can find.
<MoZ> Norm, w.r.t pattern see
[18]http://www.w3.org/XML/XProc/2010/01/07-minutes
<Vojtech> XSLT match pattern discussion:
[19]http://lists.w3.org/Archives/Public/public-xml-processing-model-wg/2010Jan/0007.html
010 Scoping of options and variables
Norm: I didn't understand, I guess.
Henry: Take option and variable names together and make them the same as
step names.
... There's no lexical shadowing, only dynamic shadowing.
Norm: Ok.
013: multiple inputs in test expression
Norm discusses his thoughts about inputs and collection()
Vojtech: I think we need to make it well defined behavior, or leave it as
it is
Alex: Is collection() in XPath 2.
Norm: yes.
Vojtech: What I would see as the right solution would be to allow multiple
documents appearing in the XPath context and we say we take the first one
as the context item. But you can use collection() to get to the others.
Norm: I think this has gone as far as it needs to.
Alex: The status quo is implementation defined.
Norm: Proposal: leave the status quo, do nothing.
Accepted.
016: pipelines with infinite recursion
Vojtech: I was just wondering, but Norm replied.
Norm: I think we say enough.
... Proposal: leave the status quo.
Accepted.
Norm: Test suite progress
... Has the schema test resolution quesiton been resolved?
Vojtech: It's valid-xsd-004 and 011. They're the same and one is expected
to succeed and one is expected to fail.
... One relies on the default value for use-location-hints and the other
sets it to false, which is the default.
Norm: Do we have another test that explicitly sets it to true?
... Yes, 008.
... I think we should change 004 so that it's expected to fail, just like
11.
Vojtech: Do we want to change the default on validate-with-xmlschema?
Norm: Henry, what does the world expect?
Henry: For XSV, they're true and true, respectively. For Saxon, I think
it's true and false, respectively.
... No, the default is false. That's probably why we did it the way we
did.
Norm: Proposal: leave the status quo and change the test.
Accepted.
Change the type of prefix value to NCName
Norm: Mohamed observes that we have options that are expected to contain
prefixes that are of type string. He suggests we change their types to
NCName.
... I have no objection.
Henry: I don't think that's a breaking change.
Proposal: Accept this change?
Accepted.
More string changes
Mohamed: There are at least two issues in p:label-elements
Some discussion of the questions. Type of label changed to
XPathExpression.
Any other business?
None heard.
Adjourned.
Summary of Action Items
[End of minutes]
--------------------------------------------------------------------------
Minutes formatted by David Booth's [20]scribe.perl version 1.135 ([21]CVS
log)
$Date: 2010/02/11 16:48:04 $
References
1. http://www.w3.org/
2. http://www.w3.org/XML/XProc/2010/01/21-agenda
3. http://www.w3.org/2010/02/11-xproc-irc
4. http://www.w3.org/XML/XProc/2010/02/11-minutes#agenda
5. http://www.w3.org/XML/XProc/2010/02/11-minutes#item01
6. http://www.w3.org/XML/XProc/2010/02/11-minutes#item02
7. http://www.w3.org/XML/XProc/2010/02/11-minutes#item03
8. http://www.w3.org/XML/XProc/2010/02/11-minutes#item04
9. http://www.w3.org/XML/XProc/2010/02/11-minutes#item05
10. http://www.w3.org/XML/XProc/2010/02/11-minutes#item06
11. http://www.w3.org/XML/XProc/2010/02/11-minutes#item07
12. http://www.w3.org/XML/XProc/2010/02/11-minutes#item08
13. http://www.w3.org/XML/XProc/2010/02/11-minutes#item09
14. http://www.w3.org/XML/XProc/2010/02/11-minutes#item10
15. http://www.w3.org/XML/XProc/2010/02/11-minutes#ActionSummary
16. http://www.w3.org/XML/XProc/2010/02/11-agenda
17. http://www.w3.org/XML/XProc/2010/01/21-minutes
18. http://www.w3.org/XML/XProc/2010/01/07-minutes
19. http://lists.w3.org/Archives/Public/public-xml-processing-model-wg/2010Jan/0007.html
20. http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm
21. http://dev.w3.org/cvsweb/2002/scribe/
Received on Thursday, 11 February 2010 16:49:27 UTC