Re: (Experimental) W3C document dependencies' roadmap for publishing

> On 2 Oct 2017, at 04:32, Florian Rivoal <florian@rivoal.net <mailto:florian@rivoal.net>> wrote:
> 
>> 
>> On Oct 1, 2017, at 16:19, Ivan Herman <ivan@w3.org <mailto:ivan@w3.org>> wrote:
>> 
>>> 
>>> On 29 Sep 2017, at 19:18, Jiminy Panoz <jiminy@chapalpanoz.com <mailto:jiminy@chapalpanoz.com>> wrote:
>>> 
>>> Ivan,
>>> 
>>> I can indeed relate, I’m trying to keep a list of modules which are likely to impact EPUB 3.1 at some point, hence the Readium CSS project, and it’s super painful. 
>>> 
>>> To clarify, this is the reason why I tried to find some “scope” in CSS Modules in the first place; I was wondering where the limit should be drawn. Basically, all CSS modules dealing with layout and text are related to publishing.
>>> 
>>> 
>> 
>> Yes. That being said, it would probably of help if the large number of CSS modules (and I am sure that list will grow) would have a decent categorization from our point of view, shown on that page. But I need help for this, I certainly do not have a deep enough knowledge of all the CSS modules to be able to do this.
> 
> Ultimately, the web platform expects all of CSS, so everything is in scope to some degree.
> 
> However, various modules of CSS can be of stronger interest than average to this community, and I think it is worth trying to bring attention to these.
> 
> Categorizing them is probably a good idea (pagination / advanced layout / typography…)

I could try, but I do not trust my own knowledge. Can one of you propose a categorization of the documents that are already there? I can of course reedit the file itself, I do not ask you to do the HTML editing.

Thanks

Ivan



> 
> —Florian


----
Ivan Herman, W3C 
Publishing@W3C Technical Lead
Home: http://www.w3.org/People/Ivan/ <http://www.w3.org/People/Ivan/>
mobile: +31-641044153
ORCID ID: http://orcid.org/0000-0003-0782-2704 <http://orcid.org/0000-0003-0782-2704>