<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Semantic Markup on Kind of Idea</title>
    <link>https://kindofidea.com/tags/semantic-markup/</link>
    <description>Recent content in Semantic Markup on Kind of Idea</description>
    <generator>Hugo</generator>
    <language>en-US</language>
    <lastBuildDate>Thu, 28 May 2009 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://kindofidea.com/tags/semantic-markup/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Tables on the Web Should Be Super Lean!</title>
      <link>https://kindofidea.com/tables-on-the-web-should-be-super-lean/</link>
      <pubDate>Thu, 28 May 2009 00:00:00 +0000</pubDate>
      <guid>https://kindofidea.com/tables-on-the-web-should-be-super-lean/</guid>
      <description>&lt;p&gt;I know! The days of nested tables for creating layouts are long gone. Thank goodness! But we also need to be careful with the tabular information we publish on the web, whether it&amp;rsquo;s database queries, data stored in spreadsheets, or a simple table an office secretary created in a word processor (BrOffice or Word).&lt;/p&gt;&#xA;&lt;p&gt;Here&amp;rsquo;s a scenario: you&amp;rsquo;ve just received a spreadsheet (Excel or Calc) with the table below, and you need to put it on a web page as quickly as possible. The following fictional image shows an event schedule in the form of a monthly calendar table.&#xA;&lt;img class=&#34;alignnone&#34; title=&#34;Excel spreadsheet&#34; src=&#34;http://i716.photobucket.com/albums/ww163/valeriofarias/parte01tabelaemplanilha.jpg&#34; alt=&#34;&#34; width=&#34;726&#34; height=&#34;269&#34; /&gt;&#xA;Since it needs to be published immediately, your first thought is to use Excel&amp;rsquo;s Save as HTML option. That&amp;rsquo;s very inappropriate, though, because it generates a file with an absurd 311 lines of code. If we look at the code, we&amp;rsquo;ll see that most of it is unnecessary. In part two of this post, we&amp;rsquo;ll see how to eliminate all that unnecessary code with as little effort as possible.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Web Standards and the Importance of Semantic Markup</title>
      <link>https://kindofidea.com/web-standards-and-the-importance-of-semantic-markup/</link>
      <pubDate>Fri, 23 Nov 2007 00:00:00 +0000</pubDate>
      <guid>https://kindofidea.com/web-standards-and-the-importance-of-semantic-markup/</guid>
      <description>&lt;p&gt;In this first post about web standards, I’d like to discuss a topic that may seem &lt;a href=&#34;http://www.tableless.com.br/a-semantica-e-que-manda&#34;&gt;overdone&lt;/a&gt; and has been &lt;a href=&#34;http://revolucao.etc.br/archives/validacao-e-semantica/&#34;&gt;discussed extensively&lt;/a&gt;. Unfortunately, &lt;a href=&#34;http://www.tableless.com.br/desenvolvedor-retrogrado&#34;&gt;some developers&lt;/a&gt; do not follow the principles, perhaps out of convenience or lack of knowledge. So I will try to help at least some of them see the light.&lt;/p&gt;&#xA;&lt;p&gt;I’ll start with two basic concepts, according to &lt;a href=&#34;http://www.zeldman.com/&#34;&gt;Jeffrey Zeldman&lt;/a&gt;:&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;&#xA;&lt;p&gt;&lt;strong&gt;Valid Markup:&lt;/strong&gt; markup that contains no errors (for example, forgetting to close tags) and no illegal tags or attributes (for example, using the &lt;code&gt;height&lt;/code&gt; attribute on tables, which is not allowed).&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
