06:31:56 RRSAgent has joined #wot-td 06:31:56 logging to http://www.w3.org/2017/04/21-wot-td-irc 06:34:15 yingying has joined #wot-td 06:34:34 sebastian has joined #wot-td 06:36:44 present+ Kaz_Ashimura, Sebastian_Kaebisch, Danh_Le_Phuoc, Daniel_Peintner, Darko_Anicic, Maria_Poveda, Uday_Davuluru, Victor_Charpenay, Yingying_Chen 06:37:17 DarkoAnicic has joined #wot-td 06:37:24 present+ DarkoAnicic 06:37:37 present+ DanhLePhuoc 06:37:52 scribe: Uday 06:38:38 uday has joined #wot-td 06:38:58 scribenick: uday 06:39:19 sebastian: gives brief overview of previous discussions 06:39:22 victor has joined #wot-td 06:41:08 McCool has joined #wot-td 06:41:14 present+ 06:41:24 present+ Michael_McCool 06:41:31 https://github.com/json-schema-org/json-schema-spec/issues/309 06:41:35 JSON schema status: 06:43:02 Daniel-to follow up 06:44:22 Namespace: 06:45:06 https://github.com/w3c/wot-thing-description/issues/3 06:45:19 overview of new and where the old namespaces can be used 06:46:00 q+ 06:46:32 Darko- which main namespace are we going to use? 06:46:41 td: http://www.w3.org/ns/td# 06:48:17 Daniel- usually W3C namespaces start with year and month, is there a best practice for the same 06:48:19 q+ 06:48:37 https://www.w3.org/TR/2013/REC-prov-o-20130430/ 06:48:56 http://www.w3.org/ns/prov# 06:49:52 Maria- using NS with date might not be good 06:50:50 +q 06:51:06 SSN ontology does not have year : http://www.w3.org/ns/ssn/ 06:52:05 Kaz- describes W3C way of using namespace 06:52:33 taki has joined #wot-td 06:53:25 regrets: Achille_Zappa 06:54:00 sebastian-discussion needed with a list of vocabulary and which comes from where 06:54:15 [ we need to get approval for name spaces like http://www.w3.org/DIRECTLY_UNDER_THE_MAIN_HOST ] 06:54:42 [ while we can create any name spaces like http://www.w3.org/2017/04/WOT ] 06:54:43 -q 06:55:00 ack dape 06:56:12 [ guideline here: https://www.w3.org/2005/07/13-nsuri ] 06:56:34 taki has joined #wot-td 06:56:47 we can represent the reused ns as in this example http://iot.linkeddata.es/def/core/index-en.html#description 06:57:41 q? 06:57:48 rrsagent, make log public 06:57:53 rrsagent, draft minutes 06:57:53 I have made the request to generate http://www.w3.org/2017/04/21-wot-td-minutes.html kaz 06:58:28 http://lov.okfn.org/dataset/lov/vocabs?tag=W3C%20Rec 06:59:00 q+ 06:59:14 q+ 07:00:57 q? 07:01:00 kaz: I put the URL of the namespace guideline above 07:01:07 ack k 07:02:11 sure: I hust wanted to say. 07:02:11 zkis has joined #wot-td 07:02:25 that Dave defined this namespace with Phil Archer 07:02:55 Danh- just done with SSN ontology, describes the same 07:03:01 present+ Zoltan_Kis 07:03:09 s/Danh-/Danh:/ 07:03:13 or "under the guidance" of Phil Archer, so I assume it is valid. 07:03:32 I mean https://www.w3.org/ns/td 07:05:01 [ we can use https://www.w3.org/ns/td as well if we want (as described in the guideline: https://www.w3.org/2005/07/13-nsuri ] 07:07:06 TD model: 07:07:25 s/TD model:/topic: TD model/ 07:07:51 Chair: Sebastian 07:08:01 Meeting: WoT WG - TD-TF 07:08:40 s/Namespace:/topic: TD Namespace/ 07:08:43 Sebastian- are these any proposals for F2F breakouts 07:08:49 rrsagent, draft minutes 07:08:49 I have made the request to generate http://www.w3.org/2017/04/21-wot-td-minutes.html kaz 07:09:35 s/Sebastian-/Sebastian:/ 07:09:36 rrsagent, draft minutes 07:09:36 I have made the request to generate http://www.w3.org/2017/04/21-wot-td-minutes.html kaz 07:09:55 s/Darko-/Darko:/ 07:10:04 s/Daniel-/Daniel:/ 07:10:08 s/Maria-/Maria:/ 07:10:13 s/Kaz-/Kaz:/ 07:10:15 rrsagent, draft minutes 07:10:15 I have made the request to generate http://www.w3.org/2017/04/21-wot-td-minutes.html kaz 07:12:38 s/JSON schema status:/topic: JSON Schema status/ 07:12:40 rrsagent, draft minutes 07:12:40 I have made the request to generate http://www.w3.org/2017/04/21-wot-td-minutes.html kaz 07:12:47 q+ 07:13:17 ack DanhLePhuoc 07:13:22 TD model discussed 07:13:24 ack v 07:13:27 ack d 07:13:30 ack m 07:13:40 TD Model -> http://iot.linkeddata.es/def/wot/index-en.html#description 07:14:56 McCool- briefs security plans 07:15:13 s/McCool-/McCool:/ 07:16:47 q+ 07:18:02 McCool- complicated to have different security for different resources 07:18:11 can go for modular approach 07:18:37 s/McCool-/McCool:/ 07:18:41 ack m 07:21:15 rrsagent, draft minutes 07:21:15 I have made the request to generate http://www.w3.org/2017/04/21-wot-td-minutes.html kaz 07:21:31 seba- why not use same vocabulary as we use in JSON-LD instance 07:21:50 s/seba-/Sebastian:/ 07:22:03 q+ 07:23:53 Maria- we cannot use same vocab for all 07:24:24 s/Maria-/Maria:/ 07:25:05 q+ 07:25:21 q+ 07:27:20 Kaz- position of WoT ontology doc under TD repo 07:30:15 can't you just chage the template color (like yellow, as in the Vincinity logo?) 07:30:25 to avoid any confusion 07:31:07 s/Kaz-/Kaz:/ 07:31:40 s/Vincinity/Vicinity/ 07:32:12 I'll have a look at the css 07:32:50 s/position of WoT ontology doc under TD repo/kind of concerned about the positioning of this document. we should clarify this document itself is a proposal under the Vicinity project and not W3C work at the moment. we need to extract part of the content and create another document for WoT TD document./ 07:33:32 Dahn- reminds process for W3C publication 07:34:00 s/Dahn/Danh:/ 07:34:40 s/Danh:-/Danh:/ 07:36:02 Kaz:/ we can make a candidate recommendation later 07:36:58 s|Kaz:/|Kaz:| 07:36:59 q? 07:37:02 ack k 07:37:10 ack DarkoAnicic 07:37:14 ack DanhLePhuoc 07:37:17 rrsagent, draft minutes 07:37:17 I have made the request to generate http://www.w3.org/2017/04/21-wot-td-minutes.html kaz 07:37:22 ack danh 07:37:25 ack darko 07:38:37 Darko:/ we have stable vocab on TD, do we create JSON-LD context or do we stcik to one format for WoT ontology and JSON-LD representation?? 07:39:47 s/we can make a candidate recommendation later/at some point (when the TD spec draft gets good enough), we can get consensus for publication as a FPWD within this TF first and then within the whole WG next, and then publish it as a FPWD. and we can publish it as a CR, PR and REC after that (when the spec draft becomes good enough for those stages)/ 07:40:01 s|Darko:/|Darko:| 07:40:11 rrsagent, draft minutes 07:40:11 I have made the request to generate http://www.w3.org/2017/04/21-wot-td-minutes.html kaz 07:40:31 Maria:/ better to keep them as close as possible but not necessary to be same 07:41:14 Maria, the program you run to generate the doc is Widoco, isn't it? There is an option for custom styles (-useCustomStyle), in case it helps. 07:41:19 s|Maria:/|Maria:| 07:41:46 Seba:/ take this as a separate web meeting agenda 07:41:53 +1 07:42:02 s|Seba:/|Sebastian:| 07:42:07 +1 07:42:12 +1 07:42:19 rrsagent, draft minutes 07:42:19 I have made the request to generate http://www.w3.org/2017/04/21-wot-td-minutes.html kaz 07:42:26 +1 07:43:36 Maria: could you please provide us with an example where the difference between the OWL model and JSON-LD vocabulary would differ (before the next meeting on the topic)? 07:45:08 rrsagent, draft minutes 07:45:08 I have made the request to generate http://www.w3.org/2017/04/21-wot-td-minutes.html kaz 07:45:08 ok 07:45:25 [ adjourned ] 07:45:27 rrsagent, draft minutes 07:45:27 I have made the request to generate http://www.w3.org/2017/04/21-wot-td-minutes.html kaz 08:21:06 MariaPoveda has joined #wot-td 08:53:09 kaz has joined #wot-td 12:30:03 Zakim has left #wot-td 13:35:42 kaz has joined #wot-td 16:25:10 kaz has joined #wot-td 17:46:27 zkis has joined #wot-td 20:16:55 zkis has joined #wot-td 22:56:00 zkis has joined #wot-td