W3C

- DRAFT -

WoT-IG/WG

22 Jul 2020

Attendees

Present
Kaz_Ashimura, Michael_McCool, Sebastian_Kaebisch, Christian_Kurze, Cristiano_Aguzzi, Daniel_Peintner, Dave_Raggett, David_Ezell, Ege_Korkan, Jennifer_Lin, Kunihiko_Toumura, Michael_Koster, Michael_Lagally, Tomoaki_Mizushima, Ryuichi_Matsukura
Regrets
Chair
Sebastian
Scribe
dape

Contents


Agenda

Sebastian: Plan today:
... * Guests
... * Approving minutes (let's do it next week)
... * ITU-T Liaison
... * Cristiano presenting tools he is working on
... 2 expected guests
... GyuMyoung Lee from ITU-T and Christian Kurze from MongoDB
... Gyu is not here today (so far)
... Christian is aware of the W3C Patent Policy

Christian: SW solution architecture at MongoDB
... interop problems with different devices
... what does data tell me
... automation is important
... JSON-LD is important. MongoDB is JSON-based

Sebastian: Suggest inviting Christian to discovery task force

McCool: Makes perfect sense
... have already Fraunhofer solution. 2nd implementation would be very beneficial

Christian: Sounds good
... semantic search struggle nowadays once data scales

McCool: small devices support is also of importance
... discovery call, 4pm CET

Christian: Can join on Monday

Sebastian: CK is aware of W3C policy

T2TRG meeting

Sebastian: T2TRG meeting

McCool: several things were reviewed
... interesting discussions
... still some links missing
... e.g., Matthias talked about OPC-UA
... suggest defer this to next week till presentations are up

Web meeting overview

Sebastian: WoT call table
... Kaz created nice Web meetings overview
... Note: TD call is today now (not any longer on Friday)

<kaz> Web meeting overview

Koster: had issues finding the table
... might have clicked on the wrong table

McCool: Did we check TD links within all the TF wikis?

Kaz: Yes, fixed all links (also will add links from all the TF calls back to the WoT IG/WG main wiki page which includes the Web meeting overview table)

Possible new slot for the first Architecture call

Sebastian: Doodle poll ongoing about 1st Architecture call
... merge to one call?

Lagally: Several options
... extend call
... stay were we are
... shift 1st call to later time
... please fill in information

<sebastian> doodle for possible new Architecture slot

<mlagally_> Please respond to the Architecture doodle poll by the end of this week, so we have all information at hands to make a decision.

ITU-T liaison

Sebastian: ITU liaison, Gyu is not yet here
... they've confirmed the liaison on the ITU-T side
... offical liaison to be established soon

Kaz: GyuMyoung was expected to send a liaison request to team-liaisons list. he sent me the information privately and asked me to team-liaisons, so I'll do so

Sebastian: Ilyoung Chong joins use case call tomorrow to show ITU-T documents summary

Lagally: Presentation tomorrow by ITU-T fine even though the liaison request is not confirmed yet?

Kaz: Yes

<inserted> Use Case call agenda

Publication schedule

Sebastian: Schedule
... we are a bit behind schedule
... should discuss this in each task force group

Lagally: Architecture: Sept 2020 is still the plan

Sebastian: Will discuss TD 1.1 agenda for FPWD today also

WoT Application Manager

Cristiano: I am ready, no presenter right so far
... I prepared some slides
... 2 tools: WoT Application Manager and TD-code
... WoT Application Manager: helps to correctly initialize WoT application project
... node.js is the only requirement
... oriented to vscode projects
... WAM has bundling capabilities
... code completion support
... basic support for templating
... plan to add feature to download templete from GitHub
... WAM was made for node-wot
... ease the start of node-wot
... could be used for other environments as well
... Demo
... start with node installation
... "wam init demo" --> Language Selection --> name -> version -> ...
... once project is created "npm install" installs basic dependencies
... TD-code is another tool
... minimal vscode extension for validation and TD support

McCool: vocabulary extensions?

Cristiano: solve with vscode extensions, work on going
... back to WAM
... project ready, tsconfig file created
... servient config also
... td.json extension kicks in

<McCool> should capture links for tools; one option that I mentioned is here: https://github.com/w3c/wot-testing/tree/master/tools

<McCool> ... however... we might also want to discuss this under "Marketing", since this is dev tool, not a testing tool

Cristiano: code completion works just fine
... when coding similar support is given
... WoT and WotHelpers namespaces
... code completion / suggestions
... documentation is shown next to method also
... package.json has pre-set scripts like build, debug and start
... bundle.js + map for debugging also
... debugging works with "npm run debug"
... can paste links on IRC

<cris> https://github.com/UniBO-PRISMLab/wam

Sebastian: Thank you

McCool: Fantastic work

<cris> https://marketplace.visualstudio.com/items?itemName=arces-wot.td-code

McCool: where do we capture documentation for tools
... tutorials and videos would be helpful
... talk about it in marketing call

<kaz> +1

Sebastian: Cristiano, can you share the presentations
... will check

Cristiano: marketing repo?

Sebastian: Yes, makes sense

Cristiano's presentation slides

Jennifer: Video what you showed would be great
... explains more than slides

Cristiano: Will try ;-)

Sebastian: Cristiano, thank you
... let's pick it up in marketing call

Kaz: Note: we can put videos on W3C youtube channel also

F2F meeting

Sebastian: see options in doodle poll

<sebastian> https://doodle.com/poll/vywd8dpu2ge56mma

Sebastian: please mark your preference
... w.r.t. Pune we have to see what happens with Corona et cetera

TF reports

Daniel: Scripting: Talked about issues, decided to do a publication soon, open topic w.r.t. TD, ...

McCool: Security: OAuth2 flows
... Discovery: we have basic document
... PoC: discussed use cases
... PlugFest: preliminary discussion what to do. Need to schedule main call first

Sebastian: Thing Description
... minutes: security, open issues, dynamic TDs

Lagally: No use-case call last week
... pending PRs
... converting markdown files to HTML
... will have presentation from ITU-T tomorrow
... noon, CET time
... w.r.t. Prioritazion we have stakholders
... Architecture: only morning call
... walked over profile strawman
... use it as starting point
... need resolution to make current profile strawman to baseline

Sebastian: Need more time to review

(Lagally mentions he would discuss it during the Architecture calls tomorrow; and Kaz suggests we'll revisit it during the main call next week)

Sebastian: no marketing call last week

McCool: tomorrow's marketing call will happen

Koster: another conflict soon

McCool: If so we should re-think call time
... testing call: 15 minutes past the hour

[adjourned]

<kaz> [5-min break; PlugFest/Testing call on the same WebEx but on the #wot-pf IRC channel]

Summary of Action Items

Summary of Resolutions

[End of minutes]

Minutes manually created (not a transcript), formatted by David Booth's scribe.perl version (CVS log)
$Date: 2020/07/29 12:19:14 $