07:09:03 RRSAgent has joined #wot-td 07:09:03 logging to http://www.w3.org/2016/12/07-wot-td-irc 07:09:06 ... 1. updates for CP w.r.t to TD 07:09:14 meeting: WoT TD TF meeting 07:09:20 chair: Sebastian 07:09:21 ... discussed points are already integrated 07:09:30 scribe: Daniel 07:09:35 scribenick: dape 07:09:37 ... e.g. media-types 07:10:01 ... one container for Property, Action, and Event using @type 07:10:10 katsu has joined #wot-td 07:10:32 rrsagent, make minutes 07:10:32 I have made the request to generate http://www.w3.org/2016/12/07-wot-td-minutes.html yingying 07:10:41 ... local endpoint information can be described also 07:10:52 rrsagent, make log public 07:10:58 ... e.g, what is Uri, what media-type 07:11:55 http://w3c.github.io/wot/current-practices/wot-practices.html#thing-description 07:12:28 i|updates for CP w.r.t to TD|Topic: updates for CP w.r.t to TD| 07:12:58 rrsagent, make minutes 07:12:58 I have made the request to generate http://www.w3.org/2016/12/07-wot-td-minutes.html yingying 07:13:33 ... no change for integrating other contexts.... still possible to use other @types's 07:13:51 present+ Katsuyoshi_Naka 07:14:03 ... global endpoints are possible also 07:14:50 ... idea is to have a global base uri... locally one can define relative path OR override some information 07:15:07 .... e.g., switch from http to coap 07:15:43 q+ 07:16:49 DP: for next PlugFest, do we plan to "test" complex type defintitions 07:18:01 SK: lets postpone discussion when we discuss PlugFest scnerios 07:18:10 present: Takuki_Kamiya, Uday_Davluru,Katsuyoshi_Naka, Daniel_Peintner, Sebastian_Kaebisch, Yingying_Chen 07:18:17 s/scnerios/scenarios 07:19:16 SK: Internal Siemens feedback, especially from Matthias (who raised issue #287) 07:19:52 ... re-use common vocabulary 07:19:57 -> https://github.com/w3c/wot/issues/287 issue 287 07:21:08 q+ 07:21:20 ... endpoints --> link 07:21:31 ... uri --> href 07:22:04 TK: Any reason why we have to follow html example 07:22:17 ... endpoints sounds more appropriate 07:22:30 SK: MK just likes to re-use existing vocabulary 07:23:33 ... Dave also mentions that we should try to make TD Web developer friendly 07:25:10 DP: be cautious about plural form.. link, just singular ? 07:25:36 SK: TK and DP, please raise/comment issue on github 07:26:51 ... be aware that CP document might slightly change the upcoming days 07:27:30 Naka: href is still in example 3 07:28:11 ... will confuse people 07:28:53 SK: Agree 07:29:32 .. idea is global vs. local information 07:30:10 ... should try to simplify it 07:30:53 ... NakaSan, can you raise this as issue? 07:31:15 Naka: OK 07:31:47 SK: Another issue from Alex Owen #268 07:31:58 ... proposed td class field 07:32:08 ... references to CSS files 07:32:48 ... I am proposing to use @type 07:32:57 .... not sure if we really need that new field 07:33:56 SK: There are some more TD issues... no urgent ones anymore 07:35:14 TOPIC: Stick with JSON-LD or change the format to JSON 07:35:37 SK: Dave worked on that topic 07:35:58 ... think we need a more principal discussion 07:36:18 ... TD should be independent to programming languages 07:36:49 SK: Shows slide (WoT TD Basic Assumption) 07:37:11 ... Servient1 in JavaScript 07:37:17 ... Servient2 in C++ 07:37:42 ... TD format independent 07:37:56 ... JS can wrap JSON 07:38:10 ... C++ might map to structs 07:40:30 ... focus of TD is to be independent 07:40:56 Uday: strongly support your argument 07:41:07 ... want to be an abstraction layer 07:41:20 ... try to be as neutral as possible 07:42:25 DP: Not sure about consequences (JSON vs JSON-LD) 07:43:03 SK: Dave proposes to have TD similar to Web Developer application layer 07:43:18 ... mapping to JS objects 07:44:42 DP: Also would like to mention that JSON-LD is a set standard and tools are built around this 07:44:48 ... people are used to this tools 07:45:31 SK: I would like to differentiate between the abstract TD format and the actual applications working with TDs 07:46:19 ... TDs may become complex... people might tend to use tools for creating TDs 07:46:45 kaz has joined #wot-td 07:47:05 ... humans can still edit it... but might not be sensible for complex scenarios 07:48:50 TK: IF majority of languages is JS then i would go with JSON 07:48:51 Zakim has joined #wot-td 07:48:56 rrsagent, draft minutes 07:48:56 I have made the request to generate http://www.w3.org/2016/12/07-wot-td-minutes.html kaz 07:49:06 ... since we don't know yet a more neutral format is better 07:49:21 present+ Kaz_Ashimura 07:49:25 SK: Dave will present his idea in the afternoon call 07:51:01 Uday: w.r.t. to organization .... how many further TD calls 07:51:10 SK: I expect one more 07:51:25 ... Let's try to resolve issues 07:51:52 ... hope we can freeze document next week 07:52:10 ... not sure about API changes 07:52:43 ... we will then tag and publish a freezed CP document 07:52:53 s/1. updates/SK: 1. updates/ 07:52:53 rrsagent, draft minutes 07:52:53 I have made the request to generate http://www.w3.org/2016/12/07-wot-td-minutes.html kaz 07:55:08 s/... SK: 1/SK: 1/ 07:55:10 rrsagent, draft minutes 07:55:10 I have made the request to generate http://www.w3.org/2016/12/07-wot-td-minutes.html kaz 08:01:33 thanks for taking the minutes daniel 08:03:31 benfrancis|away has joined #wot-td 08:19:47 ying_ying has joined #wot-td 09:34:42 zkis has joined #wot-td 10:15:44 Zakim has left #wot-td 12:12:07 kaz has joined #wot-td 13:07:23 taki has left #wot-td 13:11:47 yingying_ has joined #wot-td 13:13:17 ying_ying has joined #wot-td 13:18:53 yingying_ has joined #wot-td