14:03:55 <RRSAgent> RRSAgent has joined #wot-td
14:03:55 <RRSAgent> logging to https://www.w3.org/2021/05/26-wot-td-irc
14:06:38 <sebastian> sebastian has joined #wot-td
14:08:48 <cris> cris has joined #wot-td
14:15:51 <dape> dape has joined #wot-td
14:16:28 <Ege> Topic: Minutes Review
14:16:35 <McCool> McCool has joined #wot-td
14:16:47 <Ege> sk: (adds roundtripping to agenda)
14:17:04 <kaz-brb> i|adds|-> https://www.w3.org/2021/05/19-wot-td-minutes.html May-19|
14:17:17 <kaz-brb> meeting: WoT-WG - TD-TF
14:17:30 <mjk> mjk has joined #wot-td
14:17:53 <Ege> sk: 1st of June is still on trick for WD publication
14:18:06 <Ege> ... probably july for the CR
14:18:09 <kaz-brb> present+ Kaz_Ashimura, Sebastian_Kaebisch, Andrea_Cimmino, Cristiano_Aguzzi, Daniel_Peintner, Ege_Korkan, Michael_McCool, Tomoaki_Mizushima
14:18:25 <mjk> (koster regrets, I have a conflicting meeting this morning)
14:18:29 <Ege> mm: testing will be focused on the WD version
14:18:32 <kaz-brb> i/1st of/topic: Publication/
14:18:41 <kaz-brb> regrets+ Michael_Koster
14:18:51 <kaz-brb> s/on trick/on track/
14:19:14 <sebastian> https://github.com/w3c/json-ld-api/issues/514
14:20:09 <Ege> sk: an issue was found in the jsonld specification
14:20:21 <Ege> mm: we need to workaround this in directories
14:22:33 <Ege> ac: the only technology agnostic way of doing it would be by defining frames
14:22:50 <Ege> ... so it is hard to do it in a generic way
14:23:32 <Ege> ... kehio, another library of us, parses java models into rdf
14:24:55 <Ege> ... rdf is a graph and json is tree, so when you have cycles in json, you cannot tell where in rdf
14:26:03 <Ege> ... so it took me a couple of months but the Java library is open source
14:26:42 <dape> q+
14:27:38 <Ege> mm: how do we validate extensions?
14:27:44 <dape> ack dape
14:27:53 <kaz> rrsagent, make log public
14:27:53 <Ege> dp: victor has validation shacl generated from ttl
14:27:59 <kaz> rrsagent, draft minutes
14:27:59 <RRSAgent> I have made the request to generate https://www.w3.org/2021/05/26-wot-td-minutes.html kaz
14:28:07 <kaz> s/shacl/SHACL/
14:28:08 <Ege> mm: that is for the core document
14:28:32 <Ege> mm: we need a way to get more information on the extension just by using its context
14:28:33 <kaz> Chair: Sebastian
14:28:47 <Ege> mm: we should ask this the JSON-LD guys
14:28:55 <dape> s/dp: victor has validation shacl generated from ttl/dp: victor uses shacl shabe for generating the others
14:28:56 <cris> +1
14:29:36 <Ege> sk: so you want to put it in the context?
14:29:44 <Ege> mm: yes, maybe some context negotiation?
14:29:53 <Ege> ac: so you want shacl in the context?
14:30:12 <Ege> mm: that or computing another url for finding the shacl
14:31:28 <Ege> sk: we can invite someone from json-ld group to a call?
14:31:34 <Ege> mm: an issue would be good
14:35:12 <Ege> sk: (writing issue in json-ld-api repository)
14:38:14 <Ege> ca: it is clear if there is a way to state or if there is a repository with the validation file
14:39:45 <sebastian> https://github.com/w3c/json-ld-api/issues/530
14:39:52 <kaz> rrsagent, draft minutes
14:39:52 <RRSAgent> I have made the request to generate https://www.w3.org/2021/05/26-wot-td-minutes.html kaz
14:40:04 <Ege> sk: (created issue is https://github.com/w3c/json-ld-api/issues/530)
14:40:16 <Ege> sk: something more about this topic?
14:41:41 <kaz> i|json-ld-api/issues|topic: JSON-LD and roundtrip|
14:42:16 <Ege> Topic: Modbus Binding
14:42:28 <victor> victor has joined #wot-td
14:43:14 <Ege> ca: we discussed about how to map sub types of integers in json schema
14:45:27 <McCool> s/shabe/shapes/
14:46:03 <Ege> ac: you can use xsd: (something) to allow that
14:49:23 <victor> q+
14:53:00 <Ege> https://github.com/ajv-validator/ajv-formats
14:53:11 <Ege> cris look at this link :)
14:54:09 <Ege> ac: @type is not the right place for this
14:54:22 <kaz> q?
14:54:27 <Ege> ege: json schema min/max or the new vocabulary extensions can be used
14:54:33 <kaz> present+ Victor_Charpenay
14:54:40 <Ege> ca: I see, that makes sense
14:55:44 <victor> ack
14:58:05 <Ege> vc: I agree with ege
14:58:07 <Ege> ca: I will check
14:58:39 <Ege> ca: I have a question about the ontology
14:58:51 <zkis> zkis has joined #wot-td
14:59:08 <Ege> ... we are defining these ontology for mapping but we are not experts. How to be prefix independent
15:01:14 <Ege> mm: prefixes are sometimes cached
15:01:33 <Ege> ac: for schema.org people find it too long and use other prefixes
15:02:05 <Ege> ... it is not a good idea to rely on the prefix
15:04:01 <kaz> rrsagent, draft minutes
15:04:01 <RRSAgent> I have made the request to generate https://www.w3.org/2021/05/26-wot-td-minutes.html kaz
15:06:46 <kaz> i|we discussed|-> https://github.com/w3c/wot-binding-templates/pull/109 wot-binding-templates PR 109 - Refining Modbus protocol binding|
15:08:00 <Ege> ca: so also we have the idea to have an ontology for the protocol and another document for how to use it in wot
15:09:04 <Ege> ca: also another ontology about binding would be nice
15:09:10 <Ege> vc: but that is already in the TD ?
15:09:38 <victor> SHACL
15:10:48 <Ege> sk: another annoying point is the byte sequence
15:17:28 <Ege> ca: yes I have seen that for the first time
15:17:41 <Ege> sk: Now I want to move the work to work on some PRs
15:19:46 <dape> q+
15:20:01 <victor> ack victor
15:20:26 <victor> q+
15:20:54 <dape> ack dape
15:22:08 <Ege> mm: it is difficult to refer to data schema for properties
15:24:46 <kaz> rrsagent, draft minutes
15:24:46 <RRSAgent> I have made the request to generate https://www.w3.org/2021/05/26-wot-td-minutes.html kaz
15:26:10 <Ege> ... it complicates canonicalizationn
15:26:32 <kaz> -> https://github.com/w3c/wot-thing-description/pull/1130 wot-thing-description PR 1130 - Update AdditionalExpectedResponses with named data schemas
15:26:36 <Ege> vc: canonical form should be direct serialization of the information model?
15:27:37 <Ege> mm: yes
15:27:44 <Ege> ... I have to update my PR
15:27:52 <Ege> vc: this should be moved to section 6?
15:37:13 <kaz> q+
15:37:36 <victor> ack victor
15:38:44 <kaz> ack k
15:39:57 <Ege> ege: why not use $ref and then allow referring to schemaDefinitions
15:40:06 <Ege> mm: why not creating an example about it?
15:42:50 <Ege> sk: then let's merge this and vc and ege will work on the proposal
15:43:12 <Ege> Topic: PR 1129
15:43:14 <kaz> -> https://github.com/w3c/wot-thing-description/pull/1129 PR 1129 - More fixes to canonicalization
15:43:27 <dape> q+
15:44:25 <dape> ack dape
15:44:55 <Ege> dp: but you should not care about such details in canonicalization
15:49:52 <Ege> mm: now I want to talk about signatures
15:50:02 <kaz> -> https://github.com/w3c/wot-thing-description/pull/1151 PR 1151 - WIP: TD Signatures
15:50:12 <kaz> i/now I/topic: PR 1151/
15:50:16 <Ege> mm: I think we should use xml signatures
15:51:20 <Ege> mm: this signature is based on ... (i missed that part)
15:51:26 <Ege> mm: this is not done yet
15:51:37 <Ege> mm: I don´t have all the keys yet
15:51:44 <dape> s/.. (i missed that part)/XML Signature
15:53:21 <cris> q+
15:55:30 <Ege> ca: why is sparql there, you are working with JSON?
15:55:36 <Ege> mm: sure, I can get rid of sparql
15:57:58 <Ege> sk: is the signature part also signed?
15:58:04 <Ege> mm: it is added only at the end
15:59:44 <cris> ack c
16:00:25 <Ege> sk: thank you very much for your work mm
16:00:33 <Ege> sk: adjourned
16:00:44 <kaz> rrsagent, draft minutes
16:00:44 <RRSAgent> I have made the request to generate https://www.w3.org/2021/05/26-wot-td-minutes.html kaz