Will be using PoC call as a general "community support" call. Should add a link to it from the web pages and also update the wiki appropriately.

The current main page (https://www.w3.org/WoT/) has a reference to the Compose project, see image below. I understand that this project was originally supporting the activities of the group however it reads as if it still does and looks confusing. Also, it gives the impression that this is some research project in the EU level. To make the matters even worse, the domain name of the Compose project seems to not belong to a proper person anymore and displays content of "Bitcoin News Deutschland - Bitcoin News". @ashimura or @draggett , could you remove the link and hopefully also the mention that WoT is still supported by it?

We would benefit from a short description of the target audiences we want to communicate with, what they can be expected to be looking for, and what messages we want to send them.

• Business people interested in the business proposition: what's the problem, why its important, and how we're addressing it. Our materials need to be credible, rational and emotional (following Aristotle's modes of persuasion).
• Technical people who are new to the Web of Things and would like to learn more, and to have an easy way to try it out; and to be able to get in touch with others in their situation
• Standards people who want to understand just what the WoT IG/WG are doing, the roadmap, and how to get involved

How do such people find their way through the W3C website, and how does that relate to what we want to do with the WoT pages?

Add (English) audio to ppt master for node-gen tutorial and regenerate video.
PPT should be master, should have embedded audio and have auto-advance on, then we can generate video from that. Using PPT as a master lets us edit it easily later, while a video can be viewed more easily by everyone.

Hello WoT Marketing Task Force,

I am submitting this issue for a feature request with following details.

Problems:

• The IG, CG and WG website are looking different from a visual and navigation point of view. This renders the W3C WoT unprofessional.
• It is difficult to navigate between these websites.
• Some content that can be written for the 3 websites (like announcing a workshop) has to be re-written for each website with its style of formatting.

Requirements:

• Constrict all websites to the same design language.
• Make the content independent from each website but usable in each website by simple referencing.
• Streamline navigation between the websites through a unified header/menu bar.

Solution Proposals:

• Use the same design template for each website. An example proposal can be found here which is built with Jekyll. The style itself is not a proposal but the fact of using the design is.

Background information:

This issue has been created since WG, IG and CG websites look completely different and makes it difficult to present them in events, such as conferences, meetings etc.

As introduced in the marketing call of 19.03.2020

The first part of the getting started page (until the Thing title) does not sound motivating and is not precise. I do agree with everything mentioned in the text but I am not sure what a newcomer should understand from this.

Also listing all the application domains sounds very generic to me. I do agree that WoT is applicable to any possible domain but listing all of them here looks as if we are not sure and putting everything that would attract visitors to a website, a bit like clickbait and thus cheap.

I find the slides presented by @wiresio that had a winemaker as a use case more convincing. It is obvious that WoT is not only for winemakers, so it makes it a concrete example but abstract/flexible enough that other use cases can rely on it. Also, it is unusual and draws attention by being fresh whereas saying transportation, healthcare, smart cities makes us look like everyone else.

I would propose to start with the winemaker example and link to another page that properly lists and discusses the other use cases.

autoselect timezone on https://w3c.github.io/wot-marketing/activities/general/

In the press release, one of the bullets listing the products using the WoT solutions, lacks detail:

Runtime systems by WoTPy (Python), SANE Web of Things Servient (Java);

What can we say to give a little bit of information on the purpose?

I would like to provide a proposal based on the draft of the redesigned wiki pages at:
https://w3c.github.io/wot-marketing/
https://w3c.github.io/wot-marketing/wg/
https://w3c.github.io/wot-marketing/ig/

The draft in the current form gives the impression that the entire WoT activity is primarily a “two company activity”, since it does not provide any further insights about task forces, their mandate and what is going on in the groups.

I think it is important to communicate to the public the tasks/task forces and current work items and also acknowledge the contributions, commitment and involvement from other people and companies.

Taking this into consideration, I recommend to provide more info about the TF, i.e. TF mandate, leads, deliverable(s), calls, meeting minutes directly on the corresponding WG/IG page.

The sequence of the items on the WG/IG page could be:

• Charter
• Task forces
• Participants
• Mailing List(s)
• How to Join

The task force section should contain the mandate and the deliverable(s) of the TF and point to the corresponding call page and github repo.

The “More” tab and the "Activities" tab could be eliminated, since the activities fall under the task forces of the corresponding working group/interest group.

I hope this proposal makes it easier for newcomers and interested parties to better understand W3C WoT.

"These solutions are in products TODAY!"

I'd like to come up with a subtitle that is more appropriate for a press release. The one sounds like it's for a product brochure.

Let's consider submitting a talk proposal to the API Specifications Conference. Call open/close: June 8/June 29. Event is online, Sept 10 to 11. Speaker should commit to attending all the talks and doing a report-out.

A couple of paragraphs are needed... Ege to do an initial draft in the comments below and/or a PR, then we can discuss. (Also thanks to @egekorkan for bringing this up).

Proposal should be from the WG, speaker will be representing the WoT WG, not themselves.

We should also discuss the format. There are talks (20-25m), discussions (on a topic of general interest, e.g. IoT, security, semantics, etc), and tutorials. I could see us making multiple proposals for discussions... but we should probably do at least a talk.

Currently, there does not seem to be information about WoT implementations.
This information should be made available.

Include a quote from Jeff Jaffe, per consensus of the group on 2020-04-02.

The WoT Marketing Task Force needs a plan for driving regular and timely updates to our pages in keeping with our mission for the Web of Things.

If you have a look at the Wikipedia Internet of Things page, there is a section about Standards and standards organizations. Although Web of Things is mentioned here and there, there is no mention of W3C standardization work in that section.

Hello WoT Marketing Task Force,

I am submitting this issue for a feature request with following details.

Problems:

• There is no clear and concrete information on the standardization's history, which makes it time-consuming to prepare such information to present to newcomers.
• History is understandable only through blog posts in the IG website.

Requirements:

• A chronological history of the WoT Standardization activity in W3C.
• A list of important events in the WoT Standardization activity in W3C.

Solution Proposals:

• A markdown file that can read on GitHub or desktop that lists the events in a chronological order. Important events would be then marked with bold or a special symbol.
• This can be then copied into presentations, Wikipedia, our wiki.

Background information:

This issue has been created when the work on Wikipedia has started. There it was realized that it is difficult to convey how everything has all started. In the meantime, I consider it powerful when we can show how much work has been put into W3C WoT by giving a timeline.

From today's marketing call:

• we need some kind of ok from the TUM side to share this material
• in the material there are many logistic information for the students--> we should remove this
• the videos should be also modified that non-based student information is available
• it would be good if there is no PDF. can that material transformed to html pages?

We need to restructure the landing page. The requirements should be

• shorting the introduction text (a sub-page like "More Background" can provide more details)
• IG and WG pages should be sub-pages of a new landing page
• use one (modern) design for all pages
• use one place for the latest news
• provide a place for developer (links to tools, background about PlugFest/Hackatons, etc)
• provide a place for manger (links to use cases, WoT architectures, etc)
• a nice explain WoT video
• ...

There exists a good proposal from @mkovatsc and @danielpeintner as a starting point. Find the rendered version here .

The new landing pages and the old home page have overlapping information and cause confusion.

The contents of the old home page contains outdated information and should be archived.
We should merge all content that is still relevant with the new pages and provide it there.

Here are some other possible improvements to some phrases in the press release:

1. Current sentence in the press release:
   The WoT building blocks increase interoperability for IoT applications and reduce integration efforts and costs.
   Proposal for replacement:
   Such a common way to Thing's assets increase interoperability for IoT applications and reduce integration efforts and costs for different kind of IoT scenarios such as Thing-to-Cloud, Thing-to-Gateway, Thing-to-Thing, and retrofitting legacy systems.
   </this statement responds a little to the picture>

2. Current sentence in the press release:
   Developers
   WoT simplifies software development and service integration.
   Proposal for replacement:
   Developers and Engineers
   WoT simplifies IoT engineering, software development, and service integration.

3. Current sentence in the press release:
   Device vendors
   WoT provides a mechanism to provide and document open APIs.
   Proposal for replacement:
   Device vendors
   WoT provides a common mechanism to provide and document device's metadata and capabilities.

4. Current sentence in the press release:
   Cloud platform and application vendors
   WoT provides opportunities to provide support services and applications.
   Proposal for replacement:
   Cloud platforms and application vendors
   WoT provides opportunities to simplify device and/or datapoint onboarding, simulating, and provide support services and application development.

For tutorial material that is tied directly to the standard, for example the explainer and perhaps a tutorial on the TD, we should use a consistent PPT template. Perhaps we can use the template from the AC meeting as a starting point, and add the WoT logo...

This can be used for other material besides tutorials as well. A consistent look and feel will help build the brand.

I think it would be nice to have a clear history of how everything began. I have realized this ambiguity when trying to update the Wikipedia page. I myself am not very certain of how everything evolved in the post 2017 times so it would be nice if someone can compile a document that clearly describes what happened in the IG and how WG was formed. The only source of information is the newsfeed in the IG website

Placeholder/Input for Studio 24 website interview (11am CET on Friday)
Feedback welcome!

Visual

• WoT has 3 groups (WG/IG/CG) --> one website with same style (colored differently?)
• easy to navigate from one group to the other
• news/meetings/workshops on 1 site (easier to maintain)
• visually appealing/modern

Technical

• easy to update/maintain (e.g., propose updates via PR --> no need to provide credentials for CMS et cetera)
• Social media integration (e.g., Twitter), youtube/videos, ...
• Auto-population of conference news (keep workload/sync low)
• Multi-language?

Issues of relevance: #19, #7

The proposed new landing are a great start to improve transparency and give newcomers a good start.

However the pages for WG /IG have no information about the task forces.
To understand which task forces are active and how to get more information requires deper knowledge about how the groups work, i.e. navigating to the WG/IG main page and digging around.

I suggest to add the task forces to the top level and include links to the task force repos / call information.

We should support the following use case:

As a newcomer I'm interested in the bi-weekly use case call, I want to find out what has been discussed in previous calls, where to find the repo and schedule and dial-in information of the next call.

The redesigned Wiki page should support a broad spectrum of users and scenarios,
including the following:

1. A new user wants to understand which work is done in which TFs and quickly find the corresponding repo and reach out to the TF chair with a question

2. A potential industrial adopter wants to understand which companies are actively contributing and supporting this standard.

3. TF chairs need to be able to provide a reference on the work they are doing to their management.

The current press release has 2 points I am not sure about.

1. It speaks about "the last two years"
   • do we want to limit the work to 2 years (the first workshop took place in 2014)
2. The text "human-&machine-readable data format" looks and reads a bit strange with the &

After the discussion in the plugfest call of 01.04.2020:

We want to set up a (weekly) meeting that anyone can join, where we introduce a concrete implementation and have sometimes meetings from non-W3C member developers. We decided to create this issue in order to collect some input. Please provide what kind of session you would like to see and whether you would like to collaborate to a session.

Some ideas for the content of these meetings:

• Have a 10 minutes tutorial on how to implement something that is recorded and shared. The rest of the time is for questions and developers talking about their experience. A concrete implementation can be developing a CoAP Thing with node-wot, developing a Consumer application with node-wot, Creating a simulation via Oracle IoT Cloud
• A blank session where people come and talk about their WoT development experience.
• In addition to any above: Organizing presentations from WoT developers (like a conference) that also include non-W3C members.

WoT logo on https://w3c.github.io/wot-marketing/ with white background does not look very nice.

change "white on blue" as recommended by @relu91

Note: @ashimura pointed out that we need to find the right place for W3C logo also

For TPAC, we have an opportunity to host a breakout session which can be used to introduce new people to WoT. In the past during F2F TPAC meetings we have set up physical demos. We could ALSO do online demos during this TPAC but the logistics would be difficult. So I propose we edit together a short demo video, about 15m long, using contributions from various people, with maybe a few bits from the plugfest, and then (for the breakout) add 45m of Q&A. The video can then be used as marketing collateral. This could be videos of actual systems or slides (eg in case of software like a directory service) but in any case should have a voice-over explanation.
To make things more consistent, we can:

• Limit each contributions to 3m
• Need a introduction and conclusion segments (may be able to reuse material from 3m "WoT introduction" video being done for Ralph)
• Can be "individual" system video segments first, followed by "interop" segments
• Maybe have a single narrator
• Decide on some speaking points, use cases, common scenarios
• Guidelines for video style, e.g. slides should use the WoT template

The IG page is currently generated by WordPress and offers limited opportunities for us to customise it.

• https://www.w3.org/WoT/IG/

For instance, I don't know how to change the colour of the red text at the top, nor how to change the HOME button to the /WoT/ landing page. I updated the content of the red text to be the same as for the IG on the landing page.

We now need new blog posts for the Munich workshop and the TPAC F2F. Any volunteers?

During the call on Oct 2, we decided to move a first living website into the https://github.com/w3c/wot-marketing repo.

As starting point we can use the sketch I showed https://danielpeintner.github.io/wot-pages/.
The code can be found here: https://github.com/danielpeintner/wot-pages/tree/gh-pages

It uses jekyll website generator that is fully backed by github.io.
Hence we can simply move it to a gh-pages branch and the dynamic parts like navigation are properly rendered.

Note: since I put it under a subdirectory "wot-pages" in my private repo we might need to update these links. Once an initial setup is done I can propose a PR.

@ashimura can you setup the initial gh-pages et cetera?

Problems:

Sustainability, ESG and SDGs are hot topics lately. It would be great if WoT can be touted to be able to help achieve these goals.

Requirements:

WEF (World Economic Forum) discusses "The effect of the Internet of Things on sustainability".

IoT are said to have effects on society and on the UN's sustainable development goals (SDGs) in the following five SDGs.

• Industry, innovation, and infrastructure (25%)
• Smart cities and communities (19%)
• Affordable and clean energy (19%)
• Good health and well-being (7%)
• Responsible production and consumption (5%)

On the other hand, "interoperability" of devices and different IT back-ends are said two be the largest two barriers to scaling the successes.

Solution Proposals:

In the press release, we can refer to WEF report and claim WoT will contribute to achieve those goals by facilitating IoT interoperability.

I think, this a very important page which different user should get first class information. My proposed structure would be:

1. Web of Things in a nutshell
   Here we should have a nice illustration of a classical IoT scenario (heterogeneous IoT systems) and how WoT would challenge this
2. Where to start
   A couple of references should be provided to find tutorials about WoT (Ege)
3. Decision makers
   We should provide a list of advantages of WoT that will have impact of IoT business. Here we can refer to success story of web. We can also include a link to the testimonials from the WoT press release.
4. Software developer and architects
   Links to developer and tutorial space.
5. Standardization activity
   How to contribute to WoT (e.g., github, getting member etc.)

This is kind of related to Issue #70 but as I mentioned during the WoT Marketing call on Sep. 15, the newly proposed WoT WG page should b upper-compatible o the current WoT WG page and should include the following items too:

• W3C logo at the left top
• Tab menus at the top: Standards, Participate, Membership, About W3C
• Mission
• Getting involved: Wiki, Calls, Mailing list, TFs and Editor's drafts
• Testing: Implementation Report, Add Results, Update Report
• Group details: Our Charter, Participants, How to Join?, Code of Conduct, Royalty Free Patent Policy
• GitHub repo (wotwg), Privacy, Terms

Maybe we could omit some of the obsolete information, though.

At the moment we use SVG images from https://www.flaticon.com/ for our website (e.g., IG Charter, Mailing List, ... ).

These icons were taken from the initial design provided by @mkovatsc. Personally I do not have much experience with the flaticon platform/service and do have issues finding nicely matching icons we might need in the future.

Hence I propose to rethink which icon set we might want to use for the web presence. There are some possible choices like

• https://fontawesome.com/icons
• https://tablericons.com
• https://icons.theforgesmith.com
• ...

I propose to pick one which kind of guarantees a better visual match across different icons.
My personal favorite would be font-awesome.

At the moment, the repository contains full-sized photos of everything. However, these are too big and are loaded like moving down a blind on a web page. I find it bad for the user experience. An example is this: https://www.w3.org/blog/wotig/2017/02/27/w3c-web-of-things-joint-igwg-meeting-in-santa-clara-5-9-february-2016/
(Make sure to do a force-refresh to see the page loading)
Even with a good Internet connection, this image takes 1-2 seconds to load and in TPAC Fukuoka it was taking more than 5 seconds to load. I think we should keep the full-size images but use 500kB (just a rough number) sized images in web pages. Some content management solutions do this automatically but we cannot rely on it since these photos can be used in other locations as well.

The content of the WoT Wikipedia page is quite outdated.

@egekorkan would take care of it.

Please also check issue w3c/wot-architecture#207

The Interest Group website (https://www.w3.org/WoT/IG/) links (towards top right) to the old charter (http://www.w3.org/2016/07/wot-ig-charter.html). It should be changed to http://w3c.github.io/wot/charters/wot-ig-2019.html

I approved too hastily #53
Until they become a W3C Member, I'll comment out that testimonial.

What changes do we want in the short term for the Working Group page, and who can apply the updates?

• https://www.w3.org/WoT/WG/

Document developer journey in order to organize tutorial and documentation

Hello WoT Marketing Task Force,

I am submitting this issue for a feature request with following details.

Problems:

• The IG, CG and WG website are created using different technologies such as WordPress, GitHub etc.
• How the website are managed and generated are not transparent to the outside, making it harder to contribute.
• WordPress restricts the contribution to a certain set of users and makes it impossible for others to contribute directly.
• WordPress makes it more difficult to set up version control.

Requirements:

• Constrict all websites to the same technology
• Make the website source code open source and thus visible for everyone.
• Make it clear where the source code is stored and managed
• Make it possible for anyone to request a change to the website but allow a set of people to accept it
• Have version control, like git.

Solution Proposals:

• Move every website to GitHub as a public repository where WoT members have write access. This solves the requirements in the following way:
  • The code will be open source, thus visible for everyone
  • The source code will be managed by GitHub which is familiar to everyone in the WoT group since all the standardization development goes on GitHub
  • Anyone can contribute to the public repository by making Pull Requests. These Pull Requests can be then merged by anyone with a write access, ideally after talking in the task force meeting.
  • GitHub is based on git version control system that stores all the previous versions and allows for multiple branches to exist

Background information:

This issue has been created since WG, IG and CG are not maintained properly due to the problems mentioned above. As spoken in the TPAC 2019 in the working group meetings, we need to market our work better and websites are one of the primary ways to do so.

Hello WoT Marketing Task Force,

I am submitting this issue for a feature request with following details.

Problems:

• There is currently no social media presence of any WoT group, which reduces our reachable audience.
• W3C Twitter account published only publication related information.
• There is no official way to give a heads-up to the WoT developers about changes. It shouldn't be mandatory to subscribe to the email lists or poll the blog posts for new information.

Requirements:

• Having active social media accounts such as Twitter.
• Have a way to inform developers on small new features without polluting blog posts section.

Solution Proposals:

• Set up a main Twitter account that can be used by CG, IG and WG. An example of the CSS WG is here

Background information:

W3C has a Twitter account where news about publications are published. However, we need a more granular approach that can publish information on little but important things for WoT developers. When we decide to add a feature to the TD spec, it would be nice to give a heads-up to the developers. E.g. "Today we have decided to introduce the keyword multipleOf to the DataSchema vocabulary of Thing Description. Check out the discussion here (link to GitHub issue)". This could be also done by individual people, like some CSS group members do.

My observation is that the Web community is the most active on Twitter.

I am unclear what people want in the short term for the landing page at

• https://www.w3.org/WoT/
  I've commented out the info on the Community Group and dropped the information on meetings.

• add dates to Events on Activities page
  • added dates, see 92c3526. Still misses links
• rename "getting started" to "documentation"
  • see PR #110
• adding "tutorials" under "developers" navigation
  • @danielpeintner suggests to wait until we have content for tutorials
• Video options, make proposals where to place it
  • first proposal see PR #111

Hello WoT Marketing Task Force,

I am submitting this issue for a feature request with following details.

[Remove the contents of each subsection and fill it accordingly before submitting the issue]

Problems:

Tutorial information is too hard to find.

Requirements:

MANDATORY. List the requirements that are needed to fix this problem

Solution Proposals:

Developer Tools -> Developer Resources. Mention "Tutorials" in description. FIRST thing on that page should be a list of tutorials. Tutorials need to be a simple sequence that a new user can follow, broken into manageable chunks. See wot-marketing/tutorials.

"Getting Started" may instead have this material. Each tutorial should also link to "further reading". But this section could also be renamed "Documentation".

Background information:

OPTIONAL. If you need to give some background information, do so here as an explainer

Below is the list of things I have found in the Wiki page and my comments. @ashimura is this what you meant more or less?

Content of W3C WoT pages

IG Wiki Page (https://www.w3.org/WoT/IG/wiki/Main_Page)

Summary of Contents

1. IG/WG co-Chairs and Staff Contacts
2. Current Status of Deliverables
   2.1. Ongoing work documents
   2.2. Concluded documents
   2.3. Delivered documents
3. WebConf Meetings
   • Table of all WoT Meetings in different time zones
   • Daylight saving information
   • Links to each Web Meeting Wiki Page
4. Face-to-Face Meetings
   4.1. Upcoming
   4.2. Past
5. Mailing Lists
6. Other Resources

Comments

Ege

1. IG/WG co-Chairs and Staff Contacts: Should be removed from IG page/Wiki, this is general information
2. Current Status of Deliverables: Not up to date
3. Mailing Lists: Should be moved to a more main page/contact page
4. Other Resources: This whole section should be reorganized

Individual Pages Content

WebConf pages content

This is what is common for each page (except Use Case):

• WebConf Information: Weekly information of when a call is (repeating the table in the main wiki)
• List of obsolete calls
• Time of the call
• Webex and Audio
• IRC Channel information
• Agendas
• List of Minutes

Differences of each page relative to the common:

• Scripting: Has Stash
• Security: Has Schedule, Actions and Future Topics
• Discovery: Has Schedule, Actions and Future Topics
• Marketing: Has Schedule and Actions
• PoC: Has Patent Policy, Purpose
• Main: Has Call Logistics title, archived meeting minutes
• Plugfest: Has actions, past events
• TD: Has victims list for scribes, schedule
• Architecture: Nothing more than common
• UseCase: The schedule is used in another way than the other ones

Comments

Ege

Some webconf pages contain more information that webconf information, like schedule of the deliverables.
I think that there should be a strict template that each TF can fill and not other random information.

README should link to pages that need to hold updated information, such as the list of articles published about WoT, tools, and products using WoT. This is both for readers and so that WoT members can easily find them to update them.

Awesome repositories are a series of curated lists of particular technologies. Of course, there is a repo dedicated to IoT technology. They have a section about IoT standards, should we add W3C WoT? if yes please let me know I can create the PR.

Do we have sign off from Siemens, Eclipse, IBM, Hitachi, Python, and Mozilla to use their names and what we say about them?