- From: Avneesh Singh <avneesh.sg@gmail.com>
- Date: Sun, 29 Nov 2020 20:11:22 +0530
- To: "Koji Ishii" <kojiishi@gmail.com>, "MURATA" <eb2mmrt@gmail.com>
- Cc: "Ivan Herman" <ivan@w3.org>, "W3C EPUB3 Community Group" <public-epub3@w3.org>, "W3C Publishing Community Group" <public-publishingcg@w3.org>, "Richard Ishida" <ishida@w3.org>, "Florian Rivoal" <florian@rivoal.net>
- Message-ID: <A8C6D336426442D9BEB119A05E08CF8C@DESKTOPG923ARA>
The proposal is for metadata, so I believe we should look at it independent of the technology used. It may use CSS media query in future or may be on very different technology like PDF. Our main focus should be if this is appropriate use case to consider for accessibility metadata. With regards Avneesh From: Koji Ishii Sent: Sunday, November 29, 2020 19:35 To: MURATA Cc: Ivan Herman ; W3C EPUB3 Community Group ; W3C Publishing Community Group ; Richard Ishida ; Florian Rivoal Subject: Re: EPUB Accessibility: Discovery of the Writing Direction (DRAFT 1.0) This proposal is only about discovering the primary writing-mode, correct? Assuming my understanding is correct, the 3 proposals (this proposal, alternate style tags, and MQ) are for different use cases. The alternate style tags spec was for single content to support both writing-modes. We added it because we saw some early digital book readers implemented the feature, but most major epub readers did not implement the feature. MQ was once discussed for the same use case, but it was not pursued much because 1) the use case itself was in question, 2) MQ should not use style as input (creates a loop), and 3) it does not provide a mechanism to switch writing-mode. Neither the alternate style tags nor MQ can discover the primary writing-mode of a content. I think the question is more about whether this is necessary to standardize or not. Are there more than one reader vendors and more than one content vendors willing to support? 2020年11月29日(日) 22:12 MURATA <eb2mmrt@gmail.com>: Ivan, Fantasai suggested that option but she was not sure if browser vendors like it. We might want to try it after we can demonstrate that a lot of users really care. Regards, Makoto 2020年11月29日(日) 21:25 Ivan Herman <ivan@w3.org>: > > (cc Koji Ishii, Richard Ishida, and Florian Rivoal, they know way more than I do about this.) > > Thanks Makoto, > > just thinking out loud for the future… wouldn't it be a better approach to have a media query dimension in CSS media queries on the writing direction? CSS has this notion of (Block flow direction) in[1] but I am not sure it can bound to media queries[2,3]. This would make the IDPF specific classes obsolete... > > I realize that is a longer term solution that should be raised by the CSS WG. Just asking at this point... > > Cheers > > Ivan > > > [1] https://www.w3.org/TR/css-writing-modes-4/#block-flow > [2] https://drafts.csswg.org/mediaqueries-4/ > [3] https://drafts.csswg.org/mediaqueries-5 > > > > > On 29 Nov 2020, at 07:10, MURATA <eb2mmrt@gmail.com> wrote: > > Dear colleagues, > > Here is another document from the Japanese > DAISY consortium. > > https://1drv.ms/w/s!An5Z79wj5AZBgtUx_1os2PNRrYkDjA?e=v9qSpH > > It summarizes discovery requirements for > accessible EPUB publications according > to user preferences on the writing direction > (horizontal or vertical). > > I hope to register Schema.org metadata > and ONIX metadata based on this > document. (BTW, Keio University is > already a member of EDItEUR for this > registration.) > > Regards, > MURATA Makoto, Keio University > > > > ---- > Ivan Herman, W3C > Home: http://www.w3.org/People/Ivan/ > mobile: +33 6 52 46 00 43 > ORCID ID: https://orcid.org/0000-0003-0782-2704 > -- -- 内閣官房IT総合推進室政府CIO補佐官 慶應義塾大学政策・メディア研究科特任教授 日本デイジーコンソーシアム技術委員会委員長 村田 真
Received on Sunday, 29 November 2020 14:41:43 UTC