- From: Norman Walsh <ndw@nwalsh.com>
- Date: Fri, 04 Dec 2009 09:51:02 -0500
- To: public-xml-processing-model-wg@w3.org
- Message-ID: <m2k4x294ix.fsf@nwalsh.com>
See http://www.w3.org/XML/XProc/2009/12/03-minutes
[1]W3C
- DRAFT -
XML Processing Model WG
Meeting 161, 03 Dec 2009
[2]Agenda
See also: [3]IRC log
Attendees
Present
Paul, Norm, Alex, Vojtech, Murray, Henry
Regrets
Mohamed
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, 17 Dec 2009
4. [8]CR issues
5. [9]174 formal qualification for things like p:xpath-context, etc.
6. [10]176 p:output and connections
7. [11]177 p:use-when on non-XProc elements
8. [12]178 exclude-inline-prefixes
9. [13]179 use-when and p:episode
10. [14]180 passing a boolean value as a with-param
11. [15]181 using tokens
12. [16]184 iteration position and size
13. [17]185 content-disposition and content-id
14. [18]186 encoding and charset
15. [19]190 Namespace attribute for steps that take wrappers
16. [20]191 Nodelists as value
17. [21]Recent editor's draft
18. [22]Last call plans
19. [23]Any other business?
* [24]Summary of Action Items
--------------------------------------------------------------------------
Accept this agenda?
-> [25]http://www.w3.org/XML/XProc/2009/12/03-agenda
Accepted.
Accept minutes from the previous meeting?
-> [26]http://www.w3.org/XML/XProc/2009/11/12-minutes
->
[27]http://lists.w3.org/Archives/Public/public-xml-processing-model-wg/2009Nov/0026.html
Accepted.
Next meeting: telcon, 17 Dec 2009
Henry and Norm gave regrets for 10 Dec; Paul is at risk; Murray possibly.
Let's cancel 10 Dec. See you all on 17 Dec.
CR issues
-> [28]http://www.w3.org/XML/XProc/2008/11/cr-comments/
174 formal qualification for things like p:xpath-context, etc.
Henry: This seems to me to be about the question of what is the error. The
answer is there's been a static error since day one.
... What is the error for p:banana in p:for-each
Norm: For ordinary behavior, I think the answer is clear. I think this is
about fowards-compatible behavior.
<ht> or my:zoolander in p:for-each
Vojtech: It's a static error because it's an unknown element or a dynamic
error if it's an unknown step.
Norm: It's a static error in the my:zoolander case because you have to
have imported a decl for it.
Henry: You have to use use-when.
Vojtech: With respect to instruction-avaialble, you can always use the
version.
Norm: You can check for an available step, but not an available new thing
like p:new-serialization.
Vojtech: That would be a new language feature.
Norm: Right, and I think we're willing to live with a little less
flexibility there.
Vojtech: Checking for p:new-serialization wouldn't be flexible enough, you
might want to check for an attribute for example.
Henry: Basically, you want to say "use-when this stylesheet will work" and
that's just not easy. You'll have to use version numbers for now.
... Version-available is all you get in V1 and that's going to have to be
enough.
<scribe> ACTION: Henry to follow-up with Vasil. [recorded in
[29]http://www.w3.org/2009/12/03-xproc-minutes.html#action01]
176 p:output and connections
<scribe> ACTION: Editor to consider whether it's possible to clarify the
definitions of atomic and compound steps. [recorded in
[30]http://www.w3.org/2009/12/03-xproc-minutes.html#action02]
177 p:use-when on non-XProc elements
Vojtech: There were two things. I think no action is necessary.
Norm: Perfect, I'll close that one.
178 exclude-inline-prefixes
This was discussed at the 12 November meeting. Decision was that no name
change was necessary.
Norm: I updated 5.12
Henry: I saw that and concluded that my action had been overtaken.
Vojtech: Yes.
Norm: Proposal: close as resolved
Accepted.
179 use-when and p:episode
Norm: Updated 3.9. Is everyone satisfied?
Henry: I'm still concerned about listing only what isn't possible. I had
listed the things that are available.
Vojtech: If you use use-when in a pipeline labeled version=1.0, then
step-available only sees the 1.0 steps, right?
Norm: Uh...
Vojtech: Which means that during pre-processing you must take version into
account.
Norm: Yes, I think that's right.
... I think the fact that you're in a 1.0 pipeline is something you must
know when you evaluate use-when expressions.
Vojtech: So a 1.0 pipeline with a 2.0 declare-step, if the declare-step
includes a use-when you have to use 2.0
Norm: Yes, that's probably worth mentioning.
<scribe> ACTION: Norm to clarify that version comes into play in use-when
[recorded in [31]http://www.w3.org/2009/12/03-xproc-minutes.html#action03]
180 passing a boolean value as a with-param
Henry: Why doesn't this just work?
Norm: Because the XPath 2 type system doesn't promote from xs:string to
anything automatically.
... I think this just a limitation in v1.0
Proposal: We just have to live with it.
Norm: Any objections?
Accepted.
181 using tokens
Norm: No new features at this point.
184 iteration position and size
Norm: I think the upshot is only viewport and for-each change the values
<scribe> ACTION: Editor to clarify [recorded in
[32]http://www.w3.org/2009/12/03-xproc-minutes.html#action04]
185 content-disposition and content-id
<scribe> ACTION: Alex to investigate and report back [recorded in
[33]http://www.w3.org/2009/12/03-xproc-minutes.html#action05]
186 encoding and charset
Vojtech: In making the request, if you say encoding=base64 with no
charset, then you just send the decoded byte sequence, right?
Alex: c:body has content-type but no charset
Norm: Right, I think Vojtech's argument to put it in the content type is
compelling.
... Yes, c:data on those steps should be consistent with unescape markup
190 Namespace attribute for steps that take wrappers
Henry: I'm happy with new-prefix.
Norm: I propose to add new-namespace and new-prefix (with appropriate
names) to all the steps that have wrapper element names as options.
... Any objections?
Accepted.
191 Nodelists as value
Norm: No new features.
... I think I should have filtered this one out.
Recent editor's draft
Henry: I'm happy with it.
Vojtech: I have one small thing regarding the XQuery step.
<alexmilowski> I'm happy with the most recent draft too.
Vojtech: I think in Santa Clara we concluded that for things like XQuery
or text input, we don't inherit any namespace bindings.
Norm: I'd have to review the minutes again.
Last call plans
Norm: We're out of time, I'll take it to email
Any other business?
None heard.
Adjourned.
Summary of Action Items
[NEW] ACTION: Alex to investigate and report back [recorded in
[34]http://www.w3.org/2009/12/03-xproc-minutes.html#action05]
[NEW] ACTION: Editor to clarify [recorded in
[35]http://www.w3.org/2009/12/03-xproc-minutes.html#action04]
[NEW] ACTION: Editor to consider whether it's possible to clarify the
definitions of atomic and compound steps. [recorded in
[36]http://www.w3.org/2009/12/03-xproc-minutes.html#action02]
[NEW] ACTION: Henry to follow-up with Vasil. [recorded in
[37]http://www.w3.org/2009/12/03-xproc-minutes.html#action01]
[NEW] ACTION: Norm to clarify that version comes into play in use-when
[recorded in [38]http://www.w3.org/2009/12/03-xproc-minutes.html#action03]
[End of minutes]
--------------------------------------------------------------------------
Minutes formatted by David Booth's [39]scribe.perl version 1.135 ([40]CVS
log)
$Date: 2009/12/04 14:50:08 $
References
1. http://www.w3.org/
2. http://www.w3.org/XML/XProc/2009/12/03-agenda
3. http://www.w3.org/2009/12/03-xproc-irc
4. http://www.w3.org/XML/XProc/2009/12/03-minutes#agenda
5. http://www.w3.org/XML/XProc/2009/12/03-minutes#item01
6. http://www.w3.org/XML/XProc/2009/12/03-minutes#item02
7. http://www.w3.org/XML/XProc/2009/12/03-minutes#item03
8. http://www.w3.org/XML/XProc/2009/12/03-minutes#item04
9. http://www.w3.org/XML/XProc/2009/12/03-minutes#item05
10. http://www.w3.org/XML/XProc/2009/12/03-minutes#item06
11. http://www.w3.org/XML/XProc/2009/12/03-minutes#item07
12. http://www.w3.org/XML/XProc/2009/12/03-minutes#item08
13. http://www.w3.org/XML/XProc/2009/12/03-minutes#item09
14. http://www.w3.org/XML/XProc/2009/12/03-minutes#item10
15. http://www.w3.org/XML/XProc/2009/12/03-minutes#item11
16. http://www.w3.org/XML/XProc/2009/12/03-minutes#item12
17. http://www.w3.org/XML/XProc/2009/12/03-minutes#item13
18. http://www.w3.org/XML/XProc/2009/12/03-minutes#item14
19. http://www.w3.org/XML/XProc/2009/12/03-minutes#item15
20. http://www.w3.org/XML/XProc/2009/12/03-minutes#item16
21. http://www.w3.org/XML/XProc/2009/12/03-minutes#item17
22. http://www.w3.org/XML/XProc/2009/12/03-minutes#item18
23. http://www.w3.org/XML/XProc/2009/12/03-minutes#item19
24. http://www.w3.org/XML/XProc/2009/12/03-minutes#ActionSummary
25. http://www.w3.org/XML/XProc/2009/12/03-agenda
26. http://www.w3.org/XML/XProc/2009/11/12-minutes
27. http://lists.w3.org/Archives/Public/public-xml-processing-model-wg/2009Nov/0026.html
28. http://www.w3.org/XML/XProc/2008/11/cr-comments/
29. http://www.w3.org/2009/12/03-xproc-minutes.html#action01
30. http://www.w3.org/2009/12/03-xproc-minutes.html#action02
31. http://www.w3.org/2009/12/03-xproc-minutes.html#action03
32. http://www.w3.org/2009/12/03-xproc-minutes.html#action04
33. http://www.w3.org/2009/12/03-xproc-minutes.html#action05
34. http://www.w3.org/2009/12/03-xproc-minutes.html#action05
35. http://www.w3.org/2009/12/03-xproc-minutes.html#action04
36. http://www.w3.org/2009/12/03-xproc-minutes.html#action02
37. http://www.w3.org/2009/12/03-xproc-minutes.html#action01
38. http://www.w3.org/2009/12/03-xproc-minutes.html#action03
39. http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm
40. http://dev.w3.org/cvsweb/2002/scribe/
Received on Friday, 4 December 2009 14:51:50 UTC