HTML 5: Become an expert

Translate This Page

HTML 5: Become an expert

Rate This
  • Comments 4


So you want to be an expert at HTML 5, good move.  If you have worked with earlier versions of HTML but never read the specification, it might be a good idea to start out this time by reading the specification.  The specification for HTML5 can be found at:

As mentioned earlier, this is the link to the latest DRAFT.  If you want to be an expert, or knowledgeable, you will need to be able to discuss the evolution of the product as well as the current version.  If you see things are that seem to be incorrect you can give feedback, the current draft should be the one you read prior to giving feedback to the commit watchers you sign up here:

Now let’s determine how you become an expert:

From the HTML 5 Specification:

1.7.1 How to read this specification

This is a good practice for many things we should read, if you are buying real estate, legal documents and things you are becoming an expert at:

“This specification should be read like all other specifications. First, it should be read cover-to-cover, multiple times. Then, it should be read backwards at least once. Then it should be read by picking random sections from the contents list and following all the cross-references.”

Those words are from the Specification, they aren’t mine, wish I could take credit.


1.7.2 Typographic conventions

These are important, the typographic conventions and understanding that there is a precision to the way the words are presented.  You might want to print this section out, put it on a separate screen when you are reading the HTML 5 Specification.  After all if you are “agile”, you may not be used to reading specifications, fair enough, but again if you want to be an “expert” you might need to be comfortable with this type of document, but then again, in software it isn’t a requirement.

1.10 Recommended reading

One of the ways to become an expert is to read other material, the HTML 5 specification asks that you also read other documents, in this case you should treat these documents the same way you treat the HTML5 specification, use the same rule for reading discussed in this document:


Initially, read the HTML5 document, this is what the authors for the books you may purchase in 18 or so months are doing right now.  If you read the HTML 5 specification, it will give you a better idea of what HTML does, and it can help you in your career.


Gratuitous mention of the “Royal Wedding”

And now a mention about the wedding of Prince Williams and Kate Middleton:

  • Is Kate Middleton checking her email in this photo? 

Image: Britain's Prince William salutes and his wife Catherine, the Duchess of Cambridge, bows her head

Leave a Comment
  • Please add 2 and 8 and type the answer here:
  • Post
  • WTF, what were you thinking about putting a Royal Wedding photo in you post?!  What a stupid thing to do!

  • Ok, now I am having my internal conversation online.  

  • Good to know, now I don't have to waste my time with Silverlight anymore...I think I will buy an IPad as well.


  • Well Troy, you might want to wait and see what the Windows 8 product looks like as well.  But anyway you look at it, doing things like HTML5 development on a slate like device is hard for me since I like to have a real keyboard and a large screen.

    But have fun.  XAML will be around for quite awhile.

Page 1 of 1 (4 items)
Generic Content

Legal Note:

  1. The author, Sam Stokes, is an employee of Microsoft
  2. There is no guarantee that anything I write is correct, I do try to make sure that what I write is correct.
  3. Use anything written in this blog at your own risk
  4. Test what I write about before using the information
  • Sometimes posts will disappear because I realized that they really don't fit with the total chaos of what I write about
  • Links are tested and available on date of publication, what others do with their links are out of my control


  • Whatever I write on this blog is unedited by management or anyone, which should be obvious from the randomness of the blog.  I simply write about things I like.
  • Microsoft does not restrict me in anyway, so I generallyblather about whatever I want to.
  • For personal reasons I will not write about:
    • Company confidential stuff, mainly because Microsoft is more transparent than any company I have ever worked for.
    • Other people unless they give me permission to write about them