<?xml version="1.0" encoding="utf-8"?>
<feed xml:lang="en-us" xmlns="http://www.w3.org/2005/Atom"><title>Simon Willison's Weblog: gordonluk</title><link href="http://simonwillison.net/" rel="alternate"/><link href="http://simonwillison.net/tags/gordonluk.atom" rel="self"/><id>http://simonwillison.net/</id><updated>2009-02-05T22:46:36+00:00</updated><author><name>Simon Willison</name></author><entry><title>Quoting Gordon Luk</title><link href="https://simonwillison.net/2009/Feb/5/microformats/#atom-tag" rel="alternate"/><published>2009-02-05T22:46:36+00:00</published><updated>2009-02-05T22:46:36+00:00</updated><id>https://simonwillison.net/2009/Feb/5/microformats/#atom-tag</id><summary type="html">
    &lt;blockquote cite="http://getluky.net/2009/01/08/a-warning-about-the-real-cost-of-microformats/"&gt;&lt;p&gt;Much like an oral agreement, publishing microformats is an informal agreement between you and (hopefully) a developer community that sets up a relationship with plenty of vagueness, inertial resistance to change, and potential landmines to step on. Would you create a real developer API without a TOS, agreement, or at the very least, guidelines? [...] are you prepared to announce all frontend markup changes? Does publishing a microformat without a special agreement mean that you are implicitly allowing comprehensive scraping of your web data?&lt;/p&gt;&lt;/blockquote&gt;
&lt;p class="cite"&gt;&amp;mdash; &lt;a href="http://getluky.net/2009/01/08/a-warning-about-the-real-cost-of-microformats/"&gt;Gordon Luk&lt;/a&gt;&lt;/p&gt;

    &lt;p&gt;Tags: &lt;a href="https://simonwillison.net/tags/apis"&gt;apis&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/gordonluk"&gt;gordonluk&lt;/a&gt;, &lt;a href="https://simonwillison.net/tags/microformats"&gt;microformats&lt;/a&gt;&lt;/p&gt;



</summary><category term="apis"/><category term="gordonluk"/><category term="microformats"/></entry></feed>