15:49:46 RRSAgent has joined #pbg 15:49:46 logging to https://www.w3.org/2019/07/02-pbg-irc 15:49:47 rrsagent, set log public 15:49:47 Meeting: Publishing Business Group Telco 15:49:47 Chair: luc 15:49:47 Date: 2019-07-02 15:49:47 Agenda: https://lists.w3.org/Archives/Public/public-publishingbg/2019Jul/0000.html 15:49:47 ivan has changed the topic to: Meeting Agenda 2019-07-02: https://lists.w3.org/Archives/Public/public-publishingbg/2019Jul/0000.html 15:49:48 Regrets+ dauwhe 15:51:11 wolfgang has joined #pbg 15:57:37 laudrain has joined #PBG 15:57:48 present+ 15:57:56 rkwright has joined #pbg 15:59:09 Jonathan_Greenberg has joined #pbg 15:59:50 Avneesh has joined #pbg 16:00:03 Daihei has joined #pbg 16:00:03 George has joined #pbg 16:00:47 present+ Karen 16:01:02 liisamk has joined #pbg 16:01:16 present+ 16:01:27 present+ 16:01:30 present+ wolfgang 16:01:46 Bill_Kasdorf has joined #pbg 16:01:50 present+ 16:01:51 present+ 16:01:53 present+ 16:01:54 present+ 16:02:12 present+ 16:02:19 jeff has joined #pbg 16:02:25 present+ 16:03:22 Very noisy here but I'll volunteer next time. 16:03:28 scribenick: George 16:03:28 scribe+ George 16:03:34 scribe: George 16:03:57 chair: liisamk 16:04:45 Liisa chairing 16:04:46 Report for PBG inJapan 16:04:47 present+ Daihei 16:04:57 present+ 16:05:28 Why not have the Japanese publishers present at the meeting. 16:05:28 s/PBG/PBG F2F/ 16:05:32 garth has joined #pbg 16:05:38 present+ Garth 16:05:54 looking at 5 to 6 items for the agenda. We will get these out and ask to polish. 16:06:04 s /inJapan/in Japan/ 16:06:25 We plan to have both English to Japanese and Japanese to English. 16:06:36 We are also working on the AV requirements. 16:07:08 The next thing is who will participate in the discussion between W3C members and the publishing community. 16:07:27 We can share the interest in publishing at the W3C with others. 16:07:41 Invited guests will be present. 16:08:00 Next week we will have more details that I will be able to share. 16:08:31 We have a question about people who are not W3C members. 16:08:42 Who would we like to have a s guests? 16:08:58 Do we have some Japanese publishers as guests. 16:09:01 s/a s guests/as guests/ 16:09:23 Rachel has joined #pbg 16:09:35 present+ 16:09:46 Next topic from PWG on the future discussions. 16:10:20 https://www.w3.org/publishing/groups/publ-wg/Meetings/Minutes/2019/2019-07-01-pwg.html 16:10:21 Tzviya: Over the last weeks chairs have raised concerns with Jeff, Ralph, and Dave. 16:11:10 , but there was lack luster participation.Our biggest concern is that we agreed to move forward with PWG 16:12:09 julieblair has joined #pbg 16:12:13 We submitted a proposal to suspend work right now and publish it as a "noThis would leave the door open for future profiles such as manga, etc. 16:12:42 We just published 3.2 in the CG and we need to figure out what happens next. 16:12:58 We decided to move forward with the audio book specification. 16:13:05 s/"noThis/WG Note - "This/ 16:13:37 There is a lot of discussion that needs to take place to make decisions on what to do. 16:13:39 Other comments? 16:13:39 q+ 16:13:42 q+ 16:14:01 q+ 16:14:02 ack laudrain 16:14:06 q+ 16:14:08 Luc: I understand that in the proposal that web publications would be a note. 16:14:24 The audio book specification would be a rec in itself. 16:14:30 laurent_ has joined #pbg 16:14:47 q+ 16:14:57 present+ laurent 16:15:00 The other profiles for manga, comics, text. 16:15:24 We originally thought that EPUB 4 would be a packaged version of a web publication. 16:15:56 George: I think multiple lines for each speaker are supposed to be preceded by an ellipsis ... 16:16:04 .What is the plan for packaging in the future 16:16:34 Ivan spocke about timing being a problem. 16:16:48 s/spocke/spoke/ 16:16:55 Is it possible to have several specifications starting with the audio book spec. 16:16:56 Cristina has joined #pbg 16:17:04 q+ 16:17:26 We see the proposal to suspend the work, but there is other approaches. 16:17:29 ack garth 16:17:51 Garth: We will publish it as a not and this allows us to return to it later. 16:18:05 s/not/note/ 16:18:51 We will take the portions of the specification and apply this toaudio book specification. We take the core of web publications and combining it with what we need for audio books. 16:19:09 This approach addresses current business needs. 16:19:11 s/toaudio/to audio/ 16:19:50 q+ to ask about the consistency of "taking the core of web publications" with not taking the part relative to "living natively on the web" 16:20:24 ack Bill_Kasdorf 16:20:25 We can take this approach and appy it to other types of content. 16:20:31 q+ 16:20:40 s/appy/apply/ 16:21:16 Bill: the Melan foundation has funded several projects that in effect are working on publications that includes web technologies. 16:21:26 q? 16:21:27 q+ 16:21:33 s/Mellon/Melan 16:21:38 s/Melan/Mellon 16:21:38 ack Rachel 16:21:47 It is important that we do not communicate that we are giving up on web publications. 16:22:13 Rachel: Ivan clarify the difference between a recommendation and a note. 16:22:18 ack ivan 16:22:21 q+ to ask bill how we can continue the work on WP in a way that will help all those orgs? 16:22:46 Ivan: The note does not represent concensis and it has not gone through the rigrious testing and implementation. 16:22:58 s/web technologies./web technologies and in effect are creating complex publications on the web./ 16:23:02 s/consensis/consensus/ 16:23:14 q- 16:23:34 At a later date time, a note can be taken up and moved forward. 16:24:12 For the record those projects include ones at Stanford, Univ. of California, Minnesota, Michigan, NYU and others. 16:24:26 Ivan: Looking at what Garth said, we have to understand in tech terms what we propose and what we do not propose. 16:24:44 Audio books are not intended to be delivered on the web. 16:24:58 Audio books are intended to be packaged and delivered. 16:25:00 s/delivered/created 16:25:51 Web publications on the web on the other hand have many requirements, including security, and index file, and eventually a web browser should understand. 16:26:39 There is a large part of the document (note) that has terms, rules, and is a separate part of the document. 16:27:09 Another portion of the document deals with security, the origin and a special implementation on the web. 16:28:04 The manifest and the processing on the web. The web part is the one we do not have concensis on. The manifest part is the part we can reuse.on and 16:28:25 s/consensis/consensus/ 16:28:28 The manifest part and the audio book specific items is what we can promote. 16:28:46 We may be able to use the manifest with other content. 16:28:49 s/reuse.on/reuse/ 16:29:11 q+ 16:29:19 Are thought is at the moment, this is all that the community wants. 16:29:34 s/Are/Our/ 16:29:43 The manifest part is good and can be used. 16:30:08 The core web part is what we will postphone until there is a time when there is more interest. 16:30:50 s/postphone/postpone 16:30:52 The WG must discuss if the manifest can be reused and not integrated in to the audio books spec. 16:30:56 Jeff: 16:30:58 ack jeff 16:30:58 jeff, you wanted to ask about the consistency of "taking the core of web publications" with not taking the part relative to "living natively on the web" 16:31:27 Rachel asked about the difference, but the W3C recommendation is a "Standard" and a note is not. 16:32:07 q? 16:32:43 q+ 16:32:47 Secondly, I am not sure that we should look at a spec made to work on the web and repurpose it for off line use. 16:34:05 delivering an audio book speciation.Third, I see little support for the chartered activity 16:34:48 Avneesh: We must be careful that we do not mismatch what we have in the charter with what we are delivering in audio books. 16:35:25 We must manage communication about the work we are doing. We need to carefully manage external communication. 16:35:41 Why not extend the charter and do more things. 16:36:13 +1 16:36:21 q? 16:36:22 +1 16:36:31 Whatever we do in the working group, which is for members, must deliver the business needs. The spec we write must be useful to their business needs. 16:36:32 ack Avneesh 16:36:32 ack Avneesh 16:36:36 ack laurent_ 16:36:47 ack laurent_ 16:37:12 q+ 16:37:47 we Laurent: I think we need to know about processing requirements for the web. 16:38:35 scribe: wolfgang 16:38:52 ack tzviya 16:38:52 tzviya, you wanted to ask bill how we can continue the work on WP in a way that will help all those orgs? 16:39:08 tzviya: a lot of people talking about potential uses of WPs 16:39:11 - We are missing a clear list of what is missing in the "core" WP work, that is not required for the audiobooks reco based on WP, either packaged or exposed on the Web. The WG should detail this before we move on. 16:39:11 - As Ivan said, most issues are linked to the native generation of a publication in a distributed Web environment, vs the exposure on the Web of a publication born on a desktop. 16:39:11 - The audiobook spec should be modular, with one module being the Manifest spec + processing on the Web. 16:39:11 - Also ebooks (text oriented ebooks, EPUB-like, with proper metadata) did not gather sufficient attention; even if we have business clues that samples are needed on the Web. I still think that a mapping from EPUB to an ebook WP profile is useful 16:39:29 ... a publication that opens on the web 16:39:38 q? 16:40:20 ... I agree that we need to make it clear that we are not ending our efforts - WP is not suitable for scholarly publications 16:41:22 ... use cases mentioned are wonderful, but we need a spec that is more robust - we need better communication what we intend to do - I'm afraid this is not viable now 16:41:39 ack wendyreid 16:42:51 wendyreid: I speak for myself - everything I heard yesterday and today is very frustrating - Audiobook gets more positive feedback, we should follow on 16:43:41 q? 16:44:19 ... we believe in WP, but some people are now telling that want WP - we need book previews on the web - but people are not here, that tell us about their need for WP - trade publishing industry not ready for WP 16:44:26 q- 16:44:38 let's focus on EPUB, but WP is not yet ready! 16:44:42 ack garth 16:44:55 q+ 16:45:51 garth: Audiobooks will be natively on the Web - I hesitate to support any sugar-coding - no browser interest in WP - we suspend work on WP and publish it on a note 16:46:49 ... manifest in JSON, etc. may be used in Audiobooks - may apply knowledge gained to other profiles in the future 16:46:55 q? 16:47:07 ack laudrain 16:47:13 ... I'm not sure there's an industry need for WP instead of EPUB 16:48:51 Laudrain: I want to acknowledge the work in the WG for WP - we do hope that Audiobook spec will be adopted - will bring confidence for W3C avtivity - should communicate carefully to enhance the work on WP that has been done 16:49:06 +1 to Luc 16:49:25 ... future of EPUB is an ebook profile based on WP for publishing on the Web 16:49:33 q+ to respond to luc 16:49:35 q? 16:49:47 ... EPUB is working well for the publsihing industry today 16:49:49 ack tzviya 16:49:49 tzviya, you wanted to respond to luc 16:49:51 ack tzviya 16:49:53 q+ 16:50:38 +1 to Tzviya 16:50:50 tzviya: EPUB was wonderful for part of the publishing industry, not for the whole - scholarly needs sth completely different - maybe we should try to fill such gaps 16:51:03 ack laudrain 16:51:38 q+ 16:52:16 q+ 16:52:36 laudrain: I completely agree with you, tzviya. Why not having a WP profile for scholarly - future of EPUB is WP as WP for text - today we are having a rec for packaging 16:52:38 ack garth 16:52:40 +1 to Luc 16:53:27 q+ 16:53:28 q+ 16:53:47 garth: respectfully disagree - the future of EPUB is WP is for me a very far future - don't see a business case for that in the short term, only in the long-term perspective 16:53:53 ack ivan 16:54:35 q+ if there is time 16:54:50 q+, if there is time 16:55:01 q? 16:55:09 ivan: we don't have the same idea what a WP is - the packaging concept is not a packaging on the Web - we are talking about a packaged publication which relies on Web technologies much like EPUB 16:55:17 q+ avneesh 16:56:26 ... not part of the Web for a browser like an HTML page - Audiobook or WP is not the same as a publication on the Web - browser vendors are not interested 16:57:13 ... the package containing web technology is web manifest plus content but not a web publication 16:57:24 q+ 16:57:26 ack Bill_Kasdorf 16:57:55 BillK: we biggest impediment to a web-native EPUB is that there are millions of EPUBs already extant 16:58:29 ack jeff 16:58:34 not so fundamental desgreement with Garth 16:58:39 jeff: we need a common view - Luke and Garth have different conceptions 16:58:45 ack avnessh 16:58:48 So do it for you, Garth 16:58:53 ack avneesh 16:58:54 ack Avneesh 16:59:43 avneesh: marketing perspective - market research needed before the development of a new product - we should ask publishers in EPUB CG and ask whether we need 2 different versions 16:59:45 ack Daihei 17:00:58 q+ 17:01:03 Daihei: EPUB is good enough for existing publishing - should be maintained - future uses may be different contexts than publishing 17:01:54 s/web-native EPUB/web-native EPUB for trade books/ 17:01:54 rrsagent, draft minutes 17:01:54 I have made the request to generate https://www.w3.org/2019/07/02-pbg-minutes.html ivan