[ietf-types] Best practice for new MIME type: application/frame-ld+json

"Markus Lanthaler" <markus.lanthaler@gmx.net> Fri, 20 January 2012 06:09 UTC

Return-Path: <markus.lanthaler@gmx.net>
X-Original-To: ietf-types@ietfa.amsl.com
Delivered-To: ietf-types@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9AF9721F8603 for <ietf-types@ietfa.amsl.com>; Thu, 19 Jan 2012 22:09:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.15
X-Spam-Level:
X-Spam-Status: No, score=-5.15 tagged_above=-999 required=5 tests=[AWL=-4.000, BAYES_00=-2.599, MSGID_MULTIPLE_AT=1.449]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id LQVVwgf+XUc6 for <ietf-types@ietfa.amsl.com>; Thu, 19 Jan 2012 22:09:41 -0800 (PST)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by ietfa.amsl.com (Postfix) with SMTP id A327521F85FD for <ietf-types@ietf.org>; Thu, 19 Jan 2012 22:09:40 -0800 (PST)
Received: (qmail invoked by alias); 20 Jan 2012 06:09:37 -0000
Received: from d175-38-188-181.per801.wa.optusnet.com.au (EHLO Vostro3500) [175.38.188.181] by mail.gmx.net (mp024) with SMTP; 20 Jan 2012 07:09:37 +0100
X-Authenticated: #419883
X-Provags-ID: V01U2FsdGVkX1+WXNxbNASW9GxRC054ICRI38qgZ89X42W44ACDAe 81rlJ6CaJe+87l
From: Markus Lanthaler <markus.lanthaler@gmx.net>
To: ietf-types@ietf.org
Date: Fri, 20 Jan 2012 14:09:32 +0800
Message-ID: <00c101ccd73a$16370000$42a50000$@lanthaler>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AczXOhNqpn6gONsnQ0q9tee1tGs6Nw==
Content-Language: de
X-Y-GMX-Trusted: 0
Subject: [ietf-types] Best practice for new MIME type: application/frame-ld+json
X-BeenThere: ietf-types@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Media \(MIME\) type review" <ietf-types.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-types>, <mailto:ietf-types-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-types>
List-Post: <mailto:ietf-types@ietf.org>
List-Help: <mailto:ietf-types-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-types>, <mailto:ietf-types-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Jan 2012 06:15:07 -0000

Hello,

We are currently working on an effort to standardize a way to describe
linked data in JSON. Consequently we plan to register a media type
application/ld+json (ld stands for linked data). We now came across the need
for another media type to label framing documents, i.e., again a JSON
document but with a completely different structure than a JSON-LD document.
The media type we came up with so far was application/frame-ld+json but some
people argued that we should follow this "+" pattern and call it
application/frame+ld+json instead.

>From talking with people from the HTTP WG this seems to be discouraged ([1],
[2]). Bjoern Hoehrmann suggested to go with application/ld-frame+json as
that "would be more in keeping with the terminology" and suggested to take
the discussion over to this mailing list. I would love to hear you opinion
on this.


[1] http://lists.w3.org/Archives/Public/ietf-http-wg/2012JanMar/0088.html
[2] http://lists.w3.org/Archives/Public/ietf-http-wg/2012JanMar/0089.html


Thanks,
Markus