06:31:54 <RRSAgent> RRSAgent has joined #wot-td
06:31:54 <RRSAgent> logging to http://www.w3.org/2017/05/26-wot-td-irc
06:32:48 <kaz> present+ Kaz_Ashimura, Danh_Le_Phuoc, Daniel_Peinter, Dave_Raggett, Maria_Poveda, Taki_Kamiya, Yingying_Chen
06:32:57 <kaz> regrets: Sebastian_Kaebisch
06:34:23 <kaz> q+
06:35:38 <kaz> Chair: Taki
06:36:55 <kaz> discussion on the serialization topic
06:37:07 <kaz> kaz wonders if Karsten also could join the TD call(s)
06:37:19 <kaz> daniel will ask Karsten about that possibility
06:37:50 <dape> scribe: dape
06:37:55 <dape> scribeNick: DP
06:38:05 <MariaPoveda> MariaPoveda has joined #wot-td
06:38:27 <dape> TOPIC: F2F Recap
06:39:14 <dape> TK: Sebastian used slides to go over TD overview (TODO link)
06:39:23 <kaz> -> https://www.w3.org/WoT/IG/wiki/images/9/95/Td_summary_osaka.pdf Sebastian's slides
06:39:26 <dsr> dsr has joined #wot-td
06:39:32 <dsr> present+ Dave_Raggett
06:39:33 <kaz> ack k
06:39:36 <dape> ... Core/information model
06:39:52 <dape> ... basic assumption vs current assumption
06:40:41 <dape> Kaz: Sebastian used 2 different versions of slides
06:40:48 <dape> TK: Use the overview version
06:40:53 <kaz> -> https://www.w3.org/WoT/IG/wiki/images/9/95/Td_summary_osaka.pdf Sebastian's slides
06:41:45 <dape> TK: Slide on #3. TD model sketch
06:42:00 <dape> ... basic agreement with that regard
06:42:14 <dape> ... model is separate from serialization
06:42:29 <dape> ... JSON-LD, JSON, ect is possible
06:43:32 <dape> ... not decided on Serialization yet. Basic model is agreed
06:43:59 <dape> ... Kajimoto-San introduced TD lifecycle
06:44:23 <dape> ... Kajimoto-San proposed addition of keywords ... for example @remove
06:44:37 <dape> ... to modify TDs over lifetime
06:45:09 <dape> ... another keyword is @available
06:45:32 <dape> ... proposed during F2F
06:45:52 <dape> ... WG concluded to contact JSON-LD first
06:46:27 <dape> ... next topic is missing parts in JSON schema
06:46:47 <dape> ... this topic was discussed also
06:47:30 <dape> ... used JSON schema example
06:47:57 <dape> ... e.g., client wants to retrieve temperature in Celsius
06:48:24 <dape> ... with semantic annotations this is possible
06:48:56 <dape> ... this scenario was used on PlugFest day also
06:49:15 <dape> ... KDDI temperature sensor was provided
06:49:54 <dape> ... Dave and Yongjing suggested other aspects
06:50:16 <dape> ... step back a little bit.. think more about use case and derive requirements from there
06:50:25 <dape> ... we decided to do so
06:51:00 <dape> ... Yongjing sees 2 approaches (bottom up vs top down)
06:51:21 <dape> ... next topic is TD namespace
06:51:33 <dape> ... (slide #6)
06:51:49 <dape> ... generic namespace does not have any version number
06:52:13 <dape> ... some members think we should have some version managements concept
06:53:01 <dape> ... suggestion during F2F was that we did not get to the point to decide... keep discussion up and conclude later
06:53:18 <dape> ... next topic was about TD serialization
06:53:30 <dape> ... DP led session
06:54:07 <dape> ... proposal was to think separately between text-based and more efficient binary representation
06:54:24 <dape> ... might be a good idea to select one default format for each
06:54:45 <dape> ... at this point we do not know which format will be picked
06:55:25 <dape> ... we should not invent another format... instead use existing one
06:55:56 <dape> ... on the table are currently 2 for the efficient formats (EXI and CBOR)
06:56:02 <achille_zappa> achille_zappa has joined #wot-td
06:56:12 <dape> .... we need to elaborate on the comparison
06:56:35 <dape> ... idea was to collect real TD examples (e.g. from PlugFest)
06:56:55 <dape> ... oneM2M integration in the future
06:57:19 <dape> ... evaluate several dimensions
06:57:44 <dape> ... separately we need think about text-based serialization
06:57:45 <dape> q+
06:59:02 <dape> DP: think the text-based format should be the basis... binary should represent this data
06:59:04 <dape> ack dape
06:59:49 <dape> TK: at the moment we can solely use the current JSON-LD format
07:00:01 <dape> ... not sure whether we can convert JSON-LD examples to JSON
07:00:55 <dape> Dave: think we could do that. The other way around is possible already
07:01:02 <dape> ... need to check that
07:01:11 <dape> .... binding is more complicated
07:02:02 <dape> DP: will try to collect JSON-LD files from PlugFest
07:02:09 <dape> ... Dave can then try to convert them
07:02:19 <dape> Dave: sounds like a good plan
07:02:29 <kaz> present+ Achille_Zappa
07:03:04 <dape> TK: On the binary format side DP and Carsten volunteered to show process
07:03:21 <kaz> q+
07:03:27 <dape> q+
07:03:47 <dape> Kaz: question about namespace version
07:04:06 <dape> ... W3C specification used XML version attribute
07:04:06 <kaz> -> https://www.w3.org/TR/speech-synthesis11/ SSML 1.1
07:04:21 <kaz> -> https://www.w3.org/TR/speech-synthesis11/#S2.1 2.1
07:04:23 <dape> ... see section example
07:04:47 <kaz> [[ <speak version="1.1" xmlns="http://www.w3.org/2001/10/synthesis" ]]
07:04:53 <dape> ... might want to have something like this
07:05:23 <dape> TK: Good point. Not listed yet.
07:05:55 <dape> ... allows to change semantics also
07:06:19 <dape> Kaz: Can also talk to W3C experts to get feedback
07:06:29 <dape> TK: thanks. that will help a lot
07:06:32 <dape> q?
07:06:47 <dape> ack kaz
07:06:56 <kaz> action: kaz to talk with W3C team experts about NS versioning for non-XML specs
07:06:57 <trackbot> Created ACTION-106 - Talk with w3c team experts about ns versioning for non-xml specs [on Kazuyuki Ashimura - due 2017-06-02].
07:07:21 <kaz> dape: any plan to change the TD itself before the Dusseldorf meeting?
07:07:28 <kaz> ack d
07:07:39 <dape> DP: any plans to update TD till Düsseldorf F2F?
07:07:53 <kaz> s/dape: any plan to change the TD itself before the Dusseldorf meeting?//
07:08:05 <dape> TK: new features should be described very quickly...
07:08:20 <dape> ... otherwise we keep current form
07:09:10 <dape> ...  opportunity to experiment
07:09:18 <kaz> rrsagent, make log member
07:09:21 <kaz> rrsagent, draft minutes
07:09:21 <RRSAgent> I have made the request to generate http://www.w3.org/2017/05/26-wot-td-minutes.html kaz
07:09:53 <dape> TK: w.r.t. to Serialization and Semantic annotation I am not sure if we can get consensus till next F2F
07:10:09 <kaz> i/F2F Recap/scribenick: dape/
07:10:13 <kaz> rrsagent, draft minutes
07:10:13 <RRSAgent> I have made the request to generate http://www.w3.org/2017/05/26-wot-td-minutes.html kaz
07:10:22 <dape> ... IF anybody can think of any idea let's discuss next week
07:11:29 <dape> TK: any other topics?
07:12:04 <dape> adjourned
07:12:09 <kaz> rrsagent, draft minutes
07:12:09 <RRSAgent> I have made the request to generate http://www.w3.org/2017/05/26-wot-td-minutes.html kaz
07:13:14 <kaz> meeting: WoT WG - TF-TD
07:13:18 <kaz> rrsagent, draft minutes
07:13:18 <RRSAgent> I have made the request to generate http://www.w3.org/2017/05/26-wot-td-minutes.html kaz
07:13:40 <kaz> rrsagent, make log public
07:13:42 <kaz> rrsagent, draft minutes
07:13:42 <RRSAgent> I have made the request to generate http://www.w3.org/2017/05/26-wot-td-minutes.html kaz
07:27:26 <taki> taki has left #wot-td
08:24:53 <dsr> dsr has joined #wot-td
10:57:17 <yingying> yingying has joined #wot-td
11:22:37 <Zakim> Zakim has left #wot-td
12:32:03 <yingying> yingying has joined #wot-td