Meeting minutes
minutes review
<kaz> Jan-31
Ege: minutes approved
agenda refinement
<kaz> agenda for today
Ege: can we extend the time slot by 10 minutes when we start late?
Kaz: We could extend, but the suggestion is to structure the agenda to end meetings 5-10 minutes before the hour
Ege: propose to move the issues to the backlog
… also move the list of protocols in the binding section to the backlog
TD
PR #1966
<kaz> PR 1966 - SHACL validation errors
<kaz> related Issue 1345 - Wrong validation errors with SHACL
Mahda: this PR addresses 2 issues listed in the comments, some of the issues are out of date
… one issue is SHACL validation around the title property
… SHACL playground is not maintained, using pyshacl now
… to fix, made the title required to be a language string or a string
… another problem is the dataschema was a string literal and needed to be an IRI
… TDs converted to triples aren't rdf thing class
Ege: TMs are rdf thing type
… should we mandate @type rdf:thing for TDs also?
Daniel: we may need to open an issue on the rdf processing
Ege: this issue isn't complete, we need to look into the tooling more
Luca: why is this required?
Mahda: SHACL shape validation rules only validate instances of type thing
… type thing can't be inferred
Luca: can we have a default?
Mahda: doubt it
Luca: we need some way to process TDs without requiring JSON-LD
Ege: maybe there is a mechanism for defaulting, otherwise existing TDs would be invalid
PR #1965
<kaz> PR 1965 - Reorganize Versioning document
Ege: please look at this PR for review tomorrow
PR #1176
<kaz> wot PR 1176 - TD Planning: First actionable roadmap
<Ege> https://
Ege: the proposal is to work on document refactoring and tooling while the use case development is in progress
… are there other suggestions for work items?
Ege: any issues with merging?
… we can discuss the items tomorrow
project management proposal
<kaz> project-management.md
Ege: reviewing the figure
… any comments?
use case discussion
<kaz> tf-issue-process.md
Ege: has everyone done the issue labeling?
<Mahda-noura> +1
Koster: has not yet
Ege: the decision was to do the work in the TD task force, then transfer to the Use Case TF
Ege: we will filter out the Use Case issues and work on the remainder of the issues first
Ege: was there discussion in the UC call about this?
Kaz: there was general discussion about policies and procedures
… there will be an issue created in the UC TF for how to handle feedback to the other task forces
<kaz> Ege's message archvied on team-wot (Team-only)
* Michael Koster: In TD Repo, Page 2. Issue 1875 to 1751. Page link for now:
https://
* Mahda Noura: In TD Repo, Page 3. Issue 1749 to 1567. Page link for now:
https://
* Tomoaki Mizushima: In TD Repo, Page 4. Issue 1559 to 1395. Page link for now:
https://
* Jan Romann: In TD Repo, Page 5. Issue 1394 to 1233. Page link for now:
https://
* Luca Barbato: In TD Repo, Page 6. Issue 1231 to 1078. Page link for now:
https://
* Kunihiko Toumura: In TD Repo, Page 7. Issue 1076 to 933. Page link for now:
https://
* Cristiano Aguzzi: In Binding Repo, Page 1. Issue 342 to 239. Page link for now:
https://
* Daniel Peintner: In Binding Repo, Page 2. Issue 226 to 124. Page link for now:
https://
* Ege Korkan: In Binding Repo, Page 3, TD Repo Page 8. Issue 121 to 8 in Binding Repo,
921 to 2 in TD Repo. Page links for now:
https://
and
https://
Kaz: can we send the request to the member mailing list also?
Ege: are there any issues that came up in the labeling we need to discuss?
Issue 1394
<kaz> Issue 1394 - name and in fields for BasicSecurityScheme and DigestSecurityScheme needed?
Jan: one issue regarding the security refactoring
Ege: added
expectations from the use case process
Ege: what do the users of TD expect from the use case process?
Luca: it will prevent gaps in the delivered specification
… there is a marketing use in exposing solutions to problems
… for developers of the spec: use cases => requirements => features
… we should not need to go back to use cases once requirements are defined
Ege: we could require a new use case if the requirements are incomplete
Kaz: as the TD task force, we should identify which stakeholders are our target, and work out with the UC task force
Ege: any other topics or comments?
… next week we invited Ben Francis to discuss his proposal
… adjourned