06:46:42 <RRSAgent> RRSAgent has joined #wot-td
06:46:42 <RRSAgent> logging to http://www.w3.org/2016/12/14-wot-td-irc
07:00:44 <taki> taki has joined #wot-td
07:01:15 <dape> dape has joined #wot-td
07:02:37 <kaz> present+ Kaz_Ashimura, Daniel_Peintner, Takuki_Kamiya
07:04:16 <kaz> present+ Sebastian_Kaebisch
07:04:21 <kaz> present+ Uday_Davuluru
07:04:29 <yingying> yingying has joined #wot-td
07:05:30 <mkovatsc> mkovatsc has joined #wot-td
07:05:58 <sebastian> sebastian has joined #wot-td
07:06:19 <yingying_> yingying_ has joined #wot-td
07:07:06 <kaz> zakim, pick a scribe
07:07:06 <Zakim> Not knowing who is chairing or who scribed recently, I propose Daniel_Peintner
07:07:17 <mkovatsc> Sorry, the button to connect audio doesn't do anything...
07:07:31 <dape> scribe: dape
07:07:35 <dape> scribeNick: DP
07:07:49 <kaz> scribenick: dape
07:08:33 <davu> davu has joined #wot-td
07:08:51 <kaz> present+ Darko_Anicic, Matthias_Kovatsch
07:09:27 <kaz> regrets: Dave
07:09:43 <dape> SK: Next week will be last TD call
07:09:50 <kaz> present+ Yingying_Chen
07:09:52 <DarkoAnicic> DarkoAnicic has joined #wot-td
07:09:56 <kaz> rrsagent, make log public
07:10:00 <kaz> rrsagent, draft minutes
07:10:00 <RRSAgent> I have made the request to generate http://www.w3.org/2016/12/14-wot-td-minutes.html kaz
07:10:08 <dape> .... next week I would like to discuss PlugFest topics
07:10:16 <DarkoAnicic> present+ DarkoAnicic
07:10:28 <dape> TOPIC:  decisions about new TD version
07:10:33 <kaz> Chair: Sebastian
07:10:40 <dape> SK: should finalize TD version
07:10:44 <kaz> rrsagent, draft minutes
07:10:44 <RRSAgent> I have made the request to generate http://www.w3.org/2016/12/14-wot-td-minutes.html kaz
07:10:56 <dape> .. updated CP document according to  change requests
07:11:10 <dape> ... got additional comments, see https://github.com/w3c/wot/issues/287
07:11:30 <dape> ... issue is about renaming... re-structering
07:11:47 <dape> ... MK proposed changes
07:12:14 <dape> ... we should manage today to make a decision and get ready for next PlugFest
07:12:36 <dape> ... MK proposed to use Web vocabulary
07:12:51 <dape> ... e.g., link vs endpoint
07:13:14 <dape> ... e.g., uri vs. href
07:13:23 <dape> ... e.g., mediaType vs type
07:14:17 <dape> MK: split up issue into 2
07:14:30 <dape> SK: issue #289
07:14:49 <dape> MK: Instead of uri we should call it href
07:15:18 <dape> ... endpoint is usually socket address..
07:15:43 <dape> ... propose to use link and href
07:15:52 <dape> ... this is mainly about name changes
07:16:26 <dape> ... also propose simplifying overall structure
07:16:42 <dape> ... under interaction you have links
07:16:50 <dape> ... should we allow mut
07:17:02 <dape> s/should we allow mut/should we allow multiple hrefs?
07:17:34 <dape> ... looked at web linking RFC.. just one mediatype is supported
07:17:50 <dape> .. propose ONE mediaType as shown in example
07:18:16 <dape> ... one more tweak... in metadata there is key "base"
07:18:24 <kaz> i|propose to|-> https://github.com/w3c/wot/blob/master/proposals/td-restructuring/mkovatsc-use-known-names.jsonld Matthias' proposal|
07:18:31 <dape> ... essentially base uri
07:18:47 <dape> ... instead of allowing array it should be at most ONE base uri
07:19:07 <kaz> i|Instead of|-> https://github.com/w3c/wot/issues/289 Issue-289|
07:19:13 <dape> ... alternate protocols may use absolute uri
07:19:14 <kaz> rrsagent, draft minutes
07:19:14 <RRSAgent> I have made the request to generate http://www.w3.org/2016/12/14-wot-td-minutes.html kaz
07:19:28 <dape> SK: changes are as follows
07:19:38 <dape> ... instead of endpoint we use links
07:22:31 <kaz> (much noise on WebEx and people had to rejoin...)
07:22:57 <dape> SK: question to group. What do people think
07:23:47 <dape> ... should simplify processing.. no arithmetic for detecting right uri et cetera
07:23:56 <dape> DP: +1
07:24:09 <dape> MK: +1
07:24:16 <kaz> Meeting: TD Restructuring
07:24:17 <dape> TK: think is good
07:24:20 <dape> Kaz: +1
07:24:35 <dape> Uday: fine by me
07:24:49 <kaz> YY: +1
07:25:10 <dape> q+
07:25:36 <yingying_> s/vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv                                                                                                 +1//
07:26:01 <dape> DP: what about type vs mediaType?
07:26:12 <dape> MK: HTML uses type
07:26:19 <dape> ... conflict in JSON schema
07:26:30 <dape> ... however, should be fine
07:26:40 <katsu> katsu has joined #wot-td
07:27:35 <dape> ... once we have everything together we might consider special naming
07:27:44 <dape> ... OR scoping should resolve issue
07:28:19 <dape> SK: Agree ... may confuse a bit
07:29:16 <dape> DP: see difference in JSON schema vs web-linking type
07:30:04 <dape> ... JSON schema tools are out there
07:30:12 <dape> MK: web linking tools come up also..
07:30:16 <dape> ... so same same
07:30:18 <katsu> present+ Katsuyoshi_Naka
07:31:29 <kaz> rrsagent, draft minutes
07:31:29 <RRSAgent> I have made the request to generate http://www.w3.org/2016/12/14-wot-td-minutes.html kaz
07:31:38 <dape> ... TD uses metadata around actual web linking node
07:32:36 <dape> ... link for "temperature" is the actual link and not the current TD
07:33:17 <dape> SK: what if we keep mediaType?
07:33:35 <dape> MK: breaks web linking.. which is somewhat broken anyway
07:34:53 <dape> DP: Let's try to stick with type and see whether we run into problems... should be resolvable according context
07:35:17 <dape> SK: Darko, do you see any issues?
07:35:54 <dape> Darko: where is "type" defined?
07:36:13 <dape> ... propose to define contexts for IANA and JSON schema
07:37:22 <dape> SK: prefix should make it clear
07:37:27 <dape> q+
07:39:02 <dape> DP: propose to look whether prefixes break JSON schema tools
07:43:33 <dape> Darko: Not sure about the issue... JSON schema tools have issue already .. type is there twice
07:43:42 <dape> DP/MK: context will resolve issue
07:44:25 <dape> Darko: agree w.r.t. to processing but not w.r.t. semantics
07:44:50 <dape> MK: think we need proper model to resolve those and similar issues
07:45:15 <dape> ...e.g., valid JSON-LD document
07:46:59 <dape> Darko: local "type" without prefix means part of TD ... not of JSON Schema
07:47:31 <dape> SK: How can we solve the issue?
07:48:02 <dape> ... going back to mediaType key OR look into JSON-LD and how we can resolve this issue
07:48:20 <dape> MK: It is not proper fixed by just renaming
07:48:34 <dape> ... scoping/context should apply
07:50:13 <dape> MK: for hot fixing propose to rename it to mediaType
07:50:35 <dape> ... anyhow.. have to look into how to resolve it
07:50:48 <dape> SK: OK, lets rename it back to mediaType
07:51:24 <kaz> present+ Katsuyoshi_Naka
07:51:46 <dape> Naka: seems ok also for me
07:52:07 <dape> SK: MK had other issue, #290
07:52:19 <dape> ... rename outputType just to output
07:52:20 <kaz> -> https://github.com/w3c/wot/issues/290 Issue-290
07:53:20 <dape> MK: compared to other examples, outputType, valueType etc it is just a hook
07:53:47 <dape> ... get rid of obsoletes nodes and simplify to input and output
07:54:32 <dape> SK: I do not have a strong opinion
07:54:55 <dape> ... type is already in JSON schema... et cetera
07:55:15 <dape> MK: renaming is less critical...
07:55:29 <dape> ... can reconsider that anyway... short and simple
07:55:42 <dape> q+
07:56:22 <dape> DP: Can you show example..
07:56:46 <dape> MK: remove "valueType"
07:57:50 <dape> SK: not sure anymore why we had "valueType" in the first place
07:58:49 <dape> .. guess it was based on semantic annotation
08:01:13 <dape> MK: propose to put semantic on "type" level
08:02:49 <dape> DP: breaks JSON schema tools
08:03:51 <dape> MK: not doing it causes issues with semantic annotations in complex types
08:04:35 <dape> SK: JSON schema people restarted their work
08:04:42 <dape> ... should get in touch with them
08:04:51 <kaz> q?
08:04:54 <kaz> ack d
08:04:56 <yingying> yingying has joined #wot-td
08:05:20 <dape> DP: Propose to get in touch with them
08:05:31 <dape> ... raise issues
08:05:36 <dape> SK: can do that
08:06:35 <dape> Darko: would not remove valueType unless issue is resolved
08:06:37 <kaz> i|remove "valueType"|-> w3c.github.io/wot/current-practices/wot-practices.html Example TD for Structured Data|
08:06:42 <kaz> rrsagent, draft minutes
08:06:42 <RRSAgent> I have made the request to generate http://www.w3.org/2016/12/14-wot-td-minutes.html kaz
08:07:00 <dape> MK: OK. lets put that on hold
08:07:58 <dape> SK: Will integrate changes to CP
08:08:11 <dape> ... freeze CP latest next week
08:08:28 <dape> ... next week is about PlugFest scenarios
08:09:16 <kaz> [ adjourned ]
08:09:18 <kaz> rrsagent, draft minutes
08:09:18 <RRSAgent> I have made the request to generate http://www.w3.org/2016/12/14-wot-td-minutes.html kaz
08:09:58 <taki> taki has left #wot-td
09:11:13 <zkis> zkis has joined #wot-td
12:58:21 <kaz> kaz has joined #wot-td
13:09:12 <yingying> yingying has joined #wot-td
13:10:45 <yingying_> yingying_ has joined #wot-td
13:24:45 <Zakim> Zakim has left #wot-td