13:58:39 <RRSAgent> RRSAgent has joined #wot-td
13:58:43 <RRSAgent> logging to https://www.w3.org/2023/10/18-wot-td-irc
13:58:52 <kaz> meeting: WoT-WG - TD-TF
14:01:41 <cris__> cris__ has joined #wot-td
14:03:16 <kaz> present+ Kaz_Ashimura, Ege_Korkan, Michael_Koster
14:04:05 <mahda-noura_> mahda-noura_ has joined #wot-td
14:04:14 <Mizushima> Mizushima has joined #wot-td
14:04:15 <mahda-noura_> present+ Mahda_Noura
14:05:55 <kaz> present+ Cristiano_Aguzzi, Jan_Romann
14:06:44 <kaz> agenda: https://www.w3.org/WoT/IG/wiki/WG_WoT_Thing_Description_WebConf#October_18.2C_2023
14:06:59 <mahda-noura_> Scribe: mahda-noura
14:07:16 <mahda-noura_> Chair: Ege
14:08:21 <mahda-noura_> Topic: Organizational
14:08:42 <mahda-noura_> ege: every Thursday the agenda will be prepared, 1 week in advance it will be ready
14:09:02 <mahda-noura_> ...also a new section in the agenda items from other members for suggestions
14:09:45 <mahda-noura_> ...minutes
14:09:52 <kaz> present+ Tomoaki_Mizushima
14:10:22 <kaz> q+
14:10:29 <mahda-noura_> ...TF moderator requests was not received by Ege neither Kaz
14:11:02 <kaz> ack k
14:11:17 <kaz> i|every|topic: Agenda|
14:12:01 <kaz> i|minutes|subotopic: minutes|
14:12:13 <kaz> s/...minutes/... minutes approved/
14:12:22 <mahda-noura_> https://www.w3.org/2023/10/11-wot-td-minutes.html
14:12:27 <Ege> proposal: The TD and Bindings Task Force moderators will be Ege Korkan and Michael Koster until further notice
14:12:35 <kaz> i|approved|-> https://www.w3.org/2023/10/11-wot-td-minutes.html Oct-11|
14:12:40 <kaz> s|https://www.w3.org/2023/10/11-wot-td-minutes.html||
14:12:50 <kaz> q+
14:13:19 <kaz> ack k
14:13:44 <Ege> resolution: The TD and Bindings Task Force moderators will be Ege Korkan and Michael Koster until further notice
14:13:49 <mjk_> mjk_ has joined #wot-td
14:14:31 <mahda-noura_> Topic: Ongoing General Topics
14:14:52 <kaz> rrsagent, make log public
14:14:54 <kaz> rrsagent, draft minutes
14:14:55 <RRSAgent> I have made the request to generate https://www.w3.org/2023/10/18-wot-td-minutes.html kaz
14:15:02 <mahda-noura_> ege: fix intel usage to intell corp PR 1899
14:15:27 <kaz> s/topic: Agenda/subtopic: Agenda/
14:15:30 <mahda-noura_> merged https://github.com/w3c/wot-thing-description/pull/1899
14:15:41 <kaz> s/subotopic/subtopic/
14:15:43 <kaz> rrsagent, draft minutes
14:15:44 <RRSAgent> I have made the request to generate https://www.w3.org/2023/10/18-wot-td-minutes.html kaz
14:16:06 <kaz> i|TF mode|subtopic: TD TF Moderators|
14:16:07 <kaz> rrsagent, draft minutes
14:16:08 <RRSAgent> I have made the request to generate https://www.w3.org/2023/10/18-wot-td-minutes.html kaz
14:16:26 <kaz> i|fix intel usage|subtopic: PR 1899|
14:16:51 <kaz> rrsagent, draft minutes
14:16:53 <RRSAgent> I have made the request to generate https://www.w3.org/2023/10/18-wot-td-minutes.html kaz
14:17:12 <mahda-noura_> ege: merging PR 6, means that the files are served by Github
14:17:14 <luca_barbato> luca_barbato has joined #wot-td
14:17:19 <kaz> i|fix intel usage|-> https://github.com/w3c/wot-thing-description/pull/1899 PR 1899 - Fix "Intel" usage to "Intel Corp."|
14:19:09 <mahda-noura_> ...Mapping files for TD 1.0 and 1.1
14:20:55 <mahda-noura_> https://github.com/w3c/wot-resources/pull/6 PR 6 - Github URL redirect
14:20:59 <Ege> q?
14:21:05 <mahda-noura_> ege: any questions about this?
14:21:24 <mahda-noura_> (none)
14:21:41 <mahda-noura_> ...we will wait for the main call to merge this PR 6
14:21:44 <kaz> i|Mapping files|subtopic: wot-resources PR 6|
14:22:06 <mahda-noura_> jan: is the namespaces file in the TD repo supposed to be kept?
14:22:37 <kaz> s|...Mapping files for TD 1.0 and 1.1|-> https://github.com/w3c/wot-resources/pull/6 wot-resources PR 6 - Mapping files for TD 1.0 and 1.1|
14:22:37 <mahda-noura_> ege: that becomes useless, we recorded the discussion previously on the namespaces.md file
14:22:51 <kaz> q+
14:22:58 <mahda-noura_> ...any opinions on this?
14:23:31 <kaz> ack k
14:23:44 <mahda-noura_> kaz: during the main call I mentioned, all the resources for this kind of information should be installed in wot resource directory
14:23:51 <kaz> s|https://github.com/w3c/wot-resources/pull/6 PR 6 - Github URL redirect||
14:24:32 <kaz> s/during the main call I mentioned/As I mentioned during the main call/
14:25:16 <mahda-noura_> ege: small fixes in the ontology by Mahda which does not affect the index.html file
14:25:44 <mahda-noura_> ...some editors face this issue and cause an error
14:26:03 <kaz> s/all the resources for this kind of information should be installed in wot resource directory/once all the resources are installed under wot-resources repository, this kind of information (redirection mapping) should be also istalled under the wot-resources repository rather than the wot-thing-description repository./
14:26:20 <kaz> rrsagent, draft minutes
14:26:21 <RRSAgent> I have made the request to generate https://www.w3.org/2023/10/18-wot-td-minutes.html kaz
14:26:46 <kaz> present+ Luca_Barbato
14:27:51 <mahda-noura_> mahda: only half of the ontology has this issue with triple quotes not all
14:28:05 <mahda-noura_> ege: do you know why it was added with triple quotes?
14:28:16 <cris__> +1
14:28:21 <mahda-noura_> mahda: no, I didn't check the history of the repo on why
14:28:34 <Ege> q?
14:29:01 <mahda-noura_> merged https://github.com/w3c/wot-thing-description/pull/1901 PR 1901
14:31:18 <mahda-noura_> ege: PR related to string or array of strings in the ontology
14:31:52 <kaz> rrsagent, draft minutes
14:31:53 <RRSAgent> I have made the request to generate https://www.w3.org/2023/10/18-wot-td-minutes.html kaz
14:32:30 <mahda-noura_> mahda: we don't require to necessarily model an array at this point as it will cause unnecessary complexity
14:32:39 <mahda-noura_> ege: do you agree cris?
14:32:42 <mahda-noura_> cris: yes
14:33:02 <kaz> i|small fixes|subtopic: PR 1901|
14:33:26 <kaz> i|small fixes|-> https://github.com/w3c/wot-thing-description/pull/1901 PR 1901 - unnecessary triple quotes around comments|
14:33:43 <mahda-noura_> ege: merged https://github.com/w3c/wot-thing-description/pull/1900 PR 1900
14:33:52 <kaz> i|PR related to|subtopic: PR 1900|
14:34:17 <mahda-noura_> Topic: building templates
14:34:32 <kaz> i|PR related to|-> https://github.com/w3c/wot-thing-description/pull/1900 PR 1900 - Modeling string or array of string in the TTL files|
14:34:44 <mahda-noura_> ege: still no feedback on the guide document, michael koster if you work on the bacnet ontology if this is good enough for the user
14:34:55 <kaz> s/building tem/Binding Tem/
14:34:59 <kaz> rrsagent, draft minutes
14:35:00 <RRSAgent> I have made the request to generate https://www.w3.org/2023/10/18-wot-td-minutes.html kaz
14:35:06 <mahda-noura_> koster: will have some more time this week
14:35:32 <mahda-noura_> ege: BACnet PRs
14:35:40 <kaz> s/guide document,/guide document./
14:35:51 <mahda-noura_> ...fix examples and one formulation on the BACnet binding
14:35:53 <kaz> s/michael koster/Michael Koster,/
14:35:55 <kaz> rrsagent, draft minutes
14:35:56 <RRSAgent> I have made the request to generate https://www.w3.org/2023/10/18-wot-td-minutes.html kaz
14:36:33 <mahda-noura_> ...will fail json-ld validation
14:37:55 <mahda-noura_> ege: any thoughts on this Michael Koster?
14:38:05 <mahda-noura_> mjk: no
14:38:17 <mahda-noura_> ege: merge https://github.com/w3c/wot-binding-templates/pull/307 PR 307
14:38:32 <mahda-noura_> ege: any other comments?
14:38:50 <mahda-noura_> q?
14:38:52 <mahda-noura_> (none)
14:39:32 <mahda-noura_> ege: there is another one on JSON Schema, a conceptual thing that we have to think of as a group
14:40:07 <kaz> rrsagent, draft minutes
14:40:09 <RRSAgent> I have made the request to generate https://www.w3.org/2023/10/18-wot-td-minutes.html kaz
14:40:27 <mahda-noura_> ...in BACnet there is the concept of datatype mappings, keywords that map to json schemas
14:40:45 <luca_barbato> q+
14:41:13 <mahda-noura_> ...where would one see this and use this, we should be more expressive
14:41:21 <kaz> i|still no|subtopic: Guide document|
14:41:39 <kaz> i|BACnet PRs|BACnet binding|
14:41:56 <mahda-noura_> ...there are three services defined in the document, the rest are additional parameters, I added the types, but I don't know how we can really use them, I also used the previous context
14:42:00 <kaz> q?
14:42:04 <cris__> q+
14:42:08 <kaz> ack l
14:42:38 <mahda-noura_> luca: I think that the comment related to open issue and something that I would like to understand better is...
14:43:03 <mahda-noura_> ...BACnet has some ontology or schema and I am not sure what can be included in the TD
14:43:33 <mahda-noura_> ...you mapped some terms, I am not clear what we want to support, and in which direction we want to interoperate
14:44:28 <kaz> s/on this/on this,/
14:44:37 <mahda-noura_> ...the part that confuses me alot is that we already we have a data schema, and hopefully in 2.0 we will have a data map so that there is another way that we take from our data model to whatever we are interacting with
14:44:42 <kaz> q+
14:45:14 <mahda-noura_> ...what is being done with the BACnet is that we are sort of being redundant
14:45:17 <kaz> rrsagent, draft minutes
14:45:18 <RRSAgent> I have made the request to generate https://www.w3.org/2023/10/18-wot-td-minutes.html kaz
14:45:51 <mahda-noura_> ...would be probably nice to have an adapter that maps rather than redundantly describing the vocabulary
14:46:14 <kaz> s|BACet PRs|subtopic: PR 307|
14:46:24 <mahda-noura_> ege: first of all I wouldn't be sad to remove it and would be fine with it
14:46:36 <kaz> s|BACet PRs|-> https://github.com/w3c/wot-binding-templates/pull/307 PR 307 - [BACnet] Fix examples and one formulation|
14:46:38 <mahda-noura_> ...regarding the word mapping, it's not the same
14:47:07 <mahda-noura_> ...if you are coming from the BACnet world, you should model e.g. term bacv:Sequence as an array
14:47:34 <mahda-noura_> luca: if we could come up with some lines of description to know what it is about
14:47:52 <Ege> q?
14:47:54 <Mizushima> Mizushima has joined #wot-td
14:47:56 <mahda-noura_> ege: creates an issue data mappings section has unclear purpose
14:48:16 <mahda-noura_> cris: your discussion with Luca clarified the situation a bit, because I also had a similar concern
14:48:21 <kaz> i|there is another one|subtopic: PR 308|
14:48:40 <kaz> i|there is another one|-> https://github.com/w3c/wot-binding-templates/pull/308 PR 308 - Adding BACnet JSON Schema|
14:48:42 <mahda-noura_> ...I noticed a small typo in the BACnet document, in the type:array missing curly braces
14:48:52 <kaz> rrsagent, draft minutes
14:48:53 <RRSAgent> I have made the request to generate https://www.w3.org/2023/10/18-wot-td-minutes.html kaz
14:49:30 <mahda-noura_> ...this is like a suggestion to not refer to data type mappings rather than vocabulary
14:49:31 <mahda-noura_> ...It's comparing to different concepts
14:50:04 <mahda-noura_> cris: maybe you can put a guide on how to use json schema for BACnet
14:50:19 <mahda-noura_> ...is it more for validating or book keeping?
14:50:25 <mahda-noura_> ege: mainly for book keeping
14:50:29 <mjk_> q+
14:50:39 <JKRhb> JKRhb has joined #wot-td
14:50:48 <cris__> ack c
14:50:48 <mahda-noura_> cris: i would remove it, because it causes clutter and confuses people
14:51:13 <kaz> ack k
14:51:33 <mahda-noura_> kaz: Clarification question regarding the minutes and PR
14:52:19 <mahda-noura_> mkj: the original idea was to use the BACnet in the binding and the json schema to validate, I agree that this is redundant
14:52:29 <kaz> s|merge https://github.com/w3c/wot-binding-templates/pull/307 PR 307|OK with merging PR 307, but would like to wait one more week to get further review./
14:52:43 <mahda-noura_> ...the json schema has the same information in it, I am wondering if there needs to be a reference in the document
14:52:45 <kaz> s|review./|review.|
14:52:47 <kaz> rrsagent, draft minutes
14:52:48 <RRSAgent> I have made the request to generate https://www.w3.org/2023/10/18-wot-td-minutes.html kaz
14:53:01 <mahda-noura_> ...but having a JSON schema is already known and the whole section can be probably be removed
14:53:36 <mahda-noura_> ege: from where
14:53:36 <mahda-noura_> mjk: from the index.html
14:54:17 <mahda-noura_> ege: The idea was to add a description in the Data type mapping section because you can't use them in the JSON schema
14:54:32 <mahda-noura_> ...you need to refer to it somehow
14:54:58 <mahda-noura_> mjk; right, because it's an identifier, now I see the point, there is nothing to actually validate
14:56:29 <mahda-noura_> ege: the really usage of this that I could see, example in JSON Editor online
14:56:31 <kaz> q?
14:56:40 <kaz> s/mjk;/mjk:/
14:56:56 <kaz> rrsagent, draft minutes
14:56:58 <RRSAgent> I have made the request to generate https://www.w3.org/2023/10/18-wot-td-minutes.html kaz
14:57:12 <cris__> q+
14:57:53 <mahda-noura_> luca: we have a @type that is the json-ld type, so that part is sort of fine, but at the same time if we have a consumer that has to care about this part, assuming we have additional forms that don't have BACnet we are back to degraded consumption
14:57:53 <kaz> s|ege: BACnet PRs|subtopic: PR 307|
14:58:23 <kaz> i|ege: BACnet PRs|-> https://github.com/w3c/wot-binding-templates/pull/307 PR 307 - [BACnet] Fix examples and one formulation|
14:58:26 <kaz> rrsagent, draft minutes
14:58:27 <RRSAgent> I have made the request to generate https://www.w3.org/2023/10/18-wot-td-minutes.html kaz
14:58:34 <mahda-noura_> ...if we agree that we can safely ignore what we cannot understand then this is fine
14:59:08 <mahda-noura_> ...I put in the issue the way it might a bit better, because then you have everything in the form where you need the information and can safely ignore the property that is using the BACnet protocol
14:59:17 <kaz> i/fix examples and/ege: BACnet PRs/
14:59:20 <kaz> i|ege: BACnet PRs|-> https://github.com/w3c/wot-binding-templates/pull/307 PR 307 - [BACnet] Fix examples and one formulation|
14:59:22 <kaz> rrsagent, draft minutes
14:59:24 <RRSAgent> I have made the request to generate https://www.w3.org/2023/10/18-wot-td-minutes.html kaz
14:59:49 <mahda-noura_> ...as it is now as 1.1, since it is not defined what to do with any kind of vocabulary term is fine, but you have a problem if you have a strict consumer that it can drop the whole affordance
14:59:50 <kaz> i/ege: BACnet PRs/scribenick: kaz/
15:00:11 <kaz> i/fix examples/scribenick: mahda-noura/
15:00:14 <kaz> rrsagent, draft minutes
15:00:15 <RRSAgent> I have made the request to generate https://www.w3.org/2023/10/18-wot-td-minutes.html kaz
15:01:25 <mahda-noura_> mjk: +1
15:02:36 <mahda-noura_> mjk: the BACnet specifc vocabulary when you see type Real form you are meant to associate it with type number in the affordance, it is not so much validation like json schema validation,
15:03:04 <mahda-noura_> ege: are you suggesting we should do some sort of validation that these do not match?
15:03:47 <mahda-noura_> mjk: it's meant to be a table that contains the correct association between BACnet items...
15:04:20 <mahda-noura_> ...it doesn't make sense to have it in the schema
15:04:40 <mahda-noura_> ...once you generate it in the affordance, you can then validate how the affordance is being used
15:04:58 <mahda-noura_> ege: yes, I think at this point we agree
15:05:09 <Ege> q?
15:05:09 <Ege> ack m
15:05:57 <mahda-noura_> cris: it's not only about consumers that will use BACnet, since you can have a mixture of protocols in the TD
15:05:57 <cris__> ack c
15:06:15 <mahda-noura_> ege: commits to remove BACnet data types
15:06:39 <mahda-noura_> ege: fixed some small things in the index.html
15:07:47 <mahda-noura_> We will wait one week before merging https://github.com/w3c/wot-binding-templates/pull/308 waiting for reviews
15:08:14 <mahda-noura_> Topic: URI variables
15:09:56 <mahda-noura_> ege: had a discussion with Klaus Hardke ,the original motivation was using it when you need to give additional parameters
15:10:21 <kaz> i|had a|-> https://w3c.github.io/wot-binding-templates/bindings/protocols/bacnet/index.html#uri-variables-0 BACnet Binding Temlate - 5.1URI Variables|
15:10:42 <mahda-noura_> ...when expressing inputs, you can give additional pararameters to the operation, but it is weird because the BACnet scheme doesn't contain parameters
15:10:47 <mjk_> q+
15:11:10 <mahda-noura_> ...I talked with Daniel to see how it will look like for in scripting API
15:11:36 <mahda-noura_> https://github.com/w3c/wot-binding-templates/issues/302
15:12:18 <mahda-noura_> ...some ideas generated under the issue
15:12:29 <cris__> q+
15:14:04 <luca_barbato> q+
15:14:19 <mahda-noura_> ege: the proposed ideas by Ege and Luca explained
15:14:56 <mahda-noura_> luca: my full proposal is for the affordance I want to be explicit on the data schema
15:15:14 <cris__> qq+ luca_barbato
15:15:26 <kaz> rrsagent, draft minutes
15:15:27 <RRSAgent> I have made the request to generate https://www.w3.org/2023/10/18-wot-td-minutes.html kaz
15:15:37 <kaz> q?
15:15:38 <mahda-noura_> ...the additional data is the idea of not all protocols require this information, the servient has to keep track of that, in the form you can be explicit in what to map
15:16:24 <mahda-noura_> ...for the mapper you can use a JSON pointer and then put it wherever you need, i.e. it can be protocol specific because you are in the form
15:16:56 <kaz> ack lu
15:17:04 <mahda-noura_> mjk: thank you Luca, great idea
15:17:21 <mahda-noura_> ...there is two concerns, how to parameterize actions
15:17:22 <Ege> let me take scribing now :)
15:17:27 <Ege> otherwise it will be too long
15:17:41 <mahda-noura_> I won't say no :-)
15:17:45 <Ege> scribenick: Ege
15:17:58 <Ege> mjk: The original design is for REST APIs
15:18:15 <Ege> ... we can make this look like an action but it is not right. So we are stuck a bit here
15:18:50 <kaz> s/let me take scribing now :)//
15:18:51 <Ege> ... general problem is that we did not provide a generic affordance
15:19:00 <kaz> s/otherwise it will be too long//
15:19:10 <Ege> ... we did not offer an affordance like colorControl
15:19:16 <kaz> s/I won't say no :-)//
15:19:23 <kaz> rrsagent, draft minutes
15:19:25 <RRSAgent> I have made the request to generate https://www.w3.org/2023/10/18-wot-td-minutes.html kaz
15:19:47 <Ege> ... also the schemas are problematic, we need to map them
15:20:16 <Ege> ... we need to express that some properties need additional parameters
15:20:19 <kaz> i|5.1|-> https://github.com/w3c/wot-binding-templates/issues/302 Issue 302 - URI Variable for BACnet|
15:20:24 <kaz> rrsagent, draft minutes
15:20:25 <RRSAgent> I have made the request to generate https://www.w3.org/2023/10/18-wot-td-minutes.html kaz
15:20:52 <Ege> ... observing has common case of saying how often you want the values or how granular the changes are
15:21:10 <Ege> ... there is a similar problem with CoAP observe
15:21:29 <Ege> ... the problem with BACnet is that there is no query parameters that exist in REST APIs normally
15:22:25 <mjk_> ack mjk
15:22:44 <Ege> ... this is a good direction in general and we need something like this
15:23:07 <Ege> ca: I am aligned with what is proposed by Luca
15:23:14 <Ege> ... we need to abstract from single protocol
15:23:53 <Ege> ... the interactions can be grouped into affordances and the current patterns work for now
15:24:14 <Ege> ... it might be difficult to do this consistently
15:24:39 <luca_barbato> q+
15:24:40 <Ege> ... it would be nice to have something like query parameters
15:24:46 <Ege> ack c
15:24:55 <Ege> ... and not rush a lot with the design
15:25:37 <Ege> ... also now it becomes confusing why one would model something as property or action
15:26:22 <Ege> ... another thing is that in TDD
15:26:54 <Ege> ... in REST APIs you can have /things endpoint and then you can have additional query parameters. These are actions in TDD spec
15:27:33 <Ege> q?
15:29:23 <mjk_> q+
15:30:45 <Ege> ca: when do we start new design on this
15:31:00 <Ege> ek: I think we should fix the bacnet issue asap and move with the new design
15:31:14 <Ege> lb: in http, there is header, body and query parameters
15:31:24 <Ege> ... we did not consider that yet
15:31:54 <Ege> ... for bacnet we can consider additional parameters in the form
15:32:35 <Ege> ... in that case, we can keep them in form so if you do not know what that form is, you can ignore
15:33:58 <Ege> lb: if you have need to put something in a "sidechannel", we have the mapping discussion in place
15:34:06 <Ege> q?
15:34:09 <Ege> ack l
15:34:09 <Zakim> luca_barbato, you wanted to react to cris__ and to
15:34:26 <Ege> mjk: that pattern sounds good
15:34:54 <Ege> ... we have same problem with websockets or other "overloaded" protocols
15:35:59 <Ege> ... also http async notification has a similar issue
15:36:11 <Ege> ... we can keep it in the form, once with constant values and once with data schema
15:36:22 <Ege> ... we can also use the default value
15:38:22 <kaz> rrsagent, draft minutes
15:38:23 <RRSAgent> I have made the request to generate https://www.w3.org/2023/10/18-wot-td-minutes.html kaz
15:39:53 <mjk_> q?
15:40:09 <mjk_> ack mjk
15:41:02 <Ege> ek: (shows proposal on json editor)
15:41:40 <kaz> i|had a discussion with|-> https://github.com/w3c/wot-binding-templates/pull/309 PR 309 - Reorganizing uri variables section|
15:42:25 <kaz> i|had a discussion with|-> https://deploy-preview-309--wot-binding-templates.netlify.app/bindings/protocols/bacnet/#form-terms Preview|
15:42:29 <Ege> mjk: we can use this proposal for now and avoid the design issue
15:42:30 <kaz> rrsagent, draft minutes
15:42:31 <RRSAgent> I have made the request to generate https://www.w3.org/2023/10/18-wot-td-minutes.html kaz
15:43:12 <kaz> q+
15:43:53 <Ege> ek: the type problem is still there though
15:45:25 <Ege> mjk: We need a schema
15:45:39 <Ege> mjk: this type can as well be a json schema
15:47:22 <Ege> ek: the proposal is available at https://github.com/w3c/wot-binding-templates/pull/309#issuecomment-1768754407
15:47:54 <Ege> topic: TD Next
15:47:59 <kaz> s/proposal/proposal including the sample code/
15:48:35 <kaz> q+
15:49:19 <kaz> s/topic: TD Next/
15:49:34 <kaz> topic: Figure issue
15:49:43 <Ege> subtopic: Issue 300
15:50:09 <Ege> tm: The commercial product of Philips is in the Figure 1 of Binding Tempaltes
15:50:17 <kaz> -> https://github.com/w3c/wot-binding-templates/issues/300 Issue 300 - "Philips Hue with HTTP" in Figure 1 of the note of the WoT Binding Templates
15:50:28 <kaz> q+
15:50:37 <Ege> ... I think it is necessary for us to obtain permission to use
15:51:06 <Ege> ... if Ege uses Philips Hue, it is easy to explain the usage
15:51:12 <Ege> ... I think there are many similar products
15:51:20 <kaz> s|-> https://github.com/w3c/wot-binding-templates/issues/300 Issue 300 - "Philips Hue with HTTP" in Figure 1 of the note of the WoT Binding Templates||
15:51:32 <kaz> i|the comme|-> https://github.com/w3c/wot-binding-templates/issues/300 Issue 300 - "Philips Hue with HTTP" in Figure 1 of the note of the WoT Binding Templates|
15:51:35 <Ege> ... it is not good to use such commercial product names
15:51:39 <Ege> ... so it is a policy issue
15:51:44 <kaz> i|The comme|-> https://github.com/w3c/wot-binding-templates/issues/300 Issue 300 - "Philips Hue with HTTP" in Figure 1 of the note of the WoT Binding Templates|
15:51:50 <Ege> ... it is also used in Architecture document
15:52:04 <Ege> ... so the issue is related to the Architecture document as well
15:52:10 <Ege> q?
15:52:15 <kaz> i|The comme|-> https://www.w3.org/TR/wot-binding-templates/images/binding-templates.svg https://www.w3.org/TR/wot-binding-templates/images/binding-templates.svg|
15:52:33 <Ege> kaz: I was not aware of this
15:52:58 <Ege> ... it would be better to say "Commercial Devices" or "Proprietary Device"
15:53:04 <Ege> ... we do not have to list everything
15:53:17 <luca_barbato> q+
15:53:23 <kaz> ack k
15:53:25 <Ege> mjk: It is a common pattern, so we can call a general category
15:54:27 <kaz> q?
15:54:45 <Ege> ek: I think we can say something like "Commercial Devices such as Philips Hue, Echo"
15:54:59 <Ege> lb: Something more generic would be nice
15:55:14 <kaz> q+
15:56:15 <Ege> ek: should we keep example of hue or remove entirely
15:56:35 <Ege> lb: we can replace the image completely with "custom" etc. and then explain later on
15:57:42 <Ege> ... we should probably mention them to advertise for them
15:58:03 <Ege> kaz: I agree with Luca
15:58:53 <Mizushima> +1 Luca
15:59:25 <Ege> https://github.com/w3c/wot/blob/main/planning/ThingDescription/work-items.md
16:00:46 <kaz> ack lu
16:00:52 <kaz> ack k
16:01:11 <kaz> i|git|topic: TD.next|
16:01:59 <Ege> adjourned
16:02:44 <kaz> i/ad/ege: let's continue the discussion on the new work items next week./
16:05:14 <kaz> rrsagent, draft minutes
16:05:16 <RRSAgent> I have made the request to generate https://www.w3.org/2023/10/18-wot-td-minutes.html kaz
20:38:27 <Zakim> Zakim has left #wot-td