WoT Comm -- 16 Dec 2015

<dsr> sorry for the delay

<koalie> Joerg: for landing page discussion, let's discuss which is best among WOT W3C page, IG page, IG wiki, CG page

<Karen> +1 get started

<koalie> scribenick: koalie

Landing page

Joerg: We have three web pages and one wiki
... if we think of a landing page, scope and activity, it seems w3.org/wot but IG page has probably more info, then wiki page has information to engage
... any comment, preference?

Daniel: We need to keep content up to date and avoid mismatch that there is on first page
... if feasible, reducing the number of pages
... less likely that we forget to update everywhere

Karen: I think from our recent experience, we like to see the landing page be at a higer level
... so that busdev and comm team can use it as first entry page to let people know of the work taking place in the area of WoT
... high-level and plain english type of page
... then, IG and eventually WG pages will have more of the technical details of what you're doing, the scope and where you are, and those need to be maintained

<joerg> could we take a look at http://www.w3.org/WoT/

Karen: the high-level page doesn't need a lot of maintenance.
... we typically update them every few months.
... information stays pretty constant.

Dave: We have an IG page (essentially a list of links and news articles, a fairly common pattern across groups), that I hope people can help populate that page
... let's ensure the info is appropriate
... when linking to a wiki page, I'm not sure we're doing a good job
... we need to ensure sections of the wiki are properly updated
... I suggest people are in charge of some

Joerg: We can try to fix all those different aspects
... I understand we have this WoT page as a kind of overview entry
... and the IG page is the one with the news and links to get engaged into details
... and wiki is the working area

http://www.w3.org/WoT/IG/

https://www.w3.org/WoT/IG/wiki/Main_Page

Joerg: I wasn't quite clear and it's hard to understand the three purposes
... then there's a community page
... which is another overview document

http://www.w3.org/community/wot/

Dave: I think we need more work on the top-level one which doesn't serve its purpose yet

<kaz> Auto and Web landing page: http://www.w3.org/auto/

<kaz> Auto WG main page: http://www.w3.org/auto/wg/

<kaz> Auto WG blog: http://www.w3.org/blog/auto/

<kaz> Auto wiki: https://www.w3.org/auto/wg/wiki/Main_Page

Kaz: These 4 pages ^^
... [Kaz goes over purpose of each]

<inserted> kaz: landing page provides high-level description for industry stakeholders, main page provides links to resources, blog includes entries of the latest news, and the wiki includes the detail of the technical discussions

Darko: Will the main pages remain as we start a WG?

Dave: Yes.
... see Kaz' examples
... there is a role for top-level landing page
... to serve the sort of purposes Karen talked about, and provide pointers to the rest of the pages.

Joerg: I'd propose to polish each
... take existing materials and from this first page, to point further to the rest of the pages

Dave: We are thinking of preparing a data sales sheet for CES early next year
... through that work, we could introduce people to what W3C is doing

Daniel: Do people use tools to keep the pages up to date?
... or is it done manually?

Kaz: landing page and main group page are rather fixed and static
... the blog part is maintained via wordpress
... the main content for the discussion is maintaing by hand in wiki

Dave: Right now, we have the admin control systems for Wordpress
... for the wiki, members of the group have write access

Kaz: We assign each wiki page or sections to specific editors

Yingying: Could we agree on which one is the landing page?
... should we point pointers on the landing page to other pages?
... how could we maintain it?
... how could we decide to @@ now?
... for w3.org/wot/ can we agree it's the WoT landing page?

Joerg: +1

[some other oral agreement]

RESOLUTION: http://www.w3.org/WoT/ is the landing page

Yingying: In the WoT IG, there's a link to the wiki. Is it good enough?

<Karen> +1 easier pointers on this page

Dave: Perhaps we could @@ wikis where we do most of our work

<Karen> Also need to add CES as next event

Joerg: The landing page, which is more static, has outdated upcoming events
... the automotive page uses the right-column differently
... testimonials could be an option
... left-hand side provides references to the sub-pages
... we might say there's a wiki, where the work of the IG happens
... I don't know if we should start testimonials like automotive landing page has
... is that something you asked for? how were they gotten?

Kaz: this was designed by Daniel Davis, formerly marcomm team member

<dsr> Another example is web payments: http://www.w3.org/Payments/

Kaz: we can ask IG members for testimonials
... W3C MarComm team has been working with team contacts like me for Automotive
... talk with stakeholders
... and got the words for testimonials
... we can ask WoT participants as well for testimonials
... Paul Boyes is the chair of the automotive group
... we can get your words, Joerg

Dave: I was going to ask MarComm team about worth of testimonials
... we don't have them on the Web Payments page
... could be a good page, what do you think?

Karen: Always great to have testimonials on landing pages
... static page is a casualty of us having not a lot of staff
... but some information needs to be evergreen
... and it's good to have the calendars updated and a trickly of information
... testimonials would be very nice

Coralie: -1 on rotation
... that adds significant overhead
... I'd suggest you take the same route as Automotive and maintain those by hand
... and rotate them by hand if you have a bunch of them

Dave: it may be easy to do with javascript

Yingying: Who can take the action to call for testimonials among the IG members?

Dave: we can provide an example and invite the IG members to provide testimonials

Joerg: Logo might be difficult for companies given trademarks
... brief testimonials, short statements, yes

Yingying: I remember Ted sent a message previously, asking for testimonials. I can check that and with Ted and Kaz about experience

<scribe> ACTION: yingying to call for testimonials among the IG members [recorded in http://www.w3.org/2015/12/16-wot-comm-minutes.html#action01]

<trackbot> Sorry, but no Tracker is associated with this channel.

trackbot, associate this channel with wot

<trackbot> Sorry, koalie, I don't understand 'trackbot, associate this channel with wot'. Please refer to <http://www.w3.org/2005/06/tracker/irc> for help.

<Karen> +1 IIC quote

trackbot, associate this channel with #wot

<trackbot> Associated this channel with #wot.

<scribe> ACTION: yingying to call for testimonials among the IG members [recorded in http://www.w3.org/2015/12/16-wot-comm-minutes.html#action02]

<trackbot> Created ACTION-17 - Call for testimonials among the ig members [on Yingying Chen - due 2015-12-23].

Kaz: We could consider a few organisation listed on the landscape page, such as echonet in Japan

<inserted> tech landscape page

Dave: I think it's a good idea to ask most well known orgs
... IIC, Open Interconnect Consortium, oneM2M etc.
... I'd like to revisit the issue with logos, we should pursue that; makes impact
... it's fine if companies do not want to provide their logos

Karen: Yes, some will, some won't.
... if you can include it in the design that will be fine.

<dsr> s/open@@consortium/OIC/

Yingying: we have this alliance, any suggestion for others from whom to get a testimonial?

[none]

Yingying: I'll start with the alliance
... after this is done, who has access to modify this page?

Dave: I do
... I'm sure we can add more poeple to the admin list

Yingying: I'll check with systeam.
... this is about landing page

<dsr> ACTION: dsr to look at what wordpress support there is for testmonials [recorded in http://www.w3.org/2015/12/16-wot-comm-minutes.html#action03]

<trackbot> Created ACTION-18 - Look at what wordpress support there is for testmonials [on Dave Raggett - due 2015-12-23].

Joerg: about landing page, testimonials would be on the right and left side would have other pages, right?
... a link to the wiki page would make sense in the left-hand side, as well as an overview description

Yingying: OK.
... I'll get permission to modify and will write something for your review.
... Any more comments?

<dsr> ACTION: Yingying to update left column of WoT landing page to include links to wiki etc [recorded in http://www.w3.org/2015/12/16-wot-comm-minutes.html#action04]

<trackbot> Created ACTION-19 - Update left column of wot landing page to include links to wiki etc [on Yingying Chen - due 2015-12-23].

Dave: That page also needs to be made useful for companies who might be interested in joining W3C for this work.

Joerg: we might find data when we take up the outreach topic

<Karen> +1 slide presentation review

Upcoming events

[[

- CES, Las Vegas(Jan 6-9) - Industry of Things World USA(Feb 25-26)

]]

Karen: W3C suite at CES Jan 5-9
... we need a presentation to show to people
... We won't have a consumer oriented data sales sheet
... but we're aiming to have it for the other event, Industry of Things World USA in San Diego in February

<dsr> Here are the slides I presented at the ETSI M2M workshop last week - http://www.w3.org/2015/12/09-wot-m2m.pdf, I am updating them for a presentation to Industry 4.0 next Monday. I plan to update this further for use in CES.

Karen: Any other event people know about?
... or that should be coming on the horizon soon?

Yingying: We need to prepare an industry-focused data sales sheet for the February event

<dsr> The wiki page with a list of events: https://www.w3.org/WoT/IG/wiki/Relevant_Conferences_for_the_Web_of_Things_IG

Yingying: and write a white-paper as starting point for that sales sheet
... I believe Dave is working on it

Dave: yes

Joerg: example to see?

Karen: sure...

-> http://www.w3.org/2012/12/auto_salesheet.pdf 2014 version of Automotive data sales sheet (in the process of being updated)

Karen: We have a designer to help on those; don't worry about the graphics
... just worry about what's interested to present in terms of graphic
... front: high-level data that speaks to the business audience
... back: technical detail that speaks to the technical audience

Joerg: what are the top five messages we want for that page?

Karen: whitepaper is a starting point, unless we know right now what those top-five messages are

Joerg: we can also draw from slides

Karen: Yes, absolutely

Dave: see slides I presented last week http://www.w3.org/2015/12/09-wot-m2m.pdf that I'll update for next week to be more industrial
... what's missing, what's wrong?

Yingying: Deadline for whitepaper, Karen?

Karen: It would be very good to have it by January 4.

Dave: That sounds right.
... we're all rushed
... I have january deadlines for EU projects.

Joerg: Darko and Daniel might have short presentations that we can draw from to provide some focus
... these have two parts: focus part of common presentation of activity and specific
... for the common part, we need to come to a joint understanding

Dave: Yes
... we have to make sure the content we're talking about is at the right marketing level
... it needs to speak to the audience
... we don't want to drill down into the detail of what the group is doing

Yingying: This white-paper can be ready for January 4.
... presentations are needed as well, what is the deadline, Karen?

Karen: 1st presentation, high-level about what W3C is doing in WoT, is January 4 as well.
... it's a hard deadline.
... the 2nd presentation for San Diego event, we have more time, we can have it at the end of January
... we can make it more interesting with a graphic
... we'll have a booth
... two companies already said they want to be part of the W3C booth and do demos

Yingying: Dave, is it OK?

Dave: we can provide a short slide deck in this time frame

Outreach

Daniel: I wanted to comment on what was said previously. We need to agree on slides content.

[review of WoT outreach materials by Daniel and Darko]

<inserted> WoT outreach slides by Daniel and Darko

<Karen> +1 explaining scope

<Karen> +1 good start on slides

<Karen> +1 use cases

karen: Thanks for starting this, Daniel. Good start, very helpful.
... for CES, I think I heard Dave took the action to build a slideset
... is it ok for Dave to re-use that material?

Daniel: Yes, feel free.

Karen: Great. Thank you very much.

kaz++

Karen: Use-cases, in particular consumers examples, would be great for CES
... something in the consumer electronics area

Joerg: Smart home?

Karen: Yes, probably a good thing

Joerg: also look at different classes of controllers, not just smartphones

<kaz> +1 with Karen

<dsr> devices, phones and hubs

Joerg: that may be a message: smart homes, and controllers other than smartphones.

Dave: the slideset we just looked at contains a lot of background information
... content depends on audiences
... for CES, we should focus on problems W3C is solving

Yingying: we'll use the mailing list for comments on the slides?

Dave: Yes, I've already sent to the group
... where I'm struggling a bit: it's hard to compare W3C with the other groups
... what is OneM2M doing

Yingying: Any more comments?

Daniel: What is the length for the presentation?
... 10, 20 minutes?

Karen: for CES, I think somethign around 10 to 15 slides, for a 10-minute conversation
... we want a short presentation
... for the booth in San Diego, similar, could be longer
... we might want to have 2 versions: high-level and more detailed for technical people who want to know more.

Dave: Industry?

Karen: Yes.

<Karen> Coralie: I have to offer regrets to leave meeting now

<scribe> scribenick: Karen

UNKNOWN_SPEAKER: look forward to next call

YingYing: Any more comments on the presentation material?
... for the last three bullets, I pulled them out of minutes from last meeting
... we want to have domain specific use cases
... shall we agree how to collect the domain specific use cases; what else do you propose?

Joerg: I think that should be be covered by this slide set
... those are common questions; differentiation of WoT and IoT we should have a slide
... and even that we can volunteer to have a first shot at that one
... Also what Dave commented on, how our activities relate to others like IIC
... those two are on the radar
... Having our slides for CES and then for industrial, we need to come up with easy to understand stuff
... We have use cases that we compiled at very beginning of IG; they are too complex
... here it's to have them be as easy to understand for the slides
... For CES would be good to use smart home
... and the industrial for February

scribe: Also start one slide each

YingYing: use cases are already there but need to modify for the target audiences

Joerg: not elaborate, but make it easier to understand

YingYing: So these three points are being covered by this material
... we have all the agenda finished
... Are there any other topics to discuss here?

Dave: yes
... I put up a blog for the San Diego event
... on the IG page
... will also be available on the main W3C page

YingYing: pointer?

Dave: It refers to IoTW event in San Diego
... I also want to put up a short blog post promoting the upcoming F2F in January
... Soumya provided me with a logo and a quote
... I will draft text and quote later today; can send around to this list for comments
... We need to remind people to book travel asap
... Meeting at Sophia-Antipolis

<yingying> https://www.w3.org/WoT/IG/

Karen: Good to include that in the CES presentation especially for European companies who may want to observe

Dave: yes, we will have an open day again
... host is looking at who is being invited
... we will charge a fee as host does not have funds to cover meeting expenses

YingYing: ok
... any other comments here?

<Zakim> koalie, you wanted to be excused from this call for conflicting thing

Kaz: Probably we should talk in detail during the next call
... we need to think about testimonials from other standards orgs
... and think about improving or adding liaison organizations to the W3C liaison page
... some are included in the present page, but may want to add some more

Dave: I think this is a topic for a further call; there is a long list of groups in which we are in various stages of discussion

Kaz: right

YingYing: Any more comments?
... if not, I think we can close today's meeting
... thank you for joining
... Next call is 20th of January
... the third Wed of the month

Karen: Good to prepare 20 Jan for San Diego
... and rest for CES by email

YingYing: thanks all

[adjourned]

- DRAFT -

WoT Comm

16 Dec 2015

Attendees

Contents

Landing page

Upcoming events

Outreach

Summary of Action Items

Summary of Resolutions

Scribe.perl diagnostic output