– DRAFT –
WoT Plugfest/Testing

Minutes

<kaz> Feb-8

McCool: we agree at the end of the meeting to to update the 27th
… more typos fixed

no objections to publish

Quick updates

Playground update

Ege: Playground update, TM support
… Validation of the TD using the fully expanded TM
… To be used in the TestFest

McCool: Impact on people reporting manually

Ege: No problems

Ege: Problems with stable url though

McCool: Stable url are a problem

McCool: Experimenting with ip cameras
… Adding rtsp support to camera object
… rtsp is universal for ip/security camera

Luca: RTSP verbs have both mapping to property or action

McCool: Offline discussion about protocol binding for it

Kaz: 2 comments or maybe questions
… ip camera as item for potential plugfest in the next charter

McCool: Important for AI
… input for future work

Kaz: Can we make a report from the previous testfest. Given we've got updated implementation reports, we can summarize the situation with links to those implementation reports at the end of the Testfest page.?

McCool: It can be future work
… for the next agenda

Ege: I have past experience with streaming as well

McCool: RTMP is not fully standardized

Luca: it does have a standard though

McCool: RTSP is more widespread for the IP camera

McCool: MATTER might focus on HLS/DASH

Kaz: It could be a potential topic for the next charter

McCool: Agreed to make an issue about it for the next WoT WG Charter

<kaz> s|(MEETING TITLE)|WoT Plugfest/Testing|

<kaz> wot-charter-drafts issue 60 - Streaming

PR & Issues

McCool: 4 PRs

PR 535

<kaz> PR 535 - Add CoAP and UDP-related DNS-SD assertions to Discovery template.csv file

McCool: fixing things in Discovery for DiD regarding the assertions in the spec
… some results to be updated
… merge it and look at refining in the Discovery meeting later

PR 534

<kaz> PR 534 - Add manual.csv for DNS-SD CoAP implementation

McCool: another one is fixing the template and updating the results as well

Jan: Just joined

McCool: I prefer if Jan fixes the PR to concatenate the two csv

PR 533

<kaz> PR 533 - Update DRAFT-atrisk-explanations.md

McCool: This one is related to the developer meetup
… leave it open and work on it further with Lagally

<McCool> https://github.com/w3c/wot-testing/pull/533/files

Lagally: Agreed

PR 528

<kaz> PR 528 - Jan 2023 Result Updates

McCool: The last one will be fixed soon as well

Developer Meeting

<kaz> Developer Meeting logistics

McCool: Change the meeting date to the week of March 27
… Doodle missing

Kaz: I will set up one today

McCool: Week of 20th open for the TestFest
… 2-3 Days of TestFest and focus on Profiles
… include both 20th and 27th in the Doodle

<kaz> s/data to/date to/

McCool: An explanatory document for the At-Risk items
… is needed

<Ege> wot-thing-description PR 1758 - Updating at risk assertions in the main body

Ege: Update the TD spec section

McCool: The document should be a stand alone md
… objectives for the developer meetup
… one purpose is having more developers
… the other is receive feedback from the developers
… less focus on promotion and more on gathering feedback
… focus on finalising the current spec
… the md files should help experienced developers in reporting assertions

<Zakim> Ege, you wanted to react to Ege

Ege: More about talking with developers than advertising

McCool: Do not post on twitter but have a targeted list of developers

cris: Why are we limiting it to implementor, we could expand to newcomers

McCool: We have 1 hour for a large amount of items

McCool: Better to cut down to a narrow scope
… other meeting for newcomers

Kaz: agree with McCool, and think we could clarify also the name and scope of the meetup

Kaz: maybe Testing Meeting or Assertion Meeting? Assertion

McCool: Let's call it "Assertion Resolution Meeting" then.

McCool: Making a list of developers to invite
… first who already presented their implementations
… then SDO collaborators
… e.g., ECHONET

Ege: Who maintains implementations

Testfest

McCool: We target March, let's capture some input

Ege: We have a CG meetup 23rd March as well, avoid conflict

<Ege> https://www.w3.org/groups/cg/wot/calendar#card-e72912b5-3087-440e-950e-886acbab645d is the conflict

McCool: Week of the 20th, 2-3 days
… 1h per day
… use the Doodle from the devmeeting to avoid conflicts

Kaz: Maybe we need yet another Doodle for this Testfest as well.

McCool: One for 20th and one for 27th

ACTION: Kaz to generate two doodle polls, one for Testfest during the week of March 20 and another for Assertion Resolution Meeting during the week of March 27

<kaz> [adjourned]