W3C

- DRAFT -

WoT online PlugFest - Day 2

29 Sep 2020

Attendees

Present
Kaz_Ashimura, Michael_McCool, Hazel_Kuok, Philipp_Blum, Cristiano_Aguzzi, Kunihiko_Toumura, Sebastian_Kaebisch, David_Ezell, Michael_Koster, Ryuichi_Matsukura, Tomoaki_Mizushima, Ege_Korkan, Daniel_Peintner
Regrets
Chair
McCool
Scribe
sebastian

Contents


<kaz> scribenick: sebastian

Agenda

McCool: do some agenda updates

Guests

Philipp Blum is introduced

Philipp is a contributor of the RIOT OS project

W3C Patent Policy

FAQ 6

(McCool and Kaz explain the summary of the W3C patent policy, and Philipp understands the requirement.)

Checking the minutes from yesterday

Sep-29

any comments on the minutes?

there are no objections

PR 66

<kaz> PR 66

McCool: I merged the easy ones
... Siemens added a virtual thing
... TUM added photo devices
... there is an open PR about RIOT OS
... the TD there has some issues
... there are relative href used, however, no base

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

Sebastian: we have a same issue that is quite hard to provide a base since the IP address is changing quite often

McCool: It would be good to have issue that addresses this topic

<scribe> ACTION: Sebastian creates an issue

Philipp: we have routing issues

McCool: I will merge this PR and mark as not accessible in the active.csv

Ege: why not providing a dynamic base ?
... is it not the same in Thing Model?

McCool: comments the PR from Philipp

Philipp: I checked my TD against the Playground. There were some strange errors

PR 68

PR 68

McCool: shows next PR from Intel
... I have added geolocation to the TD
... there is also SDF definitions

Sebastian: how the SDF definition come from? Relied on JSON Schema?

<kaz> related issue 47

McCool: shows where the SDF definitions are

<kaz> Koster's comment including the resources

Sebastian: for now, it is a hint that OneDM is used, right?

McCool: yes

Koster: yes, it should be referenceable. OneDM provides URI
... there is OneDM playground
... I can help you with your example
... I will check why the links not working

McCool: people define latitude and longitude as strings

<kaz> Issue 58 on geolocation

McCool: recommend to use negative numbers
... use float for this

Ege: processor have to process this

McCool: this should work

Cristiano: this is not TD, it is JSON-LD file

<kaz> schema.org latitude

Kaz: do you mean "unrestricted double" as the type by "negative numbers" here?

<kaz> 5.1. The GeolocationSensor Interface from the Generic Sensor API

<citrullin> kaz, Yes, exactly. That is what I was talking about. Thanks.

McCool: yes, that's what I mean

PR 69

McCool: shows more examples of its PR

<kaz> PR 69

Cristiano: explains the usage of the link to describe the host thing

https://github.com/w3c/wot-testing/pull/69

Ege: Singapore has a same use case with its robots about geolocation data

Kaz: would agree with McCool and suggest we concentrate on the "static location" this time, though we need to think about how to deal with the static part of TD and the dynamic part of TD separately in the (near) future

McCool: comment issue https://github.com/w3c/wot-testing/issues/58
... https://github.com/w3c/wot-testing/issues/58#issuecomment-700722259
... I'm going to merge the PRs from University of Bologna
... and the TUM mashup

PR 70

PR 70

Kaz: merging the PRs is OK but people are encouraged to add some supplementary description on how to generate which TD automatically, etc., later :)

Ege: gives some overview about the PR

AOB

Kaz: did you receive any feedback from Farshid?

McCool: no

Kaz: we need to think about what we could do without the LinkSmart directry service for the PlugFest then.

[adjourned]

Summary of Action Items

[NEW] ACTION: Sebastian creates an issue
 

Summary of Resolutions

[End of minutes]

Minutes manually created (not a transcript), formatted by David Booth's scribe.perl version (CVS log)
$Date: 2020/09/30 10:42:48 $