W3C home > Mailing lists > Public > public-html@w3.org > January 2009

Re: HTML is a declarative mark-up language

From: Jirka Kosek <jirka@kosek.cz>
Date: Thu, 29 Jan 2009 23:43:00 +0100
Message-ID: <498230F4.1030209@kosek.cz>
To: Ian Hickson <ian@hixie.ch>
CC: HTML WG <public-html@w3.org>
Ian Hickson wrote:
> On Thu, 29 Jan 2009, Jirka Kosek wrote:
>> Ian Hickson wrote:
>> Such index would be very useful, indeed. But I was thinking about adding 
>> links to global attributes to every element definition so it is clear 
>> from the first sight that those attributes are available there.
> There's something on the order of 40 or more attributes that apply to 
> every element; listing them explicitly for each element seems like a lot 
> of redundant text. (There's even more if you start counting common APIs.)

I'm not asking for listing 40 attributes but for adding just one link
that will point to section defining these 40 global attributes. So every
reader will easily find that element XYZ has those 5 element specific
attributes and also shares other global attributes.

>> It would be also useful to have more explicit content model presented 
>> there. Yeah, this sounds like HTML5 markup-spec.
> More explicit than what? I don't understand what you mean here. Do you 
> mean having non-normative formalisms as well as the exhaustive normative 
> text we have now?

Yep, some formalism would it be something like DTD/RELAX NG content
models or something different will be really useful. Let's take <a>
element as an example. Spec in 4.6.1 says:

Content model:
Transparent, but there must be no interactive content descendant.

Now tell me how can I find which elements I can use inside <a>? I was
trying to follow link around "Transparent" and read target text and then
follow other links, ... Maybe it is because late time here, but I was
unable to find this answer.

Having something like hyperlinked grammar is much straightforward there.
For example something like


Personally I think that it is much more natural to have such formal
grammar normative and use prose text only as a supplement. But
normativeness/non-normativeness of such formal content-models was not my
point for now. I was questioning practical usability of the current
shape of spec.


  Jirka Kosek      e-mail: jirka@kosek.cz      http://xmlguru.cz
       Professional XML consulting and training services
  DocBook customization, custom XSLT/XSL-FO document processing
 OASIS DocBook TC member, W3C Invited Expert, ISO JTC1/SC34 member

Received on Thursday, 29 January 2009 22:43:49 UTC

This archive was generated by hypermail 2.4.0 : Saturday, 9 October 2021 18:44:42 UTC