Meeting minutes
Agenda
Ege: Agenda got a little bit shorter
… we don't include PRs anymore they are hosted in the project table
… reminder tomorrow is cancelled
README updates
<kaz> PR 2016 - Readme alignment
<kaz> rendered README.md
Ege: one organizational thing is about README update
… I created a PR that align the readme to the format
… declared in the general template
… I removed a TAG review link
… a note from July 2023
… rename a section to Publications
… one open point is the labeling convention which is not yet finished
Cristiano: about the labeling conventions you can use the github page dedicated to list all the labels
Ege: I want to mention categories and give more explanation later
Daniel: I didn't have time to review it before the call, there is a space missing
Kaz: good direction thank you
Ege: ok merged
Minutes review
<kaz> May-8
Ege: we already reviewed them
Ege: any objections?
Ege: none, minutes approved
TD errata
Ege: we had a resolution in the main call to remove the script in the html file
… if you go to the errata.html file
… you can fine at lines 11 12 to scripts that we will remove
… see the related issue
Toolchain discussion
Ege: last week we talked about the toolchain and to create a short round of people to work on it
… currently we are Mahda, Cris, Luca, Jan and myself. If you want to join we are using the TD zoom call
… we noticed some issues and did some fixes
… typescript generation does not really work
… json schema generation is broken too
… we are working on this issues
Binding note review
Ege: last week I've sent an email with a call for review
… in the main call we confirm the resolution to publish the binding Templates
… the review is until next week
… right?
Kaz: asked to McCool for confirmation
<kaz> Issue 364 - Figure Improvement and minor bug
Ege: following up on this, daniel created one issue
… please create them now
… don't be afraid
<kaz> figure 2 from Binding Templates
Ege: it seems that the second point mentioned in the issue is not a problem
Daniel: right I was wrong
Kaz: given we have already sent the call for review (and made the resolution in the main call) we should let people know about the change
Ege: sure we mentioned it in the changelog
Kaz: but also sending a email
Ege: ok
Thing Description
Ege: we can remove a bunch of draft items
Ege: last we week we identified a set of issues to fixed quickly
… they are all under the in progress column
… try to do the work when you have time
Cristiano: with this layout is not easy to understand if a issue is ready for review
Daniel: can't we use draft PRs for that?
Ege: they show in the column with a different color
<kaz> WoT TD Project
Ege: but we should not see PRs in that column
… only issues
Daniel: they can be useful to understand if the work is done or not
Ege: yeah.. but it duplicates items
… I would be fine to have another column and keep everything on the issue level
Koster: done will just keep getting bigger and bigger
… the in-review column is even more helpful
… things will not be reviewed right-away
… we can even remove done or rename it in-review
Kaz: done means merged in closed so I agree that is really helpful
Ege: ok then just delete the done column and add in-review
Issue 1878
<kaz> Issue 1878 - Wrong id for a security example
<kaz> PR 2015 - refactor: use proper ids for examples in Multiple Security Definitions
Ege: this editorial change
… it fixes some of html ids
… in the examples
… there should be no real diff
Daniel: I also double checked if there was some reference to that id
… I couldn't find any
… merged
Ege: noticed that the project is not updated correctly when you close the issue
… I'm adding a new workflow for automation
… but it seems I can't remove the card automatically
… I can only move them to a column ("Done" column with hide setting)
… I'm adding a done column that is not visible in the view
issue 1957
<kaz> Issue 1957 - title reference is not correctly linked
<kaz> PR 2014 - remove title id from static files
<kaz> Issue 2013 - Holistic id definition rules
Ege: the PRs removes the titles in the ontology files
… id in title
… we don't have a solution for 1.1 and 1.0
… we can't change the id because it will break the link
… is it fine ?
Luca: I would consider that the main part is that respec has a bug.
… it is something that should be fixed in respec
… for the PR itself, removing the id after the fact, for now it is fine
… but respec needs to be fixed and somebody needs to open an issue in there
Ege: agree
Cristiano: +1
Ege: what should we record in the issue?
Luca: respec should understand that the context of the ids
Ege: it is not respec
… it is our tooling
… the problem is the toop level title generated by respec
Luca: understood, then respec should try to be smart
Daniel: I would open an issue with two options: respec check for coflicts/collisions and at least emit a warning (or even generate a new id)
… or it could autofix it
Jan: Or maybe you can add a configuration option to manually find it or generate it
Kaz: class=title is required by the CSS for recomendation, you can also use the html validator
Ege: the validator actually find the problem
… we should have used it before publication
Ege: ok pr merged
Issue 1885
<kaz> Issue 1885 - Documenting that td-context-1.1.jsonld refers to JSON-LD spec version
Cristiano: I got some ghost changes, shoud I remove them?
Ege: yes
Ege: looking good
Issue 1818
<kaz> Issue 1818 - Better explain difference between observable properties and events
Ege: we are overtime I'll look into it after the call
Jan: great, I put one or two questions in the PR body.
[ajourned]