draft agenda for ixml community group call Tuesday 12 April 2022

ixml meeting 12 April 2022

When:  Tuesday 12 April 2022 14:30 UTC for 1 hour
https://www.timeanddate.com/worldclock/fixedtime.html?msg=ixml+online+meeting+29+March&iso=20220412T1430

Where: Location: https://meet.google.com/dfz-rwpj-opq 
  
Minute taker: tbd (TH? NDW?)

IRC: the meetings will be minuted on IRC at [1].  Details of W3C IRC
use are at [2] and [3], hints for using RRSAgent at [4] and [5].

[1] irc://irc.w3.org:6667/%23ixml
[2] https://www.w3.org/wiki/InternetRelayChat
[3] https://www.w3.org/wiki/IRC
[4] https://www.w3.org/2002/03/RRSAgent
[5] https://w3c.github.io/scribe2/scribedoc.html

Previous minutes:
https://lists.w3.org/Archives/Public/public-ixml/2022Apr/0014.html
https://www.w3.org/2022/04/05-ixml-minutes

****************************************************************
Topic: Review of agenda
****************************************************************

    0 Identify minute-taker
    1 Review of action items
    2 Status reports
      Status of implementations
      Status of testing and test suites
    3 Review and resolution of issues
      See below.
    4 Other topics
      Terminology
      Website
      Release plan
    5 Next meeting (and next scribe)
    6 Any other business


****************************************************************
Topic: Previous Actions
****************************************************************

ACTION 20220322-001: Michael to update schema for test catalogs to add
       dynamic error.

ACTION 20220322-002: Norm to edit the pull request for #56.

ACTION 20220322-003: John, Steven, Bethan, Tomos to review the errors
       proposal.

ACTION 20220322-005: Michael to provide a schema for ixml in XML.

ACTION 20220405-001: Steven: solve Issue #57 (s missing in set)

ACTION 20220405-002: Steven: implement '**' and '++' as separator
       infix operators

ACTION 20220405-003: Norm: Add the error code linkages to the spec.

ACTION 20220405-004: Norm: to add prose specifying the namespace to
       use if error codes are given as qualified names.

ACTION 20220405-005: Tom: start email discussion on namespaces for the
       coming week.

ACTION 20220405-006: Steven: Add insertions in the specification.


****************************************************************
Topic:  Status reports
****************************************************************

Topic:  Status of implementations

Topic:  Status of testing and test suites


****************************************************************
Topic:  Review and resolution of bug reports and technical issues
****************************************************************

For all active issues, see
https://github.com/invisibleXML/ixml/issues/

Current survey:  see Norm Walsh's mail at
https://lists.w3.org/Archives/Public/public-ixml/2022Apr/0024.html

................................................................
* Issues relating to the specification
................................................................
** Open PRs awaiting review
................................................................

+ Draft of errors with inline markup
  + https://github.com/invisibleXML/ixml/pull/65
  + This (probably) supersedes the previous draft of errors PR
    + https://github.com/invisibleXML/ixml/pull/54
+ Fix markup error
  + https://github.com/invisibleXML/ixml/pull/64

................................................................
** Open issues awaiting action from Steven
................................................................

+ Adopt the insertions proposal
    + https://github.com/invisibleXML/ixml/issues/60
+ Change repeat0 and repeat1 to use '**' and '++', respectively, when a separator is specified
    + https://github.com/invisibleXML/ixml/issues/59
+ I believe the 3/17 grammar is missing an "s" in set
    + https://github.com/invisibleXML/ixml/issues/57
+ an ambiguity in the ixml grammar for ixml grammars
    + https://github.com/invisibleXML/ixml/issues/48
+ Should the ixml spec distinguish between static and dynamic grammar errors?
    + https://github.com/invisibleXML/ixml/issues/25

................................................................
** Open issues awaiting action from Norm
................................................................

+ Proposal to add error codes to the specification
    + https://github.com/invisibleXML/ixml/issues/44
+ If the errors proposal is accepted, add a note about an errors namespace
    + https://github.com/invisibleXML/ixml/issues/61

#61 is complete in the “inline markup” draft, if that’s the one accepted.

................................................................
** Open issues heaped onto Michael’s lap last week
................................................................

+ Conformance of grammars
    + https://github.com/invisibleXML/ixml/issues/43
+ Desiderata for an ixml schema
    + https://github.com/invisibleXML/ixml/issues/28
+ How is ambiguity defined? What obligations do processors have in cases of ambiguity?
    + https://github.com/invisibleXML/ixml/issues/26
+ Conformance issue: one rule per nonterminal
    + https://github.com/invisibleXML/ixml/issues/19

................................................................
** New issues not yet assigned actions
................................................................

Each of these issues, in fact, comes with a concrete proposal that we could adopt.

+ Is the distinction between "s" and "S" insufficient from an accessibility point of view
    + https://github.com/invisibleXML/ixml/issues/62
+ Simple Namespaces Proposal
    + https://github.com/invisibleXML/ixml/issues/66
+ Optional version declaration?
    + https://github.com/invisibleXML/ixml/issues/63

................................................................
* Issues relating to the test suite
................................................................
** Open PRs awaiting review
................................................................

+ Some correct ixml grammar tests testsuite
    + https://github.com/invisibleXML/ixml/pull/58

** Open issues awaiting action from Michael

+ Fix the expected result of expr1 testsuite
    + https://github.com/invisibleXML/ixml/pull/56

................................................................
* Other issues
................................................................

+ Improve README
  + https://github.com/invisibleXML/ixml/pull/11

    This has been partially implemented, I think. I propose that we
    assign Norm to make a commit applying the still relevant portions
    to the repo and close it.

+ Add a link for automatic HTML preview of the specification
  + https://github.com/invisibleXML/ixml/pull/3

    Is this completed? Can it be closed? If not, who has the action to
    complete it?



****************************************************************
Topic: Other topics
****************************************************************

Topic: Terminology

Topic: Website
  
     https://invisiblexml.org
     https://github.com/invisibleXML/

Topic:  Release plan


****************************************************************
Topic: Next meeting
****************************************************************

Normal date for ixml meetings is every Tuesday at 14:30 UTC

On the usual schedule, the next meeting would be Tuesday 19 April, at
14:30 UTC for one hour.

https://www.timeanddate.com/worldclock/fixedtime.html?msg=ixml+online+meeting&iso=20220419T1430

Expected scribe next week:  volunteers sought.

For the record: the current state of the minute-taking rota is:

  Tomos Hillman      2022-03-01
  Norm Tovey-Walsh   2022-03-15
  Steven Pemberton   2022-03-22
  M Sperberg-McQueen 2022-03-29
  John Lumley        2022-04-05



****************************************************************
Topic: Any other business 
****************************************************************



-- 
C. M. Sperberg-McQueen
Black Mesa Technologies LLC
http://blackmesatech.com

Received on Tuesday, 12 April 2022 01:35:22 UTC