15:48:39 RRSAgent has joined #pbg 15:48:39 logging to https://www.w3.org/2020/10/13-pbg-irc 15:49:24 Meeting: Publishing Business Group TPAC Telecon 15:50:37 Date: 13 October 2020 15:51:09 Chairs: Daihei Shiohama, Cristina Mussinelli, Liisa McCloy-Kelley 15:55:41 present+ 15:55:43 present+ wolfgang 15:55:56 Cristina has joined #pbg 15:56:09 Yanni has joined #pbg 15:56:13 present+ 15:59:02 Avneesh has joined #pbg 15:59:14 kaz has joined #pbg 15:59:50 hazel has joined #pbg 16:01:07 present+ 16:01:16 present+ 16:01:22 DanielWeck has joined #pbg 16:01:56 Mizushima has joined #pbg 16:02:22 scribe: Karen 16:02:24 present+ 16:02:27 present+ 16:02:31 present+ 16:02:40 present+ 16:02:53 present- 16:02:54 scribenick: kaz 16:02:56 Liisa: I co-chair with Daihei and Cristina 16:02:56 present+ 16:03:05 Daihei: First presentation, thanks to WoT 16:03:05 present+ Tomoaki_Mizushima 16:03:08 present+ 16:03:29 ...we have Michael McCool, Sebastian and Kaz Ashimura 16:03:39 s/scribenick: kaz/scribenick: Karen/ 16:03:41 sebastian has joined #pbg 16:03:42 ...in publishing we have to learn about what will happen in future, and especially about W3C 16:03:52 ...look at what things are upcoming from W3C, such as WoT 16:03:54 present+ angela 16:03:54 present+ ralph 16:03:55 Vagner_Br has joined #pbg 16:03:59 George has joined #pbg 16:03:59 present+ wolfgang 16:04:01 ...WoT provides collections to all kinds of smart technologies 16:04:03 present+ yanni 16:04:08 present+ hazel 16:04:12 ...I am going to hand this over to Michael to start the presentation 16:04:14 CharlesL has joined #pbg 16:04:16 present+ 16:04:20 present_ vagner 16:04:23 Michael: Thank you; it's a short presentation 16:04:27 present+ vagner 16:04:30 present+ 16:04:32 ...first, talk about what is IoT and what is WoT 16:04:38 ...and how to connect publishing in interesting ways 16:04:41 ...What is IoT 16:04:42 present+ jblair 16:04:48 ...idea of putting devices onto the network 16:04:50 present+ leslie 16:05:01 ...a plant monitor, drone, health device, etc. on internet and send commands to it 16:05:10 ...data collection analysis, plus edge computing 16:05:11 present+ Guilian_Hetzler 16:05:17 present+ charles 16:05:18 ...sensors in environment to control network 16:05:23 present+ dezell 16:05:30 ...IoT is large; many verticals, many places where IoT is deployed 16:05:45 Daihei has joined #pbg 16:05:46 ... al ot of value comes from bridging different verticals; connecting traffic to parking; fire to security systems 16:05:47 ReinaldoFerraz has joined #pbg 16:05:52 present+ 16:05:53 present+ Michael_McCool 16:05:58 ...value is not in the device themselves, but in the services you build on top of them 16:06:05 ...important to make the services available 16:06:12 ...to make these use cases exist 16:06:30 ...IoT has narrow silos, targeting specific verticals such as smart home 16:06:34 ...figure out how to span silos 16:06:45 ...IoT devices often use special protocols for these devices 16:06:47 DanielWeck has joined #pbg 16:06:49 ...payload size might be small 16:07:00 ...Goal of WoTs work inside W#C is to support interoperability 16:07:09 ...the way we are doing this is taking a descriptive approach 16:07:22 ...build your device, and then use WoT description so that others can use it easily 16:07:36 ...have a formal description of how device works 16:07:46 ...basically a JSON file to talk to device, assuming you have authentication for it 16:07:53 ...have to have the right keys to talk to the device 16:08:08 ...you could use OAuth and token server to talk to devices 16:08:18 ...mention we are experimenting with ease of use 16:08:20 ...node red 16:08:26 ...way to talk to devices and do stuff 16:08:32 ...that would fit well into the publishing environment 16:08:35 ...Some use cases 16:08:50 ...Publishing is in transition, going from print books to ebooks 16:08:52 Kyrce has joined #pbg 16:08:57 ...includes text, pictures, formatting like mathmatics 16:09:03 ...know these are still open 16:09:06 ...what is beyond this 16:09:15 ...do you want to embed video, interactive simulations in books 16:09:24 ...use book to do things in your environment, as a user interface 16:09:31 ...this is where IoT use cases come up 16:09:40 ...Let me talk about three use cases that are interesting 16:09:47 ...Hybridcast from NHK 16:09:48 Present+ Kyrce 16:09:57 ...looking to connect TV to home environemnt 16:10:00 ...connect IoT devices 16:10:08 ...you might say, this is a movie, have mood lighting 16:10:08 present+ Ana_Duarte 16:10:21 ...and tells your home environment to set lighting to complement the movie 16:10:28 ...or trigger channel changes based on scheduling system 16:10:35 ...or control the TV as an IoT device 16:10:43 ...novel interface systems; related to accessibility 16:10:55 ...a blind person needs a braille reader; or need a haptic interface 16:11:08 ...connecting can also include to different input/output devices needed for accessibility 16:11:12 ...show you other use cases 16:11:15 ...Interactive education 16:11:28 ...take a science text book that lets me run simulations, or set up an experiment from the book 16:11:40 ...Look at growing plants; understand how water and light affects growing plant 16:11:54 ...plug sensor into soil, see how light affects it; a curriculum example 16:12:02 ...web things do this, but don't connect to IoT devices 16:12:09 ...other things with Hybridcast event 16:12:13 ...consider an audio book 16:12:18 ...a media experience, or with video 16:12:25 ...looking more like a hybridcast 16:12:30 ...ebook is a device 16:12:37 ...maybe command book to play back 16:12:40 ...done in cloud 16:12:43 ...media controls 16:12:46 ...interesting use cases 16:12:52 ...maybe have a discussion 16:13:10 ...this slide shows node red with channel devices; maybe combine with weather app 16:13:16 ...Example of a science notebook 16:13:22 ...embedding math simulations in a book 16:13:27 ...imagine this in a web page 16:13:33 ...ebooks are based on web engines 16:13:39 ...would be helpful for math and science teaching 16:13:44 ...I will stop there for discussions 16:13:50 Daihei: thank you, Michael 16:13:58 ...I am one of co-chairs of Publishing Business Group 16:14:13 ...I am going to talk about... 16:14:16 persent+ danielw 16:14:34 ...WoT for Publishing business; Why IoT? 16:14:41 ...After Michael's wonderful presentation 16:14:45 ...clear that WoT is coming 16:15:00 ...back in the early 2010, I followed these platforms and apps 16:15:03 ...speakers and all that 16:15:15 ...WoT can be a vision of the future of the Web itself 16:15:23 ...lifestyles will benefit from WoT 16:15:39 ...thanks to WoT globally, device systems, content management opportunities 16:15:46 ...likely to contribute to publishing content 16:15:56 ...relate to meeting, watching, listening, playing and learning 16:16:06 ...value of our existence could be missed out 16:16:32 ...provide you with the opportunity to introduce what WoT is, and what it means for Publishing - all types, trade, academic, journal 16:16:36 ...Go through slides here 16:16:40 ...and leave time for Q&A 16:16:51 ...these kinds of technologies are available everywhere and connected to the web 16:17:06 ...various IoT platforms (e.g. smart homes, wearables, healthcare) are all coming together 16:17:20 ...IoT is middleware platform to interconnect among these different IoT technologies 16:17:33 ...on left side you see publishing starting from printing on paper products 16:17:34 q+ 16:17:40 ...from aesthetic level move to movies 16:17:47 ...and combine them into interactive things 16:18:04 ...IoT can integrate all of them into one system, or depending upon lifestyle, connect to all 16:18:10 ...Provide you with an idea of mine 16:18:29 ...multimedia...with multiple interfaces 16:18:35 ...presents new business opportunities 16:18:46 ...My case example, in audio content file with metadata 16:18:49 ...to reproduce 16:18:55 ...with speakers in a house or car 16:19:06 ...and also display recipes where cooking is taking place in case of a recipe ebook 16:19:12 ...based on WoT architecture 16:19:20 ...user can make sure of content on a given devices 16:19:29 ...go through procedures at any moment of reading experience 16:19:35 ...can be applied if web content is available 16:19:42 ...can call up @ content 16:19:52 ...call up video, XR, video games, to play with video content 16:20:03 ...practically, I am trying to introduce idea to collaborate with the WoT team 16:20:06 ...to get to know more about 16:20:10 q+ 16:20:18 ...and to seek opportunities for publishing business interest 16:20:26 ...Give you opportunity to discuss here 16:20:36 ...and here is link to the WoT Interest Group 16:20:57 Daihei: any questions or ideas? 16:21:02 ack Cristina 16:21:04 Cristina: I wanted to add one other point of view 16:21:14 ...discussion on product from pub POV 16:21:24 ...interesting possibilities on the tool and production POV 16:21:29 ...not only the final product you sell on the market 16:21:38 ...but also on the internal workflow in the publishing house 16:21:42 ...could be better understood 16:21:45 JulieBlair has joined #pbg 16:21:46 Daihei: wonderful 16:21:51 ...Michael, any comment? 16:22:04 q+ 16:22:08 Michael: to extent that a publishing house is a manufacturer, yes, it applies 16:22:13 ...back to example of a recipe book 16:22:25 ...have an IoT scale, instant pot, and configure my devices in my kitchen 16:22:35 ...to help me through the recipe; scale displays grams, etc. 16:22:39 ...great example of a use case 16:22:45 ... a whole industry there developing recipes 16:22:48 present+ Reinaldo_Ferraz 16:22:54 ...worth talking about what are people doing in real life? 16:23:04 ...IoT is all about interacting in the real world 16:23:08 present+ 16:23:11 ...where do I connect books and real world 16:23:22 ...Doing home carpentry; cut wood, my hands are busy 16:23:38 ...book is great, but want something to walk me through it because I have gloves on 16:23:43 ...more examples of real world examples 16:23:44 ack Kaz 16:23:51 Kaz: thank you for this discussion 16:23:55 ...in the production phases 16:24:08 ack Kaz 16:24:17 ...Michael mentioned some discussion with Media & Entertainment IG, there were also discussion on the workflow 16:24:28 ...can see production workflow discussions for publishing as well 16:24:41 Michael: where data comes from is important; tooling is important; as with Hybridcast 16:24:54 Kaz: tech in the publishing industry, use Web tech if needed 16:24:59 Daihei: Liisa, please 16:25:01 ack Liisa 16:25:09 Liisa: Wondering in this recipe book scenario 16:25:12 q+ 16:25:17 ...a lot of times the struggle we have as publishers 16:25:30 ...is that the content has to be sliced, diced and delivered 16:25:37 guillian-hetzler has joined #pbg 16:25:43 ...Let's use your example of smart kitchen and scale 16:25:49 ...can we actually put data into the books? 16:26:01 Michael: lots of devices from different vendors 16:26:11 ...instant pot vendor has its own data 16:26:19 ...we are trying to open up the application so you can mix and match 16:26:23 ...that is a general IoT problem 16:26:29 ...second issue is interoperability 16:26:38 ...different vendors have different pressure cooker 16:26:42 ...try to solve that too 16:26:46 ...have a simple interface 16:26:51 ...from content creator POV 16:27:00 ...have temperature cited for example 16:27:08 ...It will be a long struggle, but that is end goal 16:27:17 ...it will take a long time, like with app ecosystem 16:27:25 ...takes a while, and suddenly it is here 16:27:30 ...you also mentioned payments 16:27:35 q+ 16:27:39 ...device manufacturers have motivation to open up interface 16:27:47 ...to monitize data or access to service 16:27:48 q+ 16:27:49 ...adding value to content 16:27:54 ...more of a selling point to publisher 16:28:00 ...not ask customer to pay for, a value add 16:28:04 Liisa: also raise for you 16:28:09 ...smart frames and screens 16:28:21 ...I have a picture frame, and sends new artwork; art books are another example 16:28:33 Michael: yes, buy an art book and show the art in the picture frame in your home 16:28:36 q- 16:28:44 Daihei: we have two minutes left for this item 16:28:49 ...we have three people on queue 16:28:52 ack Sebastian 16:28:59 Sebastian: I like the idea of the recipes 16:29:00 Garth has joined #pbg 16:29:08 ... I am not an expect; do you have APIs? 16:29:11 ...for ebooks, etc.? 16:29:22 Daihei: could you respond, Liisa? 16:29:33 ...I am glad the whole discussion is arising; let's come back 16:29:38 ...and why don't we extend from there 16:29:49 ack Jeff 16:29:55 Jeff: I found this very interesting 16:29:59 ...DRM issues 16:30:04 ...characterize this 16:30:08 ...with digital signage 16:30:12 ...batches on devices 16:30:29 ...in remote areas, at home; manufacturer can provide their manual as an EPUB and set up device through reading system 16:30:32 ...it's DRM and secure 16:30:35 ...question about API 16:30:43 s/expect;/expert;/ 16:30:55 ...if API provided by publisher, who are manufactuers themselves; we can extend these characteristics to publishing 16:30:58 ack Charles 16:31:16 Charles: I was thinking the opposite, that the environment controls the book 16:31:27 ...I was stuff in metric, or Imperial or another language; this is very interesting 16:31:30 Daihei: very good 16:31:36 ...Let's keep discussion going 16:31:43 ...I am going to introduce WoT IG group link 16:31:49 ...to Publishing BG participants 16:32:00 ...Let me hand this conversation over to Liisa for the next item 16:32:05 Liisa: Thank you for joining us today 16:32:13 ...we look forward to working on use cases with the WoT team 16:32:26 ...next segment is speaking with content developers 16:32:45 ...We have Zheng (Jeff) Xu and @ 16:33:00 ...Help us understand how to prioritize what is next for content to focus on? 16:33:14 Jeff: Kobo is a device manufacturer 16:33:18 ...we cover a lot of users 16:33:29 ...in terms of narrowing to a focus to reading app itself 16:33:32 ...we gather first 16:33:34 ...requirements 16:33:41 ...user feedback from many different channels 16:33:48 ...we have feedback featuring our app as well as our device 16:33:54 ...reader can send feedback directly 16:34:09 ...we also have a marketing team to connect publisher to end users to collect feedback 16:34:13 ...besides those teams 16:34:34 ...we have special team to help us work on which requirements we want to prioritize and put these features into the next roadmap 16:34:40 ...we also have product developers 16:34:44 ...everyone is a reader here 16:34:50 ...We have some requirements directly 16:34:56 ...sent from our developers 16:35:05 ...decide which feature has a lot of users 16:35:18 ...a bunch of us like the feature and want to experiment and see if it can fit into the product 16:35:25 ...and get feedback from end user 16:35:42 ...different approaches to get feedback from end user and inside the company 16:35:46 ...there are many steps 16:35:51 ...Some times we found 16:35:56 ...the thing we wanted to avoid 16:36:02 ...when we introduce new features 16:36:11 ...it is interesting, but we don't see much feedback onit 16:36:25 ...need to have some analysis on it to see if we keep this feature 16:36:51 @: We implement SDKs 16:36:54 ...have different goals 16:36:59 ...for Readium Foundation 16:37:05 ...we aimed to be a reference implementation 16:37:30 ...way we approach dev is different; today we are more pragmatic; we raise funds for development help integrators/vendors 16:37:39 ...business perspective, customers, end users drive demand 16:37:50 ...collaborative annotations, synchronized sign language 16:38:00 ...help create demand and capture market segments 16:38:04 ...purely from tech standpoint 16:38:10 ...there is a notion of chicken and egg 16:38:16 ...standards and supporting implementations 16:38:22 ..."user agents" in W3C world 16:38:27 s/@/Daniel_Weck 16:38:29 ...interop rules set by IDPF for EPUB 16:38:33 ...have been lacking clarify 16:38:44 ...thinking of performance requirements for nonlinear reading order 16:38:55 ...From user perspective 16:39:11 ...developers, either alignment with lowest common denominator to ensure broadest target 16:39:20 ...or advanced features in publishing silos 16:39:30 ...rich intereactive multimediaexperiences 16:39:41 ...as implementers, we have to fill gaps for lack of clarity 16:39:48 ...and decide what to support for legacy 16:40:02 ...practice of existing corpus and arhives to support 16:40:08 ..top of my head 16:40:19 ...we have had support for @ bindings for a number of years 16:40:28 ...digital publishing...relatively easy to update web pages 16:40:45 ...as reading system implementors, we have to look at proprietary features 16:40:54 ...for example Apple's ibooks... 16:40:59 ...@ not standardized 16:41:02 Liisa: thank you 16:41:08 ...that is a really great segway 16:41:17 ...are there use cases that we can collectively agree upon and advance? 16:41:29 ...Things like pop-ups, local storage to fill in; workbooks 16:41:39 ...so many things happening; things that have not seen light of day in digital book world 16:41:47 ...one of our authors published a great fill-in book 16:41:57 ...but we don't have support across reading systems to create an ebook of it 16:42:04 ...how do we make advancement collectively 16:42:11 ...to get support to make it worth making the books 16:42:16 Jeff: one difficulty for publisher 16:42:27 ...would be can this book be played on other devices? 16:42:32 ...this is probably one mission 16:42:37 ...that we can work on in the CG 16:42:55 ...and define a certain amount of reading application to reduce the complexity to publishers of supporting different reading apps 16:42:58 ...and collectively 16:43:05 ...example of footnotes 16:43:09 ...we really want to 16:43:11 q+ 16:43:16 ...implement something good for user 16:43:31 ...but if we receive different types of footnotes from different publishers, we cannot handle each case for the reading app 16:43:36 ...I think it would be a really good idea 16:43:40 ...even if not just in spec 16:43:43 ...make an incubation 16:43:53 ...and work with some publishers to make experiments with different reading apps 16:44:02 ...look at these features, and then maybe push to specifications 16:44:09 ...and maybe create some best practices 16:44:14 Daniel: excellent point 16:44:26 ...makes me think about how we can connect the idfferent communities 16:44:34 ...with my decade of experience 16:44:47 ...these communities operate under different perrogatives 16:44:54 ...seen this in different standardization groups 16:45:01 ...W3C rec track is time consuming 16:45:09 ...some industries need to adapt faster to changes in the market 16:45:28 ...we found it difficult to connect with diverse groups with different priorities and philosophies 16:45:37 ...someone would join a group for weeks, months, and then they vanish 16:45:45 ...so we lose track of the latest developments 16:45:54 ...W3C is a good place for this; good culture for collaboration 16:46:01 ...but pace of standardization is challenging 16:46:08 ...Readium foundation have out own publishing spec 16:46:19 ...we don't promote as a standard to distribute content 16:46:40 ...but represents the richness of ebook for visual narratives; have support for comics, audio books 16:46:51 ...shares commonalities with W3C audio books 16:47:00 ...we have to move faster than W3C; but interop is still key 16:47:07 ...meet the needs of publishers and end users