W3C home > Mailing lists > Public > public-wot-ig@w3.org > September 2021

[wot-marketing] minutes - 7 September 2021

From: Kazuyuki Ashimura <ashimura@w3.org>
Date: Mon, 27 Sep 2021 11:43:47 +0900
Message-ID: <87tui6lov0.wl-ashimura@w3.org>
To: public-wot-ig@w3.org, public-wot-wg@w3.org
available at:

also as text below.

Thanks a lot for taking the minutes, McCool!



      [1] https://www.w3.org/

                             WoT Marketing

07 September 2021

   [2]Agenda. [3]IRC log.

      [2] https://www.w3.org/WoT/IG/wiki/Marketing_WebConf#Sept_7.2C_2021
      [3] https://www.w3.org/2021/09/07-wot-marketing-irc


          Daniel_Peintner, Kaz_Ashimura, Michael_McCool,
          Philipp_Blum, Sebastian_Kaebisch, Tomoaki_Mizushima





    1. [4]review minutes
    2. [5]web page review
    3. [6]new articles
    4. [7]dissemination
    5. [8]other issues

Meeting minutes

  review minutes


      [9] https://www.w3.org/2021/08/31-wot-marketing-minutes.html

   McCool: one thing; we added dates for the F2F but we are still
   discussing them, so maybe we should add a "subject to change"
   … as for contacts, the discussion was about how to do contacts
   without posting emails, which are troublesome
   … github is an option

   Sebastian: and github has a new feature, discussions, we should
   look at

   Sebastian: I see we also looked into issue 179, on tooling to
   keep events updated
   … who was going to check into it?

   Kaz: we should look at PLH's message first

   McCool: could this be copied to the issue so we can find it?

   <kaz> [10]just to make sure, PLH's message pasted again

     [10] https://lists.w3.org/Archives/Member/chairs/2021JulSep/0038.html

   Sebastian: (copies link to issue - members only)

   <kaz> [11]also meeting organization guideline

     [11] https://www.w3.org/Guide/meetings/organize.html

   McCool: can also add above link to guidelines

   McCool: it also occurs to me this might be a better system than
   the outlook invites I have been using

   Daniel: can these events be public or private?

   Kaz: I think all events are public

   Daniel: would be good to see if we can merge this content
   inline into our page

   McCool: probably a database and a script under the covers on
   that page

   Kaz: we should clarify our requirements and then ask PLH and
   Denis about possible Web APIs for that purpose

   Sebastian: would also be useful to have a link to events on the
   main page (just under the opening para)

   Sebastian: any objections to publishing the minutes?
   … hearing none, these will be published

  web page review

   Sebastian: ok, so back to my thought about events, we can add
   another sentence

   McCool: or just extend the current one with "and Events" where
   "Events" is a link.

   Sebastian: creating issue [12]https://github.com/w3c/

     [12] https://github.com/w3c/wot-marketing/issues/198

   McCool: as for other changes, the dates listed for the F2F are
   not correct anymore
   … in the last main call we discussed/decided to delay the
   second week of meetings to align with the official TPAC

   Daniel: I will make these changes immediately then

   Sebastian: ok

   McCool: the wiki page for the vF2F also needs cleanup

   Sebastian: some tweets would be good, i.e. for the plugfest

   McCool: for the plugfest, can link to the event directory in
   … but we should not tweet a link to the f2f page until after we
   clean it up

   <sebastian> [13]https://www.youtube.com/watch?v=i_bNWV1CgeA

     [13] https://www.youtube.com/watch?v=i_bNWV1CgeA

   McCool: under videos there was a short status update I prepped
   for the AC meeting that we could link

   McCool: I would also organize the videos so the first couple
   are recent intros, and then the "others" are in another
   category that are in reverse chronological order

   Daniel: I can do that

   Kaz: btw the W3C Team is looking at another video provider
   (other than youtube)

   <kaz> [14]new video service test, fyi

     [14] https://www.w3.org/Graphics/Color/Workshop/slides/talk/verou

   Sebastian: let's have a look when it is ready

  new articles

   Sebastian: see the agenda, I found a number of new articles
   … first one I wrote (in German), is a practical introduction
   … published in Heise Online
   … links to a github site providing sample code in node-wot
   … kaz also shared a link to an article in Japanese
   … about Takanaka using WoT for smart building systems

   Kaz: they are using WoT to integrate various systems, also
   using digital twins, etc.
   … we are currently trying to contact them, ask them to join as
   a member, or at least the CG

   Sebastian: unfortunately google translate did not work

   <kaz> [15]same news from NEDO

     [15] https://www.nedo.go.jp/news/press/AA5_101428.html

   Sebastian: also, today there was a new video from Siemens on
   building automation using WoT
   … and semantic web technologies
   … unfortunately the audio is in german

   McCool: think we should post link to video page anyways, people
   can use the autotranslation feature

   McCool: should we be updating the "implementations" page?
   … with both Desigo and Takanaka

   Daniel: we do link to sayWoT

   Sebastian: Desigo CC is not a consumer thing, but a business

   McCool: still, I think the information is useful even if the
   average developer can't use it directly
   … i.e. for business people to see who is using it

   McCool: one problem is the page with the list of
   implementations is called "Developer Tools" and is not just a
   list of systems using it
   … suggest another page called "Usage" or "Adoptions"

   Sebastian: let's discuss next time


   Sebastian: would like to hear about TUM's tutorials; but they
   are not here today
   … and Philipp has been working on some tutorials

   Philipp: shared some short videos already
   … current status is the Arduino library is basically migrated
   to use WoT standard
   … also wrote to a couple of news outlets about publishing

   Sebastian: will this be a blog article?

   Philipp: they are open to multiple articles, so I am thinking a

   Sebastian: how about next week we see if we can review a draft?
   … need to avoid posting it public before it goes to to the

   McCool: suggest just sending drafts by email to specific

  other issues

   <kaz> [16]https://github.com/w3c/wot-marketing/issues/189

     [16] https://github.com/w3c/wot-marketing/issues/189

   Kaz: issue 189
   … have updated "about" section

   <kaz> [17]Issue 164

     [17] https://github.com/w3c/wot-marketing/issues/164

   Kaz: just a link to the web page

   Kaz: issue 164
   … wendy was hesitant to put logos on our web page
   … only want logos that we have MOUs with

   <kaz> [18]issue 142

     [18] https://github.com/w3c/wot-marketing/issues/142

   Kaz: finally, blog content move
   … Coralie is looking into this and is asking system team again;
   about archiving older blogs and/or moving them to the new page

   <kaz> [adjourned]

    Minutes manually created (not a transcript), formatted by
    [19]scribe.perl version 136 (Thu May 27 13:50:24 2021 UTC).

     [19] https://w3c.github.io/scribe2/scribedoc.html
Received on Monday, 27 September 2021 02:43:53 UTC

This archive was generated by hypermail 2.4.0 : Monday, 27 September 2021 02:43:55 UTC