From bjh21@cam.ac.uk Tue Jul 7 07:57:19 2015 Return-Path: X-Original-To: media-types@ietfa.amsl.com Delivered-To: media-types@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 73B1D1ACD4B for ; Tue, 7 Jul 2015 07:57:19 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.8 X-Spam-Level: X-Spam-Status: No, score=0.8 tagged_above=-999 required=5 tests=[BAYES_50=0.8] autolearn=ham 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 Bg-TCmMhSXm5 for ; Tue, 7 Jul 2015 07:57:17 -0700 (PDT) Received: from pechora4.lax.icann.org (pechora4.icann.org [IPv6:2620:0:2d0:201::1:74]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ADC3C1AC41C for ; Tue, 7 Jul 2015 07:56:52 -0700 (PDT) Received: from ppsw-51.csi.cam.ac.uk (ppsw-51.csi.cam.ac.uk [131.111.8.151]) by pechora4.lax.icann.org (8.13.8/8.13.8) with ESMTP id t67EuVGh021443 for ; Tue, 7 Jul 2015 14:56:52 GMT X-Cam-AntiVirus: no malware found X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ Received: from puff.ds.cam.ac.uk ([131.111.8.65]:38428) by ppsw-51.csi.cam.ac.uk (ppsw.cam.ac.uk [131.111.8.139]:25) with esmtps (TLSv1.2:DHE-RSA-AES128-SHA:128) id 1ZCTwZ-0002w2-ZM (Exim 4.82_3-c0e5623) for media-types@iana.org (return-path ); Tue, 07 Jul 2015 15:33:56 +0100 Received: from bjh21 (helo=localhost) by puff.ds.cam.ac.uk with local-esmtp (Exim 4.82) (envelope-from ) id 1ZCTwZ-0002aD-SM for media-types@iana.org; Tue, 07 Jul 2015 15:33:55 +0100 Date: Tue, 7 Jul 2015 15:33:55 +0100 (BST) From: Ben Harris To: media-types@iana.org Message-ID: User-Agent: Alpine 2.10 (DEB 1266 2009-07-14) MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="1870872840-617897347-1436279570=:29345" Content-ID: Sender: "B.J. Harris" X-Greylist: Delayed for 00:22:35 by milter-greylist-4.0 (pechora4.lax.icann.org [192.0.33.74]); Tue, 07 Jul 2015 14:56:52 +0000 (UTC) Archived-At: X-Mailman-Approved-At: Tue, 07 Jul 2015 15:49:13 -0700 Subject: [media-types] Proposed media type registration for YAML X-BeenThere: media-types@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "IANA mailing list for reviewing Media Type \(MIME Type, Content Type\) registration requests." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Jul 2015 15:02:58 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --1870872840-617897347-1436279570=:29345 Content-Type: TEXT/PLAIN; CHARSET=UTF-8; format=flowed Content-Transfer-Encoding: 8BIT Content-ID: Below is a media type registration I'm proposing to submit for YAML. I have one specific question for the list: * Is it appropriate to use a "text/*" type for something that might be encoded in UTF-16 or UTF-32? I'm confident that YAML in UTF-8 fits the line-break requirements of RFC 2046, but I'm not sure whether that permits UTF-16 or UTF-32. Type name: text Subtype name: vnd.yaml Required parameters: None Optional parameters: There is a single optional parameter, "version", whose value MUST match the ns-yaml-version production in YAML 1.1 or YAML 1.2. If provided, it identifies a version of the YAML specification to which the corresponding entity conforms. The "charset" parameter is not used: The YAML specifications define how a YAML processor should determine whether a YAML stream is encoded in UTF-8, UTF-16, or UTF-32. Encoding considerations: binary Security considerations: Interpreting arbitrary YAML can be dangerous. Many YAML processors are able to serialise and deserialise arbitrary objects in their host programming language, which can include arbitrary executable code. Applications consuming YAML from untrusted sources MUST restrict the range of object types that can be deserialised to those that are safe. YAML allows for the construction of complex data structures, including cyclic ones. This can create structures that simple reference-counting garbage collectors cannot collect when they become unreferenced. YAML consumers using such garbage collectors may need to record which references were generated using aliases and to break those references before allowing the structure to become unreferenced. Interoperability considerations: N/A Published specification: YAML Ain’t Markup Language (YAMLâ„¢) Version 1.2, http://yaml.org/spec/1.2/spec.html YAML Ain’t Markup Language (YAMLâ„¢) Version 1.1, http://yaml.org/spec/1.1/ YAML Ain't Markup Language (YAMLâ„¢) 1.0, http://yaml.org/spec/1.0/ In each case, a text/vnd.yaml entity is a complete YAML stream, which might potentially contain multiple YAML documents. Applications that use this media type: A wide variety of implementations are listed at . Fragment identifier considerations: Fragment identifiers are reserved for future standardisation. While having them refer to YAML anchor names is tempting, those are deliberately not unique within a stream and hence would not make good fragment identifiers. Additional information: Deprecated alias names for this type: N/A Magic number(s): N/A File extension(s): .yaml .yml Macintosh file type code(s): N/A Person & email address to contact for further information: YAML mailing list Intended usage: COMMON Restrictions on usage: N/A Author: Ben Harris, University of Cambridge Change controller: Ben Harris, University of Cambridge on behalf of Oren Ben-Kiki , Clark Evans , and Ingy döt Net Provisional registration? (standards tree only): N/A -- Ben Harris, University of Cambridge Information Services. --1870872840-617897347-1436279570=:29345-- From nobody Tue Jul 14 02:38:43 2015 Return-Path: X-Original-To: media-types@ietfa.amsl.com Delivered-To: media-types@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F422B1A88E1 for ; Tue, 14 Jul 2015 02:38:41 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 2.365 X-Spam-Level: ** X-Spam-Status: No, score=2.365 tagged_above=-999 required=5 tests=[BAYES_50=0.8, J_CHICKENPOX_34=0.6, MIME_8BIT_HEADER=0.3, SPF_SOFTFAIL=0.665] autolearn=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 3cIqjRGqeHbI for ; Tue, 14 Jul 2015 02:38:39 -0700 (PDT) Received: from pechora7.dc.icann.org (pechora7.icann.org [IPv6:2620:0:2830:201::1:73]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 026881A912B for ; Tue, 14 Jul 2015 02:38:38 -0700 (PDT) Received: from APC01-PU1-obe.outbound.protection.outlook.com (mail-pu1apc01on0127.outbound.protection.outlook.com [104.47.126.127]) by pechora7.dc.icann.org (8.13.8/8.13.8) with ESMTP id t6E9cG53000626 for ; Tue, 14 Jul 2015 09:38:37 GMT Authentication-Results: iana.org; dkim=none (message not signed) header.d=none; Received: from [133.2.210.64] (133.2.210.64) by TY1PR01MB0144.jpnprd01.prod.outlook.com (10.161.134.148) with Microsoft SMTP Server (TLS) id 15.1.213.14; Tue, 14 Jul 2015 05:00:52 +0000 To: Ben Harris , References: From: "=?UTF-8?Q?Martin_J._D=c3=bcrst?=" Organization: Aoyama Gakuin University Message-ID: <55A4977A.2080508@it.aoyama.ac.jp> Date: Tue, 14 Jul 2015 14:00:42 +0900 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.1.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: 8bit X-Originating-IP: [133.2.210.64] X-ClientProxiedBy: TY1PR0201CA0039.apcprd02.prod.outlook.com (25.164.90.177) To TY1PR01MB0144.jpnprd01.prod.outlook.com (25.161.134.148) X-Microsoft-Exchange-Diagnostics: 1; TY1PR01MB0144; 2:Th0/rqHFBSxA8JTlsqrOjqBnheKKzqXd415yMY/HHAD2pznGbvYwEDePsEaexVdT; 3:dw4NLYKLBQMDnBZnjxOwMFZlhnqzTE3UQhq8zYdWeKiRescjo5vmZQdXHLjsmgLEWD5KSfJ/IVUU+0w+Bl2ngVJN+2Zi0cm9w4MkEaPXp6i9D4bCjXhpPn4dl1ZPfo5fe52/xIZIpbLKU5nRsmuCfw==; 25:meUgeeOiRuV/1fOXrCAGjEQU6nFoRvLljoMyfpEVcMCgJLxzgNIInwptCM1h9tAKn1lU6AkfUpN/scsouoJqJMOjm/KRtjEV/9/B1BuEt2ANRjULzZClMcMsu2wIZYpxl2fCeOIpdCcrwdmMy4t8qL+XV1BvaOqxLwaG9cksTE66RaFgUjOi56EunPc1K2S40hscvPS3Pgdzz3ZRUchkoFKXijB3sAmfWwUEaHj4GlqsZLgQFP+pgA4BqARZFs546cmKu4j0h49zntsvivFkMA==; 4:0rNbx/HloG+FVQpqaQkBqXThd9EEi5qZajx/hU1CJgdrlEvVCkLXfJTRGv0/RtAPkV4GzJmQSLKXId3UmK3KuiEh3qWASW1cgj9EbSlzpWQTKqyx17plRo6VOv0+o2Vt1JCQRCT/vpNyyFAi4Xe7lL0SfSIKKPLVN+77llGFNXdc1OmndS7a6vWbThKl2G8o9Wv8zdbLGf3D2rAWXs5PQ0WlT4xa4wdezENjutE7Exs+sLo0P+0Y0bAP0PSuu4ylqyQeq/ViyN2KkhWYZD9ujQ== X-Microsoft-Antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:TY1PR01MB0144; X-Microsoft-Antispam-PRVS: X-Exchange-Antispam-Report-Test: UriScan:; X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(5005006)(3002001); SRVR:TY1PR01MB0144; BCL:0; PCL:0; RULEID:; SRVR:TY1PR01MB0144; X-Forefront-PRVS: 0637FCE711 X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10019020)(6009001)(6049001)(24454002)(479174004)(51704005)(54356999)(33656002)(189998001)(86362001)(77096005)(122386002)(92566002)(15975445007)(2950100001)(19580395003)(19580405001)(40100003)(59896002)(62966003)(5001960100002)(23676002)(50466002)(77156002)(4001350100001)(107886002)(87976001)(74482002)(76176999)(50986999)(5001770100001)(42186005)(83506001)(46102003)(5001920100001)(64126003)(87266999)(65806001)(19300405004)(65816999)(65956001)(66066001)(47776003)(15395725005)(3940600001)(562404015); DIR:OUT; SFP:1102; SCL:1; SRVR:TY1PR01MB0144; H:[133.2.210.64]; FPR:; SPF:None; MLV:sfv; LANG:en; X-Microsoft-Exchange-Diagnostics: =?utf-8?B?MTtUWTFQUjAxTUIwMTQ0OzIzOjhkbHgyb2ZjSWFVYzI1TmliTDYvclVvUEV1?= =?utf-8?B?WkVYRTBVRDFNV0FSVkt6Mzd4UVJoS2dqR25wYlNwUjVhQmFNK3Q1SW1WdHpk?= =?utf-8?B?SldhdDdmaS8rcGZyemVsTzRuTGRxeG1qaEI3eityd3JJRVAyVFowMVNMZ3BQ?= =?utf-8?B?VUhJeTdJUE00ZWdzOGMxdEtlUnpKckF2cmFFaThuRlFpUm9ld3VvbmdjazEw?= =?utf-8?B?SWhOeHE0UHdIOWdYTnQvL25vU1ZYQml0Z3ZrOEd5VnVZb1cxeGRXWXRKei9j?= =?utf-8?B?eXNhTW5TemR0L3h2bi8rNFFCTTcyU0xXUUp2U25OUS9WSHRQNDB5ME5PUm5F?= =?utf-8?B?WkpYVEFMTCtYOWRrVXpaczE3cjlMMFFLZXUvbTg0SVNPKzRlYWhoU0V3WHVB?= =?utf-8?B?dkhnaGs0OW1xaHFJTS8zRlFXTCtQQnhKZWZ2YUtFMUhVT1J3SEhXN0JCTUdv?= =?utf-8?B?VFY0ZGR4V09PTGJmYk9Xd3JkaUZhaS9sajZIWTRBL25EZDlSWTVvWmpqdHNQ?= =?utf-8?B?NDY0NVFzRkFrYlR1ZWU4UjZZK2ZBOUtvRWo1TDVGNkZMRkExdXR6N09EOU1J?= =?utf-8?B?TWduYmU2VmFxMk96SnlJWkNmVHNGMm5YNkF5VWl2VjhOeXVJYVdKZkpZYmpP?= =?utf-8?B?ZWd6b1poZWxldURHbzkxMm16dXczdW1LVDJselNiOFNVeTI5emgvcXRjZEQ5?= =?utf-8?B?STFUbkxkOTNwZlhOVjNJQzdVMExGbkRWUEpMQ1NRaHllc3BIUExxYUdUMHpi?= =?utf-8?B?QWJoMGRVU05ySG9kNVR1ejJKbDl1Q2xudGtLSGR2Nno5am1Qb0dvSis1N29B?= =?utf-8?B?T2ZBdk1McCtOeW5KekVwaTJvRTRpdVc5dnllSG1leXBwMUx3SFY3eVFpWjdI?= =?utf-8?B?TjdEZTBRdVdDTWdrSW45M0c0dEYwOXVyNmpZREQ3RkZlK2IrRm9SSUxoTndC?= =?utf-8?B?RHZWNE9QMXlaR0NEbENyM3ZyWHA2QjA4NEsxUURYQzNjUHByVDh3NVpJSHNw?= =?utf-8?B?cFdwN2lWYUFrRzJibVZZdTR6a3VxT0cvTDVzaW1yZjFycUJ3dGk2TFB3eUZh?= =?utf-8?B?MXpIVEZsQ0NhVm1PTnJBYmNodDNaL2lLZ1QrcGZJMFNBSmZnanBMSVUydm9v?= =?utf-8?B?SFVIY0RXNUo1b2lvQ3lJblFKbW5UVS9CTjM1Zm1pQmRGVXlndk02RlZVN2Vm?= =?utf-8?B?UjZuU2dIaUlkZGZvV1VjTExhMEp4eXhTZFVkOENiRlVEME5LVms0MTkvd21n?= =?utf-8?B?RW1lQmprTnpvSHdDTHRWVlFlcVpyQ1E0VWpNa0ZhS001VSs1YmpzQUpIVWU1?= =?utf-8?B?UWdmeExJb0Z5UjZpYmNtUnozOWRacHYyUTFQZm1ya0tqQ2tra0NjQjdGMEtv?= =?utf-8?B?ZlZGUXZ5NmI5dWFkRUwzY09aK3pCYkNwQjFGeXBUT0dlQzlESXFCcDE5L0NO?= =?utf-8?B?MEY5UkZwTjFmcE5Wd0pCa2syR0wwdTZVRklraElUdmJIVWRCZkErZ0xBbExV?= =?utf-8?B?YXMwWTdMRzE2Y2lOSVE1QXVDdlgydlp1UXEvZml0dTZaTlNVbURIVEpWR2VY?= =?utf-8?B?dkh4SjhXWEZxMVJvWnB1aSsrd2UzS2YzRms4cHV6aER6YzJhMThRNTY3WXdJ?= =?utf-8?Q?YQnXYwFYIpk49YBH8Gv+?= X-Microsoft-Exchange-Diagnostics: 1; TY1PR01MB0144; 5:WAgc02kWfAfoKe2geDIu6/5PnkEJNXvH0Td9fR9OIsSRF0lSB9kOgPowbvA5jsqQ6yGP1byStcyW632WNqvogBOHVVf4uqvTQkMlPdaF8ziPOJZjvDe5mvzYhFcUfWxjNKjo6Z/uV0HafV5nl8zIzA==; 24:r2AqaLhr1MGC0vVkoXRKIo0lloV9TqqhzcZDdJHWB1t90GUmLR7Pu9lCr8KznrKcvAcYg3y+h8yY21ch1QJju39t68xo4/9l81VkdaL/WT4=; 20:TsQkekOwvT2TQsug3Ng8P20HhfJp0X2im0IE2DGDp0SkeWBRlr2hOPaat6BAmDG6Kf/K0Mf9mQCgGeAMzCZlXg== SpamDiagnosticOutput: 1:23 SpamDiagnosticMetadata: NSPM X-OriginatorOrg: it.aoyama.ac.jp X-MS-Exchange-CrossTenant-OriginalArrivalTime: 14 Jul 2015 05:00:52.5196 (UTC) X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted X-MS-Exchange-Transport-CrossTenantHeadersStamped: TY1PR01MB0144 X-Greylist: IP, sender and recipient auto-whitelisted, not delayed by milter-greylist-4.2.3 (pechora7.dc.icann.org [192.0.46.73]); Tue, 14 Jul 2015 09:38:38 +0000 (UTC) Archived-At: Subject: Re: [media-types] Proposed media type registration for YAML X-BeenThere: media-types@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "IANA mailing list for reviewing Media Type \(MIME Type, Content Type\) registration requests." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Jul 2015 09:38:42 -0000 Hello Ben, On 2015/07/07 23:33, Ben Harris wrote: > Below is a media type registration I'm proposing to submit for YAML. I > have one specific question for the list: > > * Is it appropriate to use a "text/*" type for something that might be > encoded in UTF-16 or UTF-32? I'm confident that YAML in UTF-8 fits the > line-break requirements of RFC 2046, but I'm not sure whether that > permits UTF-16 or UTF-32. The answer is "it depends". For more details, see e.g. http://tools.ietf.org/html/rfc7303#section-9.2 (or rather actually http://tools.ietf.org/html/rfc7303#section-9.1) or the somewhat older http://tools.ietf.org/html/rfc3023#section-8.2. Because YAML is only rarely used to transmit actual human-readable prose (as opposed to structured data in textual form), a top-level type of application/, with less restrictions, may be much more appropriate. That's the conclusion XML came to, after many years and some detours. > Type name: > > text > > Subtype name: > > vnd.yaml I wonder whether the vnd. prefix here is really appropriate. YAML isn't a company in any way. Ideally, something like YAML should just be text/yaml (or actually application/yaml, see above). The spec at e.g. http://yaml.org/spec/1.2/spec.html definitely looks very detailed and well worked out, although I can't speak for the actual quality. Regards, Martin. > Required parameters: > > None > > Optional parameters: > > There is a single optional parameter, "version", whose value MUST match > the ns-yaml-version production in YAML 1.1 or YAML 1.2. If provided, it > identifies a version of the YAML specification to which the > corresponding entity conforms. > > The "charset" parameter is not used: The YAML specifications define how > a YAML processor should determine whether a YAML stream is encoded in > UTF-8, UTF-16, or UTF-32. > > Encoding considerations: > > binary > > Security considerations: > > Interpreting arbitrary YAML can be dangerous. Many YAML processors are > able to serialise and deserialise arbitrary objects in their host > programming language, which can include arbitrary executable code. > Applications consuming YAML from untrusted sources MUST restrict the > range of object types that can be deserialised to those that are safe. > > YAML allows for the construction of complex data structures, including > cyclic ones. This can create structures that simple reference-counting > garbage collectors cannot collect when they become unreferenced. YAML > consumers using such garbage collectors may need to record which > references were generated using aliases and to break those references > before allowing the structure to become unreferenced. > > Interoperability considerations: > > N/A > > Published specification: > > YAML Ain’t Markup Language (YAMLâ„¢) Version 1.2, > http://yaml.org/spec/1.2/spec.html > YAML Ain’t Markup Language (YAMLâ„¢) Version 1.1, http://yaml.org/spec/1.1/ > YAML Ain't Markup Language (YAMLâ„¢) 1.0, http://yaml.org/spec/1.0/ > > In each case, a text/vnd.yaml entity is a complete YAML stream, which > might potentially contain multiple YAML documents. > > Applications that use this media type: > > A wide variety of implementations are listed at . > > Fragment identifier considerations: > > Fragment identifiers are reserved for future standardisation. While > having them refer to YAML anchor names is tempting, those are > deliberately not unique within a stream and hence would not make good > fragment identifiers. > > Additional information: > > Deprecated alias names for this type: N/A > Magic number(s): N/A > File extension(s): .yaml .yml > Macintosh file type code(s): N/A > > Person & email address to contact for further information: > > YAML mailing list > > Intended usage: > > COMMON > > Restrictions on usage: > > N/A > > Author: > > Ben Harris, University of Cambridge > > Change controller: > > Ben Harris, University of Cambridge > on behalf of Oren Ben-Kiki , Clark Evans > , and Ingy döt Net > > Provisional registration? (standards tree only): > > N/A > > > > _______________________________________________ > media-types mailing list > media-types@ietf.org > https://www.ietf.org/mailman/listinfo/media-types > From nobody Wed Jul 15 05:49:58 2015 Return-Path: X-Original-To: media-types@ietfa.amsl.com Delivered-To: media-types@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A71541A8AD0 for ; Wed, 15 Jul 2015 05:49:53 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 1.422 X-Spam-Level: * X-Spam-Status: No, score=1.422 tagged_above=-999 required=5 tests=[BAYES_50=0.8, FM_FORGED_GMAIL=0.622] autolearn=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 GcuBq0PMLJry for ; Wed, 15 Jul 2015 05:49:52 -0700 (PDT) Received: from pechora1.lax.icann.org (pechora1.icann.org [IPv6:2620:0:2d0:201::1:71]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 08A941A8ACC for ; Wed, 15 Jul 2015 05:49:46 -0700 (PDT) Received: from mail-wi0-f170.google.com (mail-wi0-f170.google.com [209.85.212.170]) by pechora1.lax.icann.org (8.13.8/8.13.8) with ESMTP id t6FCnQlE024483 for ; Wed, 15 Jul 2015 12:49:46 GMT Received: by wiga1 with SMTP id a1so128160459wig.0 for ; Wed, 15 Jul 2015 05:49:25 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=JCLLN1fvNx5UtkT7GtrqImkzavAXzGM2zxvS2xhYttg=; b=HH3Use3rjBm2RArcanBlUzgf9nwpFMVP5B225Cv0+3XfVs7HKyAsMJABhoIpjnjeK4 d7uDvsPho3C+AMcl3nY+jS2Ls2u+bSnZvM6YtgO2hDQ8dqgCX4tZwvCHpObc+JhC/WNl /ShlYjBywPRSafS+zlhHfVUc/rceBZcesi7Uq0beg8dLqa0tGgJET74v4v1ja0Rw9RmN 7xYru7LXZyEdoo5u1cNsWR4GhXg+72pFrCkxZxXsRiG1VXAPPpl5YD1tECCxFYYwAzgM 4Lt93x5lzXJZpu1Bq7GacJU61UzJAmrnTlpdAaW54KgZua+uZYFSMgRiwUlKwzCUgevJ +MJA== X-Gm-Message-State: ALoCoQklV2/Z5X7a3ga1BW5KOlPjQxrteOnh7TBRJFT/LQQ73Xz33CWXy87Xn+Rh+vf0erfVmjRD MIME-Version: 1.0 X-Received: by 10.180.24.65 with SMTP id s1mr14997065wif.66.1436964565870; Wed, 15 Jul 2015 05:49:25 -0700 (PDT) Sender: mark@coactus.com Received: by 10.194.33.230 with HTTP; Wed, 15 Jul 2015 05:49:25 -0700 (PDT) X-Originating-IP: [23.233.56.241] In-Reply-To: References: Date: Wed, 15 Jul 2015 08:49:25 -0400 X-Google-Sender-Auth: 2Tle1fMGmcU9hF53z5rmYxd_nfU Message-ID: From: Mark Baker To: Ben Harris Content-Type: text/plain; charset=UTF-8 X-Greylist: IP, sender and recipient auto-whitelisted, not delayed by milter-greylist-4.0 (pechora1.lax.icann.org [192.0.33.71]); Wed, 15 Jul 2015 12:49:46 +0000 (UTC) Archived-At: Cc: media-types@iana.org Subject: Re: [media-types] Proposed media type registration for YAML X-BeenThere: media-types@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "IANA mailing list for reviewing Media Type \(MIME Type, Content Type\) registration requests." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Jul 2015 12:49:55 -0000 I concur with Martin's comments, and have one of my own... On Tue, Jul 7, 2015 at 10:33 AM, Ben Harris wrote: > Optional parameters: > > There is a single optional parameter, "version", whose value MUST match the > ns-yaml-version production in YAML 1.1 or YAML 1.2. If provided, it > identifies a version of the YAML specification to which the corresponding > entity conforms. In general, versioning and similar mechanisms don't belong in a parameter because the media type itself is a compatibility statement, i.e. it serves as a name given to a series of largely compatible formats. Do you have a use case for it? Mark. From nobody Wed Jul 15 09:43:53 2015 Return-Path: X-Original-To: media-types@ietfa.amsl.com Delivered-To: media-types@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9CAEE1B318D for ; Wed, 15 Jul 2015 09:43:51 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.8 X-Spam-Level: X-Spam-Status: No, score=0.8 tagged_above=-999 required=5 tests=[BAYES_50=0.8] autolearn=ham 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 wJhM-9ZGw0Gx for ; Wed, 15 Jul 2015 09:43:50 -0700 (PDT) Received: from pechora8.dc.icann.org (pechora8.icann.org [IPv6:2620:0:2830:201::1:74]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 28FF31B311C for ; Wed, 15 Jul 2015 09:43:49 -0700 (PDT) Received: from ppsw-41.csi.cam.ac.uk (ppsw-41.csi.cam.ac.uk [131.111.8.141]) by pechora8.dc.icann.org (8.13.8/8.13.8) with ESMTP id t6FGhSpw013617 for ; Wed, 15 Jul 2015 16:43:48 GMT X-Cam-AntiVirus: no malware found X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ Received: from puff.ds.cam.ac.uk ([131.111.8.65]:48519) by ppsw-41.csi.cam.ac.uk (ppsw.cam.ac.uk [131.111.8.137]:25) with esmtps (TLSv1.2:DHE-RSA-AES128-SHA:128) id 1ZFPU0-0001mZ-Py (Exim 4.82_3-c0e5623) (return-path ); Wed, 15 Jul 2015 17:24:32 +0100 Received: from bjh21 (helo=localhost) by puff.ds.cam.ac.uk with local-esmtp (Exim 4.82) (envelope-from ) id 1ZFPTz-00013n-Ux; Wed, 15 Jul 2015 17:24:31 +0100 Date: Wed, 15 Jul 2015 17:24:31 +0100 (BST) From: Ben Harris To: Mark Baker In-Reply-To: Message-ID: References: User-Agent: Alpine 2.10 (DEB 1266 2009-07-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Sender: "B.J. Harris" X-Greylist: Delayed for 00:18:55 by milter-greylist-4.2.3 (pechora8.dc.icann.org [192.0.46.74]); Wed, 15 Jul 2015 16:43:48 +0000 (UTC) Archived-At: Cc: media-types@iana.org Subject: Re: [media-types] Proposed media type registration for YAML X-BeenThere: media-types@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "IANA mailing list for reviewing Media Type \(MIME Type, Content Type\) registration requests." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Jul 2015 16:43:51 -0000 On Wed, 15 Jul 2015, Mark Baker wrote: > I concur with Martin's comments, and have one of my own... > > On Tue, Jul 7, 2015 at 10:33 AM, Ben Harris wrote: >> Optional parameters: >> >> There is a single optional parameter, "version", whose value MUST match the >> ns-yaml-version production in YAML 1.1 or YAML 1.2. If provided, it >> identifies a version of the YAML specification to which the corresponding >> entity conforms. > > In general, versioning and similar mechanisms don't belong in a > parameter because the media type itself is a compatibility statement, > i.e. it serves as a name given to a series of largely compatible > formats. Do you have a use case for it? I don't think I currently have a use case for the "version" parameter. I've never noticed any YAML libraries' having any means to select the version of YAML that they produce, so I doubt it would be of any use for content negotiation. I'll remove it from the next draft. -- Ben Harris, University of Cambridge Information Services. Tel: (01223) 334728 From nobody Wed Jul 15 11:02:39 2015 Return-Path: X-Original-To: media-types@ietfa.amsl.com Delivered-To: media-types@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2ABB61ACDDB for ; Wed, 15 Jul 2015 11:02:38 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: 0.4 X-Spam-Level: X-Spam-Status: No, score=0.4 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, J_CHICKENPOX_34=0.6, MIME_8BIT_HEADER=0.3] autolearn=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 dn8tszdIvtSM for ; Wed, 15 Jul 2015 11:02:36 -0700 (PDT) Received: from pechora1.lax.icann.org (pechora1.icann.org [IPv6:2620:0:2d0:201::1:71]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A4C7E1ACD6A for ; Wed, 15 Jul 2015 11:02:35 -0700 (PDT) Received: from ppsw-50.csi.cam.ac.uk (ppsw-50.csi.cam.ac.uk [131.111.8.150]) by pechora1.lax.icann.org (8.13.8/8.13.8) with ESMTP id t6FI2Erk012437 for ; Wed, 15 Jul 2015 18:02:35 GMT X-Cam-AntiVirus: no malware found X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ Received: from puff.ds.cam.ac.uk ([131.111.8.65]:56192) by ppsw-50.csi.cam.ac.uk (ppsw.cam.ac.uk [131.111.8.138]:25) with esmtps (TLSv1.2:DHE-RSA-AES128-SHA:128) id 1ZFQfk-0003RF-rR (Exim 4.82_3-c0e5623) (return-path ); Wed, 15 Jul 2015 18:40:44 +0100 Received: from bjh21 (helo=localhost) by puff.ds.cam.ac.uk with local-esmtp (Exim 4.82) (envelope-from ) id 1ZFQfk-0004CD-Fo; Wed, 15 Jul 2015 18:40:44 +0100 Date: Wed, 15 Jul 2015 18:40:44 +0100 (BST) From: Ben Harris To: =?ISO-8859-15?Q?Martin_J=2E_D=FCrst?= In-Reply-To: <55A4977A.2080508@it.aoyama.ac.jp> Message-ID: References: <55A4977A.2080508@it.aoyama.ac.jp> User-Agent: Alpine 2.10 (DEB 1266 2009-07-14) MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="1870872840-1040522449-1436979055=:9824" Content-ID: Sender: "B.J. Harris" X-Greylist: Delayed for 00:21:29 by milter-greylist-4.0 (pechora1.lax.icann.org [192.0.33.71]); Wed, 15 Jul 2015 18:02:35 +0000 (UTC) Archived-At: Cc: media-types@iana.org Subject: Re: [media-types] Proposed media type registration for YAML X-BeenThere: media-types@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "IANA mailing list for reviewing Media Type \(MIME Type, Content Type\) registration requests." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Jul 2015 18:02:38 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --1870872840-1040522449-1436979055=:9824 Content-Type: TEXT/PLAIN; CHARSET=ISO-8859-15; FORMAT=flowed Content-Transfer-Encoding: 8BIT Content-ID: On Tue, 14 Jul 2015, Martin J. Dürst wrote: > On 2015/07/07 23:33, Ben Harris wrote: >> Below is a media type registration I'm proposing to submit for YAML. I >> have one specific question for the list: >> >> * Is it appropriate to use a "text/*" type for something that might be >> encoded in UTF-16 or UTF-32? I'm confident that YAML in UTF-8 fits the >> line-break requirements of RFC 2046, but I'm not sure whether that >> permits UTF-16 or UTF-32. > > The answer is "it depends". For more details, see e.g. > http://tools.ietf.org/html/rfc7303#section-9.2 (or rather actually > http://tools.ietf.org/html/rfc7303#section-9.1) or the somewhat older > http://tools.ietf.org/html/rfc3023#section-8.2. I think that's slightly helpful, as is the sentence "See [RFC2046] for additional information on the restrictions MIME imposes." from RFC 6838. That suggests that, possibly with some extra notes about using only UTF-8 with MIME, permitting UTF-16 and UTF-32 would be tolerable. > Because YAML is only rarely used to transmit actual human-readable prose (as > opposed to structured data in textual form), a top-level type of > application/, with less restrictions, may be much more appropriate. > That's the conclusion XML came to, after many years and some detours. The highest-priority design goal for YAML is stated to be "YAML is easily readable by humans" (YAML 1.2 section 1.1). So while not designed to transmit prose, it is designed to transmit human-readable data. My experience is that even machine-generated YAML is generally more readable than XML, JSON, or CSV. >> Subtype name: >> >> vnd.yaml > > I wonder whether the vnd. prefix here is really appropriate. YAML isn't a > company in any way. Ideally, something like YAML should just be text/yaml (or > actually application/yaml, see above). The spec at e.g. > http://yaml.org/spec/1.2/spec.html definitely looks very detailed and well > worked out, although I can't speak for the actual quality. I would much prefer to be able to use the standards tree rather than the vendor tree, but RFC 6838 doesn't make this easy. In the vendor tree, third-party registrations are explicitly permitted and "vendor" is described as being "construed very broadly", which I think is enough to let me register this type on behalf of the YAML authors. The standards tree, on the other hand, would either require me to write an RFC or require the YAML authors to submit the request themselves and to be approved as a "standards-related organization" by the IESG. I'll see if I can find a way to make either of the standards-tree routes work. Is there any guidance (or history) on what the IESG considers to be a standards-related organization? -- Ben Harris, University of Cambridge Information Services. --1870872840-1040522449-1436979055=:9824-- From nobody Wed Jul 15 11:19:46 2015 Return-Path: X-Original-To: media-types@ietfa.amsl.com Delivered-To: media-types@ietfa.amsl.com Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 285F41B336E for ; Wed, 15 Jul 2015 11:19:45 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.5 X-Spam-Level: X-Spam-Status: No, score=-0.5 tagged_above=-999 required=5 tests=[BAYES_05=-0.5] autolearn=ham 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 JwLMjQHtUBP7 for ; Wed, 15 Jul 2015 11:19:44 -0700 (PDT) Received: from pechora1.lax.icann.org (pechora1.icann.org [IPv6:2620:0:2d0:201::1:71]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D4F491AD06A for ; Wed, 15 Jul 2015 11:19:43 -0700 (PDT) Received: from ppsw-40.csi.cam.ac.uk (ppsw-40.csi.cam.ac.uk [131.111.8.140]) by pechora1.lax.icann.org (8.13.8/8.13.8) with ESMTP id t6FIJNdi016748 for ; Wed, 15 Jul 2015 18:19:43 GMT X-Cam-AntiVirus: no malware found X-Cam-ScannerInfo: http://www.cam.ac.uk/cs/email/scanner/ Received: from puff.ds.cam.ac.uk ([131.111.8.65]:34415) by ppsw-40.csi.cam.ac.uk (ppsw.cam.ac.uk [131.111.8.136]:25) with esmtps (TLSv1.2:DHE-RSA-AES128-SHA:128) id 1ZFQrt-0003ij-mD (Exim 4.82_3-c0e5623) (return-path ); Wed, 15 Jul 2015 18:53:17 +0100 Received: from bjh21 (helo=localhost) by puff.ds.cam.ac.uk with local-esmtp (Exim 4.82) (envelope-from ) id 1ZFQrt-0004j9-Qg; Wed, 15 Jul 2015 18:53:17 +0100 Date: Wed, 15 Jul 2015 18:53:17 +0100 (BST) From: Ben Harris To: Chris Rebert , media-types@iana.org In-Reply-To: Message-ID: References: <55A4977A.2080508@it.aoyama.ac.jp> User-Agent: Alpine 2.10 (DEB 1266 2009-07-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII Sender: "B.J. Harris" X-Greylist: Delayed for 00:26:04 by milter-greylist-4.0 (pechora1.lax.icann.org [192.0.33.71]); Wed, 15 Jul 2015 18:19:43 +0000 (UTC) Archived-At: Subject: Re: [media-types] Proposed media type registration for YAML X-BeenThere: media-types@ietf.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: "IANA mailing list for reviewing Media Type \(MIME Type, Content Type\) registration requests." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 15 Jul 2015 18:19:45 -0000 On Tue, 14 Jul 2015, Chris Rebert wrote: > (My apologies for replying off-list like this. I wasn't yet a > subscriber when you posted your message, so I can't reply to it > on-list properly. However, feel free to publicly reference or quote > from this reply.) > > Based on YAML's entry in the de facto *nix MIME types database > (http://cgit.freedesktop.org/xdg/shared-mime-info/tree/freedesktop.org.xml.in > ), you might consider including the following among the list of > deprecated aliases: > > * application/x-yaml > > * text/yaml > * text/x-yaml Thanks. I'll add them. While they're listed as "YAML document", I doubt the author was considering the technical distinction between a YAML document and a YAML stream when writing that. -- Ben Harris, University of Cambridge Information Services.