IETF Logo Mail Archive

Re: [media-types] Notice for a potential media type registration: application/td+json

Matthias Kovatsch <w3c@kovatsch.net> Fri, 03 May 2019 15:10 UTC

Return-Path: <w3c@kovatsch.net>
X-Original-To: media-types@ietfa.amsl.com
Delivered-To: media-types@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ED801120148 for <media-types@ietfa.amsl.com>; Fri, 3 May 2019 08:10:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_FAIL=0.001] autolearn=no autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SSwu5Z8IzwCu for <media-types@ietfa.amsl.com>; Fri, 3 May 2019 08:10:49 -0700 (PDT)
Received: from pechora6.dc.icann.org (pechora6.icann.org [192.0.46.72]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5DDB8120228 for <media-types@ietf.org>; Fri, 3 May 2019 08:10:32 -0700 (PDT)
Received: from ma04-relay.lansolnet.com (ma04-relay.lansolnet.com [176.95.46.38]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by pechora6.dc.icann.org (Postfix) with ESMTPS id 12D591E05A0 for <media-types@iana.org>; Fri, 3 May 2019 15:10:30 +0000 (UTC)
Received: from unknown ([192.168.8.236]) by ma04-relay.lansolnet.com; Fri, 03 May 2019 17:10:09 +0200
Received: from MBX100D.cloud4partner.com (192.168.8.236) by MBX100D.cloud4partner.com (192.168.8.236) with Microsoft SMTP Server (TLS) id 15.0.1156.6; Fri, 3 May 2019 17:10:08 +0200
Received: from MBX100D.cloud4partner.com ([fe80::1438:a47a:e7b7:aed8]) by MBX100D.cloud4partner.com ([fe80::1438:a47a:e7b7:aed8%18]) with mapi id 15.00.1156.000; Fri, 3 May 2019 17:10:08 +0200
From: Matthias Kovatsch <w3c@kovatsch.net>
To: Mark Baker <distobj@acm.org>
CC: "media-types@iana.org" <media-types@iana.org>
Thread-Topic: [media-types] Notice for a potential media type registration: application/td+json
Thread-Index: AdUBjvDgPXIk9DLnTCumvM9fM/S++gABoANAAAAR7oAABXHAgAAEdL5Q
Date: Fri, 03 May 2019 15:10:08 +0000
Message-ID: <215d4438d9184b6781a88b6d3af8fa46@MBX100D.cloud4partner.com>
References: <bef5f77d59484b78a5cdc4caab167ee2@MBX100D.cloud4partner.com> <fadb0a6df97c4f8c9eb722f7104b5741@MBX100D.cloud4partner.com> <c6f6897e3b58441aaf5dfd83c1668e63@MBX100D.cloud4partner.com> <CALcoZirUygJtmA2z7eRL3mWS2YCpQX5md-51A3DMDPLwtiCkNg@mail.gmail.com>
In-Reply-To: <CALcoZirUygJtmA2z7eRL3mWS2YCpQX5md-51A3DMDPLwtiCkNg@mail.gmail.com>
Accept-Language: en-US, de-DE
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [192.168.8.246]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-cloud-security-sender: w3c@kovatsch.net
X-cloud-security-recipient: media-types@iana.org
X-cloud-security-Virusscan: CLEAN
X-cloud-security-disclaimer: This E-Mail was scanned by E-Mailservice on ma04-relay.lansolnet.com with BB773B80076
X-cloud-security-connect: unknown[192.168.8.236], TLS=1, IP=192.168.8.236
X-cloud-security: scantime:.1355
Archived-At: <https://mailarchive.ietf.org/arch/msg/media-types/7kT3dXdqY9OZUT7gKIrtWRwTLbE>
Subject: Re: [media-types] Notice for a potential media type registration: application/td+json
X-BeenThere: media-types@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IANA mailing list for reviewing Media Type \(MIME Type, Content Type\) registration requests." <media-types.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/media-types>, <mailto:media-types-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/media-types/>
List-Post: <mailto:media-types@ietf.org>
List-Help: <mailto:media-types-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/media-types>, <mailto:media-types-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 May 2019 15:10:51 -0000

Dear Mark

> Can you explain why application/ld+json, the JSON-LD media type,
> was insufficient for your needs? Thanks.

The main reason is avoiding an entry barrier for IoT devices and developers. While WoT Thing Description (TD) has a syntax compatible with JSON-LD (1.1) to enable "semantic processing," we already got strong comments during the WG charter period that we should not have a dependency on RDF. Thus, we put quite some effort that TDs are also processable with a "raw JSON approach," meaning no knowledge of JSON-LD is necessary. Furthermore, this helps in resource-constrained environments that cannot afford JSON-LD processing, which is common in IoT (we have experience with running code here).

There are also technical reasons such as using Web Linking to express different relations between Things. The "type" target attribute should identify it as a Thing, however, it can only take a media type, i.e., no parameters such as the profile. We also investigated a CBOR representation of TD. In the future, we might want to register "application/td+cbor" for a CBOR representation based on the same TD Information Model.

I hope this explains our choice.

Best wishes,
Matthias

v2.23.0 | Report a Bug | By Email