[whatwg] Elements to markup article headings
There are some analog conventions that does make sense to standardize
in different markup languages. This is not necessarily the job of the
HTML5 team, but it may have those issues in mind. There are a few
regarding the heading of newspaper articles, specific names differs,
but meaning is the same:
—The kicker / running head: a phrase that goes right before the
heading, usually a short teaser or the name of a section.
—The headline: the article title.
—The drop deck / lead /lede: the paragraph that gives a short abstract
of the article.
—The byline: the line that contains meta info like the author, and/or
the date of the article. This can go before the lead, after it or at
the end of the article.
There have been some discussion regarding each one which have been
more or less clarified. The way to markup that with the current
standard:
Kicker
Headline
Deck
Byline
[...]
It looks fine, but I'm not entirely convinced by the tag for the
byline, mainly because, even when it could be place differently or
even multiple times inside a newspaper article, when it appears at the
beginning it could make more sense to have it between the ,
but that is not possible due to the rule of not having tags
with descendants and vice-versa. That does makes sense when
sticking to what the names of the elements imply, yet conceptually I
see no reason a as in "textual metadata of a section" can't
be inside a ("lead of a section"). Alternatives could be
using the element, yet that's an inline element and I'm not
sure it complies with the byline meaning as well as the
element. I could rather propose a change to the behavior or
even a new element, but not sure if that is worth it.
Any suggestion or comments regarding the way to markup newspaper
article headings?
Re: [whatwg] Encoding Sniffing
On Sat, Apr 21, 2012 at 8:21 PM, Anne van Kesteren wrote: > Hey, > > This morning I looked into what it would take to define Encoding Sniffing. > http://wiki.whatwg.org/wiki/Encoding#Sniffing has links as to what I looked > at (minus Opera internal). As far as I can tell Gecko has the most > comprehensive approach and should not be too hard to define (though writing > it all out correctly and clear will be some work). > > I have some questions though: > > 1) Is this something we want to define and eventually implement the same > way? > 2) Does this need to apply outside HTML? For JavaScript it forbidden per the > HTML standard at the moment. CSS and XML do not allow it either. Is it used > for decoding text/plain at the moment? We've had some discussion on the usefulness of this in WebVTT - mostly just in relation with HTML, though I am sure that stand-alone video players that decode WebVTT would find it useful, too. Cheers, Silvia. > 3) Is there a limit to how many bytes we should look at? > > Thanks, > > > -- > Anne van Kesteren > http://annevankesteren.nl/
[whatwg] Encoding Sniffing
Hey, This morning I looked into what it would take to define Encoding Sniffing. http://wiki.whatwg.org/wiki/Encoding#Sniffing has links as to what I looked at (minus Opera internal). As far as I can tell Gecko has the most comprehensive approach and should not be too hard to define (though writing it all out correctly and clear will be some work). I have some questions though: 1) Is this something we want to define and eventually implement the same way? 2) Does this need to apply outside HTML? For JavaScript it forbidden per the HTML standard at the moment. CSS and XML do not allow it either. Is it used for decoding text/plain at the moment? 3) Is there a limit to how many bytes we should look at? Thanks, -- Anne van Kesteren http://annevankesteren.nl/
