Re: 'about' and 'describes' appear to have significant overlap

Erik Wilde <> Mon, 29 October 2018 07:55 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id BA78B130DC2 for <>; Mon, 29 Oct 2018 00:55:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.7
X-Spam-Status: No, score=-1.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: (amavisd-new); dkim=neutral reason="invalid (public key: not available)"
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id hSC2anu93Ajz for <>; Mon, 29 Oct 2018 00:55:58 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id E7E3312D4EC for <>; Mon, 29 Oct 2018 00:55:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed;; s=default; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:MIME-Version :Date:Message-ID:From:References:To:Subject:Sender:Reply-To:Cc:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=00ky6KNBGcMJL6KWxB1yWQSZMDlYq6Uu7wClec4G3qc=; b=zSsdQTe8spmICSBH1fLDBGQUSc KZSuaCTZ8OnJKI4PvHZKD71qWHYmS/bScd74gACXMAB6iQ+z7rXiK2pgxKfxUgAbP2d66esHTseLE zUu8ZtvqAeULaNaGAr2zImh8gEdLDnud3rfkG918RfFaJ295EnNTOTNYE30q0HZsaTC55A02Ju/Ol xRnPsfkEXJL3Xe2+faK340+9eGwh4BUq4cVCIlwQT1rl4Y8MjBWFmh64l+FwNYwbXErDVJuFU1X+G R2XvwC5QA9ErnK51a7OXNkuM6wTVyhjxF35CxWAmCioo3TdW9K6RWIuJP1Va4TJujioJh8ytpT3PU mvZ1md5g==;
Received: from [] (port=47493 helo=dretbook.local) by with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.91) (envelope-from <>) id 1gH2Oy-0004AG-9s; Mon, 29 Oct 2018 03:55:56 -0400
Subject: Re: 'about' and 'describes' appear to have significant overlap
References: <>
From: Erik Wilde <>
Message-ID: <>
Date: Mon, 29 Oct 2018 07:55:55 +0000
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname -
X-AntiAbuse: Original Domain -
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain -
X-Get-Message-Sender-Via: authenticated_id:
Archived-At: <>
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 29 Oct 2018 07:56:00 -0000

hello simon.

On 2018-10-28 23:59, wrote:
> The relations 'about' and 'describes' appear to have significant overlap.
> I’ve looked at both RFCs but neither mentions the other.
> Is there a succinct explanation of the difference?

like many link relations, 'about' and 'describes' are fuzzy in their 
scope and definition. 'describes' in particular is probably so generic 
that you can use it for pretty much anything. i would find it surprising 
if there was any possible succinct explanation of the difference.

personally, i think that link relations almost always depend on the 
context they're used in. in one API you might find something exposed as 
'about' links, which in a different API is exposed as 'describes' links. 
you have to know the context (the APIs) to understand what they expose, 
and how they do it.



erik wilde | |
            |    |
            |    |