Re: 次回、第4回ミーティング

| I noticed a few new members from Amazon joined the group. People who are developing products often give us precious feedback and insights. Probably we want to setup a meeting once GA work is up to speed.

Yes we are watching the list. Unfortunately we don’t have any Japanese speakers in our group. Feel free to loop us in as needed though.

I think we have a plan to be in Japan Sept 9-13 currently (we’re attending TPAC the following week for the CSSWG).

Thanks,
Stanton

From: Yasuo Kida <kida@mac.com>
Date: Monday, June 17, 2019 at 4:41 AM
To: "public-jlreq-admin@w3.org" <public-jlreq-admin@w3.org>
Subject: 次回、第4回ミーティング
Resent-From: <public-jlreq-admin@w3.org>
Resent-Date: Monday, June 17, 2019 at 4:40 AM

JLReq TF の皆さま（English summary follows）、

次回のミーティングです。調整さんへご都合の記入をお願いします。Gap Analysis を早く軌道に乗せたいので、ちょっと早めに来週と再来週を候補にしてあります。
https://chouseisan.com/s?h=bbcf773997124fd18353821e26ee74c9



軌道に乗って状況報告が主になれば電話会議でと思っているのですが、なかなか、議論すべきことが色々出てきますね。こんな議題になろうかと思います：


  *   Gap Analysis の状況報告

     *   特にテスト開発チーム（Murakami-san, Takase-san, Tajima-san with help from Shimono-san）
     *   CSS が欠けている部分や既にテストがある部分はレポートを書き始められる？


  *   前回のミーティングで出てきた次のポイントをどうカバーするかの議論

     *   日本人には当たり前すぎて JLReq に書いていない、もしくは軽くしか触れられていないが、重要で、Gap Analysis の対象とすべき点があるのではないか
     *   基本版面など CSS の組み合わせで達成されるものに対しては CSS 単独ではなく、組み合わせでのテストが必要なのではないか
     *   全体的に、テストは CSS が期待通りに動くか「ではなく」、その CSS により JLReq に記述されているレイアウトが再現可能か、をテストすべきではないか


  *   JLReq アップデートの状況報告


  *   他にありますか？

一点質問。怠けてミーティングノートを英語だけで出していますが、ぜひ日本語で！という方おられますか？　例えばアクションアイテムだけでも日本語が欲しいですか？ 調整さんにアンケートをつけましたので、該当項目に◯をつけて or コメントに書き込んでください。

木田
–––––––––––––––––––––––––––––––––––––––––
JLReq members,

Please add your schedule to the following site. To help ramping up the Gap Analysis work, I am planning to have the next meeting next week or the week after that.

https://chouseisan.com/s?h=bbcf773997124fd18353821e26ee74c9


Proposed agenda

  *   Status updates on Gap Analysis work

     *   especially from test case development team (Murakami-san, Takase-san, Tajima-san with help from Shimono-san)
     *   Can we (shimono-san) start writing the report for the part that lacks necessary CSS or the part which already have a test?

  *   Discuss how we address these concerns:

     *   There are features that are left unsaid in JLReq because they are so basic and natural to native speakers but they are new concepts to English speakers. → We want to capture them in a section of the GA report, as well as in the future version of JLReq.
     *   There are features that are achieved by combinations of CSS, e.g. section 2 “Kihon-hanmen”. A concern is that they are not properly tested with approach of developing tests for individual CSS or for particular aspect of a feature. (This might be similar to the concept of unit tests vs integration tests)
     *   Tests should be developed in a way that they try to reproduce good results that JLReq expects, rather than to test CSS to see if they work in a way that they are designed for.

  *   Status updates on JLReq updates
  *   Any other topics?


I noticed a few new members from Amazon joined the group. People who are developing products often give us precious feedback and insights. Probably we want to setup a meeting once GA work is up to speed.

- kida