W3C

– DRAFT –
WoT-WG - TD-TF

01 September 2021

Attendees

Present
Cristiano_Aguzzi, Daniel_Peintner, Kaz_Ashimura, Michael_Koster, Michael_McCool, Philipp_Blum, Sebastian_Kaebisch
Regrets
-
Chair
Sebastian
Scribe
kaz, sebastian

Meeting minutes

Ege will be back Sept 20. The planed session about protocol binding will be held on Sept. 22

minutes check

<kaz> Aug-4

any objections?

no

PR overview

PR 1151

TD signature https://github.com/w3c/wot-thing-description/pull/1151

Oliver provided a review

McCool: no time yet for review it. Will do it for next time

some examples would be good

maby a nice diagram would good for clearification. There is an example such as from EXI canonical

https://www.w3.org/TR/exi-c14n/#signatureProcessingSteps

PR 1167

<kaz> fix: fix RDF triples example from Thing description json-ld 1.1 #1167

next PR fix RDF triples example from Thing description json-ld 1.1

no news here

McCool: there should be no metadata in the id value

e.g., "id": "urn:dev:ops:32473-WoTLamp-1234"

same is also true

this recommendation should be mentioned in the security consideration sectopion

MM will provide an issue

Kaz: we should have a joint meeting with the DID WG

PR 1205

Fix issues in TM schema generation script https://github.com/w3c/wot-thing-description/pull/1205

waiting for Ege's feedback

<McCool> just created issue for URL/Id not having metadata: https://github.com/w3c/wot-thing-description/issues/1216

Add queryaction and cancelaction operations https://github.com/w3c/wot-thing-description/pull/1208

still WIP, we should provide some comments about this PR and about the query naming

<McCool> the readme should list specific files under context and ontology that are autogenerated

<McCool> sorry. have to drop - will talk again soon

check issues

Issue 1199

Small incoherence in forms Thing Description core vocabulary https://github.com/w3c/wot-thing-description/issues/1199

we will replace the sentance with Ege's proposal

Issue 1202

next issue: unit for human-readable / display purposes or as semantic annotation?

https://github.com/w3c/wot-thing-description/issues/1202

Cristiano: support also to use the unit mainly for semantic purposes

Koster: units for human purposes typically have more information as a single value like symbl, the full name, pointer etc

Issue 1214

next issue: TD File Extension Convention https://github.com/w3c/wot-thing-description/issues/1214

Cristiano: how about extend the IANA registry with .td.json since it says "File extension(s)"

Kaz: we should talk with PLH about this
… also please remember W3C Process 2021 will include the capability of registry handling ourselves

<dape> https://www.iana.org/assignments/media-types/application/sarif+json

Daniel: JSON-LD also used the .jsonld. Maybe this was the motivation to use the single dot form with .jsontd

Daniel: Sarif uses .sarif and .sarif.json

Kaz: again, let's talk with PLH
… I personally don't think we should change the file extension definition given the old definition is included in the official REC

Issue 1200

Is there a need for invokeanyaction/queryallactions operations? #1200

Sebastian: since Ben is not here, would suggest we postpone this issue

Related Issue 302

also additional descriptions on Hypermedia Controls

(some discussion)

Kaz: in any ways, we need Ben and Ege for further discussion. right?

Sebastian: right

Daniel: just wanted to remind that there would be possible security issues on the dynamic approach

Cristiano: right

Sebastian: would ask McCool as well about his opinion

Issue 878

Describing initial connection #878

Sebastian: (goes through the issue)
… we should have a PR

Kaz: so we should add the "need PR" label to this

Sebastian: ok

(kaz added "PR needed" label)

Issue 1195

[discussion] TD Linting #1195

Cristiano: this would allow people better persistence

Sebastian: (adds comments)
… instead using the IP address at the interaction level. the base can be used
… should check if there is no conflict

Sebastian's updated comments

Issue 1215

Specify format of additional information for TM-to-TD conversion? #1215

Cristiano: (summarizes the issue)
… I'm OK with this process itself
… but some remaining questions

Sebastian: how to create TDs?
… many ways/tools to handle this

related issue 121

AOB

Philipp: wondering about SenML
… IETF spec for sensor data

SenML (RFC8428)

Kaz: given the Editors of this spec include Ari and Carsten, we can simply talk with them about possible binding during the vF2F meeting at TPAC
… we're still finalizing the joint sessions in general :)

Philipp: should I generate some proposal for binding templates?

Sebastian: not really sure
… what do you think, Koster?

Koster: we should think about possible binding
… that's a good issue
… maybe more study needed

Kaz: we're out of time, and would suggest we bring this topic to the main call next week as well

Sebastian: yeah, let's continue the discussion next week

[adjourned]

Minutes manually created (not a transcript), formatted by scribe.perl version 136 (Thu May 27 13:50:24 2021 UTC).