Meeting minutes
Logistics
Kaz: maybe you should split the agenda wiki content into several pieces based on the year like the main wiki
Cristiano: agree
Minutes
approved
PRs
PR 524
PR 524 - Update text and examples regarding the fetching of TDs
Cristiano: Jan, could you explain?
Jan: mostly cleaning up
… we had discussion around "fetch"
… explain the rationale at an appendix
Cristiano: let's see the changes
Kaz: "fetching" converted to "requesting"
Jan: wording change
Cristiano: (shows Appendiex A.2)
A.2 Requesting and validating a TD
Kaz: As I mentioned the other day, we should have an Editor's Note describing why we added these changes around section 5.1 (on "Fetching" => "Requesting")
Cristiano: let's merge this PR 524 itself, and then create an issue
Kaz: that's fine
PR 489
PR 489 - Better types for Scripting API
Cristiano: would like to skip this because need some more updates
Issues
Issue 529
Issue 529 - Clean-up Scripting API wiki page
Cristiano: proposal from Daniel
… Kaz also mentioned similar ideas at the beginning of this call
Daniel: like the Marketing wiki
… the Scripting wiki should have the information only about this year
Kaz: would suggest we simply one page for one year and put old content to that yearly page
Daniel: just copy over the old content
… can do that later offline
RESOLUTION: Scripting TF also will put older content to yearly subpages like 2023, 2022, 2021, ...
Cristiano: after Daniel has done that, let's close Issue 529
Issue 528
Issue 528 - Add support for URI variables to exploreDirectory method
Cristiano: use case description to be written
… we can work on the use case description
Jan: wanted to ask if the "Use Case" to be included in the Use Cases document on the wot-usecases repo
Kaz: think we as the whole group should start with some Use Case description within the Use Cases document
… the extract requirements from the use cases
Cristiano: we can make contribution but maybe lower priority
Kaz: that kind of policy should be discussed during the use cases call and partly the main call too
Daniel: agree we should start with the use case description
… but probably we need to think about use cases handled by the use cases document and another use cases handled by spec TFs
Cristiano: yeah
… but don't want to talk about the procedure now
… we can propose our ideas to the Use Cases TF
Kaz: right
… so we need to clarify the procedure as the whole WG/IG
Jan: (describes the proposal a bit more)
… exposed to the user
… maybe some access limitation would make sense
Zoltan: URI Variables should be optional
… URI Variables are standardized by HTTPS. right?
… we should provide some standardized range of the variables too
Cristiano: good point
… want to add a label to this issue
… (adds "use case" label)
Jan: would like to work on some use case description then
Cristiano: yeah
… but that depends on the Use Cases TF's activity
Kaz: the Use Cases TF will restart the day after tomorrow on Wednesday
Select important issues
Cristiano: would like to skim all the remaining issues again
Kaz: we should clarify some criteria like a need for actual system implementations and deployment
… from that viewpoint, issue 200 would be "important"
Cristiano: yeah
Kaz: we should record that criteria first before diving into concrete issues
<JKRhb> +1
Kaz: resolution on the minutes would be fine
<cris__> proposal: Scripting TF would like make Issues important ones when they have need for actual system implementation
RESOLUTION: Scripting TF would like make Issues important ones when they have need for actual system implementation
Issue 200
Cristiano: from the viewpoint of the need for implementations, this is important
Kaz: agree
Cristiano: would add a label for "use case"
… and "priority: high"
Issue 352
Issue 352 - Next charter topics
Cristiano: would propose to close this issue because this was a generic need and we're already getting new concrete issues
Daniel: ok
Cristiano: will close this when we've confirmed it's redundant and obsolete
Issue 193
Issue 193 - Should writeProperty() return a value
Cristiano: a long-standing issue
… discussion during the TD call in 2021
… need use case and add "use case" label
Kaz: what about the next steps?
Cristiano: visiting issues with "for next iteration" label first
… and then the other remaining issues
Kaz: ok
[adjourned]