<?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: HTML5: &lt;b&gt; and &lt;i&gt; tags are going to be useful (read: semantic) again!</title>
	<atom:link href="http://stellify.net/html5-b-and-i-tags-are-going-to-be-useful-read-semantic-again/feed/" rel="self" type="application/rss+xml" />
	<link>http://stellify.net/html5-b-and-i-tags-are-going-to-be-useful-read-semantic-again/</link>
	<description>On web design, technology, the Philippines, and more.</description>
	<lastBuildDate>Sun, 19 Feb 2012 17:14:16 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: Who Says -b- and -i- are Non-semantic Markup? &#124; HowWhyWeb.com</title>
		<link>http://stellify.net/html5-b-and-i-tags-are-going-to-be-useful-read-semantic-again/#comment-71526</link>
		<dc:creator>Who Says -b- and -i- are Non-semantic Markup? &#124; HowWhyWeb.com</dc:creator>
		<pubDate>Wed, 19 May 2010 19:36:35 +0000</pubDate>
		<guid isPermaLink="false">http://stellify.net/html5-b-and-i-tags-are-going-to-be-useful-read-semantic-again/#comment-71526</guid>
		<description>[...] got to the bottom of what &#8220;semantic&#8221; actually means. Maybe that&#8217;s why HTML5 will let them go free. But while we can&#8217;t all have a different interpretation of what a tag does, who says we [...]</description>
		<content:encoded><![CDATA[<p>[...] got to the bottom of what &#8220;semantic&#8221; actually means. Maybe that&#8217;s why HTML5 will let them go free. But while we can&#8217;t all have a different interpretation of what a tag does, who says we [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ia</title>
		<link>http://stellify.net/html5-b-and-i-tags-are-going-to-be-useful-read-semantic-again/#comment-33784</link>
		<dc:creator>ia</dc:creator>
		<pubDate>Sun, 27 Jul 2008 10:27:05 +0000</pubDate>
		<guid isPermaLink="false">http://stellify.net/html5-b-and-i-tags-are-going-to-be-useful-read-semantic-again/#comment-33784</guid>
		<description>Usage will always vary by locale, the same way grammar does, but again I raise my point about word processors using B, I, and U not just for &lt;em&gt;styling&lt;/em&gt; text but giving meaning to text. For decades, it&#039;s been dictated to us that if you&#039;re going to cite the title of a book, it should be in italics. HTML should be the same way, ideally. Don&#039;t ask the people to memorize a completely different tag for just the title of a book.</description>
		<content:encoded><![CDATA[<p>Usage will always vary by locale, the same way grammar does, but again I raise my point about word processors using B, I, and U not just for <em>styling</em> text but giving meaning to text. For decades, it&#8217;s been dictated to us that if you&#8217;re going to cite the title of a book, it should be in italics. <acronym title="HyperText Markup Language">HTML</acronym> should be the same way, ideally. Don&#8217;t ask the people to memorize a completely different tag for just the title of a book.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ian</title>
		<link>http://stellify.net/html5-b-and-i-tags-are-going-to-be-useful-read-semantic-again/#comment-33783</link>
		<dc:creator>Ian</dc:creator>
		<pubDate>Sun, 27 Jul 2008 10:18:21 +0000</pubDate>
		<guid isPermaLink="false">http://stellify.net/html5-b-and-i-tags-are-going-to-be-useful-read-semantic-again/#comment-33783</guid>
		<description>The examples are too shallow: &quot;stylistically offset&quot; a span of text from the natural flow? &lt;span class=&quot;some_class_to_set_it_apart&gt; comes to mind. Tedious, sure, but semantically correct, and in line with the W3C&#039;s objective of separating content from presentation.

Encouraging the use of presentational elements in HTML is a step backward in the evolution of the language.  &quot;Usage varies by language&quot; -- precisely the reason why contextual standards should be in place.</description>
		<content:encoded><![CDATA[<p>The examples are too shallow: &#8220;stylistically offset&#8221; a span of text from the natural flow? &lt;span class=&#8221;some_class_to_set_it_apart&gt; comes to mind. Tedious, sure, but semantically correct, and in line with the <acronym title="World Wide Web Consortium">W3C</acronym>&#8217;s objective of separating content from presentation.</p>
<p>Encouraging the use of presentational elements in <acronym title="HyperText Markup Language">HTML</acronym> is a step backward in the evolution of the language.  &#8220;Usage varies by language&#8221; &#8212; precisely the reason why contextual standards should be in place.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: JC John SESE Cuneta</title>
		<link>http://stellify.net/html5-b-and-i-tags-are-going-to-be-useful-read-semantic-again/#comment-31682</link>
		<dc:creator>JC John SESE Cuneta</dc:creator>
		<pubDate>Fri, 02 May 2008 10:55:57 +0000</pubDate>
		<guid isPermaLink="false">http://stellify.net/html5-b-and-i-tags-are-going-to-be-useful-read-semantic-again/#comment-31682</guid>
		<description>Yah, hehe.  It&#039;ll be very interesting to see how B vs STRONG and I vs EM will turn out.  Well, overall it is good W3C will re-introduce basic HTML rather than blended XHTML.</description>
		<content:encoded><![CDATA[<p>Yah, hehe.  It&#8217;ll be very interesting to see how B vs STRONG and I vs EM will turn out.  Well, overall it is good <acronym title="World Wide Web Consortium">W3C</acronym> will re-introduce basic <acronym title="HyperText Markup Language">HTML</acronym> rather than blended <acronym title="eXtensible HyperText Markup Language">XHTML</acronym>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ia</title>
		<link>http://stellify.net/html5-b-and-i-tags-are-going-to-be-useful-read-semantic-again/#comment-31672</link>
		<dc:creator>ia</dc:creator>
		<pubDate>Fri, 02 May 2008 06:26:23 +0000</pubDate>
		<guid isPermaLink="false">http://stellify.net/html5-b-and-i-tags-are-going-to-be-useful-read-semantic-again/#comment-31672</guid>
		<description>Of course there can be presentational differences with CSS. But I get your point, which is kind of my point too: if we&#039;ve been using B and I in word processors to denote all those things, including emphasis, why do we need STRONG and EM anyway? But I think the HTML5 descriptions for B and I differentiate themselves enough from STRONG and EM already. It&#039;s now up to the HTML coders if they think it&#039;s too big of an issue to follow it!</description>
		<content:encoded><![CDATA[<p>Of course there can be presentational differences with <acronym title="Cascading Style Sheets">CSS</acronym>. But I get your point, which is kind of my point too: if we&#8217;ve been using B and I in word processors to denote all those things, including emphasis, why do we need STRONG and EM anyway? But I think the HTML5 descriptions for B and I differentiate themselves enough from STRONG and EM already. It&#8217;s now up to the <acronym title="HyperText Markup Language">HTML</acronym> coders if they think it&#8217;s too big of an issue to follow it!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: JC John SESE Cuneta</title>
		<link>http://stellify.net/html5-b-and-i-tags-are-going-to-be-useful-read-semantic-again/#comment-31671</link>
		<dc:creator>JC John SESE Cuneta</dc:creator>
		<pubDate>Fri, 02 May 2008 04:17:09 +0000</pubDate>
		<guid isPermaLink="false">http://stellify.net/html5-b-and-i-tags-are-going-to-be-useful-read-semantic-again/#comment-31671</guid>
		<description>Ah I see it now.  B and I can be used now for almost anything except &#039;emphasis&#039; which is the purpose of STRONG and EM.

If that&#039;s the case, wouldn&#039;t be better if we drop STRONG and EM then?  I mean, it&#039;s not like there&#039;s any presentational difference between B and STRONG; I and EM.  Unlike when compared to INS and DEL.

Unless W3C plans on imposing a presentational difference for B and I similar to INS and DEL.</description>
		<content:encoded><![CDATA[<p>Ah I see it now.  B and I can be used now for almost anything except &#8216;emphasis&#8217; which is the purpose of STRONG and EM.</p>
<p>If that&#8217;s the case, wouldn&#8217;t be better if we drop STRONG and EM then?  I mean, it&#8217;s not like there&#8217;s any presentational difference between B and STRONG; I and EM.  Unlike when compared to INS and DEL.</p>
<p>Unless <acronym title="World Wide Web Consortium">W3C</acronym> plans on imposing a presentational difference for B and I similar to INS and DEL.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ia</title>
		<link>http://stellify.net/html5-b-and-i-tags-are-going-to-be-useful-read-semantic-again/#comment-31658</link>
		<dc:creator>ia</dc:creator>
		<pubDate>Thu, 01 May 2008 15:23:03 +0000</pubDate>
		<guid isPermaLink="false">http://stellify.net/html5-b-and-i-tags-are-going-to-be-useful-read-semantic-again/#comment-31658</guid>
		<description>JC, it never was deprecated. It was just deemed unsemantic. B and I still work, and they don&#039;t cause invalid HTML documents. But as I have mentioned, in HTML5 it will have new recommended uses which help support the idea that they can be semantic elements too. To avoid creating new elements, too, I&#039;m sure. We don&#039;t really need new elements that address what can be done using typographic conventions. Which is what the new uses of B and I basically are.</description>
		<content:encoded><![CDATA[<p>JC, it never was deprecated. It was just deemed unsemantic. B and I still work, and they don&#8217;t cause invalid <acronym title="HyperText Markup Language">HTML</acronym> documents. But as I have mentioned, in HTML5 it will have new recommended uses which help support the idea that they can be semantic elements too. To avoid creating new elements, too, I&#8217;m sure. We don&#8217;t really need new elements that address what can be done using typographic conventions. Which is what the new uses of B and I basically are.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rico S.</title>
		<link>http://stellify.net/html5-b-and-i-tags-are-going-to-be-useful-read-semantic-again/#comment-30482</link>
		<dc:creator>Rico S.</dc:creator>
		<pubDate>Sun, 23 Mar 2008 02:25:08 +0000</pubDate>
		<guid isPermaLink="false">http://stellify.net/html5-b-and-i-tags-are-going-to-be-useful-read-semantic-again/#comment-30482</guid>
		<description>@ia, I agree, and my position in the issue is to just go and use B and I anyway. For instance, if I just have to italicize something (like a part of a mailing address? I can&#039;t think of an example now), and not give it &quot;emphasis&quot; from a block of text as EM suggests, I don&#039;t mind adding in an I tag.</description>
		<content:encoded><![CDATA[<p>@ia, I agree, and my position in the issue is to just go and use B and I anyway. For instance, if I just have to italicize something (like a part of a mailing address? I can&#8217;t think of an example now), and not give it &#8220;emphasis&#8221; from a block of text as EM suggests, I don&#8217;t mind adding in an I tag.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ia</title>
		<link>http://stellify.net/html5-b-and-i-tags-are-going-to-be-useful-read-semantic-again/#comment-30481</link>
		<dc:creator>ia</dc:creator>
		<pubDate>Sun, 23 Mar 2008 02:19:11 +0000</pubDate>
		<guid isPermaLink="false">http://stellify.net/html5-b-and-i-tags-are-going-to-be-useful-read-semantic-again/#comment-30481</guid>
		<description>In the case of HTML/CSS, it&#039;s meaningful as opposed to merely presentational, which bold and italic tags are. However, that becomes a problem with writing conventions that are dependent  on the likes of bold and italic to actually provide meaning. So that&#039;s the dilemma right there. Do you use or create a different element just to provide meaning and avoid presentational markup, or compromise?</description>
		<content:encoded><![CDATA[<p>In the case of <acronym title="HyperText Markup Language">HTML</acronym>/<acronym title="Cascading Style Sheets">CSS</acronym>, it&#8217;s meaningful as opposed to merely presentational, which bold and italic tags are. However, that becomes a problem with writing conventions that are dependent  on the likes of bold and italic to actually provide meaning. So that&#8217;s the dilemma right there. Do you use or create a different element just to provide meaning and avoid presentational markup, or compromise?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rico S.</title>
		<link>http://stellify.net/html5-b-and-i-tags-are-going-to-be-useful-read-semantic-again/#comment-30480</link>
		<dc:creator>Rico S.</dc:creator>
		<pubDate>Sun, 23 Mar 2008 02:14:51 +0000</pubDate>
		<guid isPermaLink="false">http://stellify.net/html5-b-and-i-tags-are-going-to-be-useful-read-semantic-again/#comment-30480</guid>
		<description>I never really fully subscribed to the B-and-I-are-not-semantic school of thought. What makes B less meaningful that STRONG anyway? (Bonus: even if you look up &#039;bold&#039; and &#039;strong&#039; in the dictionary they&#039;re pretty much the same.)</description>
		<content:encoded><![CDATA[<p>I never really fully subscribed to the B-and-I-are-not-semantic school of thought. What makes B less meaningful that STRONG anyway? (Bonus: even if you look up &#8216;bold&#8217; and &#8216;strong&#8217; in the dictionary they&#8217;re pretty much the same.)</p>
]]></content:encoded>
	</item>
</channel>
</rss>

