WoT-WG/IG – 08 November 2023

Meeting minutes

New Members

McCool: Kaz already on-boarded the new member
… Kudzai Manditereza
… from HiveMQ

Kudzai: HiveMQ around since 2012
… we provide MQTT broker
… joined WG last month
… interested in MQTT binding
… have open source software where we would like to integrate WoT

McCool: I suggest to also look at MQTT discovery ..besides binding
… welcome!

Kaz: Thank your for joining and welcome!

<sebastian> welcome Kudzai :-)

Minutes

-> November-01

McCool: Any objections to publish minutes?
… -> none -> minutes approved

Notices (Information only)

McCool: FYI, IIWoT 2024 Workshop - Jan 6 2024

Quick Updates

Smart Cities update

<kaz> Nordic Chapter Smart City CG

Kaz: Daniel Dersen (W3C Nordic Chapter Evangelist) contacted me
… about Nordic Chapter Smart City / Web of Things CG
… They want me to join their CG's meeting on Nov 27 to discuss Smart Cities at W3C
… will report back

McCool: I would like to join as well
… W3C calendar entry might be useful

Kaz: calendar entry should be available

McCool: call themself " / Web of Things CG "

Kaz: Maybe kind of too broad :)
… getting potential new members

McCool: consider adding them to IG charter
… join call on Nov 27 as well

RDF Dataset Canonicalization

https://www.w3.org/TR/rdf-canon/

McCool: now a Candidate Recommendation
… we should review it
… it says implementations welcome
… there seem to be 4 implementations

Marketing

McCool: Marketing TF wants to discuss some points

Ege: we discussed GitHub Topic curation in yesterdays marketing call
… topics on GitHub can be curated
… shows a little landing page
… there is not a thing for web of things
… no landing page
… we would need to create PR to specific repo etc
… did that with JSON schema recently
… did an initial version
… we need to agree on some fields
… like name, aliases, ...
… we need to decide on created_by and url
… shall we associate it with W3C?

McCool: do we mean "web of things" or W3C web of things
… I am okay with "web of things"
… we should allow to integrate others
… need to talk to Marcom team
… "wot" is too generic

Ege: anyone can add topics
… we can just propose it

Kaz: We should think about if we really want to do it
… not every nice GH feature is useful for us
… some parts in the end would not be related to W3C
… I don't recommend doing it without clarifying the mechanism a bit more

McCool: I am concerned that everyone can use the topic also

Ege: at the same time anybody could create the topic

McCool: If we do it... we have somehow more control

<Mizushima> +1 kaz

McCool: I think we can define a topic for "W3C Web of Things"
… marcom should agree also

McCool: We can define both tags .... web-of-things and W3C web-of-things

Kaz: W3C is interested in branding ... but it is also delicate for "Web of Things"

McCool: Web-Assembly do that aleady
… anyhow.. I suggest to talk to Marcom first

Kaz: Agree

Ege: I see, we should get better understanding
… 2nd topic
… about marketing minutes

Kaz: we should clarify what do do with some meeting minutes ... from non official part

Ege: we don't really have minutes
… we just collected some notes

Kaz: Do you want to publish the HackMD notes?

Ege: not really

Kaz: First meeting of the month is recorded on IRC ... and already public

McCool: Chairs minutes are not public.. we can do the same for the non official marketing meetings

Meeting Schedule Changes

McCool: not aware of any conflict

Kaz: due to Nordic CG meeting I have a conflict ... on Nov 27

McCool: we gonna cancel discovery call this day
… security call canceled on Nov 6 and 13

Mahda: I am aware next week.. just not this week

McCool: Will try to uncancel the discovery meeting for Nov 13
… BTW, US time and EU time are in sync again... Japan is on winter time

McCool: Reschedule TD call ?

Ege: Will send email

McCool: suggest 2 separate calls for TD and binding

Kaz: I let Ege know about my availability
… difficult to find better slot .. if we avoid existing calls

McCool: Could look at alternate calls also?
… but I am not convinced
… for e.g., using security call

Kaz: Which of the other task forces would like to change their slot?

McCool: Not that many at the moment
… we can use chairs call
… but we should have it on Tuesday .. before main call

Ege: Security can be moved?

McCool: Maybe ... depends on Mahda's schedule also
… slot after chairs calls should be avoided also.. OPCUA call
… suggest Ege to propose some slots

Planning for New WG Charter Period

IG Charter call is today

<McCool> proposal: 2h call on Nov 15 to include 1h to discuss policies.

Policies

RESOLUTION: 2h call on Nov 15 to include 1h to discuss policies.

McCool: Suggest 2 hour call next week

Project management

McCool: waiting for management..

Kaz: Yes, still waiting

Open Day/F2F/Plugfest

McCool: Proposed: Berlin, June 2024

Recommendations

McCool: Double-check: are we ready

New Process Document

Kaz: BTW, the W3C Process Document has just been updated, so need to regenerate the static HTML

McCool: Just for TD ?

Kaz: No, all of the three specs (TD, Discovery and Architecture)

Ege: will look into that for TD

TD

<kaz> TD meeting on Nov 2

McCool: 4 editorial fixes have been merged ?

Ege: Yes

Ege: ontology fix and figure fix

McCool: resources updated also?

Ege: no, will do that later in one go
… Pr 1911 updates readme about figures
… PR 1913 ... tool-chain is not correct... spec text is/was correct .. just the figures were not

McCool: some important terms were missing

Kaz: Maybe we should mention the basic issue: The automated script was wrong to get correct figures from the TTL files.

McCool: Yes, we can consider figures editorial bugfix

Ege: w3c/wot-thing-description#1913 (comment) mentions issues that have been fixed

McCool: This PR has been already merged
… last PR 1912 not yet merged
… w3c/wot-thing-description#1912

Ege: It fixes TM regex
… regex feature is not supported on all platforms
… changes still does validation

McCool: compatibility issue ?

Ege: yes

McCool: I am ok with the change
… any objection?

<McCool> proposal: accept change in TD PR#1912 to address validation compatibility issue; will update resources

Cristiano: In TD call we talked about the opposite, right ?
… it is not our problem solving implementations ?

Ege: Yes, but this is a fix that support all (most?) libraries

<McCool> proposal: accept change in TD PR#1912 to address validation compatibility issue; will update resources

RESOLUTION: accept change in TD PR#1912 to address validation compatibility issue; will update resources

McCool: Ege please go ahead to merge

REC transition resolution for all the three specs

McCool: Ege, is TD draft for REC ready?

Ege: Yes

McCool: likewise Discovery and Architecture are also ready
… hence I suggest to move on with the Recommendations

<McCool> proposal: Proceed with REC transition as soon as possible for Thing Description 1.1, Architecture 1.1, and Discovery after update to the Nov 3 process document link.

RESOLUTION: Proceed with REC transition as soon as possible for Thing Description 1.1, Architecture 1.1, and Discovery after update to the Nov 3 process document link.

Related resources like Ontologies and Schemas

McCool: feedback from PLH ?

Kaz: PLH very busy, will ping him again
… need 1 week for transition

McCool: Okay than I suggest to publish the resources
… we need to tell Ege that resources should be updated
… press release and REC should come out mostly at the same time

Kaz: REC transition request review usually takes 1 week.. but might take a little longer. So let's submit a transition request once the REC drafts are ready.

McCool: We should just make sure that press release comes out after REC

Kaz: Yes

McCool: I think we should proceed with resources ...

Koster: I can mention it in the TD call

Press Release

McCool: Are we ready?

Sebastian: My latest status is that everything is now on GoogleDoc for further review
… still looking for more testimonials

McCool: Okay ... that we are in process..

Sebastian: Correct

<kaz> [ first part ends; second part starts in 10 mins ]

New IG Charter

Logistics

Koster: we do not have much time anymore in this current IG charter

Kaz: we should start with the existing PR which generates the latest draft Charter

Koster: seems the PR on wot repo has been closed... I've moved the draft IG Charter from the wot repo to the wot-charter-drafts repo. So let's see the draft Charter on the wot-charter-drafts repo.

<kaz> draft IG Charter

<kaz> rendered version

McCool: I created some issues what we have to do

<kaz> IG 2023 Charter issues

Chairs

<kaz> Issue 130 - Add Michael Koster as proposed chair

McCool: no time yet to work on this issues

Policy and Procedure

Kaz: we should clarify procedure and policy before
… I'm ok adding Michael Koster as co-chair, but we should clarify our policy and procedure a bit.
… for example, anybody can add any issues based on their ideas, or we have some preliminary brainstorming before creating actual issue during this call.

<kaz> s/as co-chair, but we should clarify our policy and procedure a bit/

McCool: anybody can create an issue, while creating a PR is a group decision.

kaz: OK. That can be our basic policy, and let's record that so that people can give concrete input.

Koster: we can prioritize the existing issues today

Koster: lets start with the mission statement

Kaz: we can scan the sections from the current draft and see if there is anything missing

mm: thoroughly tried to generate the GitHub issues for each section :)

kaz: in that case, let's look into the issue one by one and assign somebody to work on concrete PRs

Mission

issue 120 - IG Charter 2023: Update Mission Statement

McCool: the mission statement is not really appropriate what the IG is doing

Koster: agree

McCool: the text should say that IG supports the WG in its goals

Kaz: agree, the current mission statement is more for the WG rather IG

<kaz> [assigned to McCool]

Background

<kaz> Issue 121 - IG Charter 2023: Update background

McCool: we should mention that there are version updates

McCool: The first paragraph in Section 1 looks good

<kaz> [assigned to Koster]

Scope

<kaz> Issue 122 - IG Charter 2023: Update scope

Koster: its strange that IG runs the PlugFest, but content is managed by the WG

McCool: PlugFest is more exploring, TestFest is more checking the spec
… we should seperate this. PlugFest belongs to IG, TestFest belongs to WG

Sebastian: I'm ok with the split, however, we should be aware that we also invite non-w3c members to PlugFest and TestFest. Wondering if this still possible to do

McCool: Testing is WG responsibility. we can still report results from PlugFests

Kaz: I'm also ok with the seperation.
… we should clearly define what is meant by PlugFest, TestFest and Testing
… we need also update the diagram in the charter about the relationship between IG and Wg

<McCool> (time check - 3m left)

<kaz> relationship diagram

<kaz> [assigned to Koster]