W3C

– DRAFT –
Invisible XML CG

19 March 2024

Attendees

Present
bethan, jimS, john, michael, norm, steven
Regrets
-
Chair
steven
Scribe
john, John Lumley, jwL

Meeting minutes

Previous Actions

ACTION: 2023-01-10-f: continues

ACTION: 2023-11-28-a: completed

ACTION: 2023-11-28-c: continues - needs a link

ACTION: 2024-02-20-b: completed

ACTION: 2024-03-05-a: completed

ACTION: 2024-03-05-b: continues

ACTION: 2024-03-05-c: continues

Status reports

No particular progress worth recording now on implementations. Minor merging on testsuites

Publication of iXML W3C CG Report

Some brokken links.

ACTION: Steven to check links

Bug Reports

#224 has been closed.

#227 continues

#233 continues

#139 - permit both grammars - is ACTION 2024-03-05-c which continues

#137 - pending

v.Next issues

#199 - whitespace between prolog and first rule. No further discussion. Michael will merge

ACTION: michael to merge #199

#202 - Unicode version. Need to review changes

To be reviewed next meeting

#236 - version number changes.

Norm: grammars without versions assume 1.0 - consensus to permit 'use any you like'

Michael: suggestion 'It is implementation-defined what version shall be used.'

Steven: what objection to using the latest version?

Michael: implemntation-defined

<john> s/implemnation/implementation/

Michael: what about the 'stable'/quality version?

Agreed: move to implementation-defined rather than default 1.0. Implementations can configure.

ACTION: Norm to draft a PR to define response in the spec. e.g. unrecognised, different options for choice of which version to be used.

JimS: Has the format of the version string been altered? Rather is the prolog defined finally.

Norm: a conforming 1.0 implementation must support a prolog

Reminder - the version is a QuotedString

#192 Normalizing line endings in input

See https://lists.w3.org/Archives/Public/public-ixml/2023Oct/0021.html

Steven: an implementation might not know where the input comes from.

Norm: We should do the same as XML in input normalisation - CR/LF -> LF

Michael: Say nothing, or declare that implementations may permit (user-option) suspension of such normalization

norm: Worth making the deployment of iXML grammars more robust across platforms

Lots of discussion about the possibilities, and possible benefits and costs to user

ACTION: Norm to draft a section of the spec. to cover this topic.

AOB

<john> Next Meeting: 2nd April

Summary of action items

  1. 2023-01-10-f: continues
  2. 2023-11-28-a: completed
  3. 2023-11-28-c: continues - needs a link
  4. 2024-02-20-b: completed
  5. 2024-03-05-a: completed
  6. 2024-03-05-b: continues
  7. 2024-03-05-c: continues
  8. Steven to check links
  9. michael to merge #199
  10. Norm to draft a PR to define response in the spec. e.g. unrecognised, different options for choice of which version to be used.
  11. Norm to draft a section of the spec. to cover this topic.
Minutes manually created (not a transcript), formatted by scribe.perl version 221 (Fri Jul 21 14:01:30 2023 UTC).

Diagnostics

Succeeded: s/inks/links/

Failed: s/implemnation/implementation/

Succeeded: s/a 1.0 must/a conforming 1.0 implementation must/

Succeeded: s/time/topic/

Found 'Next meeting:' not followed by a URL: '2nd April'.

Maybe present: Agreed

All speakers: Agreed, JimS, Michael, Norm, Steven

Active on IRC: john, Steven