Meeting minutes
Previous Minutes
<kaz> Apr-24
<cris_> suggest I think we over the issues I wanted to discuss
Cristiano: Could please expand the names and fix the sentence above
Cristiano: Ok with the minutes amended?
Scripting API on the next charter
Cristiano: Do we have any action item pending on this regard?
Cristiano: We can check the previous main call minutes to make sure, but
… in the next charter the Scripting API will not be normative.
PR
PR 462
<cris_> PR 462 - Update README.md with versioning information
Cristiano: I try to explain the relationship between the packages versions
Cristiano: Any concerns about it?
Zoltan: we should establish criteria on when release 1.0
Cristiano: Consensus on merging?
merged
PR 473
<cris_> w3c/
Cristiano: this PR has issues to be addressed
Cristiano: There are problems with the Pubrules checker
Kaz: The problems seems that we cannot get the response from the checker itself
… usually those problems happen when the document is not valid html
… we should apply the checker to the static html once we are sure it is valid
Cristiano: PR updated with the suggestions
Kaz: The procedure should be already documented in the repository README.md
<kaz> README.md about "How to edit the draft for publication" within wot-thing-description repo
Cristiano: It seems missing currently
Issues
Issue 465
<cris_> Issue 465 - Check if record is better than map
Cristiano: It should be solved by the PR 469
Issue closed
Issue 466
<cris_> Issue 466 - Check pair vs tuple usages
Cristiano: Also solved
Issue 427
<kaz> Issue 427 - Consider aligning with IntersectionObserver
Zoltan: The issue can stay open since we may reconsider as the web platform evolves
Issue 470
<cris_> Issue 470 - Update listener internal slots to map<name, structure>
Zoltan: We should doublecheck the document. Until then we should leave it open.
Issue 471
<cris_> Issue 471 - Update the "expand an ExposedThingInit" steps wrt security definitions
<kaz> Editor's draft - 6.2.1 Expand an ExposedThingInit
Luca: We should make clear that the Scripting API is focused on Typescript or try to rework the note to fit additional languages better?
Zoltan: This specification was focused on being a web-specification
<Zakim> dape, you wanted to we have browser implementation
Zoltan: the algorithm presented should be useful on other languages, the api itself might not fit, but if there are inconsistencies in other languages we should open issues
Kaz: I agree with zk
… we are using the document to provide an example on how to implement the algorithms. So what is more important from my viewpoint is that we need to clarify how to expand the capability of ExposedThingInit based on some concrete use case scenarios a bit more, e.g., when, how, who to handle what.
Cristiano: We can improve the introduction section to explain the document purpose
Backtrack
PR 473
<cris_> w3c/
Cristiano: Daniel is now available
… do you have anything to add regarding this issue?
Daniel: I need to try again with the REST api and check with Kaz
Kaz: My suggestion is to first generate the static html and then feed it to the checker
Daniel: I'm already running the checker on the static html
Kaz: Let's try to rework the PR to first create the static html and then add the improvements on top of it
Cristiano: We can land this PR and open a new issue to address the problem separately
Cristiano: merged
<kaz> [adjourned]