Hi Robin, thanks for your email and pleased to meet you too! > That is just one topic amongst potentially several that I would like to > discuss (but there is no rush). In general, I am interested in features that > EPUB adds that aren't available on the vanilla "browser" web. I believe that > those should provide use cases for additions to HTML. (Note that I'm not > saying that HTML should just import them as is — but I do think that we > should strive for convergence and I want to help with that.)
Glad to hear this -- and also agree that among the topics that relate to further harmonisation between EPUB and the OWP, usage of @role is just one of many items, and @role is not necessarily the sole or ideal solution the particular "problem" of structural inflection either. That said, @role is arguably the closest relative that we have for @epub:type in W3C space right now, so we are definitely interested in continuing this discussion. > The first questions I received were about how much this was implemented in > actual readers, i.e. how actual implementations change their behaviour > (compared to an unmodified HTML engine) based on these types. If you have any > way in which I could easily find such information, it would be most helpful. Right. There are not many demoable implementations of specific reading system behaviours at this point (beyond the footnote behaviours in ibooks that everybody seems to know about). But there are several concrete (and general, as opposed to AT-specific) use cases for it in the pipeline, including as Ivan mentions the identification of structures such as glossaries, dictionaries and indexes. I will keep you updated as implementations emerge, both general and AT-specific. For now, /markus On Apr 2, 2013, at 3:21 PM, Robin Berjon <[email protected]> wrote: > Dear Markus, > > On 27/03/2013 14:49 , Ivan Herman wrote: >> Robin, please meat Markus Gylling, CTO of IDPF and also possible >> chair of the upcoming Digital Publishing IG. > > Pleased to meet you! > >> Markus, I had some discussions with Robin on the question we were >> discussing a while ago you and me, on whether the @role attribute >> could be used in EPUB3.01 to replace the current idpf:type attribute >> for, say, glossary items. I just forward you the relevant issues; I >> let you two discuss the technical details, if any... > > That is just one topic amongst potentially several that I would like to > discuss (but there is no rush). In general, I am interested in features that > EPUB adds that aren't available on the vanilla "browser" web. I believe that > those should provide use cases for additions to HTML. (Note that I'm not > saying that HTML should just import them as is — but I do think that we > should strive for convergence and I want to help with that.) > > Concerning @role, I started discussing the potential usage of it from EPUB > types. The first questions I received were about how much this was > implemented in actual readers, i.e. how actual implementations change their > behaviour (compared to an unmodified HTML engine) based on these types. If > you have any way in which I could easily find such information, it would be > most helpful. > > Thanks! > > -- > Robin Berjon - http://berjon.com/ - @robinberjon
