draft agenda for ixml community group call 2024-06-11

ixml meeting 11 June 2024

When: Tuesday 11 June 2024 14:00 UTC for 1 hour
https://www.timeanddate.com/worldclock/fixedtime.html?msg=ixml+online+meeting&iso=20240611T1400

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

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/2024Apr/0009.html
https://www.w3.org/2024/04/30-ixml-minutes.html

(The meetings of 14 and 28 May were canceled owing to conflicts.)

****************************************************************
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 2024-03-05-c: SP to prepare pull request to resolve issue #139
                     (new grammars, new README).

ACTION 2024-03-19-a: Steven to contact W3C to get the report links
                     fixed on the report and ixml group pages:
                     https://www.w3.org/community/reports/
                     https://www.w3.org/community/ixml/
                     Both pages have links which return a 404.

                     [Still broken 11 June 2024 -- secure connection
                     fails, see [1], while trying to dereference
                     https://ixml.nwalsh.com/ixml/CG-FINAL-ixml-20230710/]

[1] https://support.mozilla.org/en-US/kb/secure-connection-failed-firefox-did-not-connect?as=u&utm_source=inproduct

ACTION 2024-04-16-a: MSM to revise the EBNF document in light of
                     Steven's review.

ACTION 2024-04-16-b: Norm to reconstruct the previous W3C-styled
                     draft.                     

ACTION 2024-04-16-c: Norm to sort out the broken link in the report
                     (404 on link to 'latest published version').

                     [29 April 2024: link to
                     https://www.w3.org/community/reports/ixml/ixml/
                     still broken] [10 June 2024: where is this link?
                     I don't find the string 'latest published
                     version' in the spec.]

ACTION 2024-04-30-a: Norm to propose wording for possible changes to
                     status reporting, with particular respect to
                     reporting of iXML version used by processor.

ACTION 2024-04-30-b: Bethan to open an issue on whether to adopt a
                     scheme to distinguish 'major' from 'minor'
                     versions in version numbers.

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

Topic:  Status of implementations

Topic:  Status of testing and test suites

See also test-suite related issues below.


****************************************************************
Topic:  broken links on CG and CG Reports pages
****************************************************************

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 an TLS error:

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

See also action 2024-03-19-a and 2024-04-16-c.

At this point (10 June 2024) the agenda preparer is completely lost on
this issue.  The links under "drafts" in the W3C pages listed don't
work, but Norm's action 2024-04-16-c mentions link text that the
agenda preparer cannot find.


****************************************************************
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.

* Bug reports against the current spec

Topic:  Issue #250 49 A subtraction operator
        https://github.com/invisibleXML/ixml/issues/250


* Issues relating to test suite

N.B. Issue #246 (linebreak tests needed) requires a volunteer but
needs no discussion.


* v.Next issues:  version numbers

There are several intertwingled issues here.  Bottom line of
discussion on 2 April was "Norm: I will take another stab at it."

  - Pull request #243
    https://github.com/invisibleXML/ixml/pull/243

    Intended to close issues #237 and #238.
    
  - Issue #237 What should the absence of a version number mean?
    https://github.com/invisibleXML/ixml/issues/237

  - Issue #238 When the input specifies an unknown version, what should a processor do?
    https://github.com/invisibleXML/ixml/issues/238

  - Issue #236 When must version numbers change?
    https://github.com/invisibleXML/ixml/issues/236

* v.Next issues:  other prolog issues

Topic:  Issue #235 Problems with prolog (syntax and semantics)
        https://github.com/invisibleXML/ixml/issues/235

Topic:  Issue #234 Alternative syntaxes for prolog
        https://github.com/invisibleXML/ixml/issues/234



* Other v.Next issues

Topic:  Issue #252 Er, where are the authoritative versions of ixml.ixml and ixml.xml?   
        https://github.com/invisibleXML/ixml/issues/252

        See also #253.

Topic:  Issue #253 Update the build process so that all generated grammar files explicit "build" metadata
        https://github.com/invisibleXML/ixml/issues/253

        Partial resolution of #252.

Topic:  Issue #249 A subtraction operator
        https://github.com/invisibleXML/ixml/issues/249

Topic:  Issue #239  Support simple data types?
        https://github.com/invisibleXML/ixml/issues/239

Topic:  Issue #75 Combining grammars (for v.Next)
        https://github.com/invisibleXML/ixml/issues/75

        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 
        https://github.com/invisibleXML/ixml/issues/168

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



* Issues relating to Web site and ancillary documents

Topic:  Issue #248 Schemas for vxml grammars need updating
        https://github.com/invisibleXML/ixml/issues/248

Topic:  Issue #139 Sample grammars for IRIs and URIs
        https://github.com/invisibleXML/ixml/issues/139

        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://github.com/invisibleXML/ixml/issues/137

        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).



****************************************************************
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 14 May, at
14:00 UTC for one hour.

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

  John Lumley        2024-03-19
  Steven Pemberton   2024-04-02
  Norm Tovey-Walsh   2023-04-16
  M Sperberg-McQueen 2024-04-30


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




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

Received on Tuesday, 11 June 2024 01:37:00 UTC