- From: <bugzilla@jessica.w3.org>
- Date: Mon, 10 Jan 2011 14:11:19 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11715
Philip Jägenstedt <philipj@opera.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |philipj@opera.com
--- Comment #1 from Philip Jägenstedt <philipj@opera.com> 2011-01-10 14:11:19 UTC ---
After implementing most of
<http://www.whatwg.org/specs/web-apps/current-work/multipage/links.html#extracting-atom>
I found this to be a useful addition.
Just using <meta name=author> for feed-wide author isn't as awesome as it could
be if you're converting a planet-like page with many authors.
rel=author is already suitable defined, so this HTML
<article>
<header>
<h1>Title</h1>
by <a href="http://foolip.org" rel=author>Philip Jägenstedt</a>
</header>
Bla bla bla...
</article>
would give something like the following Atom:
<entry xml:base="...">
<title type="html">Title</title>
<author><name>Philip Jägenstedt</name><uri>http://foolip.org/</uri></author>
<content type="html">
Bla bla bla...
</content>
</feed>
(I'm using the plain-text textContent of <a> as <author><name>.)
This has the benefit that you can get both a URL and a name for an author,
which you can't do with a combination of <meta> and <link> since you can't be
sure that it's for the same author.
With this change, it might be worth making the algorithm fail if there's not
enough <author> sprinkled around to make it valid Atom, but that's another
issue.
--
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Monday, 10 January 2011 14:11:23 UTC