Summary of open issues (11 April 2022)

Good morning,

The summary of open issues that I sent last week as an adjunct to the
agenda seemed to be useful, so here’s another one for this week:

* Issues relating to the specification

** Open PRs awaiting review

+ Draft of errors with inline markup
  + https://github.com/invisibleXML/ixml/pull/65
  + This (probably) superscedes 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

(By which I mean, in Michael’s absence, we were unsure if these had
been addressed sufficiently, or if actions had been taken to address
them.)

+ 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?

                                        Be seeing you,
                                          norm

--
Norm Tovey-Walsh
Saxonica