IRC log of xproc on 2015-09-02

Timestamps are in UTC.

14:04:20 [RRSAgent]

RRSAgent has joined #xproc

14:04:20 [RRSAgent]

logging to http://www.w3.org/2015/09/02-xproc-irc

14:04:26 [Norm]

rrsagent, set logs world-visible

14:04:27 [Norm]

Meeting: XML Processing Model WG

14:04:27 [Norm]

Date: 2 September 2015

14:04:28 [Norm]

Meeting: 276

14:04:30 [Norm]

Chair: Norm

14:04:32 [Norm]

Scribe: Norm

14:04:34 [Norm]

ScribeNick: Norm

14:04:41 [Norm]

Topic: Accept this agenda?

14:04:41 [Norm]

-> http://www.w3.org/XML/XProc/2015/09/02-agenda

14:04:48 [Norm]

Accepted.

14:04:48 [alexmilowski]

alexmilowski has joined #xproc

14:04:59 [Norm]

Topic: Accept minutes from the previous meeting?

14:04:59 [Norm]

-> http://www.w3.org/XML/XProc/2015/07/08-minutes

14:05:14 [alexmilowski]

(wow, we're slackers)

14:06:05 [Norm]

Accepted.

14:06:28 [Norm]

Topic: Next meeting, 9 July 2015

14:06:48 [Norm]

s/July/September/

14:06:53 [Norm]

No regrets heard.

14:07:12 [Norm]

Topic: The latest "small fixes" branch

14:07:27 [Norm]

-> https://ndw.github.io/specification/langspec/small-fixes/head/xproc20/

14:13:19 [jfuller]

ok here now

14:14:05 [alexmilowski]

I now really hate WebEx

14:14:19 [Norm]

We can't here you

14:14:20 [Norm]

hear

14:14:23 [alexmilowski]

spinning ball of death

14:14:57 [Norm]

Henry: I have a pedantic suggestion, in 2.10.2, in the first new paragraph, it says "this section describes how..."

14:15:14 [Norm]

... There is no corresponding paragraph in 2.10.1.

14:15:39 [Norm]

... I think there should be.

14:16:13 [Norm]

Norm: Sure, I think that's a good idea.

14:17:01 [Norm]

Henry: I'm still distracted by the contradictory statements that AVTs are attributes and strings, but fixing that is probably not worth it.

14:19:47 [ht]

Alex, are you talking now????

14:23:41 [Norm]

Alex: Do we say that it's an XPath expression?

14:23:48 [Norm]

Norm: I can check that.

14:27:51 [Norm]

Henry: Last time we talked about this, we talked a lot about the interaction between media type and charset.

14:28:34 [Norm]

... I think there's an implicit flowchart here. Would it help to summarize the order of what you're going to find out before it starts?

14:29:18 [Norm]

... The order of play is: if there's an encoding, the string is decoded. After that you have a string and don't care about the encoding anymore.

14:29:27 [Norm]

s/string/byte sequence/

14:29:49 [Norm]

... If there's a charset param, you then construct a string using either the charset parameter or UTF-8

14:29:51 [Norm]

Norm: Yes

14:31:02 [Norm]

Henry: I think this "flowchart" should be the the second paragraph of the section.

14:31:11 [Norm]

Alex: Generate a sequence of bytes, etc.

14:32:11 [Norm]

Henry: If the media type is a non-XML media type, and there is no charset parameter, what is used to decode the byte sequence.

14:32:33 [Norm]

... I think we can say UTF-8, unless it's XML, in which case the XML decl wins.

14:32:40 [Norm]

Alex: If it's a text media type, utf-8.

14:33:00 [Norm]

Alex: The situation about the XML decl never arises, because we've made that an error.

14:34:25 [Norm]

Norm: We should say utf-8 is the default.

14:35:57 [jfuller]

I can hear you

14:36:00 [jfuller]

a few secs ago

14:36:02 [jfuller]

nothing now

14:36:07 [Norm]

right. call died. redialing

14:36:10 [ht]

All we've heard are metacomments

14:36:23 [alexmilowski]

lol. webex wins!

14:36:30 [Norm]

that or my phone service

14:36:38 [Norm]

nobody look at my scheudle. it's sekrit

14:40:04 [Norm]

Henry: It might be useful in the flow chart to just have almost footnote numbers cross-referencing the errors.

14:40:37 [Norm]

Alex: In 5.10.1, non-XML is implementation-dependent.

14:41:14 [Norm]

... Are we open to being able to treat any kind of semi-structured data as something you can run expressions across?

14:41:57 [Norm]

Norm: In principle, yes.

14:43:14 [Norm]

Alex: Can you do non-XML in implicit inlines

14:43:17 [Norm]

Norm: Not today.

14:43:44 [jfuller]

changes look good to me

14:44:03 [Norm]

Henry: I still don't understand what it means to remove in-scope namespaces.

14:44:38 [Norm]

... And there's a typo in 5.10.2.

14:48:24 [Norm]

Some discussion of removing in-scope namespaces.

14:49:27 [Norm]

Alex: We have a different situation; sometimes we hand documents to a tool.

14:50:19 [Norm]

Norm: We could have used exclude-result-prefixes but it would have to be used everywhere and that might lead to conflicts.

14:52:46 [Norm]

Proposed: accept this doucment as the status quo, with the understanding that the flowchart will be added.

14:52:51 [Norm]

Accepted.

14:54:57 [jfuller]

note I redrafted errors proposal

14:54:57 [jfuller]

https://github.com/xproc/specification/issues/136

14:55:02 [jfuller]

for next week

14:55:24 [Norm]

Thanks, Jim.

14:56:17 [Norm]

Some discussion of possible future f2f meetings.

15:01:26 [Norm]

rrsagent, make logs world visible

15:01:31 [Norm]

rrsagent, draft minutes

15:01:32 [RRSAgent]

I have made the request to generate http://www.w3.org/2015/09/02-xproc-minutes.html Norm

15:02:37 [ht]

Note that Norm believes that the name of the room for this call on WebEx is "XProc Weekly Call"

15:02:52 [ht]

Bother, missed the minutes.

15:02:58 [Norm]

I can put that in if you'd like

15:03:02 [ht]

Perhaps, norm, you would add that to the Agenda template

15:03:06 [Norm]

Yes

15:03:29 [ht]

Sorry to miss Summer School once again -- what are the dates?

15:04:08 [Norm]

week after next, uhm...13-18

15:04:24 [Norm]

Agenda template updated

15:05:32 [ht]

Bother, ish. I'm at my in-laws in Croxley Green 11--13, but train home is already booked for Sunday evening . . .

15:42:15 [ht]

ht has left #xproc

16:24:43 [jfuller]

jfuller has joined #xproc