第3回 F2F meeting は来週水曜日 6/12 10 am JST (6/11 6 pm PDT)

JLReq Task Force contributors,（English follows）

次のミーティングは来週の6月12日水曜日10時からです。現在参加予定は7名。調整さんに書き込まれた方以外で参加が可能な方は教えてください。会議室が使えるのが12:30までなので、チャカチャカ進めてその時間までにきっちり終わらせましょう。

日時と場所
6/12 Wed 10 am JST @ 前回と同じ MediaDo 会議室
Nat joins from Seattle (6/11 6 pm PDT)

議題案
JLReq updates: 状況のシェア（下農さん）
Thank you Richard, 下農さん and 敏先生。
公開に向けて残っている仕事はあるか？
Gap Analysis：タスクの全体像のレポート（村上さん）
村上さんが作ってくださった比較表が Gap Analysis の仕事の全容を把握するためにも大変有用だということで前回何点かの変更をお願いしました。JLReq をもとにして Gap Analysis を行うにあたって、どの機能にどのような作業が必要なのか、下のような感じにまとめて説明していただけるとありがたい。
CSS が存在しない項目の数
CSS が存在する項目の数
テストが存在するもの (International, WPT)
テストが存在しないもの
CSS の問題ではないもの
Gap Analysis：JAGAT の成果などをどのように Gap Analysis に活用できるか（田嶋さん）
open question です。今回結論を出す必要はないので10分くらい軽く意見交換する感じで
Gap Analysis：この先の作業、手順、割り振りなどを決める（木田）
（時間があれば）ユーザーフィードバックで注目すべきものはあるか（田嶋さん）
 他に追加はありますか？

参考のために下に前回の meetings notes を添付してあります。
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
Time and Place
F2F meeting on 6/12 Wed 10 am JST @ MediaDo meeting room
Nat joins on screen from Seattle (6/11 6 pm PDT)

New members: If you would like to join the meeting online please let me know. Please note that the meeting is done in Japanese. The meeting notes in English will be sent to the group.

Proposed Agenda
JLReq updates: status updates (Shimono-san)
Thank you Richard, Shimono-san & Bin-sensei.
Are there remaining tasks before pushing it to live?
Gap Analysis: Summary of overall tasks (Murakami-san)
Murakami-sans chart is useful to grasp the overall tasks required for Gap Analysis. Based on his chart Murakami-san reports the overview such as:
Number of features that lacks necessary CSS
Number of features that have corresponding CSS
how many of them already have tests (International, WPT)?
how many of them lacks tests?
Number of features that is relevant but not CSS issues
Gap Analysis: How we can take advantage of analysis by JAGAT, EBPAJ or Vivliostyle? (Tajima-san)
Gap Analysis: Next steps (kida)
(if we have time) are there useful user feedback?
Please let me know if you have a topic that we should discuss at the meeting.
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
JLReq TF 2nd F2F meeting notes (sent to the group on 5/24)
2019 May 21st @ MediaDo Holdings from 10 am to 2 pm JST (4 hours!)

Attendee
Kobayashi, Tatsuo
Kobayashi, Toshi (Bin-sensei)
McCully, Nat (online)
Murakami, Shinyu
Murata, Makoto
Shimono, Atsushi
Tajima, Jun
Takase, Hiroshi
Kida, Yasuo
Meeting notes
Welcomed Tajima-san
of course everybody knew him already

Updates on JLReq update (Shimono-san)
Consensus
This update is not a new revision, meaning for stability sake we should limit changes to fixing errors and maintenance work. Improvements will be made in the 3rd revision in the future.
The page will open in English by default, and allow easy switching to Japanese, and "all" for people who want to check translation.
Discussions based on a summary Shimono-san sent on 5/30 "current status on JLReq document errata”.
Let’s integrate items in section 1 and 2. (Shimono-san)
Section 3 need a translation check. There is another in section 4. (Nat)
Discussions on some items in section 4 and 5 as regard to fixing errors vs improvements. A consensus was made that what we should focus on fixing errors for this update.
Other
Bin-sensei handed source of all images used in JLReq to Shimono-san.
Action items
Shimono-san will integrate fixes.
Nat will check translations.

Making progress on ruby (Murata-san)
Murata-san summarised the situation around ruby. The situation on the ruby support has not changed for 20 years. There are confusions due to two separate standards. The support from browsers fall short of requirements from publishers. Despite the situation however publishers are unwilling to support the efforts and cost of pushing it through (probably because ebooks are not yet their main business).
Discussed possible approaches but no specific conclusions here.
Features mentioned include (just examples): add support for rb tag in WHATWG spec, simplification of W3C specification and unification with the WHATWG spec, support for centred position, controlling space between the base characters.
Ruby is also important for universal access (what’s missing for this purpose?)
Some of the issues could be relieved by developing a guideline?
Ruby on both sides - the market too niche and small. Is it necessary for the future of e-publishing?
APL is working on a proposal for simplified ruby spec, which is a possible contents of JLReq 3rd revision.

Gap Analysis: Comparison of the gap analysis with other requirement lists (Murakami-san)
Murakami-san developed the comparison chart and sent to the list on 5/16 “各Gap Analysis調査項目の比較表”.
The coverage concerns cleared by the comments from Richard (in a mail on 5/20 in reply to the meeting agenda). He clarified the intention of the use of the second and third digits of the Gap Analysis section numbers. In short the top level structure uses up to the second level digits (e.g. 3.10), and ones with third level digits are subsections that describes specific issues, and thus they are not comprehensive.
As mentioned below the chart Murakami-san developed serves as a good start of our task analysis.

Reviewing a proposal from Nat (Nat)
Nat prepared a short but an excellent presentation describing how JLReq could be improved.
It puts developers as centre of the readers. Most of them are familiar with Western line layout and the line layout engines on the platform and the web, but not with Japanese line layout. The Japanese line layout contains some unique concepts that are subtle but critical. The current document however takes them as granted and does not explain them in details and how they are important. He proposed a document that would fill the gap.
Agreement is that his proposal will be one of the framework of the next revision of the JLReq.
Action items
Kobayashi-san will talk to Richard. (done)

Gap Analysis: next steps - task analysis
Gaps can be categorised as below in terms of the nature of the required work. As the first step we want to analyse requirements in JLReq and categorise them.
The corresponding CSS specification does not exist, or still under development.
The CSS exists, and the test cases exists. We can identify issues by running the test.
The CSS exists, and there is no test cases yet. The test case needs to be developed.
As Murakami-san's chart already link requirements and related CSS, it is an excellent start for this task analysis.
Action items
Murakami-san will update the chart based on the JLReq requirements chart and using the Gap Analysis’s top level structure.
Shimono-san will check which css already has test cases.

Items we could not cover at this meeting
We will discuss them at the next f2f meeting.
How we can gather feedback from wider audience
Tajima-san reported that he started gathering feedback using his twitter.
JAGAT XML publishing subgroup is working on compatibility check between EPUB readers. How we can take advantage of this work?

Next meeting
Will be f2f again. Kida to setup a date.
––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––


> R1/06/06 9:24、Yasuo Kida <kida@mac.com>のメール:
> 
> みなさま、
> 
> 記入ありがとうございます。6月12日にしましょう。ただ、会議室が12:30までしか使えないので10時開始にしたいと思います。
> 
> 10時開始でご都合の悪い方おられますか？
> 
> 木田
> 
>> R1/06/03 7:07、Yasuo Kida <kida@mac.com <mailto:kida@mac.com>>のメール:
>> 
>> 遅くなりました。次回のミーティングの日時を設定したいと思います。
>> 
>> ご予定を調整さんに記入してください。
>> https://chouseisan.com/s?h=74c524cd7c94487c9404161010f3f169 <https://chouseisan.com/s?h=74c524cd7c94487c9404161010f3f169>
>> 
>> 前回4時間もかかってしまったのを反省して、次回はきっちり2時間で終わらせたいと思います。その決意のもと開始を1時間遅らせました。が、10時からに戻して、などの要望があれば調整さんのコメントで教えてください。
>> 
>> 正式なアジェンダは日時とともに出しますが、次のような内容になろうかと思います。追加の議題があったら教えてください。
>> 
>> ・村上さんのチャートをもとに、Gap Analysis の仕事の全体像を共有 + 割り振りを決める
>> ・JLReq アップデートの報告。公開に向けて議論の残っている項目があるか？
>> ・田嶋さんがまとめてくださった JAGAT の成果などをどのように Gap Analysis に活用できるか
>> ・ユーザーフィードバックで注目すべきものはあるか
>> 
>> 木田
>> 
>