- From: Norman Walsh <ndw@nwalsh.com>
- Date: Wed, 24 Jun 2015 10:12:00 -0500
- To: public-xml-processing-model-wg@w3.org
- Message-ID: <87616dkunz.fsf@nwalsh.com>
See http://www.w3.org/XML/XProc/2015/06/24-minutes
[1]W3C
- DRAFT -
XML Processing Model WG
Meeting 273, 24 Jun 2015
See also: [2]IRC log
Attendees
Present
Regrets
Chair
Norm
Scribe
Norm
Contents
* [3]Topics
1. [4]Accept this agenda?
2. [5]Accept minutes from the previous meeting?
3. [6]Next meeting
4. [7]Review of actions
5. [8]Review of the “small-fixes” draft.
6. [9]Primer
7. [10]The problem of variable placement.
8. [11]Any other business?
* [12]Summary of Action Items
--------------------------------------------------------------------------
Accept this agenda?
-> [13]http://www.w3.org/XML/XProc/2015/06/24-agenda
Accepted.
Accept minutes from the previous meeting?
-> [14]http://www.w3.org/XML/XProc/2015/06/10-12-minutes.html
Accepted.
Next meeting
Any regrets for 1 July?
Murray gives regrets.
Review of actions
Jim reports progress on A-265-02; Norm will make sure that's on the agenda
for next week.
<jfuller> [15]https://github.com/xproc/specification/issues/136
Review of the “small-fixes” draft.
-> [16]https://ndw.github.io/specification/
<alexmilowski>
[17]https://ndw.github.io/specification/langspec/small-fixes/head/xproc20/diff.html
Comments on 2.10 Value Templates
Henry: I think there are a lot of problems with the terminology. There's
overloading of the attribute/element that might contain something in curly
braces and the strings that contain curly braces.
... They're both called value templates and I don't think that's helpful.
... I tried to rework it but it wasn't obvious. Introducing different
terms for contexts where value templates are allowed on the one hand and
on the other, the thing that's in there that gets expanded and so on.
Norm: Entirely fair; I tried to copy what was in the XSLT draft and I
don't think it works.
Henry: A few more comments then.
... The word "alternating" should be removed from the first paragraph.
... It's just a sequence because {$foo}{$bar} is prefectly fine.
<alexmilowski> Isn't "{}" just a variable part that returns an empty
sequence / empty string ?
Henry: The next to last sentence of that paragraph and the note that
follows contradict each other.
<jfuller> its an error
<ht> }{
<alexmilowski> Right, got it.
<alexmilowski> (still drinking my coffee; coffee good)
Henry: The "fixed part of" following the note has only been removed in one
place. That seems an error.
... In 2.10.1 but not 2.10.2, in the second bullet don't we need a
reference to the process in XPath?
... "converting the value to a string" is non-obvious: you have to
atomize, etc.
... And finally, below the deleted note in 2.10.2, the sentence that
begins "The rules for text value templates..." should be removed.
<alexmilowski> Are we going to say something about: <x>xyzzy{@y}</x> ?
Henry: We should have a note that says that.
... Perhaps we could point to something in XQuery that describes how that
construction works.
<alexmilowski> 5.2 ?
Norm: The change in 5 is entirely editorial, I added new sections.
... In 5.2, I removed @expand-text.
<alexmilowski> 5.51 & 5.5.3 - same change
<alexmilowski> 5.5.1
Norm: The changes in 5.10 are an attempt to get non-XML inlines.
<alexmilowski> Editorial: make the non-XML content subsection first as it
is very short.
<alexmilowski> @encoding is separable from this.
Henry: "Interpretation of the content" is wrong; it's "decoding of the
content"
Alex: The right way to slice this is to say you're starting with two
things, an encoding attribute that gives you a sequence of bytes or you
have a sequence of nodes (children of the inline) and you have to coerce
that into a document.
... What happens if you have element nodes in the content.
Henry: I'm happy to special case that. If it's an XML application type,
then elements are ok.
Norm: The case of XML that's base64 encoded needs to be considered as
well.
Alex: Can't we just make encoding XML an error? This is an inline.
<alexmilowski> We have three categories: text/*, XML media types,
everything else
Henry: Are we clear that you can specify a charset on the content type?
<alexmilowski> encoding=base64, content-type=text/xml is an error
Norm: If you base64 encode the text then you have to be able to specify
the charset.
encoding=base64, content-type=text/plain; charset=ASCII should work
Alex: Maybe we should just show the matrix: encoding, text, XML, non-XML
Some discussion of media type vs. content type.
Alex: The syntax we're relying on is the value space of content type.
Change MediaType to ContentType
<jfuller> (Internet) Media Type vs Content-Type (the header ?)
Primer
Norm mutters on a bit about a primer.
Norm: We thought of you Murray.
<jfuller> to add- as well as editing primer and getting others to contrib
Murray: I'm busy for at least a month but then I might be interested.
Alex: Consensus generally was that we also need someone to think
creatively about this.
Murray: Sure.
The problem of variable placement.
<jfuller>
[18]https://lists.w3.org/Archives/Public/public-xml-processing-model-wg/2015Jun/0012.html
<jfuller> +1 to accepting p:variable everywhere
<jfuller> agree no need to put in atomics
<scribe> ACTION: Norm to draft p:variable everywhere. [recorded in
[19]http://www.w3.org/2015/06/24-xproc-minutes.html#action01]
<jfuller> and I've put a comment in
[20]https://github.com/xproc/specification/issues/132 that we should
probably close (as p:variable in atomic may not mean anything)
Any other business?
Adjourned.
Summary of Action Items
[NEW] ACTION: Norm to draft p:variable everywhere. [recorded in
[21]http://www.w3.org/2015/06/24-xproc-minutes.html#action01]
[End of minutes]
--------------------------------------------------------------------------
Minutes formatted by David Booth's [22]scribe.perl version 1.140 ([23]CVS
log)
$Date: 2015/06/24 15:10:33 $
References
1. http://www.w3.org/
2. http://www.w3.org/2015/06/24-xproc-irc
3. http://www.w3.org/XML/XProc/2015/06/24-minutes.html#agenda
4. http://www.w3.org/XML/XProc/2015/06/24-minutes.html#item01
5. http://www.w3.org/XML/XProc/2015/06/24-minutes.html#item02
6. http://www.w3.org/XML/XProc/2015/06/24-minutes.html#item03
7. http://www.w3.org/XML/XProc/2015/06/24-minutes.html#item04
8. http://www.w3.org/XML/XProc/2015/06/24-minutes.html#item05
9. http://www.w3.org/XML/XProc/2015/06/24-minutes.html#item06
10. http://www.w3.org/XML/XProc/2015/06/24-minutes.html#item07
11. http://www.w3.org/XML/XProc/2015/06/24-minutes.html#item08
12. http://www.w3.org/XML/XProc/2015/06/24-minutes.html#ActionSummary
13. http://www.w3.org/XML/XProc/2015/06/24-agenda
14. http://www.w3.org/XML/XProc/2015/06/10-12-minutes.html
15. https://github.com/xproc/specification/issues/136
16. https://ndw.github.io/specification/
17. https://ndw.github.io/specification/langspec/small-fixes/head/xproc20/diff.html
18. https://lists.w3.org/Archives/Public/public-xml-processing-model-wg/2015Jun/0012.html
19. http://www.w3.org/2015/06/24-xproc-minutes.html#action01]
20. https://github.com/xproc/specification/issues/132
21. http://www.w3.org/2015/06/24-xproc-minutes.html#action01
22. http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm
23. http://dev.w3.org/cvsweb/2002/scribe/
Received on Wednesday, 24 June 2015 15:12:27 UTC