12:05:08 RRSAgent has joined #wot-script 12:05:08 logging to https://www.w3.org/2021/01/11-wot-script-irc 12:07:27 Meeting: WoT Scripting 12:07:59 scribe: zkis 12:08:06 Chair: Daniel Peintner 12:08:36 cris has joined #wot-script 12:08:51 Agenda: https://www.w3.org/WoT/IG/wiki/WG_WoT_Scripting_API_WebConf#Agenda 12:08:55 present+ Daniel_Peintner, Cristiano_Aguzzi, Kaz_Ashimura, Zoltan_Kis 12:09:11 Topic: last minutes 12:09:18 -> https://www.w3.org/2020/12/14-wot-script-minutes.html Dec-14 12:09:48 Mizushima has joined #wot-script 12:11:15 present+ Tomoaki_Mizushima 12:11:16 Minutes approved. 12:11:44 Topic: issuu#285 12:11:47 https://github.com/w3c/wot-scripting-api/issues/285 12:11:49 s/issuu/issue 12:13:24 DP: addressed most points, we could close it 12:13:36 ZK: yes, we can close it 12:13:50 DP: any open topic remained? 12:13:59 CA: we can close it 12:14:32 Topic: issue#284 and #278 12:14:44 https://github.com/w3c/wot-scripting-api/issues/284 and https://github.com/w3c/wot-scripting-api/issues/278 12:14:45 DP: mostly about the links updated for the publication 12:15:47 Topic: issue#574 12:15:49 TOPIC: Architecture Terminology, see https://github.com/w3c/wot-architecture/issues/574 12:16:29 DP: M.Lagally brought it up about the Thing fragments. 12:18:16 CA: we should define what is the minimum content of Thing fragment 12:19:00 ... Thing Model vs Thing fragment is a bit open and confusing, we should clarify 12:20:07 ZK: we need a private concept in Scripting, meaning a simple dictionary for initialization 12:20:18 ... and if we can align, we can define a term in Architecture 12:20:36 ... if there is a minimum required content, we should spec it 12:20:44 DP: the minimal content is the empty object 12:21:12 ... it is not clear what is the difference in Thing Model vs Thing fragment 12:21:34 ... a Model is like a typical description, a fragment is more like a JSON 12:21:43 ... instance 12:22:43 ZK: implementations can override the provided dictionary 12:22:56 DP: they should be able to do that even with models 12:24:48 ZK: still think we should have separate definitions for Scripting and Architecture 12:25:09 CA: but it's not just a normal dictionary, since it has to conform certain requirements 12:25:43 ... like syntactic issues 12:26:03 ZK: so you'd like a formal definition and also a validation algorithm 12:26:27 DP: the problem is the JSON schema instance for validating would fail if you'd provide just a property name without and href 12:26:43 ... so it is difficult to come up with this 12:27:43 ... and it has to be the same for every implementation, so it should not be private 12:27:51 CA: we also need to consider the directory use case as well 12:28:03 ... like searching for Things similar to the ones passed 12:28:29 ZK: so a Thing should pass as a model 12:28:38 CA: probably yes 12:29:06 ... but mainly a separate entity, copy some stuff and then throw it away 12:29:34 DP: for a JSON schema validation, we should pick what we have now and mark the rest as optional 12:29:47 CA: then it's just a fragment, if things are optional 12:30:29 DP: the "required" stances could be made optional, then it becomes usable for model/fragment 12:31:43 ZK: we should use "arbitrary fragment", rather than model 12:31:47 CA: I agree here 12:32:11 ... every model should have id, title, ... at least 12:33:00 DP: I hear the Thing Model is more restrictive, but IMO it's generic 12:33:05 ... need to look into this 12:33:26 ZK: we could go by examples, then definitions 12:33:52 DP: we can have a simple definition: take JSON schema and prune all "required" stances 12:34:13 ZK: this is a necessary step, maybe also sufficient 12:34:15 CA: agree 12:35:02 s/Topic: issue#574// 12:35:08 rrsagent, make log public 12:35:12 rrsagent, draft minutes 12:35:12 I have made the request to generate https://www.w3.org/2021/01/11-wot-script-minutes.html kaz 12:35:55 rrsagent, make log public 12:35:57 rrsagent, draft minutes 12:35:57 I have made the request to generate https://www.w3.org/2021/01/11-wot-script-minutes.html kaz 12:37:43 DP: we need to attend the Architecture call with this agreement 12:37:45 CA: I can do that 12:38:34 Topic: validating Thing fragment 12:38:52 DP: we need to spec this, based on today's discussion as well 12:39:14 ZK: should that be in the TD spec? 12:40:16 ... if there are any constraints, we should have an algorithm in the Scripting spec 12:40:31 CA: I agree with Daniel's proposal for validation 12:41:43 DP: so in node-wot, if there is a "required" stance, we just ignore that it is required, i.e. the href can be there, but it can be overridden 12:42:52 ZK: why not creating an explicit JSON schema then for fragments? 12:42:58 CA: I agree 12:43:29 DP: we do it on the fly currently 12:43:54 ... not sure if there are more restrictions on the Thing model? 12:45:09 DP: we should wait on what others will say from the other task forces 12:45:15 ... we leave the issue open 12:45:33 ... in the best case we can assume model == fragment, but let's see 12:46:15 CA: we should track it in an issue 12:46:24 DP: will do that after the call 12:47:27 Topic: discovery-related updates 12:47:36 DP: need to wait on the Discovery TF 12:50:33 Topic: versioning 12:50:46 DP: in the issue we say it's good practice to not break 12:50:57 ZK: but we need to track ABI changes somehow 12:51:18 CA: an impl should be able to tell during runtime which semantic is used 12:51:48 ... what if I want a script to work both with old and new API 12:51:57 ... a version number would allow that 12:52:04 s/ABI/API 12:52:30 s/API/ABI 12:53:35 ZK: looks like we move more towards a REST API style 12:54:36 ZK: the question is what do we need to spec so that every impl respects it 12:54:57 ... is it enough if we track version on node-wot level, or I want all impls behave the same way? 12:55:22 CA: looks like we need at spec level, across all implementations, need to check 12:56:59 ZK: it's easier to have a version in the spec, than not having it, but what text we put in the spec 12:57:26 DP: it's not straightforward in the implementations, though - it must be updated, otherwise useless 12:58:19 ... so I like more that the implementations are clear about versions 12:58:45 ZK: so we can stay with the current status-quo 12:59:01 DP: yes, but CA might have use cases for a spec version 12:59:37 ZK: I am not sure if other web APIs have versions any more 13:00:24 [adjourned] 13:00:29 rrsagent, draft minutes 13:00:29 I have made the request to generate https://www.w3.org/2021/01/11-wot-script-minutes.html kaz 13:16:51 zkis2 has joined #wot-script 13:29:36 Mizushima has left #wot-script 13:53:04 zkis2 has joined #wot-script 14:03:07 zkis3 has joined #wot-script 14:37:32 Zakim has left #wot-script 14:37:39 zkis2 has joined #wot-script