- From: Yasuo Kida <kida@mac.com>
- Date: Mon, 20 May 2019 21:15:19 +0900
- To: r12a <ishida@w3.org>
- Cc: public-jlreq-admin@w3.org
Hi Richard, Thank you very much for providing us the background, and the guideline. However I am feeling most if not all requirements can be categorised under the current top level structure, if there are areas we are not sure we will certainly consult with you. Just to be sure, by the top-level structure do you mean up to the first decimal of the Japanese Gap Analysis document? For example 3.10 "Inline notes & annotations” is a part of the top level structure but headings with the second level decimal, e.g. 3.10.1 “Tabular markup not supported”, is not. In fact my understanding is that adding these subsections describing identified gaps is what we are expected to do (as you explained in the guideline item a.) I ask because I feel many of concerns about the missing coverage is coming from the confusion of the structure of the headings. > The top-level structure of the gap-analysis doc, the typography index, and the language matrix need to be the same, so that these items can work together. I see it between the gap analysis document and the language matrix. For example 3.10 "Inline notes & annotations” corresponds to “Inline annotations” in the Language matrix, which is clear by the link. It looks however the typography index has a different structure. There is no top level item that corresponds to "Inline notes & annotations” and “ruby” which would be a subsection of 3.10 appears as one of the top level item. Probably I am missing something here. Best regards, - kida > 2019/05/20 18:29、r12a <ishida@w3.org>のメール: > > Perhaps it will be useful for me to mention a couple of things here that may be relevant to the discussion: > > The top-level structure of the gap-analysis doc, the typography index, and the language matrix need to be the same, so that these items can work together. > > On the other hand,for the jlreq doc (and lreq docs in general) although the top-level structure mentioned above may provide a useful starting point, there is no need to follow that structure if a better one is possible. > > > GAP ANALYSIS DOC STRUCTURE > > Within each set, top-level section in the gap-analysis doc, the actual content can be organised however you like in order to provide maximum clarity and coverage. The current subsections (for example under vertical text) are simply what occurred to me off the top of my head when i quickly pulled together an example document for people to refer to. > > However, i would recommend that content of each subsection in the gap analysis doc should aim to do the following things: > > a. use subsection headings to describe one specific issue at a time, by explaining what is expected to happen (or point to jlreq or specs for requirements), and what actually happens. (The gap-analysis doc should not duplicate the lreq text, but it may be useful to summarise the key points.) > > b. demonstrate current support by browsers by pointing to tests or other evidence wherever possible, and being specific as possible about which browsers lack support. (There is a styling convention in the examples that highlights browsers with colours related to support level, which may help readers.) > > c. describe the impact of the lack of support, and how that translates to the coloured priority levels in the gap-analysis doc and the matrix. > > > hope that helps, > ri > > > On 20/05/2019 00:54, Yasuo Kida wrote: >> # 元資料のURL: >> * Japanese Gap Analysis: https://w3c.github.io/jlreq/gap-analysis/ >> * JLREQ: https://w3c.github.io/jlreq/ >> * Analysis of requirements in JLREQ: >> https://www.w3.org/Submission/2017/SUBM-CSJTUWT-20170102/jlreq-analysis.html >> * 電書協EPUB3要望表(EPUB3 Petition): http://ebpaj.jp/counsel/youbou >> * Analysis of requirements in EPUB3 Petition of Japanese Typesetting: >> https://www.w3.org/Submission/2017/SUBM-CSJTUWT-20170102/epub-req-analysis.html >> * JAGAT各社EPUBビューア日本語組版表示チェック（JAGAT XMLパブリッシング >> 準研究会）: >> https://docs.google.com/spreadsheets/d/e/2PACX-1vR_p0FU0Y3Gdo3kr0nRf1J-aAu3XKkKZ1h8fNohtcFaYZYJlum7lI_rK9ebLuJu0utuZsjeJ9ootH_e/pubhtml >> * International text layout and typography index: >> https://w3c.github.io/typography/ >> * Language matrix: >> https://w3c.github.io/typography/gap-analysis/language-matrix.html >
Received on Monday, 20 May 2019 12:15:49 UTC