W3C

– DRAFT –
ixml group call

12 July 2022

Attendees

Present
Bethan, JoelDubinko, John, Michael, Norm, Steven
Regrets
-
Chair
Steven
Scribe
Steven

Meeting minutes

rrssagent, make minutes

rssagent, make minutes

Previous Actions

Steven: All done

Norm: Not ACTION (2022-06-21): Tom to set up a schematron demo

Michael: I didn't find large and unexpected XPath expressions

John: I got all but 11 QT tests running
… they fail on "-" as operator or namecharacter
… with lots of ambiguity
… whitespace can be very critical

Michael: I expect whitespace to be the biggest issue for newcomers
… we need to warn people

<mjoel> offline: I had a low-priority query about the community page https://www.w3.org/community/ixml/ which is a bit out of date, for example in specifying meeting times ... and how to update it

Steven: I will be handling that in an advanced ixml tutorial for Declarative Amsterdam in November

Bethan: I'm thinking of offering a mode in my implementation to handle whitespace

Status of implementations

Norm: I'm close to v2.0 with GLL parser, but not there yet

John: Close to v1.0 release of workbench
… also a stub library for Saxon
… away on hol until Balisage

Michael: About John's implementation, is there a direct link?

John: That's the current link

Michael: Apologies

Status of testing and test suites

Michael: I've added a couple of groups of performance tests
… with exponential increasing size input/grammar
… to see what happens to response times

Review and resolution of bug reports and technical issues

[None]

Plans for Balisage

Norm: I took all inputs and crafted them as docbookml, needs copy editing

Bethan: I'

'll do the copy edit

Michael: I will draft my implementation text by today eob

John: Please list my implementation as working

Steven: Is the total version on github?

Norm: Yes

Bethan: Do people want to do slides for their individual bit, or shall I do slides?

<Steven> s/DO?Do/

<Steven> s/DO?Do/

AOB

JoelDubinko: I'm going by "Joel" these days
… I'm unaffiliated.
… I'm interested in Rust and ixml, so I want to build a Rust implementation
… I've ordered the Dragon book

John: What is the plan for the talk?

Steven: Split according to the bits we've written.

Norm: My suggestion is Steven a few slides intro, and then each implementor about their implementations
… then a sort of panel

John: I would like to demo the workbench
… three to four minutes

Bethan: Four people talking about implementations?

Norm: We have 30+15 minutes

Michael: Let us talk about implementations in the order that they have become publically available - Tom, me, Steven, Norm, John

Steven: Sounds good.

Bethan: How about I do the intro?

Steven: Go for it.

s/Go/Go/

John: One of the big developments is that we have taken it through a community group, with a lot of work done. We should mention it

Bethan: Agree

Steven: We should be checking the paper Thursday.

Norm: Meet next Tuesday to discuss the slides

Bethan: Lets make that the 26th

John: I'll be on holiday, so won't be able to do much

Joel: About the community page
… ... needs updating

ACTION: Steven update community page

[ADJOURN]

S/Go for/Go for/

Summary of action items

  1. Steven update community page
Minutes manually created (not a transcript), formatted by scribe.perl version 192 (Tue Jun 28 16:55:30 2022 UTC).

Diagnostics

Succeeded: s/whait/white/

Succeeded: s/GLC/GLL/

Succeeded: s/reponse/response/

Failed: s/DO?Do/

Failed: s/DO?Do/

Succeeded: s/DO/Do/

Succeeded: s/GO/Go/

Succeeded: s/rhough/through/

Succeeded: s/ciommunity/community

Succeeded: s/didn;t/didn't/

Succeeded 2 times: s/Micah/JoelDubinko/G

Succeeded: s/whitee/white

Succeeded: s/v1,.0/v1.0

Succeeded: s/or shal I/or shall I

Succeeded: s/workbench'/workbench

Succeeded: s/minutesw/minutes

Succeeded: s/GO for/Go for/

Succeeded: s/GO for/Go for/

No scribenick or scribe found. Guessed: Steven

Maybe present: Joel