11:00:25 <RRSAgent> RRSAgent has joined #wot-marketing
11:00:25 <RRSAgent> logging to https://www.w3.org/2022/07/05-wot-marketing-irc
11:00:47 <kaz> meeting: WoT Marketing
11:01:57 <Ege> Ege has joined #wot-marketing
11:02:47 <Mizushima> Mizushima has joined #wot-marketing
11:03:41 <dape> dape has joined #wot-marketing
11:03:58 <kaz> present+ Kaz_Ashimura, Ege_Korkan, Daniel_Peintner
11:05:41 <McCool> McCool has joined #wot-marketing
11:05:56 <kaz> present+ Michael_McCool, Tomoaki_Mizushima
11:06:40 <cris> cris has joined #wot-marketing
11:06:46 <kaz> present+ Cristiano_Aguzzi
11:07:40 <dape> scribe: dape
11:08:07 <dape> TOPIC: Approve previous minutes
11:08:21 <dape> -> Jun 14 -> https://www.w3.org/2022/06/14-wot-marketing-minutes.html
11:09:37 <dape> EK: Minutes look good to me.
11:09:46 <dape> ... any remarks?
11:10:10 <dape> -> none -> minutes approved
11:10:19 <dape> TOPIC: Updates
11:10:28 <dape> SUBTOPIC: Analytics
11:10:44 <dape> <Ege showing dashboard>
11:11:03 <dape> EK: currently only I have access
11:11:14 <dape> ... share report in monthly banner
11:11:35 <dape> ... I can invite other to get this report also
11:11:44 <cris> q+
11:12:18 <dape> EK: FYI, report got into Gmail spam
11:12:28 <dape> CA: Ahh, okay... i did not get any email
11:12:36 <dape> ... maybe because of spam also
11:12:41 <dape> q+
11:13:04 <dape> EK: "documentation" page was mostly viewed one
11:13:20 <dape> ... after landing page
11:13:42 <dape> MMC: map is also interesting
11:13:49 <kaz> q?
11:13:51 <dape> ... most people from India
11:13:56 <kaz> ack c
11:13:58 <dape> ack cris
11:15:01 <dape> DP: didn't get email either.. think team-wot should work
11:15:08 <dape> EK: team-wot is chairs only..
11:15:14 <dape> DP: Okay .. I see
11:15:15 <Ege> q?
11:15:16 <dape> ack dape
11:15:25 <dape> EK: Will add you Daniel
11:15:42 <dape> CA: Still issues finding the report in mailbox
11:15:51 <dape> ... we can resolver after the call
11:16:16 <dape> TOPIC: Issues
11:16:24 <dape> SUBTOPIC: Unified Readme
11:16:30 <dape> ->  JSON Schema ca
11:16:40 <dape> s/->  JSON Schema ca/
11:16:46 <dape> ->  https://github.com/w3c/wot-marketing/issues/326
11:17:13 <dape> EK: run into different readmes in repos
11:17:23 <dape> ... suggest to synchronize
11:17:31 <McCool> q+
11:17:39 <dape> ... Cristiano also mentioned the logo
11:17:48 <kaz> ack m
11:17:53 <dape> MMC: agree with harmonizing readme
11:18:08 <dape> ... suggest to also add latest publications
11:18:18 <dape> ... and/or implementation reports
11:18:33 <dape> ... should start with drafting one repo
11:18:38 <kaz> q+
11:18:44 <dape> ... and then take it over for other repos
11:19:06 <dape> ... starting with TD repo
11:19:42 <dape> EK: Yes, TD has several deliverables
11:19:50 <dape> MMC: And TD hast *past* report also
11:20:21 <dape> q?
11:20:42 <dape> Kaz: Clarifying expected topics is good ..
11:21:02 <dape> ... however this is not a marketing issue
11:21:12 <dape> ... maybe discuss it in editors/main call
11:21:58 <dape> MMC: marketing topic since it is about consistency
11:22:10 <dape> ... we can work on template and show it in main call
11:22:21 <dape> Kaz: Agree, but should bring it back to main call
11:22:54 <kaz> ack k
11:22:58 <dape> MMC: Yes, create a template like proposed-readme.md first
11:23:03 <dape> EK: Agree
11:23:09 <cris> q+
11:23:19 <dape> ... back to logo discussion, https://github.com/w3c/wot-marketing/issues/190
11:23:45 <dape> MMC: If we want to have it... it should be small
11:23:48 <dape> q?
11:24:21 <dape> CA: we don't have to block the other issue...
11:24:33 <dape> ... and agree, it shouldn't be very BIG
11:26:00 <dape> EK: can propose the style in template
11:26:48 <dape> SUBTOPIC: New links to WGs
11:26:55 <dape> -> https://github.com/w3c/wot-marketing/issues/285
11:27:17 <dape> MMC: We are still in draft
11:27:33 <dape> ... will publish discovery next week
11:28:02 <dape> EK: TD is fine
11:28:10 <dape> ... nothing todo on this today
11:28:59 <dape> Kaz: w.r.t. to latest published draft.. we can get this automatically
11:29:08 <dape> EK: Agree, should look into this
11:29:10 <kaz> s/to late/the late/
11:29:12 <dape> SUBTOPIC: JSON Schema case study
11:29:18 <dape> ->  https://github.com/w3c/wot-marketing/issues/329
11:29:50 <dape> EK: We talked with postman people and JSON schema people
11:30:36 <McCool> q+
11:30:37 <dape> ... information needs to be published as the WG
11:30:50 <dape> ... we are using JSON schema a lot
11:31:13 <dape> ... got positive feedback from Coralie also
11:31:18 <dape> MMC: Agree
11:31:34 <cris> q+
11:31:37 <dape> ... should collect what we are using JSON schema for
11:32:16 <dape> ... we use it to describe data (and validation)
11:32:50 <dape> ... but we are also using it for describing semantics of data
11:33:58 <dape> ... and in multiple places
11:34:10 <kaz> q+
11:34:22 <dape> CA: different point of view: describe operation input and output
11:34:42 <dape> ... absence of value can not be described (issue exists)
11:34:46 <kaz> ack c
11:34:59 <dape> ... we use JSON schema for validation
11:35:12 <dape> ... and we have a special view.. e.g., extensions
11:35:52 <dape> MMC: lets describe use-cases and the limitations we are running into
11:35:59 <cris> +1
11:36:19 <kaz> ack m
11:36:39 <dape> EK: we also have "JSON Schema in RDF" document
11:37:58 <dape> Kaz: This is a liaison issue .. not just marketing
11:38:04 <dape> MMC: Agree
11:38:30 <dape> ... someone needs to start writing the case study
11:38:44 <dape> EK: Yes, kind of a press release.. with review phase
11:39:08 <dape> MMC: I plan to talk about it tomorrow in main call
11:39:29 <dape> TOPIC: Discussion
11:39:39 <dape> SUBTOPIC: CG Collab: CG Charter
11:39:47 <dape> -> https://github.com/w3c/charter-drafts/pull/392
11:40:22 <dape> EK: we have own repo, see https://github.com/w3c/wot-cg
11:41:04 <dape> ... at the moment most of the referred documents are empty
11:41:13 <kaz> s/we have/the WoT CG/
11:41:15 <kaz> q+
11:42:18 <dape> EK: Draft charter, see https://github.com/w3c/charter-drafts/blob/d76cdd5db4caff82e7bbb2167ad91ed1f3d05ddf/2022/wot-cg-2022.html
11:43:07 <dape> MMC: coordination vs. reporting back paras should be merged
11:43:32 <dape> EK: I merged MMCs suggestions
11:43:51 <kaz> q?
11:44:05 <dape> MMC: current text is ok
11:44:35 <dape> Kaz: I am ok with updated charter draft
11:44:44 <dape> ... would like to repeat important points
11:45:28 <dape> ... 1. clear whether you are acting as chair or as a person
11:45:54 <dape> ... 2. updated charter draft is fine. need to think about concrete activity
11:46:02 <cris> Michael's lost suggestion: https://github.com/w3c/charter-drafts/pull/392#discussion_r902615486
11:46:08 <dape> EK: concrete activity  ? Do you mean web meeting
11:46:28 <dape> Kaz: which part of scope/target by which group
11:46:34 <Mizushima> +1 kaz
11:48:40 <kaz> s/which part/we need to continue to clarify which part/
11:49:06 <dape> EK: one thing about contribution mechanics
11:49:31 <kaz> s|by which group|by which group when we (=WoT-IG/WG and WoT-CG) start actual collaboration.|
11:49:34 <dape> MMC: deliverable in favor of specification
11:50:16 <dape> EK: limitation on chat platforms like gitter?
11:50:41 <dape> MMC: we should not be too specific
11:50:57 <dape> ... like "organizing appropriate tools" ..
11:51:38 <dape> q?#
11:51:42 <kaz> ack k
11:51:44 <dape> ack kaz
11:53:03 <dape> ... CG not being responsible
11:53:25 <dape> Kaz: CGs use different mechanism
11:53:45 <dape> ... handled by Wendy and Ian Jacobs.. not W3C license
11:53:45 <cris> q+
11:54:11 <dape> ... person by person license
11:54:37 <dape> MMC: Chat considered as contribution ?
11:54:59 <dape> Kaz: should talk with the communication team
11:56:59 <dape> ... CG should concentrate use-cases and requirements
11:57:14 <dape> ... actual work should be done in IG
11:57:25 <dape> CA: final directions makes sense
11:57:40 <dape> ... can we also define code of conduct?
11:57:57 <dape> ... just in case.. someone is violating the rules
11:58:05 <kaz> s/should talk/I personally don't think so, but should talk/
11:58:21 <kaz> s/communication team/Communications Team to make sure/
11:58:42 <dape> EK: I think we have one
11:59:02 <dape> https://www.w3.org/Consortium/cepc/#unacceptablebehavior
11:59:34 <kaz> s|actual work should be done in IG|also I personally think technical spec work should be done by the WG/IG side|
12:00:21 <dape> CA: Should we gather a resolution? MMC asked to join in main call.
12:00:29 <dape> ... like accepting charter proposal
12:00:50 <dape> MMC: Maybe send email also
12:01:14 <dape> ... cleaning up draft and mention it in main call#
12:01:22 <dape> s/call#/call
12:01:39 <dape> EK: Okay... will update draft as decided and send email
12:02:17 <dape> MMC: and mentioning "supporting the charter" instead of accepting
12:02:59 <dape> Kaz: I am wondering whether we have concluded the discussion?
12:03:11 <dape> ... or shall we extend this call some more minutes
12:03:56 <dape> MMC: Okay, lets type in proposed resolution
12:05:11 <Ege> proposed resolution: The Marketing TF agrees to bring the WoT CG Charter Draft to the WoT IG Main Call on 06.07.2022 in order to get the support of the IG and start the 1 month review process at the WoT CG.
12:05:55 <Ege> proposed resolution: The Marketing TF agrees to bring the WoT CG Charter Draft to the WoT IG Main Call on 06.07.2022 to request the support of the IG and start the 1 month review process at the WoT CG.
12:06:24 <Ege> resolution: The Marketing TF agrees to bring the WoT CG Charter Draft to the WoT IG Main Call on 06.07.2022 to request the support of the IG and start the 1 month review process at the WoT CG.
12:06:50 <dape> <adjourned>
12:07:01 <kaz> rrsagent, make log public
12:07:05 <kaz> rrsagent, draft minutes
12:07:05 <RRSAgent> I have made the request to generate https://www.w3.org/2022/07/05-wot-marketing-minutes.html kaz
14:01:23 <Zakim> Zakim has left #wot-marketing