draft agenda for invisible XML community group call Tuesday 19 March 2024

ixml meeting 19 March 2024

When: Tuesday 19 March 2024 15:00 UTC for 1 hour
https://www.timeanddate.com/worldclock/fixedtime.html?msg=ixml+online+meeting&iso=20240319T1500

N.B. Most of the U.S. will be on daylight savings time for this
meeting, so the meeting will be at 11 Eastern Daylight Time (not 10
Eastern Standard Time) and so on.

Where: https://meet.google.com/dfz-rwpj-opq 
  
Minute taker: JL (or he being absent SP)

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/2024Mar/0022.html
https://www.w3.org/2024/03/05-ixml-minutes.html

One error has been reported in the previous minutes.  They state that
"JL uses an ixml grammar to parse the source code for the
specification of the XPath 4.0 grammar in the specs, and produces an
ixml grammar."  They should have said that JL uses XSLT to read the
XML used in the XPath spec to define the grammar and produce
XML-format iXML, from which he generates a grammar in iXML notation.


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

    0 Identify minute-taker
    1 Review of action items
    2 Status reports
    3 Review, discussion, resolution of issues
    4 Other topics
    5 Next meeting (and next scribe)
    6 Any other business

Details below.
        

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

ACTION 2023-01-10-f: Norm and Michael to do a bit of revision to
                     improve the draft documentation of the XML
                     vocabulary (see #137) for further discussion.

ACTION 2023-11-28-a: SP to make pull request adding his proposed
                     addition to section 3.3 ("Names are
                     case-sensitive.").

ACTION 2023-11-28-c: SP to review the EBNF to BNF document.

ACTION 2024-02-20-b: Steven to amend the specification to describe how
                     Unicode is version-dependent

ACTION 2024-03-05-a: Norm to test the correctness of PR #224 and merge
                     if it is correct.

                     Done:  https://lists.w3.org/Archives/Public/public-ixml/2024Mar/0032

ACTION 2024-03-05-b: Norm to add a section to the home page pointing
                     to other things named "ixml" or "9ml" or ...

ACTION 2024-03-05-c: SP to prepare pull request to resolve issue #139
                     (new grammars, new README).


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

Topic:  Status of implementations

Topic:  Status of testing and test suites

See also test-suite related issues below.


****************************************************************
Topic:  publication of ixml spec as W3C CG Report
****************************************************************

Rules: https://www.w3.org/community/about/faq/#how-do-we-publish-a-report

Published report:
  https://www.w3.org/community/reports/ixml/CG-FINAL-ixml-20231212/

There is one problem: CG Reports are linked from the Reports page and
from the page for the responsible CG:

  https://www.w3.org/community/reports/
  https://www.w3.org/community/ixml/

Currently, both of those link use not the URL of the report but to a
URL which returns a 404:

  https://ixml.nwalsh.com/ixml/CG-FINAL-ixml-20230710/

Progress report needed on action 2024-02-20-a.


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

NB The list below shows only issues open as of the time this agenda
was last revised.  It does not show any issues raised only in email:
if you wish an issue to be discussed, please open an issue in Github.

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


* Issues against the 1.0 spec

None.


* Issues relating to test suite

Topic:  Pull request #224 Mitigating ambiguity in mod357

Topic:   Pull request #227 Add .gitattributes
         preventing Git from converting CR to CRLF upon checkout (was:
         Extraneous #D in performance/oberon expected results)


* Issues relating to Web site and ancillary documents

Topic:  Issue #233 There are other things called iXML

Topic:  Issue #139 Sample grammars for IRIs and URIs
        
        See proposal at
        https://lists.w3.org/Archives/Public/public-ixml/2023Mar/0004.html

        Revised proposal from Steven:
        https://lists.w3.org/Archives/Public/public-ixml/2023Jun/0009.html

        And now:
        https://lists.w3.org/Archives/Public/public-ixml/2024Feb/0003.html


Topic:  Issue #137 Document the XML tag set of ixml grammars

        https://lists.w3.org/Archives/Public/public-ixml/2023Jan/0003.html
        https://ixml.nwalsh.com/xmlguide/

        Awaiting progress on action 2023-01-10-f (Norm and Michael).


* v.Next issues

Topic:  Issue #199 Require whitespace between prolog and first rule?

        Proposed resolution in PR #222.  Any further discussion?  Or
        merge it?

Topic:  Issue #202 Spec should say Unicode version is implementation-defined

        Awaiting proposal (action 2024-02-20-b).

Topic:  Issue #203 Spec should say nonterminals are case-sensitive

        Awaiting pull request (action 2023-11-28-a).

Topic:  Issue #236 When must version numbers change?

Topic:  Issue #235 Problems with prolog (syntax and semantics)

Topic:  Issue #234 Alternative syntaxes for prolog

Topic:  Issue #192 Normalizing line endings in ixml inputs

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

Topic:  Issue #75 Combining grammars (for v.Next)

        https://lists.w3.org/Archives/Public/public-ixml/2023Jan/0002.html

        We need to discuss the use-cases document proposed by Norm.
        MSM proposes the functionality of RNG as a minimum.

Topic:  Issue #168 Dynamic naming / name from the input data 

        See discussion document from John:
        https://lists.w3.org/Archives/Public/public-ixml/2023May/0005.html


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

Topic:  Plans for further work

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


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

Normal date and time for ixml meetings is every other Tuesday at 3 pm
British Time, 4 pm Central European Time (14:00 UTC during summer
time, 15:00 UTC during winter time).  For the foreseeable future, we
meet in weeks whose numbers in the ISO week numbering are even.

On the usual schedule, the next meeting would be Tuesday 19 March, at
15:00 UTC for one hour.

N.B. For that meeting, times in the U.S. will be one hour later than
usual (11 am EDT instead of 10 am EST, and so on).  After 31 March
both sides of the Atlantic will be on summer / daylight savings time.

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

  John Lumley        2023-11-28
  Steven Pemberton   2024-01-09
  Norm Tovey-Walsh   2023-02-20
  M Sperberg-McQueen 2024-03-05


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




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

Received on Tuesday, 19 March 2024 02:18:38 UTC