<story><title>A new Curl logo</title><url>https://daniel.haxx.se/blog/2016/05/27/a-new-curl-logo/</url></story><parent_chain><item><author>efaref</author><text>For something that claims to &amp;quot;grok&amp;quot; URLs, using &amp;quot;:&amp;#x2F;&amp;#x2F;&amp;quot; as part of the logo seems to be misunderstanding how URLs (are supposed to) work.&lt;p&gt;According to RFC3986, URIs (the proper name; URLs are a kind of URI) are correctly of the form:&lt;p&gt;&lt;pre&gt;&lt;code&gt;    &amp;lt;scheme&amp;gt;:&amp;lt;scheme-specific-part&amp;gt;
&lt;/code&gt;&lt;/pre&gt;
For &lt;i&gt;some&lt;/i&gt; schemes, the &amp;lt;scheme-specific-part&amp;gt; may contain a &amp;lt;hierarchical-part&amp;gt;, the format for which is:&lt;p&gt;&lt;pre&gt;&lt;code&gt;    &amp;#x2F;&amp;#x2F;&amp;lt;authority&amp;gt;[&amp;#x2F;&amp;lt;path&amp;gt;] | &amp;lt;path&amp;gt;
&lt;/code&gt;&lt;/pre&gt;
So it&amp;#x27;s only hierarchical URIs with a defined authority that have the (admittedly iconic) &amp;quot;:&amp;#x2F;&amp;#x2F;&amp;quot; in them.&lt;p&gt;I know most people identity URIs as having that sequence in them, but these are all valid URIs:&lt;p&gt;&lt;pre&gt;&lt;code&gt;    mailto:bob@example.com
    sip:bob@example.com
    tel:+18005550123
    file:&amp;#x2F;path&amp;#x2F;to&amp;#x2F;file
&lt;/code&gt;&lt;/pre&gt;
I&amp;#x27;m not saying I expect everyone to understand these subtleties, but people who claim to grok URLs ought to.</text></item></parent_chain><comment><author>jcater</author><text>In the article:&lt;p&gt;&amp;quot;I also suggested we’d try to work with :&amp;#x2F;&amp;#x2F; (colon slash slash) somehow as a symbol, since after all the :&amp;#x2F;&amp;#x2F; letter sequence is commonly used in all the URL formats that curl supports. And it is sort of a global symbol for URLs when you start to think about it. Made sense to me.&amp;quot;&lt;p&gt;They seem to grok it perfectly well, but recognize the modern association people have with :&amp;#x2F;&amp;#x2F; and urls.</text></comment>
<story><title>A new Curl logo</title><url>https://daniel.haxx.se/blog/2016/05/27/a-new-curl-logo/</url></story><parent_chain><item><author>efaref</author><text>For something that claims to &amp;quot;grok&amp;quot; URLs, using &amp;quot;:&amp;#x2F;&amp;#x2F;&amp;quot; as part of the logo seems to be misunderstanding how URLs (are supposed to) work.&lt;p&gt;According to RFC3986, URIs (the proper name; URLs are a kind of URI) are correctly of the form:&lt;p&gt;&lt;pre&gt;&lt;code&gt;    &amp;lt;scheme&amp;gt;:&amp;lt;scheme-specific-part&amp;gt;
&lt;/code&gt;&lt;/pre&gt;
For &lt;i&gt;some&lt;/i&gt; schemes, the &amp;lt;scheme-specific-part&amp;gt; may contain a &amp;lt;hierarchical-part&amp;gt;, the format for which is:&lt;p&gt;&lt;pre&gt;&lt;code&gt;    &amp;#x2F;&amp;#x2F;&amp;lt;authority&amp;gt;[&amp;#x2F;&amp;lt;path&amp;gt;] | &amp;lt;path&amp;gt;
&lt;/code&gt;&lt;/pre&gt;
So it&amp;#x27;s only hierarchical URIs with a defined authority that have the (admittedly iconic) &amp;quot;:&amp;#x2F;&amp;#x2F;&amp;quot; in them.&lt;p&gt;I know most people identity URIs as having that sequence in them, but these are all valid URIs:&lt;p&gt;&lt;pre&gt;&lt;code&gt;    mailto:bob@example.com
    sip:bob@example.com
    tel:+18005550123
    file:&amp;#x2F;path&amp;#x2F;to&amp;#x2F;file
&lt;/code&gt;&lt;/pre&gt;
I&amp;#x27;m not saying I expect everyone to understand these subtleties, but people who claim to grok URLs ought to.</text></item></parent_chain><comment><author>dbalan</author><text>This might shed some light - Curl Developer on URLs&lt;p&gt;&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;webcache.googleusercontent.com&amp;#x2F;search?q=cache:hGPFWPPOv-8J:https:&amp;#x2F;&amp;#x2F;daniel.haxx.se&amp;#x2F;blog&amp;#x2F;2016&amp;#x2F;05&amp;#x2F;11&amp;#x2F;my-url-isnt-your-url&amp;#x2F;+&amp;amp;cd=2&amp;amp;hl=en&amp;amp;ct=clnk&amp;amp;gl=in&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;webcache.googleusercontent.com&amp;#x2F;search?q=cache:hGPFWP...&lt;/a&gt;</text></comment>