Re: [Styling and Layout] new use case added: Lists, Outline Lists

On 17 Dec 2013, at 19:38 , Jean Kaplansky <Jean.Kaplansky@aptaracorp.com> wrote:

> I’ll go fix the wording in the Use Case to be more specific. It’s still relevant to the HTML and CSS working groups within the W3C, though, right?

Yes, thank you.

> 
> Which leads to a question: When a use case such as the use case for formal outlines is identified, when does a decision get made about which standards body working group (W3C|IDPF) will provide the solution, and who (W3C|IDPF) gets to make that call?

Good question; I would expect that would be the topic of discussion on the calls concentrating on that specific task force... In many cases we may not know the answer and we would have to discuss explicitly with some persons on those groups. We have Bert Bos on our IG who is also a staff contact for CSS and MathML, and Robin Berjon who is also editor of the HTML spec. We may get, eventually, Ed O'Connor to the IG, too, who is also an editor of the HTML spec. They should be able to give an initial reaction...

Thanks!

ivan


> 
> Thanks,
> Jean
> 
> From: Ivan Herman <ivan@w3.org>
> Date: Tuesday, December 17, 2013 at 10:42 AM
> To: Dave Cramer <Dave.Cramer@hbgusa.com>
> Cc: Jean Kaplansky <jean.kaplansky@aptaracorp.com>, DPUB <public-digipub-ig@w3.org>, Bert Bos <bert@w3.org>
> Subject: Re: [Styling and Layout] new use case added: Lists, Outline Lists
> 
> 
> On 17 Dec 2013, at 16:28 , Cramer, Dave <Dave.Cramer@hbgusa.com> wrote:
> 
> <snip/>
>>> I don’t think this use case starts with the CSS group. It should start with the HTML group where the markup can be modeled effectively. UA’s can then use browser default CSS to support the markup.
>> You mentioned above that it might be OK for an outline list to be marked up as ol with a special type attribute. Does that make this a case where the problem isn't so much that HTML needs a new list structure, but that HTML needs a better/more standard mechanism for adding semantic information to existing markup?
> 
> Right. And this is where this issue meets the use cases edited by Tzviya, and the discussion we had in Shenzhen. I think the conclusion is that it *is* possible to define 'dash' attributes for HTML5; ie, it is possible to
> 
> - decide to use the idpf-type (or whatever) attribute (and possibly others)
> - define the possible values for the attribute(s)
> - a reputable group like, say, IDPF or a W3C group, document this precisely
> 
> After that, the HTML5 WG would accept that as a bona fide extension, and the attribute name(s) as well as the possible values are incorporated in the various HTML validators (including a check whether the attribute values are o.k.). This is what Markus referred to as the 'ITS model'...
> 
> Ivan
> 
> 
> ----
> Ivan Herman, W3C
> Digital Publishing Activity Lead
> Home: http://www.w3.org/People/Ivan/
> mobile: +31-641044153
> GPG: 0x343F1A3D
> FOAF: http://www.ivan-herman.net/foaf
> 
> 
> 
> 
> 
> 


----
Ivan Herman, W3C 
Digital Publishing Activity Lead
Home: http://www.w3.org/People/Ivan/
mobile: +31-641044153
GPG: 0x343F1A3D
FOAF: http://www.ivan-herman.net/foaf