Use of describedby link relation
"Markus Lanthaler" <markus.lanthaler@gmx.net> Thu, 15 November 2012 12:59 UTC
Return-Path: <markus.lanthaler@gmx.net>
X-Original-To: link-relations@ietfa.amsl.com
Delivered-To: link-relations@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E1A7D21F88D9 for <link-relations@ietfa.amsl.com>; Thu, 15 Nov 2012 04:59:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.264
X-Spam-Level: *
X-Spam-Status: No, score=1.264 tagged_above=-999 required=5 tests=[BAYES_40=-0.185, MSGID_MULTIPLE_AT=1.449]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id FtmkfL7NDAnr for <link-relations@ietfa.amsl.com>; Thu, 15 Nov 2012 04:59:47 -0800 (PST)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by ietfa.amsl.com (Postfix) with SMTP id D56FD21F88D4 for <link-relations@ietf.org>; Thu, 15 Nov 2012 04:59:46 -0800 (PST)
Received: (qmail invoked by alias); 15 Nov 2012 12:58:43 -0000
Received: from unknown (EHLO Vostro3500) [84.115.182.43] by mail.gmx.net (mp069) with SMTP; 15 Nov 2012 13:58:43 +0100
X-Authenticated: #419883
X-Provags-ID: V01U2FsdGVkX1+4cbE+/rC4Edh2un6b+z/JjMH4HlSm+fNjLeHDie TdKJTdWZMsiDxb
From: Markus Lanthaler <markus.lanthaler@gmx.net>
To: link-relations@ietf.org
Subject: Use of describedby link relation
Date: Thu, 15 Nov 2012 13:58:26 +0100
Message-ID: <010001cdc330$e75a1720$b60e4560$@lanthaler>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Content-Language: de
Thread-Index: Ac3DMOasmSzqsMCeTE2qwnU85+AuBQ==
X-Y-GMX-Trusted: 0
X-BeenThere: link-relations@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <link-relations.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/link-relations>, <mailto:link-relations-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/link-relations>
List-Post: <mailto:link-relations@ietf.org>
List-Help: <mailto:link-relations-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/link-relations>, <mailto:link-relations-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Nov 2012 12:59:48 -0000
Hi, I have a question regarding the use of the describedby link relation. In JSON-LD [1] we have something that we call a "context". Its purpose is mainly to map terms to IRIs to allow their unambiguous identification. In a JSON-LD document that context is stored in a "@context" property like so: { "@context": { "name": "http://example.com/name" }, "name": "Markus Lanthaler" } To allow developers to build on existing infrastructure, i.e., keep their JSON documents unchanged but nevertheless allow them to link to such a "context" we use a HTTP link header with the relation type "descibedby" [2]: Link: <http://json-ld.org/contexts/person.jsonld>; rel="describedby"; type="application/ld+json" We now got some complaints [3] that we are abusing "describedby" since a) we are not linking to POWDER documents, and b) the way we use it doesn't match the semantics of that link relation. I would appreciate your opinion on that. Do you think we should mint a new link relation or is it a sensible decision to use "describedby" for this!? Thank you very much, Markus [1] http://json-ld.org/ [2] http://json-ld.org/spec/latest/json-ld-syntax/#referencing-contexts-from-jso n-documents [3] https://github.com/json-ld/json-ld.org/issues/197 -- Markus Lanthaler @markuslanthaler
- Use of describedby link relation Markus Lanthaler
- Re: Use of describedby link relation Mark Nottingham
- RE: Use of describedby link relation Markus Lanthaler