[html5] Author of a quote - how to mark up?

[Steven Rossi]

Personally I agree with Luis. I can see some styling things where an authors
name would be offset to the bottom-right of a quote, etc., but I don't
really see the value in using an extra element to serve this purpose.
Styling an author item would be no less intuitive if it was done with a span
than it would be with this proposed author element. If we're just providing
more specific elements without adding new functionality, I don't see the
point.
On the other hand, I wouldn't mind <author> if some kind of new
functionality was provided. The author link type serves as an example, and I
believe something like that makes much more sense, because it specifies who
is the author of the parent article/page. If something of equivalent value
could be developed for the author element, I'd be all for it.

2009/8/13 Luis-Miguel Rodríguez Rojas <lmrodriguezr at gmail.com>

>  <p><span class='author'>Douglas Crockford</span> writes in
>> <cite>Javascript: The Good Parts</cite>: <q>Deep down, Javascript has
>> more in common with Lisp and Scheme than with Java. It is Lisp in C’s
>> clothing.</q></p>
>
>
> - AND -
>
> <p><author id="douglas-crockford">Douglas Crockford</author> writes in
>> <cite id="douglas-crockford-javascript-the-good-parts"
>> author="#douglas-crockford">Javascript: The Good Parts</cite>:
>> <q cite="#douglas-crockford-javascript-the-good-parts">Deep down, Javascript
>> has more in common with Lisp and Scheme than with Java. It is Lisp in C’s
>> clothing.</q></p>
>
>
> Are both displayed (without any further advantage on CSS or JavaScript, for
> example) as:
>
> Douglas Crockford writes in ‘Javascript: The Good Parts’: ‘Deep down, Javascript
>> has more in common with Lisp and Scheme than with Java. It is Lisp in C’s
>> clothing.’
>
>
> Therefore, what's the point to create <author>? Many new elements can be
> proposed if we think in search engines as main scope.  However, search
> engines must search for what people see in websites, not vice versa.  As
> Google itself recommends, make your site for people, not for search engines.
>
>
> On Thu, Aug 13, 2009 at 9:01 PM, Aryeh Gregor <Simetrical+w3c at gmail.com<Simetrical%2Bw3c at gmail.com>
> > wrote:
>
>> On Thu, Aug 13, 2009 at 8:35 PM, Samer Ziadeh<samerziadeh at gmail.com>
>> wrote:
>> > There are tons of HTML elements out there and so many of them are barely
>> > used by authors. Adding an extra elements such as "author" wouldn't hurt
>> > anyone, isn't hard to implement, and only take a line to explain what it
>> > does.
>>
>> If concrete use-cases were not required for new elements, the number
>> of elements in HTML would be ridiculous.  I think it would be pretty
>> easy to come up with twenty to fifty elements that are about as
>> reasonable or useful as a generic <author> tag.  What's the point?  It
>> would just be bloat.  This is why we have the class attribute, and
>> microdata.  Why not use the existing mechanisms for marking up content
>> if you don't have a specific reason to ask for a whole new element?
>> _______________________________________________
>> Help mailing list
>> Help at lists.whatwg.org
>> http://lists.whatwg.org/listinfo.cgi/help-whatwg.org
>>
>
>
>
> --
> Luis M. Rodriguez-R
> [http://bioinf.uniandes.edu.co/~miguel/]
> ---------------------------------
> Unidad de Bioinformática del Laboratorio de Micología y Fitopatología
> Universidad de Los Andes, Colombia
> [http://bioinf.uniandes.edu.co]
>
> + 57 1 3394949 ext 2619
> luisrodr at uniandes.edu.co
> lmrodriguezr at gmail.com
>
> _______________________________________________
> Help mailing list
> Help at lists.whatwg.org
> http://lists.whatwg.org/listinfo.cgi/help-whatwg.org
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.whatwg.org/pipermail/help-whatwg.org/attachments/20090813/f1982c95/attachment-0003.htm>