<?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: Semantic Markup</title>
	<atom:link href="http://ifacethoughts.net/2006/10/18/semantic-markup/feed/" rel="self" type="application/rss+xml" />
	<link>http://ifacethoughts.net/2006/10/18/semantic-markup/</link>
	<description>Thoughts on software development and related, by Abhijit Nadgouda</description>
	<lastBuildDate>Sun, 21 Mar 2010 09:59:15 -0600</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Using Markup To Communicate &#124; iface thoughts</title>
		<link>http://ifacethoughts.net/2006/10/18/semantic-markup/comment-page-1/#comment-102066</link>
		<dc:creator>Using Markup To Communicate &#124; iface thoughts</dc:creator>
		<pubDate>Sat, 15 Sep 2007 07:13:51 +0000</pubDate>
		<guid isPermaLink="false">http://ifacethoughts.net/2006/10/18/semantic-markup/#comment-102066</guid>
		<description>[...] advantages of semantic markup are getting popular. I see that more developers are now getting involved in discussions and realize [...]</description>
		<content:encoded><![CDATA[<p>[...] advantages of semantic markup are getting popular. I see that more developers are now getting involved in discussions and realize [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Changes For Semantic Markup Here &#124; iface thoughts</title>
		<link>http://ifacethoughts.net/2006/10/18/semantic-markup/comment-page-1/#comment-47589</link>
		<dc:creator>Changes For Semantic Markup Here &#124; iface thoughts</dc:creator>
		<pubDate>Wed, 02 May 2007 03:19:07 +0000</pubDate>
		<guid isPermaLink="false">http://ifacethoughts.net/2006/10/18/semantic-markup/#comment-47589</guid>
		<description>[...] Chris Pearson has written an excellent guide to semantic markup for blogs. It is a collection of excellent tips for blogs on arriving at the semantic stage. [...]</description>
		<content:encoded><![CDATA[<p>[...] Chris Pearson has written an excellent guide to semantic markup for blogs. It is a collection of excellent tips for blogs on arriving at the semantic stage. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Towards Better Markup on iface thoughts</title>
		<link>http://ifacethoughts.net/2006/10/18/semantic-markup/comment-page-1/#comment-37026</link>
		<dc:creator>Towards Better Markup on iface thoughts</dc:creator>
		<pubDate>Fri, 13 Apr 2007 03:32:08 +0000</pubDate>
		<guid isPermaLink="false">http://ifacethoughts.net/2006/10/18/semantic-markup/#comment-37026</guid>
		<description>[...] additional tip that has helped me is to create a semantic markup. Of course, its benefits are not unknown, however I find it useful for even communication between project members. The markup can be [...]</description>
		<content:encoded><![CDATA[<p>[...] additional tip that has helped me is to create a semantic markup. Of course, its benefits are not unknown, however I find it useful for even communication between project members. The markup can be [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Is HTML 5 More Semantic? on iface thoughts</title>
		<link>http://ifacethoughts.net/2006/10/18/semantic-markup/comment-page-1/#comment-6104</link>
		<dc:creator>Is HTML 5 More Semantic? on iface thoughts</dc:creator>
		<pubDate>Sat, 13 Jan 2007 12:34:01 +0000</pubDate>
		<guid isPermaLink="false">http://ifacethoughts.net/2006/10/18/semantic-markup/#comment-6104</guid>
		<description>[...] This is very interesting, it seems HTML 5 is acknowledging the Semantic Web, which was done using the divs. I think eventually usage of div will reduce, I am not sure if it can be completely eliminated. This can strong impact choosing HTML or XHTML for your web site. I am not sure if these elements will be built into the XHTML versions too. If not would HTML 5 be considered more semantic? I wonder if these things will be addressed in the specification being worked upon. [...]</description>
		<content:encoded><![CDATA[<p>[...] This is very interesting, it seems HTML 5 is acknowledging the Semantic Web, which was done using the divs. I think eventually usage of div will reduce, I am not sure if it can be completely eliminated. This can strong impact choosing HTML or XHTML for your web site. I am not sure if these elements will be built into the XHTML versions too. If not would HTML 5 be considered more semantic? I wonder if these things will be addressed in the specification being worked upon. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Firefox 3 To Understand on iface thoughts</title>
		<link>http://ifacethoughts.net/2006/10/18/semantic-markup/comment-page-1/#comment-4734</link>
		<dc:creator>Firefox 3 To Understand on iface thoughts</dc:creator>
		<pubDate>Wed, 03 Jan 2007 05:41:03 +0000</pubDate>
		<guid isPermaLink="false">http://ifacethoughts.net/2006/10/18/semantic-markup/#comment-4734</guid>
		<description>[...] Alex Faaborg illustrates one of the best uses of the Semantic Web. Mozilla Firefox 3 might identify of microformats and associating them with specific applications. As an example, how about if you can export a contact from the HTML page to an application. It can identify a vcard or hResume and associate it with your contacts manager. [...]</description>
		<content:encoded><![CDATA[<p>[...] Alex Faaborg illustrates one of the best uses of the Semantic Web. Mozilla Firefox 3 might identify of microformats and associating them with specific applications. As an example, how about if you can export a contact from the HTML page to an application. It can identify a vcard or hResume and associate it with your contacts manager. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: WYSIWYM on iface thoughts</title>
		<link>http://ifacethoughts.net/2006/10/18/semantic-markup/comment-page-1/#comment-2282</link>
		<dc:creator>WYSIWYM on iface thoughts</dc:creator>
		<pubDate>Wed, 06 Dec 2006 04:42:43 +0000</pubDate>
		<guid isPermaLink="false">http://ifacethoughts.net/2006/10/18/semantic-markup/#comment-2282</guid>
		<description>[...] I am sure a lot of you are aware of WYSIWYG. Most of the editors where you can select the font, the style and the colors are WYSIWYG editors, where the underlying markup is hidden under these GUI controls for formatting. I got introduced to What You See Is What You Mean (WYSIWYM) through Peter Krantz. The difference can be expressed in one word - semantics - but makes a world of difference! [...]</description>
		<content:encoded><![CDATA[<p>[...] I am sure a lot of you are aware of WYSIWYG. Most of the editors where you can select the font, the style and the colors are WYSIWYG editors, where the underlying markup is hidden under these GUI controls for formatting. I got introduced to What You See Is What You Mean (WYSIWYM) through Peter Krantz. The difference can be expressed in one word &#8211; semantics &#8211; but makes a world of difference! [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: First Markup Then Style on iface thoughts</title>
		<link>http://ifacethoughts.net/2006/10/18/semantic-markup/comment-page-1/#comment-1986</link>
		<dc:creator>First Markup Then Style on iface thoughts</dc:creator>
		<pubDate>Sun, 26 Nov 2006 05:05:33 +0000</pubDate>
		<guid isPermaLink="false">http://ifacethoughts.net/2006/10/18/semantic-markup/#comment-1986</guid>
		<description>[...] I always insist of developing the markup, in fact semantic markup, before it is styled. The basic reason is that content is still the king and the markup structures the content. Markup is what the search engines see. It is important enough to design it separately without thinking about how it looks. Then implement the layout using CSS. Then apply styles. This also helps in physically separating the three aspects - markup, layout and style. Do no change the markup to ever define how it looks. If you want a visual representation, check out a design lifecycle as it should be. [...]</description>
		<content:encoded><![CDATA[<p>[...] I always insist of developing the markup, in fact semantic markup, before it is styled. The basic reason is that content is still the king and the markup structures the content. Markup is what the search engines see. It is important enough to design it separately without thinking about how it looks. Then implement the layout using CSS. Then apply styles. This also helps in physically separating the three aspects &#8211; markup, layout and style. Do no change the markup to ever define how it looks. If you want a visual representation, check out a design lifecycle as it should be. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Web 3.0 Or How To Kill Simplicity on iface thoughts</title>
		<link>http://ifacethoughts.net/2006/10/18/semantic-markup/comment-page-1/#comment-1669</link>
		<dc:creator>Web 3.0 Or How To Kill Simplicity on iface thoughts</dc:creator>
		<pubDate>Mon, 13 Nov 2006 03:44:37 +0000</pubDate>
		<guid isPermaLink="false">http://ifacethoughts.net/2006/10/18/semantic-markup/#comment-1669</guid>
		<description>[...] Or if it really works well, we should have News 2.0, Radio 2.0, Humanity 2.0, or Life 2.0! I wonder the conversations when version numbers would be flying around. Now Semantic Web is being touted as Web 3.0. Were semantics not stressed on earlier? Is the software community not aware of its benefits? Does Web 3.0 now imply that every website that has to qualify should have semantic markup? [...]</description>
		<content:encoded><![CDATA[<p>[...] Or if it really works well, we should have News 2.0, Radio 2.0, Humanity 2.0, or Life 2.0! I wonder the conversations when version numbers would be flying around. Now Semantic Web is being touted as Web 3.0. Were semantics not stressed on earlier? Is the software community not aware of its benefits? Does Web 3.0 now imply that every website that has to qualify should have semantic markup? [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: XHTML/CSS - You do the design, we do the code.</title>
		<link>http://ifacethoughts.net/2006/10/18/semantic-markup/comment-page-1/#comment-891</link>
		<dc:creator>XHTML/CSS - You do the design, we do the code.</dc:creator>
		<pubDate>Thu, 19 Oct 2006 17:24:23 +0000</pubDate>
		<guid isPermaLink="false">http://ifacethoughts.net/2006/10/18/semantic-markup/#comment-891</guid>
		<description>[...] Semantic Markup [...]</description>
		<content:encoded><![CDATA[<p>[...] Semantic Markup [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: iface thoughts &#187; Blog Archive &#187; In fadtastic</title>
		<link>http://ifacethoughts.net/2006/10/18/semantic-markup/comment-page-1/#comment-888</link>
		<dc:creator>iface thoughts &#187; Blog Archive &#187; In fadtastic</dc:creator>
		<pubDate>Thu, 19 Oct 2006 12:35:39 +0000</pubDate>
		<guid isPermaLink="false">http://ifacethoughts.net/2006/10/18/semantic-markup/#comment-888</guid>
		<description>[...] My third article on Semantic HTML in fadtastic.net is up. It is a kind of follow up to my article on the generic Semantic Markup. [...]</description>
		<content:encoded><![CDATA[<p>[...] My third article on Semantic HTML in fadtastic.net is up. It is a kind of follow up to my article on the generic Semantic Markup. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
