Meeting minutes
Organizational
Draft minutes of last week, Wednesday
https://
Ege: Checked them already with M. Koster
… no objections -> minutes approved
Regrets
Ege: Mahda this and next week not available
Cancellation
Ege: TD cancelled for next Wednesday
… Thursday as usual with M. Koster chairing
TD
Toolchain Discussion
PR 1983
Ege: Merged PR, w3c/
… need still to work on it
… added big box on bottom part
… about testing pipeline
… we had to merge the PR
Kaz: Clarifying data-flow is nice
… anyhow, we should clarify task a bit more
… as input and output
Ege: Yes, it will come next
PR 1975
<kaz> PR 1975 - Toolchain requirements
Ege: w.r.t Agreeing on the requirements: https://
… we agreed in the call
… asked Cristiano to have final look
… "lightweightness" was mentioned by Cristiano
… meaning easier to install etc
… part of the ideal requirements
… functionality should come first
… if we are fine I will add this to the list in requirements.md
… another point Cristiano mentioned is the validation folder
… there are 2 things
… examples with valid TDs
… and the JSON schemas
Ege: Suggest to add it this aspect as well...
… we can now have a final look at the requirements
<Ege> https://
<Ege walking over the MD file>
Kaz: Minor comment: "general requirements " might be clearer than "Overall Requirements"
Ege: Agree
Ege: w.r.t. "Output Resources"
… it should be always synced
… some parts done only once
DP: TypeScript definition part of the toolchain? Currently done by Scripting TF
Ege: I think it should be part of the toolchain
… might affect Scripting API specification
Kaz: minor: Maybe it might be better to describe the expectations a bit clearer
Ege: Agree
… changing to "the following resources are updated each time ..."
… BTW, there could be more than TypeScript
Ege: w.r.t. "source of truth"
… it is the input resources
<EK creates another commit to have final look>
Ege: I think it looks good. Are there are further remarks?
… none -> merging PR 1975
Kaz: Merging is okay
… however, don't we want to mention the potential input resources based on the current practice?
Ege: Turtle file might be generated in the future
Kaz: At some point we need to clarify what is the input
Ege: Correct
Ege: as a next step I propose to extend the tool analyses to see whether they match our requirements
… tracked in issue 1984
Management
Project Management Proposal
<kaz> PR 1977 - Project Management Improvements
Ege: see Project Management https://
Ege: We worked on making the steps more visual
Ege: steps are properly mentioned in the beginning
… steps correspond to lifecycle diagram
… it is still open how we prioritize items
… last week we started the discussion already
… we need to find a rough idea
Kaz: we can skim the document a bit more... states & diagram match
… you expect to use the GitHub projects, correct?
<kaz> project-management.md document
Ege: Yes, but I am open to other tools as well
Luca: As long the tool allows to export data it is fine
… I remember that I have seen a way to export stuff
Ege: It seems CSV export is possible
Kaz: the step number is useful for understanding the diagram (2, 4 and 6 is part of 1)
… maybe it can be 1.1, 1.2 and 1.3 or so
EK/Kaz: step 4 is important
<Ege going over https://
Ege: are there any objections, otherwise I would like to merge the PR...
… and I would like to work on the numbering issue mentioned by Kaz
… merging PR 1977
[adjourned]