W3C home > Mailing lists > Public > public-publ-wg@w3.org > May 2018

Regrets: [PWG] 20180521 Agenda

From: <laurent.lemeur@edrlab.org>
Date: Fri, 18 May 2018 10:58:16 +0200
To: W3C Publishing Working Group <public-publ-wg@w3.org>
Message-Id: <45033172-FB17-47C5-9309-A9FED7416FE9@edrlab.org>
Regrets, I’ll be on vacation. 

Please note that I’m totally ok with the 3  resolutions proposed by the chairs, and hope that this will help the group going out of an infernal circle and tackling asap interesting work on:

- Finalizing a consensus on the metadata we must standardize and the extension points we must provide.
- Deciding how to author relative URLS for intra-publiation links (set *before the content is exposed as a WP*).
- ... Which means creating pointers to  precise fragments of content that can replace EPUB CFIs AND be accepted by Web developers.
- Working on a standardization of an audiobook format in the context of WP and EPUB 4.
- Working on EPUB 4 (i.e. the packaging aspect).
- Getting CSS pagination right with the CSS WG.
- Working with experts to see if CSS grids can be the proper evolution of fixed layout. 
- Discussing a basic profile of EPUB that could be processed in an interoperable way by any device which has a custom (basic, in-house) rendering engine. This would seriously help making EPUB 2 obsolete for real.  

Best regards
Laurent Le Meur

Le 18 mai
> Resolve "What is the Browsing Context of a Web Publication?" [5]
> Proposed resolution: A WP definition does not specify whether the content is rendered in a Progressive Web App, in the browser directly or via an extension, or in a separate app (or whatever else).  Therefore we propose to  ...”.  Further propose to alter the current draft to remove the reference to "Publication Context."
> Resolve "Is it acceptable to use HTML for the serialization of some infoset items, or should it all be in separate (JSON) file?" [9.2] 
> Proposed resolution: The infoset mostly resides within a JSON manifest (WP manifest). That JSON may optionally be ... duplication issues can be sufficiently avoided.
> Resolve "To WAM or not to WAM?" direction
> Proposed resolution: Publications, as specified here, are not necessarily Progressive Web Applications. On the other hand, WAM is tightly coupled to a Progressive Web Applications, thus,, we will not require the usage of the WAM and our specification should not be dependent on it. The WP Manifest should be specified independently of the WAM. Of course, a particular WP may be rendered via a PWA, and therefore use a WAM, but that is orthogonal to this specification.
> Offline discussion continued, time permitting
> A WP MUST or MAY be "offline-able" or "package-able"?
> Gaps from "classic" EPUB (continued) [6]
> Hadrien's list; create issues 
> Should go where? WP, PWP/EPUB4
> In what section?  Infoset, lifecycle, navigation, et al
> Other business (or frivolity)
> [0] https://www.timeanddate.com/worldclock/fixedtime.html?msg=PWG&iso=20180521T12&p1=43 <https://www.timeanddate.com/worldclock/fixedtime.html?msg=PWG&iso=20180521T12&p1=43>
> [1] https://www.w3.org/publishing/groups/publ-wg/Meetings/gotomeetings <https://www.w3.org/publishing/groups/publ-wg/Meetings/gotomeetings>
> [2] https://www.w3.org/publishing/groups/publ-wg/WorkMode/newbie <https://www.w3.org/publishing/groups/publ-wg/WorkMode/newbie>
> [3] https://www.w3.org/publishing/groups/publ-wg/ <https://www.w3.org/publishing/groups/publ-wg/>
> [4] https://www.w3.org/publishing/groups/publ-wg/Meetings/Minutes/2018/2018-05-07-pwg.html <https://www.w3.org/publishing/groups/publ-wg/Meetings/Minutes/2018/2018-05-07-pwg.html>
> [5] https://github.com/w3c/wpub/issues/104 <https://github.com/w3c/wpub/issues/104>
> [6] https://github.com/w3c/wpub/issues/176#issuecomment-382634697 <https://github.com/w3c/wpub/issues/176#issuecomment-382634697>
> [7] https://docs.google.com/document/d/1Qe8Q8wMC1LKy_-JO-UCy8bFw4D4VN0si1Q5EPW9c-rY/edit?usp=sharing <https://docs.google.com/document/d/1Qe8Q8wMC1LKy_-JO-UCy8bFw4D4VN0si1Q5EPW9c-rY/edit?usp=sharing>
> [8] https://goo.gl/forms/UZ0yv8EBXBujTePw1 <https://goo.gl/forms/UZ0yv8EBXBujTePw1> - please respond only if you are attending F2F in person
> [9] http://hotelocho.com/food.html <http://hotelocho.com/food.html>
> [9.1] https://docs.google.com/document/d/1Qe8Q8wMC1LKy_-JO-UCy8bFw4D4VN0si1Q5EPW9c-rY/edit#heading=h.wxsg3gz7h6ps <https://docs.google.com/document/d/1Qe8Q8wMC1LKy_-JO-UCy8bFw4D4VN0si1Q5EPW9c-rY/edit#heading=h.wxsg3gz7h6ps>
> [9.2] https://github.com/w3c/wpub/issues/193 <https://github.com/w3c/wpub/issues/193>
> -------------------------------------------------
> To join this teleconference, use the following logistics:
> GoToMeeting [10].  To mute/unmute your line press "*6".
> Join chat and minutes on IRC/Zakim (see below)
> We will also use an IRC channel to minute the discussions:
> Address:  irc.w3.org <http://irc.w3.org/>  (channel #pwg)
> Available ports (choose one): 6667, 6665, 21 IRC channel: #pwg See how to connect [11] using an IRC client [12] or our web interface [13] User Instructions for Zakim [14]. 
>  To place yourself on the speaker queue ('q+' in irc) press 41# (Handup).
>  Unqueue ('q-' in irc) is 40#.
> -------------------------------------------------
> [10] https://www.w3.org/publishing/groups/publ-wg/Meetings/gotomeetings <https://www.w3.org/publishing/groups/publ-wg/Meetings/gotomeetings>
> [11] http://www.w3.org/Project/IRC/ <http://www.w3.org/Project/IRC/>
> [13] http://www.w3.org/Project/IRC/#Client <http://www.w3.org/Project/IRC/#Client>
> [13] http://irc.w3.org/ <http://irc.w3.org/>
> [14] http://www.w3.org/2002/01/UsingZakim <http://www.w3.org/2002/01/UsingZakim>

Received on Friday, 18 May 2018 08:58:55 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:52:25 UTC