- From: Kazuyuki Ashimura <ashimura@w3.org>
- Date: Wed, 02 Dec 2020 18:06:36 +0900
- To: public-wot-ig@w3.org, public-wot-wg@w3.org
available at:
https://www.w3.org/2020/11/18-wot-minutes.html
also as text below.
Thanks a lot for taking the minutes, Dave!
Kazuyuki
---
[1]W3C
[1] http://www.w3.org/
WoT-IG/WG
18 Nov 2020
[2]Agenda
[2] https://www.w3.org/WoT/IG/wiki/Main_WoT_WebConf#18_November_2020
Attendees
Present
Kaz_Ashimura, Daniel_Peintner, Dave_Raggett,
Kunihiko_Toumura, Michael_McCool, Sebastian_Kebisch,
Ege_Korkan, Michael_Lagally, Takahisa_Suzuki,
Tomoaki_Mizushima, Jennifer_Lin, David_Ezell,
Jack_Dickinson
Regrets
Chair
Sebastian
Scribe
dsr__
Contents
* [3]Topics
1. [4]Agenda
2. [5]Publication status
3. [6]Possible new slot for WoT Use Cases
4. [7]New patent policy
5. [8]input from non WG members
6. [9]ITU-T liaison statement
7. [10]Minutes from last call
8. [11]upcoming events
9. [12]Monday's joint call with IEC TC57 CIM
10. [13]Upcoming joint calls
* [14]Summary of Action Items
* [15]Summary of Resolutions
__________________________________________________________
<kaz> scribenick: dsr__
Agenda
Lagally: we should talk about the liaison statement ...
Publication status
Sebastian: where are we in respect to the publication of the
updated Architecture WD?
<kaz> [16]WoT Architecture is ready
[16] https://w3c.github.io/wot-architecture/publication/ver11/1-fpwd/
He shows the draft, Kaz is on the job for this and the other
documents
Kaz: I've checked the documents, but think we need a little
more time and aim for publication next Tuesday
<kaz> [17]WoT Thing Description has a remaining issue
[17] https://lists.w3.org/Archives/Member/member-wot-wg/2020Nov/0008.html
Possible new slot for WoT Use Cases
The WoT Use Cases call is rather too early for some people, and
we are looking for another slot
Sebastian: please respond to the doodle poll
Lagally: we should consider alternating the slots to enable
participation from people in widely spread time zones
Sebastian: we tried that in the past but it was a bit confusing
Daniel: I agree with that
Sebastian: the use cases call is every 2 weeks, right?
Lagally: yes. If we can't find a single slot that works for
all, we should consider the alternating approach
... lets set the poll deadline to the end of this week
New patent policy
The revised patent policy - we have a chance to decide whether
to keep the old one or move to the new one?
Sebastian: I will check with my company's lawyers to get their
insights
... we need to hear from others ...
McCool: we don't have to adopt the new policy, it involves work
to do so, and perhaps the easiest option is to stick with the
old policy unless we have a pressing need to change
Sebastian: agreed
Kaz: the chairs need to respond to the questionnaire for each
WG, if we do decide to switch policies we will need to
recharter
Sebastian: that makes sticking with the old policy attractive
If any company needs to change to the new policy, please let us
know
Lagally: is there a diff marked version for the two policies?
Sebastian: yes
Kaz: this should have been in the AC Members email from May
2020
<inserted> [18]diff between PP2017 and PP2020 (member-only)
[18] https://www.w3.org/2020/04/PP-update-2020-March30-diff.pdf
input from non WG members
Kaz: we're still waiting on Wendy Seltzer
ITU-T liaison statement
Lagally: shows the draft statement
We haven't yet looked at all the ITU-T SG20 documents as yet. I
will upload the relevant documents to make them easier for us
to review
Lagally: do we make the liaison documents public?
Sebastian: kaz can you clarify?
Kaz: we usually forward the liaison document to the public
list, but we can check with the ITU-T in this case
Lagally: who will do the check? The chairs or me?
Kaz: I will look after this
Minutes from last call
<kaz> [19]Nov-11
[19] https://www.w3.org/2020/11/11-wot-minutes.html
Sebastian shows the minutes ...
Any objections to making them public? [no]
Sebastian: let's also check the minutes from our TPAC meetings.
Please take a look.
Kaz: the task forces should review the minutes from their
perspective
<kaz> [20]vTPAC
[20] https://www.w3.org/2020/10/05-22-wot-minutes.html
Sebastian: we can then approve them at next week's main call
upcoming events
The IETF had a meeting on JSON Path and JSON Schema, anyone
attend?
Koster summarises the discussion and how it relates to our use
cases. The take away is that we need to provide our use cases
for their review.
McCool: do we have a contact we can reach out to?
Koster: Carsten is the best advocate I think
McCool: Okay, we can discuss this and identify the important
use cases for JSON Path
JSON Path could be quite ubiquitous in our applications
Koster: Two issues: 1) the syntax for paths, and 2) what's the
expected result
McCool: we need to look beyond discovery and also discuss this
in a TD call
Koster: Carsten wrote an initial draft for discussion in the
IETF
... the other IETF meeting I attended was JSON Schema in
relation to hackathons
<McCool> [21]https://github.com/w3c/wot-discovery/issues/100 -
issue to capture JSONPath requirements
[21] https://github.com/w3c/wot-discovery/issues/100
some discussion relating to enum and AnyOf
Koster: I advocated for the IETF spec to cover events and
actions as well as properties given that that is important to
the W3C WoT useage
some more people to support this would be helpful, the next
ASDF meeting is Dec 14/15
Koster: I will attend the CBOR meeting. There is some near
final discussion on resource directories
Monday's joint call with IEC TC57 CIM
McCool: we got some feedback from CIM group on use of SAREF and
SOSA
Two different binding conventions for properties, some
challenges with subclassing
we asked if there are any best practice guidelines
we may want to produce a WG Note on that
Some discussion about continuing involvement: as W3C Member, as
invited experts or via liaison, kaz to look into that
McCool: we need to figure out the purpose of the next call with
them
Kaz: as I mentioned during the joint call itself, I think it
would be better to establish the liaison between IEC TC57 and
WoT first
They were certainly interested in using SSN/SOSA
We could ask Victor
Koster: who are the users for SAREF?
McCool: distributed energy grids was the big use case
I think the work is still at a proposed standard level
David: listening to McCool, I strongly recommend keeping
actions and events as they are really useful abstractions, e.g.
for node-wot and node-red
Koster: that's a super good point, so thanks
Upcoming joint calls
Today we have folks from the Linked Building Data in the TD TF
On Dec 9: meeting with the APA WG
Still looking for a slot for meeting with the Spatial Data on
the Web IG
McCool: the OGC want to be part of the same meeting and suggest
a 2 hour long call
any objections? [no]
Kaz: I am checking with who want to attend from their side
McCool: let's try for December 10
we can then work on the agenda
Koster: one more report, we're working with folks on the SDF
language and some other things
<McCool> already an issue for SDWIG/OCG meeting, let's continue
to use that: [22]https://github.com/w3c/wot/issues/939
[22] https://github.com/w3c/wot/issues/939
Koster: including SI units and inconjunction with the OCF
Koster can't attend today's TD call, so we can discuss this
next week
Sebastian: anything important to share from the task forces?
Please look at the proposed new web pages and provide your
feedback
<dape> [23]https://w3c.github.io/wot-marketing/
[23] https://w3c.github.io/wot-marketing/
we want to synchronise the release of the web pages and the WoT
video
Siemens and Bosch working on a new editing project - I will
introduce that in the marketing call
Kaz: we could talk about Ege's new testing code, WoTest, in the
next hour (Plugfest slot)
<kaz> [main call adjourned; Testing call will start 10mins past
the hour]
Summary of Action Items
Summary of Resolutions
[End of minutes]
__________________________________________________________
Minutes formatted by David Booth's [24]scribe.perl version
1.152 ([25]CVS log)
$Date: 2020/12/02 09:05:37 $
[24] http://dev.w3.org/cvsweb/~checkout~/2002/scribe/scribedoc.htm
[25] http://dev.w3.org/cvsweb/2002/scribe/
Received on Wednesday, 2 December 2020 09:06:42 UTC