Nofollow Makes it Into HTML5 Specification

Friday, January 25, 2008 by Mistlee



Recent Articles

Firefox & The FileUpload Control In ASP.NET
I've been pretty annoyed about the fact that FireFox ignores the width property of the ASP.NET FileUpload control. It doesn't matter if you set it by CSS or even in JavaScript, Firefox always ignores it and...

Rearchitecture For Better Maintainability & Scalability.
I'm working with just three clients right now and with each of them I am essentially doing the same thing: taking an existing system that has been built up over a number of years and helping them rearchitect it for better...

Coldfusion: Flexible String Comparisons
Martin asks a pretty interesting question about comparing strings: Is there a way to compare the similarities of variable strings in ColdFusion? For instance, lets say...

Upgrading To WordPress 2.3.1
For the longest time I let my blog remain on the 2.02 version of Wordpress. One of the reasons that this was the case is that upgrading Wordpress used to...

SEO And Development Must Work Closely Together
Have you ever written up a beautiful technical SEO plan for a site and then have it come back from development all messed up? There truly is no win in making a set of...

Dueling Document Object Model Inspectors
The "DOM", in web page speak, is the Document Object Model. The W3C explains it: What is the Document Object Model?: The Document Object Model is a platform- and language-neutral interface that willf...

Google Chart API Released
Google released a chart generator service they are calling the Google Chart API. Usage is quite straightforward: you link to an image in the form of a parameterized...


01.25.08

Nofollow Makes it Into HTML5 Specification

By Philipp Lenssen

HTML5 appeared as first working draft at the World Wide Web Consortium.

Partially, XHTML2 made more sense to me (e.g. a simple instead of

,

and so on could be used for headings, accompanied by a
element... and RSS features were integrated right into the document). We'll have to see where the W3C wants to go – and then wait some years for browsers to actually implement any of this... and then wait for those browsers to be reasonably deployed.

Right now, this Alpha specification seems to try to acknowledge some web realities (like an
element for typical blogs, called "Web logs" in the draft), while ignoring others (for instance, elements like
are still included even though they remain to be largely ignored by web authors even after years). It's a bit of a manifesto – written in rather non-accessible language, in good W3C tradition – trying to merge different "HTML religions" (e.g. Plain Old HTML vs XHTML/ XML), so many aspects of it are merely of religious interest it seems. At one point, this aspect is even made explicit when the draft says (my emphasis):

Though it has absolutely no effect and no meaning, the html element, in HTML documents, may have an xmlns attribute specified, if, and only if, it has the exact value "http://www.w3.org/1999/xhtml". ... In HTML, the xmlns attribute has absolutely no effect. It is basically a talisman. It is allowed merely to make migration to and from XHTML mildly easier.

Try a Better Way Today. Try WebEx PCNow

Interestingly enough, the "nofollow" attribute value for links – originally introduced by several search engines, including Google (nofollow was only used a document's meta section before that) – has made it into the specification, along with a couple of other values. Perhaps not coincidentally, one of the two editors listed for the document is Ian Hickson, who works at Google. Quote from the draft:

• "The nofollow keyword may be used with a and area elements. The nofollow keyword indicates that the link is not endorsed by the original author or publisher of the page."

• "The noreferrer keyword may be used with a and area elements. If a user agent follows a link defined by an a or area element that has the noreferrer keyword, the user agent must not include a Referer HTTP header (or equivalent for other protocols) in the request."

• "The search keyword may be used with link, a, and area elements. ... The search keyword indicates that the referenced document provides an interface specifically for searching the document and its related resources."

• "The help keyword may be used with link, a, and area elements. ... For a and area elements, the help keyword indicates that the referenced document provides further help information for the parent of the element defining the hyperlink, and its children."

• "The license keyword may be used with link, a, and area elements. For link elements, it creates a hyperlink. The license keyword indicates that the referenced document provides the copyright license terms under which the current document is provided."

• "The archives keyword indicates that the referenced document describes a collection of records, documents, or other materials of historical interest."

• "The feed keyword indicates that the referenced document is a syndication feed."

[Via Martin Porcheron at Friendfeed.]

Comments


About the Author:
Philipp Lenssen from Germany, author of 55 Ways to Have Fun With Google, shares his views & news on the search industry in the daily Google Blogoscoped.


About DevWebPro
DevWebPro is for professional developers ... those who build and manage applications and sophisticated websites. With over 300,000 subscribers, DevWebPro delivers via news and expert advice New Strategies In Development.

DevWebPro is brought to you by:

SecurityConfig.com NetworkingFiles.com
NetworkNewz.com WebProASP.com
DatabaseProNews.com SQLProNews.com
ITcertificationNews.com SysAdminNews.com
LinuxProNews.com WirelessProNews.com
CProgrammingTrends.com ITmanagementnews.com


DevWebPro News Archives About Us Feedback DevWebPro Home Page About Article Archive News Downloads WebProWorld Forums Jayde iEntry Advertise Contact

0 comments: