- From: Norman Walsh <ndw@nwalsh.com>
- Date: Thu, 26 Mar 2015 08:07:35 -0500
- To: public-xml-processing-model-wg@w3.org
- Message-ID: <87twx7di08.fsf@nwalsh.com>
See http://www.w3.org/XML/XProc/2015/03/25-minutes
[1]W3C
- DRAFT -
XML Processing Model WG
Meeting 267, 25 Mar 2015
[2]Agenda
See also: [3]IRC log
Attendees
Present
Norm, Alex, Jim
Regrets
Henry, Loren, Murray
Chair
Norm
Scribe
Norm
Contents
* [4]Topics
1. [5]Accept this agenda?
2. [6]Accept minutes from the previous meeting?
3. [7]Next meeting
4. [8]Review of open action items
5. [9]Close issue #43 without action
6. [10]Collector steps, issue 148
7. [11]Clarify p:load, issue #145; see proposed changes to
p:document and p:load.
8. [12]semantics of p:cast-content-type, issue #116
9. [13]Any other business?
* [14]Summary of Action Items
--------------------------------------------------------------------------
Accept this agenda?
-> [15]http://www.w3.org/XML/XProc/2015/03/25-agenda
Accepted.
Accept minutes from the previous meeting?
-> [16]http://www.w3.org/XML/XProc/2015/03/11-minutes
Accepted.
Next meeting
Proposed: 1 April 2015 does anyone have to give regrets?
No regrets heard. Possible regrets from Henry, I can't recall for sure.
Review of open action items
Jim: I spent some time on mine, but haven't got anything ready for review
yet.
No other progress reported.
Close issue #43 without action
-> Topic: Review of open action items
-> [17]https://github.com/xproc/specification/issues/43
Norm proposes that there's insufficient support.
Jim wonders about new users.
Norm notes that it isn't in XSLT
Jim: I'm not sure that the XSLT user is the only thing we should consider,
but I'm not sure this wins us very much.
Proposal: Close without action.
Any objections?
None heard.
Collector steps, issue 148
-> [18]https://github.com/xproc/specification/issues/148
Jim: This came up in conversations at XML Prague.
... This is day 0 concerns, more than after you've learned it all.
... Today, if you're a new user, to get a document into a database, you
need to understand a lot of topics. That can give a negative impression.
... I wonder, now that we've considered multipart in other places, if we
could accept glob values.
... That could help new users. And if we like it there, what about
p:document as well.
... If we're going to change primitives, how does that hook into a higher
level, like a database or webdav or anything.
... I think after I talked to people about it, we're just looking at a
simple change.
... This also applies to some event driven stuff. But that's probably out
of scope for 2.0.
... In the end, I wonder if we can't do something simple.
Norm: Yeah, this came up as a comment in my proposal for p:document and
p:load as well.
Norm waffles on about some sort of filter element inside inputs.
Jim: I think the filter is an interesting idea. We allow everything to be
composed from the ground up, but I wonder where the primitives should be.
... Doesn't content-type apply to multipart.
Some discussion of Norm's proposal for p:document and p:load (item 7 on
today's agenda)
Norm observes that we could have a dtd-validate step now that we have the
ability to have non-XML documents flowing through the pipeline.
Alex proposes that we should try to define things like p:load in terms of
other subpipelines.
Clarify p:load, issue #145; see proposed changes to p:document and p:load.
-> [19]https://github.com/xproc/specification/issues/145
->
[20]https://ndw.github.io/specification/langspec/clarify-load/head/xproc20/diff.html#p.document
->
[21]https://ndw.github.io/specification/langspec/clarify-load/head/xproc20-steps/diff.html#c.load
Norm walks through what he's done.
<alexmilowski> missing a space in the p:load descritption
Jim: A question about http-request came up while reading this. How do we
deal with a GET on collections?
Norm: I don't think we do anything, there's no notion of collections in
HTTP. We could write a webDAV step, but I think that'd be a different
step.
Jim: Globbing wouldn't do anything on an http request.
Norm: Right.
Alex: I'd say building in magic is a bad idea.
Norm: Is globbing on file URIs magic?
Alex: That's different. The directory is a thing you can talk to. It has a
POSIX API etc.
Norm: How about I try to tighten this up a bit, add a p:dtd-validate step
along the lines we discussed, add globbing, and possibly add the filtering
stuff I described.
No one objects to norm doing more work.
<scribe> ACTION: Norm to make p:load more explicitly like http-request,
perhaps by adding a dtd-validate step and describing a pipeline that can
use it. He'll also add globbing for file: URIs and perhaps the filtering
stuff we discussed. [recorded in
[22]http://www.w3.org/2015/03/25-xproc-minutes.html#action01]
<scribe> ACTION: Norm to make sure that the case of casting multipart to
single part is covered; Alex believes that binaries are base64 encoded in
multipart documents (so that the boundary isn't borked) [recorded in
[23]http://www.w3.org/2015/03/25-xproc-minutes.html#action02]
semantics of p:cast-content-type, issue #116
->[24]https://github.com/xproc/specification/issues/116
-> [25]http://www.w3.org/TR/xproc20-steps/#c.cast-content-type
Alex: There are two possible expectations: what the step currently says,
and that the server lied and I want to parse it as XML.
Norm: So I think what you want is a step that just attempts to parse it.
Alex: There's the thing and the representation of the resource and which
do we mean.
Norm: So we want p:cast-content-type to attempt to parse, not make a
base64 encoded anything.
... We have (at least proposed) steps for base64 encoding/decoding.
Alex: If you take octet stream and cast to image, maybe that will work,
maybe it won't, it's going to be implementation-defined or -dependent.
Norm: So should this step take parameters?
Alex: It would be nice not to have steps that overlap in strange ways.
<jfuller> quote/unquote ?
Norm: So p:cast-content-type should try to do everything. Including base64
encode and decode.
Alex: I think the word "cast" is misleading.
... We're trying to minimally change the content type and that's not the
same as the concept of "casting". Casting implies some sort of type system
and we just don't have that.
... Getting from thing it was labeled to thing we want it to be should be
something else.
Norm: Unfortunately, we've run out of time.
Any other business?
Adjourned.
Summary of Action Items
[NEW] ACTION: Norm to make p:load more explicitly like http-request,
perhaps by adding a dtd-validate step and describing a pipeline that can
use it. He'll also add globbing for file: URIs and perhaps the filtering
stuff we discussed. [recorded in
[26]http://www.w3.org/2015/03/25-xproc-minutes.html#action01]
[NEW] ACTION: Norm to make sure that the case of casting multipart to
single part is covered; Alex believes that binaries are base64 encoded in
multipart documents (so that the boundary isn't borked) [recorded in
[27]http://www.w3.org/2015/03/25-xproc-minutes.html#action02]
[End of minutes]
--------------------------------------------------------------------------
Minutes formatted by David Booth's [28]scribe.perl version 1.140 ([29]CVS
log)
$Date: 2015-03-26 12:59:00 $
References
1. http://www.w3.org/
2. http://www.w3.org/XML/XProc/2015/03/25-agenda
3. http://www.w3.org/2015/03/25-xproc-irc
4. http://www.w3.org/XML/XProc/2015/03/25-minutes#agenda
5. http://www.w3.org/XML/XProc/2015/03/25-minutes#item01
6. http://www.w3.org/XML/XProc/2015/03/25-minutes#item02
7. http://www.w3.org/XML/XProc/2015/03/25-minutes#item03
8. http://www.w3.org/XML/XProc/2015/03/25-minutes#item04
9. http://www.w3.org/XML/XProc/2015/03/25-minutes#item05
10. http://www.w3.org/XML/XProc/2015/03/25-minutes#item06
11. http://www.w3.org/XML/XProc/2015/03/25-minutes#item07
12. http://www.w3.org/XML/XProc/2015/03/25-minutes#item08
13. http://www.w3.org/XML/XProc/2015/03/25-minutes#item09
14. http://www.w3.org/XML/XProc/2015/03/25-minutes#ActionSummary
15. http://www.w3.org/XML/XProc/2015/03/25-agenda
16. http://www.w3.org/XML/XProc/2015/03/11-minutes
17. https://github.com/xproc/specification/issues/43
18. https://github.com/xproc/specification/issues/148
19. https://github.com/xproc/specification/issues/145
20. https://ndw.github.io/specification/langspec/clarify-load/head/xproc20/diff.html#p.document
21. https://ndw.github.io/specification/langspec/clarify-load/head/xproc20-steps/diff.html#c.load
22. http://www.w3.org/2015/03/25-xproc-minutes.html#action01]
23. http://www.w3.org/2015/03/25-xproc-minutes.html#action02]
24. https://github.com/xproc/specification/issues/116
25. http://www.w3.org/TR/xproc20-steps/#c.cast-content-type
26. http://www.w3.org/2015/03/25-xproc-minutes.html#action01
27. http://www.w3.org/2015/03/25-xproc-minutes.html#action02
28. http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm
29. http://dev.w3.org/cvsweb/2002/scribe/
Received on Thursday, 26 March 2015 13:08:20 UTC