Meeting minutes
Minutes
<kaz> Apr-24
Sebastian: I scanned the minutes in advance, no big issue, only a minor formatting, kaz could you please fix this
Sebastian: any comments on the minutes?
(None)
<kaz> approved
Quick Items
IG Charter
Sebastian: we can remove this first point as we have received the required votes for the IG
<kaz> AC review results (member-only)
Sebastian: should we remove the entry point mentioned?
Kaz: IG charter base review was concluded recently and I would like to sumarrize the results
… we got 24 supports and 1 comments, the only 1 comment was from Geonovum, she suggests we add a sensor registry
… I will contact her
… we don't have any problems with the results
McCool: the sensor registry and directory are the same
IRC Client
Sebastian: there is some troubles with the new IRC Web client, and that it frequently gets disconnected, how do we solve this situation?
McCool: I suggest we live for it to now, we can use the old version, the new version is annoying with connecting. Lets communicate this, and I suspect it will be a short term issue
Kaz: if you have a problem with IRC client give me the environment you are using, I can contact the system administration team
Daniel: I just kicked out again, I didn't have an issue with the old one
McCool: I am guessing daniel has faster timing out, we should communicate this immediately with system team and so they increase the time out, and that they can relatively fix it easier
Sebastian: probably it depends on the browser used
Kaz: after the meeting let me know if you have issues
Errata
Sebastian: Ege can you please provide context here
<kaz> WoT Thing Description 1.1 REC
<kaz> errata
Ege: In all our REC documents we have a link called Errata. We did not pay enough attention to the correct way of submitting an errata
… we don't have the correct labels set, if we have that label this page has a script running and will automatically populate it
… first of all we should all be aware of this policy that we don't use
<Ege> w3c/
Ege: the problem is that if we blindly follow this, all TD version erratas will pop up in this list
Kaz: I agree with Ege to document the errata management policy
Daniel: I have two points, it is not sufficient to document the errata procedure and we need more work. Second point, we can easily drop this kind of mechanism, there is a script we can use, makes sense if we have many issues, but currently we do not have many erratas, we can currently edit the HTML.
Kaz: I agree, and during the TD call I suggested that we should think about out errata management, and then think about how to resolve our problems with potential tools. Meanwhile we can update the errata document manually if needed
Ege: I am not proposing to fix the scripts, in any case we need to use the labels in Github correctly, because everyone can submit an errata
Sebastian: the TF leads can provide an errata, and not a random person?
Ege: W3C members can, not random persons
Kaz: that should be a good starting point
Sebastian: we still don't see Michael Mccool in the call back, due to network issues, so we skip his question for now
TPAC Group Meeting
<kaz> Events Team announcement (member-only)
Sebastian: We need to decide whether we want to participate in TPAC meeting
… we have to discuss how much time we need, and whether we want to go to TPAC
… what to others think about this?
Kaz: Thank you for the information. This year is a special year for W3C, because it's the 30 year anniversary
… many people are wondering about extending the AC meetings, which means the meeting time for us could become shorter
Sebastian: I would support to have a meeting, many companies still have travel restrictions, and my proposal is to do this in the same mode as we did in the last TPAC
… since TPAC will be held in US, meetings in the morning would be more suitable, we need to decide this
Kaz: the deadline 20th May, by end of next week we need an initial availability of people. We can make a wiki page to check this
ACTION: kaz to create a wiki page to get people's availability for TPAC 2024
Sebastian: Kaz can you make this wiki page plaease to get an overview about who will be able to travel/remote
Kaz: yes
Notice
Sebastian: Currently no notices from my side, anything from the others?
(None)
Meetups
WoT CG
Sebastian: yesterday there was a CG meeting regarding semantic digital twins from UPM
Ege: the slides will be available soon, the interesting part was about aggregation of things and having more relationships. The relevant feedback for us is how we do links. In a concrete TD example, it looked a bit weird and the TDs did not look that usual
… next week we will be having the next one, about solid
Sebastian: maybe we should invite Tim Berners Lee to the meeting
… maybe we can discuss this in TPAC and in a breakout session
WoT JP CG
mizushima: we plan a use case event, we discuss about it in community groups but we haven't decided yet when the use case event will hold
Sebastian: so you are looking for a date:
mizushima: yes
Sebastian: we were discussing a Node-Red WoT extension, it was from a Japaneese guy, maybe we invite him to the JP community group
Meeting schedule Changes
<kaz> Cancellations
Sebastian: tomorrow there is a public holiday in Germany, no TD call
… in May 20 and 30 there will be also a public holiday in Germany
… this means no marketing call and TD call on May 9, and no marketting call on 20 May
Publication Schedule
Sebastian: Currently we do not have any updates here
Binding Templates
Ege: We agreed to publish a new WG note in the binding template
<kaz> wot-binding-templates Issue 362 - New WG Note Publication
Ege: I prepared a pull request today and we will basically have a look at it in the TF, and have a 2 weeks resolution time
Sebastian: please use the time to review the new note document so that we can publish the updates soon
<kaz> TD TF resolution
Kaz: normally have a 2 week review time
Ege: I will send an email for the review meeting later
TF Discussion
Profile
Luca: we need more people to attend the profile meeting, so far we made a little progress, I hope that all the implementation details regarding Profile 1.0 get sorted
… since you are organizing a plugfest soon, we would like to see how Profile can work in the implementation
Sebastian: Please take the chance to attend the discussion in the profile calls, if you have a conflict, please write Luca and maybe it's possible to find a new slot
Kaz: In addition to call-for-participation, we should think about how we organize the bigger issue on what the profile document should describe. I think having dedicated discussions during Profile calls or potentially during the meeting in June would make more sense instead of Github issues
… we probably need Ben and Michael Legally
Sebastian: If someone would like to take over the security and discovery calls, please write us and show the interest
Discovery and Security
Sebastian: We are looking for new TF for security and discovery, the candidate should send an email, it will be discussed in May 22 main call
JSON Scheme
<kaz> Ege's input for the strategy issue
Ege: during the previous meeting, we agreed as the whole group about JSON Schema usage with WoT WG. The overall idea is that W3C allows us to reference JSON Schema as a normative document
… a process document has been published, but we haven't received feedback from the W3C
F2F Planning
Sebastian: It was already communicated that we will postpone the WoT@Industry from June to November
… there is two options, I will share a slide with you to see what we are planning
… we need to select the best dates here, 18-20 Nov or 25-27th November
… originally it was planned to go to Berlin, but now Siemens has a new building in Munich. The event organiser suggested lets use this place
… showed some pictures of how the siemens location in Garching looks like, in the same building we can also hold a plugfest or a F2F meeting, or even both
… there is also a good opportunity for hotels close by and it is relatively cheap
… about the date, I would personally propose the 25-27th Nov, because it is close to Christmas and we have the opening of the Chriskindmarket
… on 25th and 26th we can organize a plugfest, and 27th the WoT@Industry, we could also use the 28th and 29th for the F2F meeting
… if you would be nice if you already mark these dates as a potential travel time, and hopefully we can finalise the planning
… any questions?
Kaz: thank you for the information, I was about to create another wiki page for the TPAC and june meeting. We can reuse the F2F wiki page and add the june event and TPAC to it
<kaz> 2024 WoT f2f planning wiki
Virtual WoT F2F in June
Sebastian: would be nice to have a plugfest in June to speed up the work in the WG
… we can already clarify two weeks before that 2 new features to the TD or prototyping the profile. we should discuss this here to speed up the progress. What do you think about this?
Kaz: I think holding a plugfest might make sense, but we should clarify our viewpoint, e.g., binding templates, profiles, or so on should be clarified
… lets ask people to put their ideas on the wiki
<Tomo> +1 for kaz
Ege: will the event be open to others outside?
Sebastian: can we welcome developers who are not member of the W3C
Kaz: we can invite anybody, lets also put this also on the wiki as part of the idea generation
Cristiano: it says it is a virtual event but also mentions physical?
<kaz> F2F planning wiki
Sebastian: completely remote, people who work close together can meet locally, though
WoT Resources
<kaz> wot-resources PR 21 - sync ontologies with td repository
Ege: there is a PR that needs to be merged, sync ontologies with the TD repository
Sebastian: are you asking for resolution in the main call?
Ege: it is syncing the resources with the ontologies
Sebastian: shall we postpone to next week?
Ege: yes
<kaz> [adjourned]