<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en-us" xmlns="http://www.w3.org/2005/Atom"><title>Simon Willison's Weblog: tantek-celik</title><link href="http://simonwillison.net/" rel="alternate"/><link href="http://simonwillison.net/tags/tantek-celik.atom" rel="self"/><id>http://simonwillison.net/</id><updated>2010-10-09T10:47:00+00:00</updated><author><name>Simon Willison</name></author><entry><title>What is the Open Web?</title><link href="https://simonwillison.net/2010/Oct/9/tantek/#atom-tag" rel="alternate"/><published>2010-10-09T10:47:00+00:00</published><updated>2010-10-09T10:47:00+00:00</updated><id>https://simonwillison.net/2010/Oct/9/tantek/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="http://tantek.com/2010/281/b1/what-is-the-open-web"&gt;What is the Open Web?&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
Tantek Çelik describes the three pillars of the open web: open publishing of content, freedom to code and implement the standards needed to access that content and open access to that content over an unfiltered internet.


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/openweb"&gt;openweb&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/tantek-celik"&gt;tantek-celik&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/recovered"&gt;recovered&lt;/a&gt;&lt;/p&gt;



</summary><category term="openweb"/><category term="tantek-celik"/><category term="recovered"/></entry><entry><title>Principles of visibility and human friendliness</title><link href="https://simonwillison.net/2005/Jun/4/principles/#atom-tag" rel="alternate"/><published>2005-06-04T20:20:05+00:00</published><updated>2005-06-04T20:20:05+00:00</updated><id>https://simonwillison.net/2005/Jun/4/principles/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="http://tantek.com/log/2005/06.html#d03t2359"&gt;Principles of visibility and human friendliness&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
Tantek makes an excellent argument that visible metadata works better than invisible metadata.


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/tantek-celik"&gt;tantek-celik&lt;/a&gt;&lt;/p&gt;



</summary><category term="tantek-celik"/></entry><entry><title>Subject: Moving on...; To: co-workers</title><link href="https://simonwillison.net/2004/Jul/1/subject/#atom-tag" rel="alternate"/><published>2004-07-01T19:30:43+00:00</published><updated>2004-07-01T19:30:43+00:00</updated><id>https://simonwillison.net/2004/Jul/1/subject/#atom-tag</id><summary type="html">
    
&lt;p&gt;&lt;strong&gt;&lt;a href="http://tantek.com/log/2004/06.html#d29t1850"&gt;Subject: Moving on...; To: co-workers&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;
Tantek on quitting Microsoft, and the highlights of his MS career.


    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/tantek-celik"&gt;tantek-celik&lt;/a&gt;&lt;/p&gt;



</summary><category term="tantek-celik"/></entry><entry><title>Tantek's Fridge</title><link href="https://simonwillison.net/2004/Jun/23/fridge/#atom-tag" rel="alternate"/><published>2004-06-23T09:33:31+00:00</published><updated>2004-06-23T09:33:31+00:00</updated><id>https://simonwillison.net/2004/Jun/23/fridge/#atom-tag</id><summary type="html">
    &lt;p&gt;Recently spotted on Tantek's fridge:&lt;/p&gt;

&lt;p&gt;&lt;a href="http://tantek.com/log/2004/06.html#d22t2210"&gt;&lt;img alt="Fridge magnets: &amp;quot;end of the Microsoft ride?&amp;quot;" height="149" src="http://simon.incutio.com/images/2004/tanteks-fridge.jpg" width="400" /&gt;&lt;/a&gt;&lt;/p&gt;
    
        &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/tantek-celik"&gt;tantek-celik&lt;/a&gt;&lt;/p&gt;
    

</summary><category term="tantek-celik"/></entry><entry><title>Targetting CSS at IE5</title><link href="https://simonwillison.net/2003/Oct/6/targetIE5/#atom-tag" rel="alternate"/><published>2003-10-06T23:35:04+00:00</published><updated>2003-10-06T23:35:04+00:00</updated><id>https://simonwillison.net/2003/Oct/6/targetIE5/#atom-tag</id><summary type="html">
    &lt;p&gt;Tantek has created/discovered a new &lt;acronym title="Cascading Style Sheets"&gt;CSS&lt;/acronym&gt; hack, the &lt;a href="http://tantek.com/CSS/Examples/midpass.html"&gt;Mid Pass Filter&lt;/a&gt;. This filter allows you to write &lt;acronym title="Cascading Style Sheets"&gt;CSS&lt;/acronym&gt; rules that will only be applied by &lt;acronym title="Internet Explorer"&gt;IE&lt;/acronym&gt; 5 and &lt;acronym title="Internet Explorer"&gt;IE&lt;/acronym&gt; 5.5 for Windows. This is great news, as those are the browsers with the &lt;a href="/2003/May/26/theBoxModel/" title="Understanding the Box Model"&gt;broken box model&lt;/a&gt; (provided you trigger standards mode in &lt;acronym title="Internet Explorer"&gt;IE&lt;/acronym&gt; 6).&lt;/p&gt;

&lt;p&gt;As with almost all hacks it looks pretty revolting. My recommendation is to accompany all hacks like this used in live stylesheets with a commented link to the page describing the technique.&lt;/p&gt;
    
        &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/css"&gt;css&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/tantek-celik"&gt;tantek-celik&lt;/a&gt;&lt;/p&gt;
    

</summary><category term="css"/><category term="tantek-celik"/></entry><entry><title>Diagonal shapes with CSS</title><link href="https://simonwillison.net/2003/Jul/4/diagonalCSS/#atom-tag" rel="alternate"/><published>2003-07-04T18:03:39+00:00</published><updated>2003-07-04T18:03:39+00:00</updated><id>https://simonwillison.net/2003/Jul/4/diagonalCSS/#atom-tag</id><summary type="html">
    &lt;p&gt;&lt;a href="http://www.infimum.dk/HTML/slantinfo.html"&gt;Information on Border Slants&lt;/a&gt; (via &lt;a href="http://www.paranoidfish.org/links/2003/07/" title="paranoidfish.org/links July 2003"&gt;Paul Hammond&lt;/a&gt;). Border slants are the effect whereby diagonal lines can be created using pure &lt;acronym title="Cascading Style Sheets"&gt;CSS&lt;/acronym&gt;, by taking advantage of the fact that thick borders around a box meet at an angle. This article describes the effect in detail and shows how it can be used to achieve a number of interesting shapes, then goes on to show off with an impressive &lt;a href="http://www.infimum.dk/HTML/heartArt.html?text=Slants"&gt;Valentine's Day Heart&lt;/a&gt;. See also Tantek's awesome &lt;a href="http://www.tantek.com/map.html"&gt;pentagon site map&lt;/a&gt; and &lt;a href="http://www.tantek.com/CSS/Examples/polygons.html"&gt;A Study of Regular Polygons&lt;/a&gt;.&lt;/p&gt;
    
        &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/css"&gt;css&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/tantek-celik"&gt;tantek-celik&lt;/a&gt;&lt;/p&gt;
    

</summary><category term="css"/><category term="tantek-celik"/></entry><entry><title>Introspection</title><link href="https://simonwillison.net/2003/Apr/22/introspection/#atom-tag" rel="alternate"/><published>2003-04-22T19:55:37+00:00</published><updated>2003-04-22T19:55:37+00:00</updated><id>https://simonwillison.net/2003/Apr/22/introspection/#atom-tag</id><summary type="html">
    &lt;p&gt;Tantek: &lt;a href="http://tantek.com/log/2003/04.html#L20030421t1700"&gt;What to do with things to do&lt;/a&gt;:&lt;/p&gt;

&lt;blockquote cite="http://tantek.com/log/2003/04.html#L20030421t1700"&gt;&lt;p&gt;
Some areas of your life you want to expand and grow. Others have been neglected, and you need to work on restoring them. Most things just need to be maintained, and it might help to make a list of all the things that demand maintenance (how much and how frequently) in your life. Some of those things should probably be pruned away. And everyone I know has areas of their lives or unfinished projects that need to be closed off and put/parked away for good.
&lt;/p&gt;&lt;/blockquote&gt;

&lt;p&gt;I can really relate to this. There are definitely things in my life that could do with either closure or pruning (or both). The problem is facing up to them.&lt;/p&gt;

&lt;p&gt;(I think this is the most introspective thing I've ever posted on here).&lt;/p&gt;
    
        &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/tantek-celik"&gt;tantek-celik&lt;/a&gt;&lt;/p&gt;
    

</summary><category term="tantek-celik"/></entry><entry><title>Merging comments and pingbacks</title><link href="https://simonwillison.net/2003/Jan/5/mergingCommentsAndPingbacks/#atom-tag" rel="alternate"/><published>2003-01-05T11:17:27+00:00</published><updated>2003-01-05T11:17:27+00:00</updated><id>https://simonwillison.net/2003/Jan/5/mergingCommentsAndPingbacks/#atom-tag</id><summary type="html">
    &lt;p&gt;&lt;a href="http://tantek.com/log/2003/01.html#L20030104t1249" title="Comment markup, presentation and plumbing"&gt;Tantek&lt;/a&gt;:&lt;/p&gt;

&lt;blockquote cite="http://tantek.com/log/2003/01.html#L20030104t1249"&gt;
&lt;p&gt;[...] we now have Trackback and Pingback to help automate generating comment hyperlinks to blog-on-blog commentary. While I certainly applaud these efforts at automating the plumbing, I must ask - why is there any distinction in the presentation? I ask because many blogs present separate and different interfaces for their comments, trackbacks, and/or pingbacks.&lt;/p&gt;

&lt;p&gt;A comment is a comment is a comment. Why should it matter whether it was posted using a web form, sent via email, entered into a blog, or posted to Netnews? From a blog reader's perspective, I'd just like to see a list of the comments, and not care (nor know) about how the comment got there. Presentation/interface should be designed to present the data (information), not the underlying plumbing.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;Good point (besides, I'm kind of fed up of having a seperate counter for comments and pingbacks under every post). I'm sure I've seen a blog that combines comments, pingbacks and trackbacks in to the same interface - I think it was &lt;a href="http://www.intertwingly.net/blog/"&gt;Sam Ruby's&lt;/a&gt; and I'm sure I've seen it elsewhere as well. Something else to add to the list for the forever forthcoming redesign.&lt;/p&gt;
    
        &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/pingback"&gt;pingback&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/tantek-celik"&gt;tantek-celik&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/trackback"&gt;trackback&lt;/a&gt;&lt;/p&gt;
    

</summary><category term="pingback"/><category term="tantek-celik"/><category term="trackback"/></entry><entry><title>Debugging HTTP headers</title><link href="https://simonwillison.net/2002/Dec/20/debuggingHttpHeaders/#atom-tag" rel="alternate"/><published>2002-12-20T20:37:55+00:00</published><updated>2002-12-20T20:37:55+00:00</updated><id>https://simonwillison.net/2002/Dec/20/debuggingHttpHeaders/#atom-tag</id><summary type="html">
    &lt;p&gt;Tantek has &lt;a href="http://tantek.com/log/2002/12.html#web20021218t0548" title="New HTTP favelets"&gt;released&lt;/a&gt; two new favelets for &lt;a href="http://tantek.com/favelets/#http"&gt;revealing HTTP information&lt;/a&gt;, using Mozilla's ever useful &lt;a href="http://webtools.mozilla.org/web-sniffer/"&gt;Web Sniffer&lt;/a&gt; and Delorie's &lt;a href="http://www.delorie.com/web/headers.html"&gt;HTTP Header Viewer&lt;/a&gt;. I spotted a similar tool on a recent trip to &lt;a href="http://mozdev.org/"&gt;MozDev&lt;/a&gt;: &lt;a href="http://livehttpheaders.mozdev.org/"&gt;LiveHTTPHeaders&lt;/a&gt; adds a "Headers" tab to the page information box in Mozilla 1.2, showing the full request and response headers used for the current page. It's a very nice tool, but unfortunately does not yet work with Phoenix (the headers tab is added to the info box but the header information does not appear).&lt;/p&gt;
    
        &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/tantek-celik"&gt;tantek-celik&lt;/a&gt;&lt;/p&gt;
    

</summary><category term="tantek-celik"/></entry><entry><title>Tantek's markup challenge</title><link href="https://simonwillison.net/2002/Dec/19/tanteksMarkupChallenge/#atom-tag" rel="alternate"/><published>2002-12-19T00:55:04+00:00</published><updated>2002-12-19T00:55:04+00:00</updated><id>https://simonwillison.net/2002/Dec/19/tanteksMarkupChallenge/#atom-tag</id><summary type="html">
    &lt;p&gt;In &lt;a href="http://tantek.com/log/2002/12.html#L20021216t2238"&gt;A Touch of Class&lt;/a&gt;, Tantek continues his series of tips on writing better semantic markup and then issues a challenge: find related improvements that can be made to his blog. I couldn't find anything in the overall structure, but I have a few (admittedly nit-picky) suggestions for his current entries. Firstly, the following line would, in my opinion, be better served with a titled &lt;code&gt;&amp;lt;dfn&amp;gt;&lt;/code&gt; element:&lt;/p&gt;

&lt;blockquote cite="http://tantek.com/log/2002/12.html#web20021217t1931"&gt;&lt;pre&gt;&lt;code&gt;New &amp;lt;strong title="shopping by surfing"&amp;gt;shurfing&amp;lt;/strong&amp;gt; tool.&lt;/code&gt;&lt;/pre&gt;
&lt;/blockquote&gt;

&lt;p&gt;Secondly, Tantek frequently uses a combination of a &lt;code&gt;pre&lt;/code&gt; and a &lt;code&gt;code&lt;/code&gt; tag to mark up sections of example code. This works fine, but could potentially be improved by adding a class element hinting at the type of code being displayed, for example:&lt;/p&gt;

&lt;pre&gt;
&amp;lt;pre&amp;gt;&amp;lt;code class="css"&amp;gt;
p.sidebartext { 
  padding:0 5px 2px;
  font-size:11px; 
  margin-top:2px
}
&amp;lt;/code&amp;gt;&amp;lt;/pre&amp;gt;
&lt;/pre&gt;

&lt;p&gt;Finally, Tantek's use of &lt;code&gt;&amp;lt;a class="local"&amp;gt;&lt;/code&gt; to differentiate local and external links introduces (technically) redundant data - the fact that the link is to a local resource is implicit in its &lt;acronym title="Uniform Resource Locator"&gt;URL&lt;/acronym&gt;. This information can even be extracted using &lt;acronym title="Cascading Style Sheets 3"&gt;CSS3&lt;/acronym&gt; selectors, as is demonstrated by Stuart's ingenous article &lt;a href="http://www.kryogenix.org/days/000233.cas#000233"&gt;External link icons the CSS way&lt;/a&gt;.&lt;/p&gt;
    
        &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/tantek-celik"&gt;tantek-celik&lt;/a&gt;&lt;/p&gt;
    

</summary><category term="tantek-celik"/></entry><entry><title>rel="bookmark"</title><link href="https://simonwillison.net/2002/Nov/29/relEqualsBookmark/#atom-tag" rel="alternate"/><published>2002-11-29T23:57:38+00:00</published><updated>2002-11-29T23:57:38+00:00</updated><id>https://simonwillison.net/2002/Nov/29/relEqualsBookmark/#atom-tag</id><summary type="html">
    &lt;p&gt;Mental note: add the &lt;code&gt;rel="bookmark"&lt;/code&gt; attribute to my permalinks, as &lt;a href="http://tantek.com/log/2002/11.html#L20021124t1454" title="More on XHTML syndication"&gt;recommended&lt;/a&gt; by Tantek. I'd never realised the rel attribute could be applied to normal hyperlinks.&lt;/p&gt;
    
        &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/tantek-celik"&gt;tantek-celik&lt;/a&gt;&lt;/p&gt;
    

</summary><category term="tantek-celik"/></entry><entry><title>Interesting but ultimately useless</title><link href="https://simonwillison.net/2002/Nov/22/interestingButUltimatelyUseles/#atom-tag" rel="alternate"/><published>2002-11-22T22:42:36+00:00</published><updated>2002-11-22T22:42:36+00:00</updated><id>https://simonwillison.net/2002/Nov/22/interestingButUltimatelyUseles/#atom-tag</id><summary type="html">
    &lt;p&gt;Via &lt;a href="http://www.kryogenix.org/days/000369.cas" title="Code and HTML and code, oh my!"&gt;Stuart&lt;/a&gt;, Tantek has an &lt;a href="http://www.tantek.com/log/2002/11.html#L20021121t1730" title="Semantic Scripting"&gt;intriguing&lt;/a&gt; new (valid) hack for adding HTML documentation to an external javascript file. The hack uses some clever multi-language comments to hide the HTML in the file from the script interpreter, while ensuring that the documentation remains readable when the file is interpreted as HTML. Unfortunately the trick does not work in Mozilla, as that browser respects the Content-Type served with the document (whereas &lt;acronym title="Internet Explorer"&gt;IE&lt;/acronym&gt; "guesses" the content is HTML from clues in the document).&lt;/p&gt;
    
        &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/tantek-celik"&gt;tantek-celik&lt;/a&gt;&lt;/p&gt;
    

</summary><category term="tantek-celik"/></entry><entry><title>Impressive CSS</title><link href="https://simonwillison.net/2002/Aug/5/impressiveCSS/#atom-tag" rel="alternate"/><published>2002-08-05T01:42:16+00:00</published><updated>2002-08-05T01:42:16+00:00</updated><id>https://simonwillison.net/2002/Aug/5/impressiveCSS/#atom-tag</id><summary type="html">
    &lt;p&gt;Take a look at &lt;a href="http://www.tantek.com/map.html" title="tantek.com"&gt;this page&lt;/a&gt; in Mozilla, view the source code and ask yourself "how on earth did he do that?". It appears to involve very creative use of borders, possibly relating to the fact that a single border in CSS (at least in Mozilla and presumably in IE5/Mac as well) is actually a trapezium, not a line. Tantek Çelik &lt;em&gt;was&lt;/em&gt; the project lead for &lt;acronym title="Internet Explorer"&gt;IE&lt;/acronym&gt; 5 for the Mac (and the creator of both the &lt;a href="http://www.tantek.com/CSS/Examples/boxmodelhack.html"&gt;Box Model hack&lt;/a&gt; and the &lt;a href="http://www.tantek.com/CSS/Examples/highpass.html"&gt;High Pass Filter&lt;/a&gt;) so general &lt;acronym title="Cascading Style Sheets"&gt;CSS&lt;/acronym&gt; wizardry is to be expected.&lt;/p&gt;
    
        &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/css"&gt;css&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/tantek-celik"&gt;tantek-celik&lt;/a&gt;&lt;/p&gt;
    

</summary><category term="css"/><category term="tantek-celik"/></entry></feed>