<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: The Address Element</title>
	<atom:link href="http://html5doctor.com/the-address-element/feed/" rel="self" type="application/rss+xml" />
	<link>http://html5doctor.com/the-address-element/</link>
	<description>helping you implement HTML5 today</description>
	<lastBuildDate>Mon, 21 May 2012 10:47:22 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=</generator>
	<item>
		<title>By: AJ</title>
		<link>http://html5doctor.com/the-address-element/#comment-25394</link>
		<dc:creator>AJ</dc:creator>
		<pubDate>Thu, 03 May 2012 20:31:34 +0000</pubDate>
		<guid isPermaLink="false">http://html5doctor.com/?p=1051#comment-25394</guid>
		<description>Awesome. Thanks for clearing this up!</description>
		<content:encoded><![CDATA[<p>Awesome. Thanks for clearing this up!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul</title>
		<link>http://html5doctor.com/the-address-element/#comment-25371</link>
		<dc:creator>Paul</dc:creator>
		<pubDate>Wed, 02 May 2012 06:18:30 +0000</pubDate>
		<guid isPermaLink="false">http://html5doctor.com/?p=1051#comment-25371</guid>
		<description>Ok. Theres more. Ive gone in a loop. Microdata -  hCard maybe a more defined way (kindof). Yes Doctor you are the Doctor and after much refinement I think your right :)

The following sold me:
http://www.webmonkey.com/2010/09/microdata-html5s-best-kept-secret/

http://www.google.com/support/webmasters/bin/answer.py?hl=en&amp;answer=99170

http://html5doctor.com/microformats/#hcard (example in this post also) 

Look forward to feedback ^-^</description>
		<content:encoded><![CDATA[<p>Ok. Theres more. Ive gone in a loop. Microdata &#8211;  hCard maybe a more defined way (kindof). Yes Doctor you are the Doctor and after much refinement I think your right :)</p>
<p>The following sold me:<br />
<a href="http://www.webmonkey.com/2010/09/microdata-html5s-best-kept-secret/" rel="nofollow">http://www.webmonkey.com/2010/09/microdata-html5s-best-kept-secret/</a></p>
<p><a href="http://www.google.com/support/webmasters/bin/answer.py?hl=en&#038;answer=99170" rel="nofollow">http://www.google.com/support/webmasters/bin/answer.py?hl=en&#038;answer=99170</a></p>
<p><a href="http://html5doctor.com/microformats/#hcard" rel="nofollow">http://html5doctor.com/microformats/#hcard</a> (example in this post also) </p>
<p>Look forward to feedback ^-^</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul</title>
		<link>http://html5doctor.com/the-address-element/#comment-25370</link>
		<dc:creator>Paul</dc:creator>
		<pubDate>Wed, 02 May 2012 05:37:11 +0000</pubDate>
		<guid isPermaLink="false">http://html5doctor.com/?p=1051#comment-25370</guid>
		<description>Although it doesnt seem the cleanest way of defining each element of a generic company address.</description>
		<content:encoded><![CDATA[<p>Although it doesnt seem the cleanest way of defining each element of a generic company address.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul</title>
		<link>http://html5doctor.com/the-address-element/#comment-25369</link>
		<dc:creator>Paul</dc:creator>
		<pubDate>Wed, 02 May 2012 05:25:48 +0000</pubDate>
		<guid isPermaLink="false">http://html5doctor.com/?p=1051#comment-25369</guid>
		<description>After reading all the replies and associated markup, W3schools cleared it up for me. http://www.w3schools.com/html5/tag_address.asp</description>
		<content:encoded><![CDATA[<p>After reading all the replies and associated markup, W3schools cleared it up for me. <a href="http://www.w3schools.com/html5/tag_address.asp" rel="nofollow">http://www.w3schools.com/html5/tag_address.asp</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike Edward Moras (e-sushi™)</title>
		<link>http://html5doctor.com/the-address-element/#comment-25263</link>
		<dc:creator>Mike Edward Moras (e-sushi™)</dc:creator>
		<pubDate>Mon, 16 Apr 2012 04:23:28 +0000</pubDate>
		<guid isPermaLink="false">http://html5doctor.com/?p=1051#comment-25263</guid>
		<description>Short addition:

&lt;blockquote&gt;The address element represents contact information.&lt;/blockquote&gt;

source: www.w3.org/TR/html-markup/address.html</description>
		<content:encoded><![CDATA[<p>Short addition:</p>
<blockquote><p>The address element represents contact information.</p></blockquote>
<p>source: <a href="http://www.w3.org/TR/html-markup/address.html" rel="nofollow">http://www.w3.org/TR/html-markup/address.html</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike Edward Moras (e-sushi™)</title>
		<link>http://html5doctor.com/the-address-element/#comment-25245</link>
		<dc:creator>Mike Edward Moras (e-sushi™)</dc:creator>
		<pubDate>Wed, 11 Apr 2012 18:34:34 +0000</pubDate>
		<guid isPermaLink="false">http://html5doctor.com/?p=1051#comment-25245</guid>
		<description>Interesting... stating that a postal address should not be marked up with the &quot;address&quot; tag is like expecting people to see without using their eyes.

There is no reason (looking at the specs) why you should not mark up a postal address in there. 

You write that &quot;the address element was not created for postal addresses&quot; and try to provide a bit of proof by writing &quot;To reinforce this, the latest spec stipulates that the address element must not be used to represent arbitrary addresses&quot; with a link to the specs.

Did you take the time to read those specs yourself?

They clearly state: &quot;The address element must not be used to represent arbitrary addresses (e.g. postal addresses), &lt;strong&gt;unless those addresses are in fact the relevant contact information.&lt;/strong&gt; (The p element is the appropriate element for marking up postal addresses in general.)&quot;

So, YES, you can put a postal address in an address tag... as long as you remember that the address tag should be seen like some of the new HTML5 tags (section,article,figure,time,etc.), as the &quot;address&quot; tag enables the classification of a document&#039;s content sections just like those new HTML5 tags. In the end, it&#039;s the thought of tags like &quot;address&quot; that is currently being re-injected into the HTML5 specs.

But hey, these are just my two cents. I&#039;m not going to try to stop you from spreading a bit of misinformation, just because you - as you write - seem to be part of a group of &quot;confused&quot; people and lost in your own interpretation of what you think you see. 

See, there is no option for confusion. Read the docs and follow their lead. Don&#039;t try to make it more difficult than it is, just because your brain is used to crack harder nuts. ;)</description>
		<content:encoded><![CDATA[<p>Interesting&#8230; stating that a postal address should not be marked up with the &#8220;address&#8221; tag is like expecting people to see without using their eyes.</p>
<p>There is no reason (looking at the specs) why you should not mark up a postal address in there. </p>
<p>You write that &#8220;the address element was not created for postal addresses&#8221; and try to provide a bit of proof by writing &#8220;To reinforce this, the latest spec stipulates that the address element must not be used to represent arbitrary addresses&#8221; with a link to the specs.</p>
<p>Did you take the time to read those specs yourself?</p>
<p>They clearly state: &#8220;The address element must not be used to represent arbitrary addresses (e.g. postal addresses), <strong>unless those addresses are in fact the relevant contact information.</strong> (The p element is the appropriate element for marking up postal addresses in general.)&#8221;</p>
<p>So, YES, you can put a postal address in an address tag&#8230; as long as you remember that the address tag should be seen like some of the new HTML5 tags (section,article,figure,time,etc.), as the &#8220;address&#8221; tag enables the classification of a document&#8217;s content sections just like those new HTML5 tags. In the end, it&#8217;s the thought of tags like &#8220;address&#8221; that is currently being re-injected into the HTML5 specs.</p>
<p>But hey, these are just my two cents. I&#8217;m not going to try to stop you from spreading a bit of misinformation, just because you &#8211; as you write &#8211; seem to be part of a group of &#8220;confused&#8221; people and lost in your own interpretation of what you think you see. </p>
<p>See, there is no option for confusion. Read the docs and follow their lead. Don&#8217;t try to make it more difficult than it is, just because your brain is used to crack harder nuts. ;)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: BotRot</title>
		<link>http://html5doctor.com/the-address-element/#comment-24850</link>
		<dc:creator>BotRot</dc:creator>
		<pubDate>Sun, 04 Mar 2012 00:26:48 +0000</pubDate>
		<guid isPermaLink="false">http://html5doctor.com/?p=1051#comment-24850</guid>
		<description>All this grey area with, use this tag for this, but not for that, unless that is this...

I wonder what div-ities and span-mania will morph into?

Think we&#039;ll footer in header disease from someone?

What if I want to show a video of an address. is this OK?

&lt;address&gt;
    &lt;video&gt;&lt;/video&gt;
&lt;/address&gt;

Semantics, its&#039; different for everybody... I think!</description>
		<content:encoded><![CDATA[<p>All this grey area with, use this tag for this, but not for that, unless that is this&#8230;</p>
<p>I wonder what div-ities and span-mania will morph into?</p>
<p>Think we&#8217;ll footer in header disease from someone?</p>
<p>What if I want to show a video of an address. is this OK?</p>
<p>&lt;address&gt;<br />
    &lt;video&gt;&lt;/video&gt;<br />
&lt;/address&gt;</p>
<p>Semantics, its&#8217; different for everybody&#8230; I think!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tchalvak</title>
		<link>http://html5doctor.com/the-address-element/#comment-21202</link>
		<dc:creator>Tchalvak</dc:creator>
		<pubDate>Thu, 05 Jan 2012 16:30:07 +0000</pubDate>
		<guid isPermaLink="false">http://html5doctor.com/?p=1051#comment-21202</guid>
		<description>Aw, and here I was scrolling through to the bottom in hope that the comment in the original article about there being address info in the footer would still be true.  But apparently not so much...</description>
		<content:encoded><![CDATA[<p>Aw, and here I was scrolling through to the bottom in hope that the comment in the original article about there being address info in the footer would still be true.  But apparently not so much&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jason Simone</title>
		<link>http://html5doctor.com/the-address-element/#comment-21189</link>
		<dc:creator>Jason Simone</dc:creator>
		<pubDate>Tue, 03 Jan 2012 23:29:54 +0000</pubDate>
		<guid isPermaLink="false">http://html5doctor.com/?p=1051#comment-21189</guid>
		<description>I&#039;ve been reading up on this element, but I can&#039;t locate a justification that pleases me regarding the restriction of this element to authorship information. Can someone clue me in?

In earlier specifications, I was always among the camp choosing to take the words &quot;address _may_ include&quot; from the specification more liberally. Admittedly, the new language in the HTML5 spec leave less wiggle room, by explicitly stating the element&#039;s intention: &quot;The address element provides contact information for a document or part of a document.&quot; I do however find the &quot;part of a document&quot; intriguing. Obviously, this could refer to a section of a page with alternate authorship, such as a multiple-author blog or a comment. 

However, it seems to make just as just as much semantic sense to me to use  to provide contact information for a document _not_ authored by the subject. For example, if I have a page about Stephen King, called Stephen King, how does it make any less sense to use  for his contact info? I&#039;ve found very little info about why such a restriction would be beneficial. Perhaps we should think carefully before stating that this approach is definitively &quot;the wrong way&quot;. If that is the W3C intention, however, then I may still exercise discretion in how closely I adhere to it...</description>
		<content:encoded><![CDATA[<p>I&#8217;ve been reading up on this element, but I can&#8217;t locate a justification that pleases me regarding the restriction of this element to authorship information. Can someone clue me in?</p>
<p>In earlier specifications, I was always among the camp choosing to take the words &#8220;address _may_ include&#8221; from the specification more liberally. Admittedly, the new language in the HTML5 spec leave less wiggle room, by explicitly stating the element&#8217;s intention: &#8220;The address element provides contact information for a document or part of a document.&#8221; I do however find the &#8220;part of a document&#8221; intriguing. Obviously, this could refer to a section of a page with alternate authorship, such as a multiple-author blog or a comment. </p>
<p>However, it seems to make just as just as much semantic sense to me to use  to provide contact information for a document _not_ authored by the subject. For example, if I have a page about Stephen King, called Stephen King, how does it make any less sense to use  for his contact info? I&#8217;ve found very little info about why such a restriction would be beneficial. Perhaps we should think carefully before stating that this approach is definitively &#8220;the wrong way&#8221;. If that is the W3C intention, however, then I may still exercise discretion in how closely I adhere to it&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Philip Jägenstedt</title>
		<link>http://html5doctor.com/the-address-element/#comment-17962</link>
		<dc:creator>Philip Jägenstedt</dc:creator>
		<pubDate>Fri, 07 Oct 2011 17:55:29 +0000</pubDate>
		<guid isPermaLink="false">http://html5doctor.com/?p=1051#comment-17962</guid>
		<description>Lijn, the situation is similar as with microformats. Microdata/microformats just embed the data, software is always required to get from that to an entry in your address book. I don&#039;t doubt that more tools are available for microformats, but it&#039;s actually slightly easier to parse microdata than microformats, for what it&#039;s worth.</description>
		<content:encoded><![CDATA[<p>Lijn, the situation is similar as with microformats. Microdata/microformats just embed the data, software is always required to get from that to an entry in your address book. I don&#8217;t doubt that more tools are available for microformats, but it&#8217;s actually slightly easier to parse microdata than microformats, for what it&#8217;s worth.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

