15:03:13 <RRSAgent> RRSAgent has joined #wot-td
15:03:17 <RRSAgent> logging to https://www.w3.org/2023/11/29-wot-td-irc
15:03:53 <kaz> present+ Kaz_Ashimura, Ege_Korkan, Cristiano_Aguzzi, Daniel_Peintner, Luca_Barbato, Michael_Koster
15:05:29 <kaz> agenda: https://www.w3.org/WoT/IG/wiki/WG_WoT_Thing_Description_WebConf#November_29.2C_2023
15:07:38 <cris_> topic: agenda
15:07:50 <mjk_> mjk_ has joined #wot-td
15:07:56 <cris_> ege: longer discussion on binding templates
15:08:01 <cris_> ... then on the TD next
15:08:14 <cris_> ... we will discuss about how to manage the process
15:08:21 <cris_> ... and finally on the IANA registry
15:08:27 <cris_> ... anything else to add?
15:08:33 <cris_> topci: minutes
15:08:44 <cris_> ege: we fixed the minutes
15:08:48 <cris_> ... anything else to be fixed?
15:09:00 <cris_> ... minutes approved
15:09:11 <cris_> s/topci/topic/
15:09:17 <cris_> topic: td call slot
15:09:18 <kaz> i/longer/scribenick: cris_/
15:09:30 <cris_> ege: we have input from toumura
15:09:32 <kaz> agenda: https://www.w3.org/WoT/IG/wiki/WG_WoT_Thing_Description_WebConf#November_29.2C_2023
15:09:43 <kaz> i|longer|-> https://www.w3.org/WoT/IG/wiki/WG_WoT_Thing_Description_WebConf#November_29.2C_2023 agenda for today|
15:10:07 <kaz> i|we fixed the|-> https://www.w3.org/2023/11/22-wot-td-minutes.html Nov-22|
15:10:12 <kaz> rrsagent, make log public
15:10:23 <kaz> rrsagent, draft minutes
15:10:24 <RRSAgent> I have made the request to generate https://www.w3.org/2023/11/29-wot-td-minutes.html kaz
15:10:32 <cris_> cris: we pass the dates
15:10:33 <kaz> present+ Tomoaki_Mizushima
15:10:41 <cris_> ege: people can't vote for the past
15:10:45 <cris_> ... it is problematic
15:11:10 <kaz> q+
15:11:14 <cris_> ... I record inputs we have and create a new one
15:11:44 <cris_> kaz: do we need anymore additional participant?
15:11:52 <cris_> ege: maybe only Kudzai
15:12:05 <cris_> kaz: ah in that case we can close it and check directly with them
15:12:08 <kaz> s/anymore/any more/
15:12:27 <cris_> s/and create a new one//
15:13:12 <cris_> ege: we will start with the new slot after holidays
15:13:21 <cris_> topic: TD 1.1
15:13:59 <cris_> ege: most of the issues got deferred to TD 2.0
15:14:04 <cris_> ... we need to categorize them
15:14:11 <cris_> ... I closed very obvious issues
15:14:45 <cris_> ... please check you emails for closed issues if you have any remarks let us know
15:14:55 <cris_> subtopic: transition request
15:15:01 <cris_> ege: it will happen next week
15:15:07 <cris_> ... we will have a publication soon
15:15:08 <kaz> q+
15:15:14 <cris_> ... 5th or 6th
15:15:30 <cris_> kaz: the request has been approved, we are working on the final details
15:15:48 <cris_> ... expected publication date is December 5th
15:16:15 <cris_> topic: binding templates
15:16:54 <cris_> subtopic: PR 318
15:17:09 <cris_> ege: last week we agreed to clean up URI schemes
15:17:19 <cris_> ... dogan did that
15:17:26 <cris_> ... and we merged the PR
15:17:35 <cris_> ... it fixes some points in the bacnet binding
15:18:00 <kaz> s/or 6th//
15:18:05 <cris_> ... with this there a still some small fixes to the bacnet that needs to be done
15:18:19 <cris_> ... use the label to search for them
15:18:23 <cris_> ... we can close issue 302
15:18:32 <cris_> ... it was fixed by 318
15:19:08 <cris_> subtopic: issue 319
15:19:16 <kaz> s/the request/the transition request/
15:19:23 <cris_> ege: it is not clear in the introduction what we are talking about
15:20:01 <kaz> i|approved|-> https://github.com/w3c/transitions/issues/579 Transition Request|
15:20:10 <kaz> ack k
15:20:12 <kaz> rrsagent, make log public
15:20:16 <kaz> rrsagent, draft minutes
15:20:17 <RRSAgent> I have made the request to generate https://www.w3.org/2023/11/29-wot-td-minutes.html kaz
15:20:23 <cris_> ... it is better to explain better use cases for non-experts and explain that is about modbus tcp
15:21:05 <cris_> cris: I can do it
15:21:09 <cris_> ege: I can also help
15:21:18 <cris_> subtopic: PR 320
15:21:20 <kaz> meeting: WoT-WG TD-TF
15:21:22 <kaz> rrsagent, draft minutes
15:21:23 <RRSAgent> I have made the request to generate https://www.w3.org/2023/11/29-wot-td-minutes.html kaz
15:21:29 <cris_> ege: it is about modbus prefix
15:21:29 <kaz> chair: Ege, Koster
15:21:31 <kaz> rrsagent, draft minutes
15:21:32 <RRSAgent> I have made the request to generate https://www.w3.org/2023/11/29-wot-td-minutes.html kaz
15:22:23 <kaz> i|we have input fro|-> https://doodle.com/meeting/participate/id/dwkzgZrd Doodle|
15:22:31 <cris_> ... plus a smal fixes in the examples
15:24:14 <kaz> i|it is about|-> https://github.com/w3c/wot-binding-templates/pull/320 PR 320 - Minor modbus improvements|
15:25:47 <kaz> i|it is not clear|-> https://github.com/w3c/wot-binding-templates/issues/319 Issue 319 - Better Explaining the current use case of the Modbus Binding|
15:25:47 <kaz> present+ Mahda_Noura
15:26:18 <cris_> cris: fixed the prefix, minor fixes in the example, and fixed the context url
15:26:18 <cris_> ege: looks good
15:26:25 <kaz> q+
15:26:42 <cris_> kaz: I'm ok with the fixes
15:26:56 <cris_> ... but why do we prefer modv instead of modbus
15:27:05 <mahda-noura> mahda-noura has joined #wot-td
15:27:15 <cris_> ege: it is from Manu Spoony recommendations
15:27:31 <cris_> ... we basically put a v to avoid people get confused
15:27:39 <cris_> ... and it also aligned with the others
15:27:49 <sebastian> sebastian has joined #wot-td
15:27:49 <mahda-noura> present+ Mahda_Noura
15:27:49 <kaz> s/confused/confused with actual modbus protocol/
15:27:58 <kaz> present+ Sebastian_Kaebisch
15:28:04 <cris_> subtopic: ISsue 293
15:28:27 <cris_> ege: we dag deper in the implementations to understand how to deal with the types in modbus
15:28:37 <cris_> ... the final outcome is promising
15:28:44 <kaz> i|last week we|-> https://github.com/w3c/wot-binding-templates/issues/118 Issue 118 - Introduce contentType byte order|
15:28:50 <cris_> ... there are lot of fine details to keep in mind
15:29:00 <kaz> q?
15:29:01 <kaz> ack k
15:29:13 <kaz> q+
15:29:31 <kaz> rrsagent, draft minutes
15:29:33 <RRSAgent> I have made the request to generate https://www.w3.org/2023/11/29-wot-td-minutes.html kaz
15:29:39 <cris_> ... I evaluated the one word and three word approach
15:29:55 <kaz> s/ISsue/Issue/
15:29:59 <cris_> ... they both have pro and cons that we discussed in the issue
15:30:22 <kaz> i|we dag|-> https://github.com/w3c/wot-binding-templates/issues/293 Issue 293 - [Modbus-binding] type conversion based on byte and word order|
15:30:28 <cris_> ... we have evaluated different libraries
15:30:46 <cris_> ... I made all findings available in the comment
15:31:31 <kaz> rrsagent, draft minutes
15:31:32 <RRSAgent> I have made the request to generate https://www.w3.org/2023/11/29-wot-td-minutes.html kaz
15:31:45 <cris_> ... defaults are easier in the three words approach
15:33:30 <cris_> ... byte swapping and endianess are the same
15:33:57 <cris_> ... the problem is that different communities use the same term for the same concept
15:34:18 <luca_barbato_> q+
15:34:20 <JKRhb> JKRhb has joined #wot-td
15:34:56 <cris_> q+
15:35:20 <cris_> ... I like sebastian's proposal
15:35:26 <kaz> present+ Jan_Romann
15:35:47 <sebastian> q+
15:35:57 <cris_> ... instead of using Change I would use another term like lowWordFirst
15:36:38 <cris_> kaz: having this kind of detail discussion is important. As I mention last week I'm still not really sure what level of databinding we have to support
15:36:59 <cris_> ... we can talk about the approach before
15:37:20 <cris_> ... for example we can concentrate to the ASCII mode as a starting point
15:37:29 <cris_> ... but if we want to go for the bytes
15:37:52 <cris_> ... we have to understand length
15:38:20 <cris_> ... modbus sensor can be polled
15:38:36 <cris_> ... implementations can store the data for one day
15:39:27 <cris_> ege: ok it is a nice use case, but for now let's keep it simple
15:39:39 <cris_> ... I agree for a real web thing we should have a streaming discussion
15:41:08 <cris_> kaz: ok, I'm not objecting with this simple starting point
15:41:17 <Ege> q?
15:41:19 <cris_> ... we need to think about future use cases too
15:41:20 <kaz> ack k
15:41:40 <cris_> luca: In the end modbus is all about dealing with 16bits registers
15:42:11 <cris_> ... all the perceived complexity is about the fact that you can read multiples registers
15:42:20 <cris_> ... we have also coils single booleans
15:42:29 <cris_> ... those are the basic building blocks
15:42:41 <cris_> ... and we have to describe them first.
15:43:06 <cris_> ege: int32 is very common, but everything more complicated is out of scope right?
15:43:47 <cris_> luca: modbus has the ability to read/write multiple registers but at the end we are dealing with 2 bytes (16 bit)
15:44:00 <cris_> ... we have to describe endianess
15:44:13 <mjk_> q+
15:44:29 <cris_> ... and when we lamp them all togheter it stars to have additional problems
15:45:08 <cris_> ... we should try to keep naming as simple as possible to allow newcomers understand
15:46:18 <kaz> s|we need|but we need to clarify now we're concentrating on a simple mechanism of one-shot request/response with one byte or two for both the TD producer and the TD consumer. And also we need to work on clarify further possible use cases on how to use Modbus data, e.g., recording multiple data for one whole day and process it at once, to think about the requirements for existing IoT systems.|
15:46:21 <kaz> rrsagent, draft minutes
15:46:23 <RRSAgent> I have made the request to generate https://www.w3.org/2023/11/29-wot-td-minutes.html kaz
15:46:34 <kaz> ack lu
15:46:36 <kaz> ack cr
15:47:04 <cris_> cris: I would prefer something else than wordOrderChange, but something more evocative
15:47:09 <kaz> s/objecting with/objecting to/
15:47:10 <dape> +1
15:47:12 <kaz> rrsagent, draft minutes
15:47:13 <RRSAgent> I have made the request to generate https://www.w3.org/2023/11/29-wot-td-minutes.html kaz
15:47:20 <cris_> seb: we don't have to over complicate this
15:47:34 <cris_> ... but we have to support the use cases and this use cases are pretty common
15:47:43 <cris_> ... there is no good guideline unfortunately
15:47:50 <cris_> ... that is the reason why we are talking about this
15:47:51 <kaz> s/As I mention/As I mentioned/
15:48:02 <kaz> s/last week I/last week, I/
15:48:07 <cris_> ... are we going to provide this information?
15:48:14 <cris_> ... one word approach is very compact
15:48:18 <kaz> s/databinding/data binding/
15:49:00 <kaz> s/understand length/understand the length to be handled at once for some specific use case./
15:49:01 <cris_> ... if you have a lot of datapoints it is more compact
15:49:16 <cris_> ... there is no perfect term anyway
15:49:28 <kaz> s/for example we/for example, we/
15:49:46 <cris_> ... let's find the words and explain them very well
15:50:18 <kaz> s/we can talk about the approach before/we should discuss some more expected use cases and requirements before diving into this level of details./
15:50:19 <cris_> ege: ideally if we have to define the order per device, you will have one word per form
15:50:22 <kaz> rrsagent, draft minutes
15:50:23 <RRSAgent> I have made the request to generate https://www.w3.org/2023/11/29-wot-td-minutes.html kaz
15:50:29 <cris_> seb: what is the default though?
15:50:42 <cris_> ege: for that I would wait for TD 2.0
15:50:50 <cris_> ... the common connection field
15:50:54 <cris_> ... we can put the information there
15:51:24 <cris_> ... default big endian
15:51:27 <kaz> s/clarify now/clarify (1) now/
15:51:28 <cris_> ... no word swapping
15:52:05 <cris_> seb: I like Ege's proposal
15:52:08 <cris_> cris: +1
15:52:08 <kaz> s/work on clarify/clarify (2)/
15:52:10 <kaz> rrsagent, draft minutes
15:52:11 <RRSAgent> I have made the request to generate https://www.w3.org/2023/11/29-wot-td-minutes.html kaz
15:52:26 <Ege> q?
15:52:29 <Ege> ack s
15:53:04 <cris_> mk: Modbus spec talks about registers and multiple registers?
15:53:07 <luca_barbato_> q+
15:53:33 <cris_> luca: there are multiple commands to do different stuff
15:53:50 <Ege> ack m
15:53:50 <cris_> ... and you cannot read more than X depending on the configuration
15:54:14 <cris_> mk: it doesn't really address the idea of having oderning
15:54:54 <cris_> ... do we really need swapping?
15:55:05 <cris_> ege: you are right
15:55:12 <cris_> ... but it is very common
15:55:19 <cris_> q+
15:55:42 <cris_> ... if you don't putting in the TD you have to do manually
15:55:55 <mjk_> ack mjk
15:56:47 <cris_> luca: you start having the problem when you try to map a double
15:57:19 <cris_> ... and then you stumble upon the swapping problem
15:59:31 <kaz> ack lu
15:59:32 <kaz> ack cr
15:59:34 <kaz> rrsagent, draft minutes
15:59:36 <RRSAgent> I have made the request to generate https://www.w3.org/2023/11/29-wot-td-minutes.html kaz
16:00:10 <cris_> cris: +1 with mk observation. in the future we should have a more systematic approach.
16:01:30 <sebastian> q+
16:01:47 <dape> q+
16:02:14 <kaz> q+
16:02:23 <kaz> ack se
16:03:39 <cris_> dape: I'm in favor of what Michael proposed, mostSignaficatByteFirst
16:04:02 <JKRhb>  I would also be in favor of "least significant" or "most significant"
16:04:37 <cris_> kaz: I agree with previous points, what kind of data should be described? If possible should be aligned with the TD 2.0 use cases.
16:04:41 <cris_> ege: +1
16:04:41 <kaz> ack k
16:04:52 <cris_> ege: anything else?
16:04:52 <dape> ack dape
16:05:15 <kaz> s/with the TD 2.0 use cases/with actual use case descriptions for TD 2.0./
16:05:40 <luca_barbato_> +1
16:06:29 <cris_> +1
16:06:53 <kaz> q+
16:06:54 <cris_> ege: let's go with the proposal and wait for a PR in the next week
16:07:06 <cris_> kaz: maybe the names are good, I'm not sure
16:07:20 <cris_> ... can we use them as candidates?
16:07:28 <cris_> ege: yes we can iterate in the future
16:07:34 <cris_> seb: any alternative?
16:07:46 <kaz> s/good/good at the moment/
16:07:47 <cris_> kaz: I don't really know but we can review them in the future
16:08:10 <kaz> s/I'm not sure/but I'm not sure if it's really good at the moment./
16:08:23 <kaz> s/review them/revisit the naming/
16:08:28 <kaz> rrsagent, draft minutes
16:08:30 <RRSAgent> I have made the request to generate https://www.w3.org/2023/11/29-wot-td-minutes.html kaz
16:09:52 <cris_> subtopic: PR 298
16:10:04 <cris_> ege: not a lot to be done at the moment
16:10:26 <cris_> ... Jan is adding a guide on how to create binding template document
16:10:34 <cris_> ... it binds with the tooling discussion
16:10:53 <cris_> ... there were some reviews to be tackled
16:11:02 <cris_> ... any questions?
16:11:10 <cris_> jan: no questions yet
16:11:13 <kaz> i|not a lot|-> https://github.com/w3c/wot-binding-templates/pull/298 PR 298 - Add additional explanations to vocabulary creation guide|
16:11:16 <kaz> rrsagent, draft minutes
16:11:18 <RRSAgent> I have made the request to generate https://www.w3.org/2023/11/29-wot-td-minutes.html kaz
16:11:30 <cris_> ... regarding Madha's comments, I hope I addressed them
16:11:43 <cris_> ... thank you for the reviews
16:12:09 <cris_> ege: we use activate
16:12:15 <cris_> ... accessing is not used
16:12:43 <cris_> q+
16:12:57 <kaz> ack k
16:13:39 <kaz> ack c
16:13:54 <cris_> cris: how much should be follow the current approach?
16:14:12 <cris_> ege: I'm not sure how much we will comply with the current process
16:17:07 <sebastian> sorry, I have to go. bye
16:19:39 <kaz> q+
16:19:43 <cris_> madha: the wordings are different between the context.jsonld and the ontology
16:20:18 <cris_> cris: yeah so basically this is done by loading the context.jsonld into a RDF database and use it to convert between the ontology
16:21:07 <cris_> q+
16:22:18 <cris_> kaz: in the end the document will be included in the html?
16:22:25 <cris_> ... or do we want to keep this as separate?
16:22:39 <cris_> ege: I don't have a quick answer
16:22:47 <cris_> ... it might be fine to include it in the spec
16:22:50 <cris_> ... it might go there
16:23:06 <JKRhb> q+
16:23:29 <kaz> ack k
16:23:36 <kaz> ack c
16:23:38 <kaz> ack jk
16:23:55 <cris_> jan: think we the creation guide we want to capture the status quo that we have right now
16:23:58 <cris_> ... we can later refine
16:24:07 <cris_> ... and make it more user-friendly
16:24:15 <mjk_> q?
16:24:58 <kaz> i/think we/kaz: this description as MD is fine as a starting point, but thinking about the final location and structure within the spec HTML would be useful to consider how to improve this description./
16:25:02 <kaz> rrsagent, draft minutes
16:25:03 <RRSAgent> I have made the request to generate https://www.w3.org/2023/11/29-wot-td-minutes.html kaz
16:25:22 <mahda-noura> ScribeNick: mahda-noura
16:25:37 <mahda-noura> topic: TD next
16:26:53 <mahda-noura> ege: ege worked on linking work items from sub documents, converted lists to headings and then in the work items we can see the links to them
16:27:57 <kaz> i|worked on|-> https://github.com/w3c/wot/blob/main/planning/ThingDescription/work-items.md TD Next work items.md
16:27:58 <mahda-noura> ...any opinions on this from others?
16:28:07 <kaz> s/work items/work-items/
16:28:07 <kaz> rrsagent, draft minutes
16:28:08 <RRSAgent> I have made the request to generate https://www.w3.org/2023/11/29-wot-td-minutes.html kaz
16:28:23 <mahda-noura> ...ege would work on simplifying the items
16:29:12 <kaz> -> https://github.com/w3c/wot/pull/1160 PR 1160 - TD Planning: Linking Work Items from Sub Documents
16:29:13 <mahda-noura> subtopic: IANA registries
16:29:15 <kaz> rrsagent, draft minutes
16:29:17 <RRSAgent> I have made the request to generate https://www.w3.org/2023/11/29-wot-td-minutes.html kaz
16:29:51 <kaz> -> https://github.com/w3c/wot/blob/main/registry-analysis/Readme.md registry-analysis/Readme.md
16:30:00 <kaz> rrsagent, draft minutes
16:30:01 <RRSAgent> I have made the request to generate https://www.w3.org/2023/11/29-wot-td-minutes.html kaz
16:30:40 <mahda-noura> cris: IANA has a range of possibilities,  in the previous text we were mentioning some examples, having such text is fine, IANA has defined some rules to be used in registries
16:30:53 <mahda-noura> ege: so IANA has a common approach?
16:31:34 <mahda-noura> cris: IANA says you are encouraged to use the policies, but could happen that this doesn't happen
16:32:26 <mahda-noura> ege: I think the generic consideration is good, but wouldn't bother with the other ones
16:32:52 <mahda-noura> ...websocket is relevant and the media types
16:33:54 <mahda-noura> https://github.com/w3c/wot/pull/1161
16:34:29 <mahda-noura> cris: all the submission goes through email
16:34:58 <mahda-noura> ege: maybe the initial submission happens via the form and the rest via email
16:35:19 <kaz> s/https/-> https/
16:35:20 <mahda-noura> ...for the official W3C mechanism we are waiting for Michale Koster
16:35:38 <kaz> s/1161/1161 PR 1161 - docs: IANA procedures for registries summary/
16:35:45 <kaz> rrsagent, draft minutes
16:35:47 <RRSAgent> I have made the request to generate https://www.w3.org/2023/11/29-wot-td-minutes.html kaz
16:35:53 <kaz> q+
16:36:08 <mahda-noura> merged PR https://github.com/w3c/wot/pull/1150
16:37:00 <mahda-noura> kaz: on Thursdays, sometimes there are project review meetings regarding technical meetings, maybe it might make sense if we want to talk about and how we want to use the registry, or questions, or improvements
16:37:31 <mahda-noura> ...I have organized several times about W3C updates, it might make sense to talk about registry track
16:37:35 <mahda-noura> ege: is it weekly?
16:37:49 <mahda-noura> kaz: any members can join
16:38:34 <mahda-noura> ege: maybe we join after we merged the PR from cristiano
16:38:59 <mjk_> q?
16:39:04 <kaz> ack k
16:39:21 <mahda-noura> ege: I talked to some persons on tpac, they gave good inputs
16:39:38 <mahda-noura> kaz: I will talk with them about this
16:39:51 <mahda-noura> subtopic: project management
16:41:04 <mahda-noura> ege: get input on what people like to see, how to you like to structure the evolution of the specification workflow, how to take issues into account, and how we plan to address PRs
16:41:27 <mahda-noura> ...if anyone has experience on this, we can improve our way of working
16:41:27 <mjk_> q+
16:42:30 <mahda-noura> mjk: I think we have alot of work items and potential need to prioritize, have been done a good job until now in prioritizing? I personally think we are doing a bit better
16:42:43 <kaz> s/how to you like/how you'd like/
16:42:59 <mahda-noura> ...we need to manage a set of features, we have alot of ideas, we don't know whether they all fit
16:43:12 <mahda-noura> ...what are requirements and use cases for project management
16:43:51 <mahda-noura> ...having an agenda items is helpful, but maybe having something more formal is helpful
16:44:27 <mahda-noura> ...maybe something lightweight, we need to think about something that is a bit more systematic
16:45:31 <mahda-noura> ege: the current approach is not well organized
16:46:00 <mahda-noura> ...recently we used the github issue and assigned it to people
16:46:43 <mahda-noura> q+
16:47:01 <Ege> ack mjk
16:47:05 <cris_> q+
16:47:08 <mjk_> ackmjk
16:47:11 <mjk_> ack mjk
16:48:37 <kaz> ack ma
16:49:06 <mahda-noura> mahda: personally, I loose track when the number of issues that I have to work on gets too much, and would prefer to have an overview
16:50:22 <mahda-noura> cris: assigning an issue definitly helps, but probably assignee would happen if you know that this will happen in a quick manner, 1 week, and that it digestible in one week. Sometimes there are issues that need more weeks, and something with a higher organization could help
16:50:42 <JKRhb> q+
16:50:47 <cris_> ack c
16:51:35 <mahda-noura> ege: ideally we assign when we know that this person can do the best, best fit, but what if there are some issues that need to do by one persons
16:51:51 <mahda-noura> ...kanban board could help
16:52:28 <mahda-noura> ...we make sure in a one week time frame that the person works on 1-2 issues per week
16:52:49 <mahda-noura> cris: if we have the kanban, we can generate the issue PR discussion by just loooking at it
16:53:24 <mahda-noura> ege: I saw one of the groups in TPAC planning the agenda using something similar to a Kanban board
16:53:35 <kaz> q+
16:54:29 <kaz> ack jk
16:54:32 <mahda-noura> jan: splitting issues that is larger into smaller chunks could also help to distribute the workload
16:56:37 <mahda-noura> jan: I had issues with an overwhelming task with the use cases and requirements
16:56:57 <kaz> -> https://github.com/w3c/wot-usecases/issues/236 an example of wot-usecases Issue 236 - Associate Discovery Requirement with Use Cases
16:57:05 <mahda-noura> ege: the issue should be small
16:58:05 <mahda-noura> jan: mentioned the task list of github
16:58:07 <Ege> q?
16:59:22 <mahda-noura> kaz: think about this kind of workflow for our standardization discussion, i personally think from my viewpoint, WoT WG has been working on different versions, there are already different modules, tools and pieces, etc.,
16:59:56 <mahda-noura> ...i would like to suggest think of a specific process for the specification generation, think about features
17:00:22 <mahda-noura> ege: I agree, the pipeline we are talking should be taken into account
17:00:41 <dape> q+
17:00:44 <mahda-noura> ...one thing I can do is to document the procedure to explain what has been happening so far
17:00:56 <kaz> s/think about this kind of workflow for our standardization discussion,/think about this kind of workflow for our standardization discussion is good./
17:01:04 <kaz> ack k
17:01:13 <mahda-noura> ...e.g., when there was a feature in TD, node-wot would try to implement it
17:01:36 <Ege> q?
17:02:42 <kaz> ack d
17:02:42 <mahda-noura> dape: I wonder in the future how we want to select and rank the isssues
17:03:21 <mahda-noura> ege: we cannot mandate how fast someone should work, I don't think we won't give specific deadlines to people
17:03:41 <kaz> s/different modules, tools and pieces, etc.,/resources and information to clarify better procedure for our spec generation./
17:03:45 <mahda-noura> ...we actually had a plan on this, how to handle all those issues, we talked about this with kaz and Michael Koster
17:05:11 <mahda-noura> ....the initial plan is to categorizing the issues, new features are prioritized, while the tooling is getting settled
17:05:22 <Ege> q?
17:05:30 <kaz> rrsagent, draft minutes
17:05:32 <RRSAgent> I have made the request to generate https://www.w3.org/2023/11/29-wot-td-minutes.html kaz
17:05:54 <kaz> i/this description as MD/scribenick: kaz/
17:06:20 <kaz> i/think we the creation/scribenick: mahda-noura/
17:06:22 <kaz> rrsagent, draft minutes
17:06:23 <RRSAgent> I have made the request to generate https://www.w3.org/2023/11/29-wot-td-minutes.html kaz
17:07:46 <kaz> i|creation guide we|scribenick: cris_/
17:07:47 <kaz> rrsagent, draft minutes
17:07:48 <RRSAgent> I have made the request to generate https://www.w3.org/2023/11/29-wot-td-minutes.html kaz
17:08:10 <kaz> i|creation guide we|scribenick: cris_|
17:08:12 <kaz> rrsagent, draft minutes
17:08:13 <RRSAgent> I have made the request to generate https://www.w3.org/2023/11/29-wot-td-minutes.html kaz
17:08:35 <kaz> [adjourned]
17:08:36 <kaz> rrsagent, draft minutes
17:08:37 <RRSAgent> I have made the request to generate https://www.w3.org/2023/11/29-wot-td-minutes.html kaz
17:09:19 <kaz> s/i personally think from my viewpoint,/On the other hand, I personally think/
17:09:21 <kaz> rrsagent, draft minutes
17:09:22 <RRSAgent> I have made the request to generate https://www.w3.org/2023/11/29-wot-td-minutes.html kaz
17:09:55 <kaz> s/working on different versions/working on spec generation for two versions of specs/
17:09:58 <kaz> rrsagent, draft minutes
17:09:59 <RRSAgent> I have made the request to generate https://www.w3.org/2023/11/29-wot-td-minutes.html kaz
17:10:20 <kaz> s/there are al/so there are al/
17:10:31 <kaz> rrsagent, draft minutes
17:10:32 <RRSAgent> I have made the request to generate https://www.w3.org/2023/11/29-wot-td-minutes.html kaz
17:10:44 <kaz> s/resources/enough resources/
17:12:31 <kaz> s/i would like to suggest think of a specific process for the specification generation, think about features/Then I'd like to suggest we think about the basic procedure to generate specs starting with the use cases first, then extract requirements, then analyze gaps with the existing version of standards, then think about necessary features based on those considerations./
17:12:37 <kaz> rrsagent, draft minutes
17:12:39 <RRSAgent> I have made the request to generate https://www.w3.org/2023/11/29-wot-td-minutes.html kaz
19:52:11 <Zakim> Zakim has left #wot-td