Simple Ruby meeting notes 2020/4/7

Simple Ruby (zoom) meeting notes 2020/4/7


Attendee
Kobayashi, Tatsuo
Kobayashi, Toshi (Bin-sensei)
Murata, Makoto
Rivoal, Florian
Shimono, Atsushi
Tajima, Jun
Takase, Hiroshi
Kida, Yasuo

Please reply to this email for any feedback to this note.


Summary

The team agreed that the document as it stands is useful enough, and the agreed to publish the document with some minor changes:
Bin-sensei will clarify his intention of the document in the introduction.
Some minor tweaks which are and will be discussed on github.


Notes

The status of the ruby specification and implementation were explained (mostly Florian)
Need to align the specification between W3C and WHATWG.
Firefox has most advanced implementation. Google is currently working on updating its engine. The ruby part of the work might start by the end of the year. Apple ? (not discussed)

Most time was spent discussing the nature of complexity, and how the Simple Ruby document can be of help
JLReq ruby explains multiple possible ways of doing things. Simple Ruby simplifies them by explaining only one way. (Bin-sensei)
CSS Ruby (level 1) leaves where JLReq offers multiple choices as implementation dependent. Simple Ruby document can help implementers to decide on the implementation. (F)
Ability to control choices among multiple possible ways is left for the level 2 specification. (F)
CSS Ruby level 1 is not meant for subsetting, i.e. prioritisation among different features. (F)
The Simple Ruby document also helps improving the specification itself. (F)
The Simple Ruby can be thought as a baseline (B)
In sum, it was general agreement that the Simple Ruby document as it stands today is useful enough to publish (kida)

Murata-san explained the two level model used, but not explained, in the Simple Ruby document
An important feature of Simple Ruby is that software can determine the size of boxes, the base text and ruby, independently from surrounding characters. The software can then just place the box in the line. This feature would help implementation (M)
He wants the Simple Ruby document to explain the model as a background information.(M)
Agreed to separate it from the initial Simple Ruby document. It might fit in an appendix, a FAQ section or worth creating a separate document. TBD.
//