W3C


Publishing Maintenance Working Group

02 February 2024

Attendees

Present
dhall, duga, gpellegrino, Hadrien, ivan, shiestyle, tzviya, Wendy
Regrets
-
Chair
shiestyle
Scribe
gpellegrino

Meeting minutes

Webtoons' proposal (PR #2602)

<tzviya> Date: 2024-02-02

<shiestyle> w3c/epub-specs#2602

Shinya: We have a PR
… can someone explain the PR?

wendy: we both change the EPUB core and EPUB RS documents, in both documents we creating a new heading for telling that renditions flow metadata apply to both FXL and reflowable EPUB
… we also created diagrams to explain the behaviour we expect when rendition flow is applied
… we also change a MUST to a MAIN when we say about RSs that may ignore renditions flow

ivan: is it correct that this change reflexts what is happening with webtoons?
… are we documenting existing practices?

shiestyle: It depends: we're using rendition-flow = continuos, Apple is using it in their apps

gpellegrino: did we discuss it at last two TPACs? Didn't we agree to move to the CG for experimenting?

ivan: We the last WG there was not enough time, I don't remember with CG

CG*

dhall: Yes, we are using it in FXLs EPUBs

Hadrien: I think it really depends on what we agree it is a webtoon
… the division is not structurale, the vertical image is split just for distribution
… this helps also for optimization in loading
… this content is consumed in specialized platforms outside the generic EPUB ecosystem
… I think that instead of discussing about webtoons, we're misusing an existing property
… that may hurt other use cases, I think there is place for a broader discussion

duga: about optimization: you can scroll the images natively, instead of using images in HTML

shiestyle: In Japan many publishers are using EPUB as an interchange format, more then for a B2C format

ivan: I'm trying to remember how it started: Japan publishers where worried of having a new big market (webtoons) outside the EPUB ecosystem

wendy: I discussed with Hadrien offline, I think his comments are valid, at the same time I think we have to respond to this emerging market
… for the comment about the "logistic" (series, episodes, etc.) I think this is a metadata issue

<Zakim> tzviya, you wanted to add to Hadrien

tzviya: I'm feeling like I felt when FXL came out
… we had an implementer who implemented it in a way and we adapted the format in that way

dhall: content specification for a true webtoon may be more performant
… I would split this PR from "webtoons", this is about how FXLs should be displayed with rendition-flow: continuos

duga: we raised this issue two years ago and suggested to move it to the CG
… we should have done it two years ago
… I think also that webtoons is a trademark and we should not use it

Hadrien: to respond to David, no one asked for continuos scrolling outside of webtoons
… continuos scrolling is difficult to get with EPUBs, and even more with EPUB FXLs
… what I see that happen around the world is to tweak the format for doing things that are outside of the standard
… I don't think that hacking something is a good approch
… I think is better just to say "this is a webtoon"
… and manage that publication in a specific way
… instead of tweaking a metadata that was intended for other stuff

shiestyle: In Japan we what to find a simple way to make comics in EPUBs
… we want to separate this PR with minor changes to the spec

wendy: I think it is important to speak with Amazon (Kindle) on this
… to understand if this solution is good enough

ivan: Hadrien propose to add a new metadata to say that the publication is a "webtoon"

shiestyle: actually we already have special metadata for webtoons

Hadrien: in Japan there are a lot of profiles
… with XML prefixes to add information
… personally I don't think it is the way to move to metadata
… we have metadata conformsTo metadata (used for accessibility), we may use it for telling the publication conforms to webtoon
… it doesn't break anything

gpellegrino: for adding metadata to EPUB is not required to change the specs, you can use the meta tag
… other comment about process, I think is better to move trough the CG, as we're doing for accessible FXL

duga: I don't like the conformsTo approach, in any cases we need a spec to say what to do, in both cases we'll end up with RSs that will display broken webtoons

tzviya: I agree with Brady, if we have to create a new profile, we don't have the charter to do this, we can only maintain the spec that is already published
… I think we should have everything in the main spec

Hadrien: to respond to Brady, I think that implementing vertical scroll is very expensive, specialized RSs are extracting images from the HTML and display them in canvas or similar
… no matter what we do, it will be broken in most of reading systems
… or we may suggest them a simpler way to ingest the EPUB and display only images

shiestyle: I understand the performance issue, I think we should separate this discussion from the PR and wait for the Amazon comment

ivan: Hadrien, do you think the additional metadata is in addition to the PR?

Hadrien: no, it is instead of the PR

<tzviya> +1 to wendy

wendy: I understand Hadrien's point, a new metadata may lead to exotic values
… where publisher expect some type of rendition

ivan: I think for the moment we'll not merge the PR
… in the meantime I think we may work on test cases
… and implementations, to be sure that it is feasible

dhall: does the PR specify a MUST or MAY conformance?

wendy: a MAY, before that rendition-flows was not available for reflowable
… not you can use that value for fixed layout

dhall: so a RS that does not support webtoons will display the publication in separated pages

Hadrien: In Japan there are already different profiles that create stuff on top of EPUBs
… I think we should look at them
… at the same time I think webtoons are quite different from the other type of publications, and requires some extra research

<Zakim> tzviya, you wanted to remind about dictionaries

dhall: I think we are not in line with the semantic of the content... webtoons are different from web comics
… so having a demo may be useful

wendy: I'll make a video

shiestyle: I'll contact Amazon for partecipating to the next meeting

Minutes manually created (not a transcript), formatted by scribe.perl version 221 (Fri Jul 21 14:01:30 2023 UTC).