- From: Sandro Hawke <sandro@w3.org>
- Date: Fri, 08 Feb 2013 13:50:34 -0500
- To: Manu Sporny <msporny@digitalbazaar.com>
- CC: W3C RDF WG <public-rdf-wg@w3.org>
- Message-ID: <511548FA.9040300@w3.org>
I just noticed this media type application on an IETF list. I haven't looking into it. Do we know about JRD and how it compares to JSON-LD? -- Sandro -------- Original Message -------- Return-path: <media-types-bounces@ietf.org> Envelope-to: sandro@jay.w3.org Delivery-date: Fri, 08 Feb 2013 12:24:54 -0500 Received: from maggie.w3.org ([128.30.52.39]) by jay.w3.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.69) (envelope-from <media-types-bounces@ietf.org>) id 1U3rgu-0006W7-Lj; Fri, 08 Feb 2013 12:24:48 -0500 Received: from mail.ietf.org ([64.170.98.30]) by maggie.w3.org with esmtp (Exim 4.72) (envelope-from <media-types-bounces@ietf.org>) id 1U3rgs-0002WE-IG; Fri, 08 Feb 2013 17:24:47 +0000 Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1184321F8A67; Fri, 8 Feb 2013 09:24:19 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1360344259; bh=hpdZwy4CeTxMHiu+pvCVewCQwFJOX1d27Vu0VriGxbQ=; h=From:To:Date:Message-ID:MIME-Version:Cc:Subject:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: Content-Type:Content-Transfer-Encoding:Sender; b=hT5mmqKbgwwO0hkPnlK2e0Vti6dvE5Hqo0CL7d5hbx0fy8AX/H8zKcTr2RoCRu/7r i22HITRcajVVtw+CDeOXoRUn3BGV/bhlIw2+tp05fk+/N/CoEg5hOaLufQHeP/AaU0 Hw5kUckIWfxfIk7sC4IdsLG6Nd4HQGwbuVAuVl3I= 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 826E221F8447 for <media-types@ietfa.amsl.com>; Thu, 7 Feb 2013 14:11:45 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.28 X-Spam-Level: X-Spam-Status: No, score=-2.28 tagged_above=-999 required=5 tests=[AWL=-0.281, BAYES_00=-2.599, J_CHICKENPOX_34=0.6] 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 gcsyGJOLDnG1 for <media-types@ietfa.amsl.com>; Thu, 7 Feb 2013 14:11:44 -0800 (PST) Received: from pechora6.dc.icann.org (unknown [IPv6:2620:0:2830:201::1:72]) by ietfa.amsl.com (Postfix) with ESMTP id AAF7421F8436 for <media-types@ietf.org>; Thu, 7 Feb 2013 14:11:44 -0800 (PST) Received: from dublin.packetizer.com (dublin.packetizer.com [75.101.130.125]) by pechora6.dc.icann.org (8.13.8/8.13.8) with ESMTP id r17MBOaQ000765 for <media-types@iana.org>; Thu, 7 Feb 2013 22:11:44 GMT Received: from sydney (rrcs-98-101-148-48.midsouth.biz.rr.com [98.101.148.48]) (authenticated bits=0) by dublin.packetizer.com (8.14.5/8.14.5) with ESMTP id r17Ls2mi016897 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 7 Feb 2013 16:54:02 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=packetizer.com; s=dublin; t=1360274043; bh=b7xbI2SSS/E0QE0qwCFMgtztUlPHJE3S3B//IoObpyY=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version:Content-Type: Content-Transfer-Encoding; b=MiqEvDz/BYdxOB0df/AyzMSZSqF7S94chQOQMC0Qa8xK6uu1oUF/X15HdY+4Ovvat OozECzo/O1pvgh+zGoi8RALOQhZJ3O5vGkdOjn4cWHcdSqWRkE4fPArJVpHAoh8ToP IrMz7k7CiSGaZu68duUCGBGhChsywYXtOXNKFoBU= From: Paul E. Jones <paulej@packetizer.com> To: <media-types@iana.org> Date: Thu, 7 Feb 2013 16:54:11 -0500 Message-ID: <00c101ce057d$aa4d3300$fee79900$@packetizer.com> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 14.0 Thread-Index: Ac4FfHmd22VIzEXXTX+0vfeMXSyCnA== Content-Language: en-us X-Greylist: Delayed for 00:17:18 by milter-greylist-4.2.3 (pechora6.dc.icann.org [192.0.46.72]); Thu, 07 Feb 2013 22:11:44 +0000 (UTC) X-Mailman-Approved-At: Fri, 08 Feb 2013 09:24:17 -0800 Cc: webfinger@ietf.org, Barry Leiba <barryleiba@computer.org> Subject: [media-types] Media type application/jrd+json X-BeenThere: media-types@ietf.org X-Mailman-Version: 2.1.12 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: <http://www.ietf.org/mail-archive/web/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> Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: media-types-bounces@ietf.org Errors-To: media-types-bounces@ietf.org Received-SPF: pass client-ip=64.170.98.30; envelope-from=media-types-bounces@ietf.org; helo=mail.ietf.org X-W3C-Hub-Spam-Status: No, score=-4.5 X-W3C-Hub-Spam-Report: AWL=-2.191, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001 X-W3C-Scan-Sig: maggie.w3.org 1U3rgs-0002WE-IG 89afed53b719a9bc8f75ff720fccbe2c Folks, Barry Leiba indicated that we should register the a media type for the resource representation defined in http://tools.ietf.org/html/draft-ietf-appsawg-webfinger called the JSON Resource Descriptor (JRD). I am sending this for your review and comments back as we are working to finalize the draft. I have not completed a template for application types before and I see there are a few new things in the template, so please do let me know if there is anything that needs clarification or should be changed. Thanks, Paul ================================================ Type name: application Subtype name: jrd+json Required parameters: N/A Optional parameters: N/A "charset" - Indicates the character set used to encode the JSON Resource Descriptor. If absent, UTF-8 is assumed. Encoding considerations: 8bit Security considerations: The JSON Resource Descriptor (JRD) is a JavaScript Object Notation (JSON) object. It is a text format that must be parsed by entities that wish to utilize the format. Depending on the language and mechanism used to parse a JSON object, it is possible for an attacker to inject behavior into a running program. Therefore, care must be taken to properly parse a received JRD to ensure that only a valid JSON object is present and that no JavaScript code is injected or executed unexpectedly. Interoperability considerations: This media type is a JavaScript Object Notation (JSON) object and can be consumed by any software application that can consume JSON objects. Published specification: RFC QQQ Applications that use this media type: WebFinger Fragment identifier considerations: N/A Additional information: Deprecated alias names for this type: N/A Magic number(s): N/A File extension(s): jrd+json Macintosh file type code(s): N/A Person & email address to contact for further information: Paul E. Jones <paulej@packetizer.com> Intended usage: COMMON Restrictions on usage: N/A Author: Paul E. Jones <paulej@packetizer.com> Change controller: Paul E. Jones <paulej@packetizer.com> Provisional registration? (standards tree only): N/A _______________________________________________ media-types mailing list media-types@ietf.org https://www.ietf.org/mailman/listinfo/media-types
Received on Friday, 8 February 2013 18:50:43 UTC