W3C

– DRAFT –
Invisible XML Community Group

29 October 2024

Attendees

Present
bethan, john, norm, steven
Regrets
david
Chair
steven
Scribe
john

Meeting minutes

<john> s/Invible/Invisible/

<norm> John, David gives regrets for today

Previous Actions

2024-08-06-a, SP to draft a PR to address [1]#263

(serialization of attributes) - Continues (access token expired)

2023-01-10-f: NTW to produce draft documentation of the XML

vocabulary (see [2]#137) - see later

2024-03-05-c: SP to prepare pull request to resolve issue

[3]#139 (new grammars, new README). - Work done - pull request outstanding

2024-03-19-a: SP to contact W3C to get the report links fixed

+ NTW: The broken link no longer appears, AFAICT. I suggest we

close this issue, and related issues, and back away slowly. - Norm can't find the broken link. CLOSED

2024-04-30-a: NTW to propose wording for possible changes to

status reporting, with particular respect to reporting of iXML

version used by processor. DONE

2024-04-30-b: Bethan to open an issue on whether to adopt a

scheme to distinguish 'major' from 'minor' versions in version

numbers. CONTINUES

2024-10-01-a: NTW to add XSLT Forms implementation to the

website DONE

2024-10-01-b: SP to try out renaming as a string NEEDS PR

2024-10-01-c: NTW to describe the discrepancy between iXML

names and XML names DONE

2024-10-01-d: NTW to make sure pragmas are on the agenda DONE

2024-10-01-e: SP to review ixml tests and correct the grammar CONTINUES

2024-10-01-f: SP to make a PR for both versions of the RFC

grammar CONTINUES

???: SP? to make a PR to fix [4]#250, alias delimiter ">"

should be hidden CONTINUES

Status Reports

Implement string renaming. Recasting the implementation in Typscript

norm: fixed a rename attribute bug

Review of change proposals

norm: iXML version fix for #271 - iXML version attribute replacing @version-mismatch. https://invisiblexml.org/pr/275/autodiff.html

Agreed to accept

norm: Fix section title: iXML in XML - DONE

norm: Add prose to allow user selection of start symbol - Accepted DONE

Open issues

Use pragmas for the prolog?

steven: not against and sees some benefit

norm: pragmas can be used by implementors for experimentation.

norm: pragmas in the spec should not change the behaviour of the grammar and parse

norm: but it could e.g. alter the performance, such as regular expressions.

norm: what do pragmas apply to - what is their locality of scope. E.g. run very fast for 'rule 17' or here is a regex you can use.

norm: can we come to common understanding of the scope of possible pragmas, such as can they be not just applied to a grammar as a whole.

<norm> Consider: {[A]} S: a.

<norm> The Balisage pragma's proposal uses {[+A]} for the pragma applies to the whole grammar.

Agreed to think a bit more about this.

ACTION: john - more detail on subtraction operator

<john> next meeting: 12th November

Summary of action items

  1. john - more detail on subtraction operator
Minutes manually created (not a transcript), formatted by scribe.perl version 238 (Fri Oct 18 20:51:13 2024 UTC).

Diagnostics

Succeeded: s/Meeting: ixml Group Teleconference//

Failed: s/Invible/Invisible/

Succeeded: s/Invisble/Invisible/

Succeeded: s/p[/p/

Succeeded: s/Previsous/Previous/

Succeeded: s/ranme/rename/

Succeeded: s/ther/here/

Found 'next meeting:' not followed by a URL: '12th November'.

Maybe present: 2023-01-10-f, 2024-03-05-c, 2024-03-19-a, 2024-04-30-a, 2024-04-30-b, 2024-10-01-a, 2024-10-01-b, 2024-10-01-c, 2024-10-01-d, 2024-10-01-e, 2024-10-01-f, ???

All speakers: 2023-01-10-f, 2024-03-05-c, 2024-03-19-a, 2024-04-30-a, 2024-04-30-b, 2024-10-01-a, 2024-10-01-b, 2024-10-01-c, 2024-10-01-d, 2024-10-01-e, 2024-10-01-f, ???, norm, steven

Active on IRC: john, norm, Steven