
Return-Path: <duerst@it.aoyama.ac.jp>
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 0A29F11E80F6 for <ietf-types@ietfa.amsl.com>; Sun, 29 Jul 2012 19:05:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.329
X-Spam-Level: 
X-Spam-Status: No, score=-102.329 tagged_above=-999 required=5 tests=[AWL=1.461, BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265,  MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 AQZrPSvh7Wpm for <ietf-types@ietfa.amsl.com>; Sun, 29 Jul 2012 19:05:37 -0700 (PDT)
Received: from scintmta02.scbb.aoyama.ac.jp (scintmta02.scbb.aoyama.ac.jp [133.2.253.34]) by ietfa.amsl.com (Postfix) with ESMTP id 5348D11E8088 for <ietf-types@ietf.org>; Sun, 29 Jul 2012 19:05:37 -0700 (PDT)
Received: from scmse02.scbb.aoyama.ac.jp ([133.2.253.231]) by scintmta02.scbb.aoyama.ac.jp (secret/secret) with SMTP id q6U25aSR007942 for <ietf-types@ietf.org>; Mon, 30 Jul 2012 11:05:36 +0900
Received: from (unknown [133.2.206.133]) by scmse02.scbb.aoyama.ac.jp with smtp id 05c0_927b_0d58b604_d9eb_11e1_8223_001d096c5782; Mon, 30 Jul 2012 11:05:35 +0900
Received: from [IPv6:::1] ([133.2.210.1]:33603) by itmail.it.aoyama.ac.jp with [XMail 1.22 ESMTP Server] id <S15E96A4> for <ietf-types@ietf.org> from <duerst@it.aoyama.ac.jp>;  Mon, 30 Jul 2012 11:05:37 +0900
Message-ID: <5015EBE4.8050305@it.aoyama.ac.jp>
Date: Mon, 30 Jul 2012 11:05:24 +0900
From: =?UTF-8?B?Ik1hcnRpbiBKLiBEw7xyc3Qi?= <duerst@it.aoyama.ac.jp>
Organization: Aoyama Gakuin University
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.9) Gecko/20100722 Eudora/3.0.4
MIME-Version: 1.0
To: Bjoern Hoehrmann <derhoermi@gmx.net>
References: <CAJCyKRopSJr=w3N2cgsDO=GLmGsNQ99kcy6W1whQHuAZ78b2KQ@mail.gmail.com>	<50126B46.8030004@ecs.soton.ac.uk>	<EMEW3|0d6af10e701ec50a4d99234c93bc21cdo6QBJs08l.moreau|ecs.soton.ac.uk|50126B46.8030004@ecs.soton.ac.uk> <br2518thvu0sa5551ks3kk87ocnt6p2802@hive.bjoern.hoehrmann.de>
In-Reply-To: <br2518thvu0sa5551ks3kk87ocnt6p2802@hive.bjoern.hoehrmann.de>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Cc: ietf-types@ietf.org, "team-prov-chairs@w3.org" <team-prov-chairs@w3.org>, public-prov-comments@w3.org
Subject: Re: [ietf-types] Mime Type registration (PROV Last Call)
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: Mon, 30 Jul 2012 02:05:38 -0000

On 2012/07/27 21:41, Bjoern Hoehrmann wrote:
> * Luc Moreau wrote:
>> Type name:
>> text
>>
>> Subtype name:
>> provenance-notation
>>
>> Required parameters:
>> None
>>
>> Optional parameters:
>> charset â€” this parameter is mandatory. The value of charset is always UTF-8.
>
> This seems to need work, it's not optional if it is mandatory, is it.
> And The second sentence is a statement of fact that is easily contr-
> dicted by content.
>
>> Encoding considerations:
>> The syntax of PROV-N is expressed over code points in Unicode
>> [UNICODE5]. The encoding is always UTF-8 [UTF-8].
>> Unicode code points may also be expressed using an \uXXXX (U+0 to
>> U+FFFF) or \UXXXXXXXX syntax (for U+10000 onwards) where X is a
>> hexadecimal digit [0-9A-F]

Why [UNICODE5]? The newest version is Unicode 6.2. Is PROV-N limited to 
Unicode version 5? That would be a very bad idea.

Regards,    Martin.


> This field should contain one of the values in RFC 4288 or its successor
> if that has been approved already, like "binary".
>
>> Applications which use this media type:
>> No widely deployed applications are known to use this media type. It may
>> be used by some web services and clients consuming their data.
>
> You can remove the first sentence, this is to give people an idea
> whether this is for Word processing applications or cryptographic
> key exchange systems or whatever.
>
>> Person&  email address to contact for further information:
>> public-prov-comments@w3.org
>
> This does not qualify as "Person&  email address".

Return-Path: <duerst@it.aoyama.ac.jp>
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 70A3A21F84B2 for <ietf-types@ietfa.amsl.com>; Sun, 29 Jul 2012 19:04:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.321
X-Spam-Level: 
X-Spam-Status: No, score=-101.321 tagged_above=-999 required=5 tests=[AWL=0.469, BAYES_00=-2.599, GB_I_LETTER=-2, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, MIME_8BIT_HEADER=0.3, USER_IN_WHITELIST=-100]
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 iDHm2+sqPLp5 for <ietf-types@ietfa.amsl.com>; Sun, 29 Jul 2012 19:04:17 -0700 (PDT)
Received: from scintmta01.scbb.aoyama.ac.jp (scintmta01.scbb.aoyama.ac.jp [133.2.253.33]) by ietfa.amsl.com (Postfix) with ESMTP id 3335D21F84AF for <ietf-types@ietf.org>; Sun, 29 Jul 2012 19:04:16 -0700 (PDT)
Received: from scmse01.scbb.aoyama.ac.jp ([133.2.253.231]) by scintmta01.scbb.aoyama.ac.jp (secret/secret) with SMTP id q6U245Tx020936 for <ietf-types@ietf.org>; Mon, 30 Jul 2012 11:04:05 +0900
Received: from (unknown [133.2.206.133]) by scmse01.scbb.aoyama.ac.jp with smtp id 17e4_6772_d725bf64_d9ea_11e1_81a2_001d096c566a; Mon, 30 Jul 2012 11:04:04 +0900
Received: from [IPv6:::1] ([133.2.210.1]:33596) by itmail.it.aoyama.ac.jp with [XMail 1.22 ESMTP Server] id <S15E96A0> for <ietf-types@ietf.org> from <duerst@it.aoyama.ac.jp>;  Mon, 30 Jul 2012 11:04:06 +0900
Message-ID: <5015EB89.3060905@it.aoyama.ac.jp>
Date: Mon, 30 Jul 2012 11:03:53 +0900
From: =?UTF-8?B?Ik1hcnRpbiBKLiBEw7xyc3Qi?= <duerst@it.aoyama.ac.jp>
Organization: Aoyama Gakuin University
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.9) Gecko/20100722 Eudora/3.0.4
MIME-Version: 1.0
To: Luc Moreau <l.moreau@ecs.soton.ac.uk>
References: <CAJCyKRopSJr=w3N2cgsDO=GLmGsNQ99kcy6W1whQHuAZ78b2KQ@mail.gmail.com>	<50126B46.8030004@ecs.soton.ac.uk> <EMEW3|0d6af10e701ec50a4d99234c93bc21cdo6QBJs08l.moreau|ecs.soton.ac.uk|50126B46.8030004@ecs.soton.ac.uk>
In-Reply-To: <EMEW3|0d6af10e701ec50a4d99234c93bc21cdo6QBJs08l.moreau|ecs.soton.ac.uk|50126B46.8030004@ecs.soton.ac.uk>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Cc: "team-prov-chairs@w3.org" <team-prov-chairs@w3.org>, public-prov-comments@w3.org, ietf-types@ietf.org
Subject: Re: [ietf-types] Mime Type registration (PROV Last Call)
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: Mon, 30 Jul 2012 02:04:18 -0000

Hello Luc,

On 2012/07/27 19:19, Luc Moreau wrote:
> Dear all,
>
> The W3C Provenance Working has published a Last Call Working Draft for
> the PROV Notation.
>
> We would be grateful for your feedback on the Media Type section of the
> specification.
>
> 1. Media Type Section: http://www.w3.org/TR/prov-n/#media-type
> 2. Text Version:
> http://dvcs.w3.org/hg/prov/raw-file/default/model/media-type-request.txt

On this list, if possible, always include the actual text of the 
registration template. The chance for feedback is much higher.

Regards,    Martin.


> We look forward to hearing your comments,
>
> Text version is included below, and followed by the last call announcement.
>
> Best regards,
> Luc Moreau
> W3C PROV-WG co-chair
>
> --------------------------------------------------------
>
> The media type of PROV-N is text/provenance-notation. The content
> encoding of PROV-N content is UTF-8.
>
> Contact:
> Ivan Herman
> See also:
> How to Register a Media Type for a W3C Specification
> Internet Media Type registration, consistency of use
> TAG Finding 3 June 2002 (Revised 4 September 2002)
> The Internet Media Type / MIME Type for PROV-N is
> "text/provenance-notation".
>
> It is recommended that PROV-N files have the extension ".provn" (all
> lowercase) on all platforms.
>
> It is recommended that PROV-N files stored on Macintosh HFS file systems
> be given a file type of "TEXT".
>
> This information that follows is being submitted to the IESG for review,
> approval, and registration with IANA.
>
> Type name:
> text
>
> Subtype name:
> provenance-notation
>
> Required parameters:
> None
>
> Optional parameters:
> charset â€” this parameter is mandatory. The value of charset is always
> UTF-8.
>
> Encoding considerations:
> The syntax of PROV-N is expressed over code points in Unicode
> [UNICODE5]. The encoding is always UTF-8 [UTF-8].
> Unicode code points may also be expressed using an \uXXXX (U+0 to
> U+FFFF) or \UXXXXXXXX syntax (for U+10000 onwards) where X is a
> hexadecimal digit [0-9A-F]
>
> Security considerations:
> PROV-N is a general-purpose language for describing the provenance of
> things; applications may evaluate given data to infer more descriptions
> or to dereference URIs, invoking the security considerations of the
> scheme for that URI. Note in particular, the privacy issues in [RFC3023]
> section 10 for HTTP URIs. Data obtained from an inaccurate or malicious
> data source may lead to inaccurate or misleading conclusions, as well as
> the dereferencing of unintended URIs. Care must be taken to align the
> trust in consulted resources with the sensitivity of the intended use of
> the data.
> PROV-N is used to express the provenance of arbitrary application data;
> security considerations will vary by domain of use. Security tools and
> protocols applicable to text (e.g. PGP encryption, MD5 sum validation,
> password-protected compression) may also be used on PROV-N documents.
> Security/privacy protocols must be imposed which reflect the sensitivity
> of the embedded information.
> PROV-N can express data which is presented to the user, for example, by
> means of label attributes. Application rendering strings retrieved from
> untrusted PROV-N documents must ensure that malignant strings may not be
> used to mislead the reader. The security considerations in the media
> type registration for XML ([RFC3023] section 10) provide additional
> guidance around the expression of arbitrary data and markup.
> PROV-N is a language for describing the provenance of things, and
> therefore a PROV-N document is metadata for other resources. Untrusted
> PROV-N documents may mislead its consumers by indicating that a
> third-party resource has a reputable lineage, when it has not.
> Provenance of PROV-N document should be sought.
> PROV-N uses qualified names mappeable to IRIs as term identifiers.
> Applications interpreting data expressed in PROV-N should address the
> security issues of Internationalized Resource Identifiers (IRIs)
> [RFC3987] Section 8, as well as Uniform Resource Identifier (URI):
> Generic Syntax [RFC3986] Section 7.
> Multiple IRIs may have the same appearance. Characters in different
> scripts may look similar (a Cyrillic "Ð¾" may appear similar to a Latin
> "o"). A character followed by combining characters may have the same
> visual representation as another character (LATIN SMALL LETTER E
> followed by COMBINING ACUTE ACCENT has the same visual representation as
> LATIN SMALL LETTER E WITH ACUTE). Any person or application that is
> writing or interpreting data in PROV-N must take care to use the IRI
> that matches the intended semantics, and avoid IRIs that make look
> similar. Further information about matching of similar characters can be
> found in Unicode Security Considerations [UNISEC] and Internationalized
> Resource Identifiers (IRIs) [RFC3987] Section 8.
> Interoperability considerations:
>
> There are no known interoperability issues.
>
> Published specification:
> PROV-N: The Provenance Notation, Moreau, Missier, (eds), Cheney,
> Soiland-Reyes http://www.w3.org/TR/prov-n/
>
> Applications which use this media type:
> No widely deployed applications are known to use this media type. It may
> be used by some web services and clients consuming their data.
>
> Additional information:
> Magic number(s):
> PROV-N documents may have the strings 'bundle' near the beginning of the
> document.
>
> File extension(s):
> ".provn"
>
> Base URI:
> There are no constructs in the PROV-N Syntax to change the Base IRI.
>
> Macintosh file type code(s):
> "TEXT"
>
> Person & email address to contact for further information:
> public-prov-comments@w3.org
>
> Intended usage:
> COMMON
>
> Restrictions on usage:
> None
>
> Author/Change controller:
> The PROV-N specification is the product of the World Wide Web
> Consortium's PROV Working Group. The W3C has change control over this
> specification.
>
>
> -------- Original Message --------
> Subject: PROV Last Call on three documents: Request for Review
> Resent-Date: Tue, 24 Jul 2012 14:53:27 +0000
> Resent-From: <team-prov-chairs@w3.org>
> Date: Tue, 24 Jul 2012 16:52:57 +0200
> From: Paul Groth <p.t.groth@vu.nl>
> To: chairs@w3.org Chairs <chairs@w3.org>
> CC: <team-prov-chairs@w3.org>
>
>
>
> Dear All,
>
> The Provenance Working has published the following three drafts as
> Last Call Working Drafts:
>
> - PROV-DM: The PROV Data Model [1]
> - PROV-O: The PROV Ontology [2]
> - PROV-N: The Provenance Notation [3]
>
> We are looking for your feedback. To introduce you to the
> specifications, we also have published an updated Primer [4]. You'll
> also find an overview blog post at [5].
>
> The Last Call period ends 18 September 2012. Comments can be sent to
> public-prov-comments@w3.org
>
> We are particularly looking for feedback from the following groups:
>
> - Semantic Web Coordination Group
> - RDFa Working Group
> - RDF Working Group
> - Internationalization Activity
> - MultilingualWeb-LT Working Group
>
> We will follow-up with the chairs of these groups individually
> outlining specific areas where feedback will be useful.
>
> We look forward to hearing your comments.
>
> regards,
> Paul
>
>
> [1] http://www.w3.org/TR/2012/WD-prov-dm-20120724/
> [2] http://www.w3.org/TR/2012/WD-prov-o-20120724/
> [3] http://www.w3.org/TR/2012/WD-prov-n-20120724/
> [4] http://www.w3.org/TR/2012/WD-prov-primer-20120724/
> [5]
> http://www.w3.org/blog/SW/2012/07/24/last-call-3-working-drafts-for-provenance-interchange/
>
>
>
>
> _______________________________________________
> ietf-types mailing list
> ietf-types@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-types


Return-Path: <derhoermi@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 DCFA421F865A for <ietf-types@ietfa.amsl.com>; Fri, 27 Jul 2012 05:41:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 fvY7CGoxW2mG for <ietf-types@ietfa.amsl.com>; Fri, 27 Jul 2012 05:41:35 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by ietfa.amsl.com (Postfix) with SMTP id 93C0321F85DB for <ietf-types@ietf.org>; Fri, 27 Jul 2012 05:41:34 -0700 (PDT)
Received: (qmail invoked by alias); 27 Jul 2012 12:41:31 -0000
Received: from unknown (EHLO netb) [89.204.130.211] by mail.gmx.net (mp071) with SMTP; 27 Jul 2012 14:41:31 +0200
X-Authenticated: #723575
X-Provags-ID: V01U2FsdGVkX19aP18N1s5a+9Bl2Z7nOm8LQ5ZKqVz52J39ToPWfR xpmaeLl8HLFd/P
From: Bjoern Hoehrmann <derhoermi@gmx.net>
To: Luc Moreau <l.moreau@ecs.soton.ac.uk>
Date: Fri, 27 Jul 2012 14:41:33 +0200
Message-ID: <br2518thvu0sa5551ks3kk87ocnt6p2802@hive.bjoern.hoehrmann.de>
References: <CAJCyKRopSJr=w3N2cgsDO=GLmGsNQ99kcy6W1whQHuAZ78b2KQ@mail.gmail.com> <50126B46.8030004@ecs.soton.ac.uk> <EMEW3|0d6af10e701ec50a4d99234c93bc21cdo6QBJs08l.moreau|ecs.soton.ac.uk|50126B46.8030004@ecs.soton.ac.uk>
In-Reply-To: <EMEW3|0d6af10e701ec50a4d99234c93bc21cdo6QBJs08l.moreau|ecs.soton.ac.uk|50126B46.8030004@ecs.soton.ac.uk>
X-Mailer: Forte Agent 3.3/32.846
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
X-Y-GMX-Trusted: 0
Cc: "team-prov-chairs@w3.org" <team-prov-chairs@w3.org>, public-prov-comments@w3.org, ietf-types@ietf.org
Subject: Re: [ietf-types] Mime Type registration (PROV Last Call)
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, 27 Jul 2012 12:41:36 -0000

* Luc Moreau wrote:
>Type name:
>text
>
>Subtype name:
>provenance-notation
>
>Required parameters:
>None
>
>Optional parameters:
>charset â€” this parameter is mandatory. The value of charset is always UTF-8.

This seems to need work, it's not optional if it is mandatory, is it.
And The second sentence is a statement of fact that is easily contr-
dicted by content.

>Encoding considerations:
>The syntax of PROV-N is expressed over code points in Unicode 
>[UNICODE5]. The encoding is always UTF-8 [UTF-8].
>Unicode code points may also be expressed using an \uXXXX (U+0 to 
>U+FFFF) or \UXXXXXXXX syntax (for U+10000 onwards) where X is a 
>hexadecimal digit [0-9A-F]

This field should contain one of the values in RFC 4288 or its successor
if that has been approved already, like "binary".

>Applications which use this media type:
>No widely deployed applications are known to use this media type. It may 
>be used by some web services and clients consuming their data.

You can remove the first sentence, this is to give people an idea
whether this is for Word processing applications or cryptographic
key exchange systems or whatever.

>Person & email address to contact for further information:
>public-prov-comments@w3.org

This does not qualify as "Person & email address".
-- 
BjÃ¶rn HÃ¶hrmann Â· mailto:bjoern@hoehrmann.de Â· http://bjoern.hoehrmann.de
Am Badedeich 7 Â· Telefon: +49(0)160/4415681 Â· http://www.bjoernsworld.de
25899 DagebÃ¼ll Â· PGP Pub. KeyID: 0xA4357E78 Â· http://www.websitedev.de/ 


Return-Path: <l.moreau@ecs.soton.ac.uk>
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 A261D21F84FE for <ietf-types@ietfa.amsl.com>; Fri, 27 Jul 2012 03:19:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.598
X-Spam-Level: 
X-Spam-Status: No, score=-4.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, GB_I_LETTER=-2, HTML_MESSAGE=0.001]
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 qZdYbYE8EYUj for <ietf-types@ietfa.amsl.com>; Fri, 27 Jul 2012 03:19:56 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [IPv6:2001:630:d0:f102::25e]) by ietfa.amsl.com (Postfix) with ESMTP id 23DA621F846B for <ietf-types@ietf.org>; Fri, 27 Jul 2012 03:19:55 -0700 (PDT)
Received: from falcon.ecs.soton.ac.uk (localhost [127.0.0.1]) by falcon.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id q6RAJsSp022550;  Fri, 27 Jul 2012 11:19:54 +0100
X-DKIM: Sendmail DKIM Filter v2.8.2 falcon.ecs.soton.ac.uk q6RAJsSp022550
DKIM-Signature: v=1; a=rsa-sha1; c=simple/simple; d=ecs.soton.ac.uk; s=200903; t=1343384394; bh=7yOm6PVbDQxUnyBuOVl3bCAbX0I=; h=Date:From:MIME-Version:To:CC:Subject:References:In-Reply-To; b=GBZFJDHCAmUozVruAR74QIrTxDdPMBI3BFglfUqHfCG6OjShap21ALwWDJFNEwmQG EJ7svB8TqdpNzS/k/QqtkUs3lXVM9Y9j+oemrWHj43bZDLgYIlebZhCuUhV2zjT0VY OIpfehhyuQDX8aaV6ZP2JkMJ5LplwMah+kTme3X8=
Received: from gander.ecs.soton.ac.uk ([2001:630:d0:f102:250:56ff:fea0:401]) by falcon.ecs.soton.ac.uk (falcon.ecs.soton.ac.uk [2001:630:d0:f102:250:56ff:fea0:68da]) envelope-from <l.moreau@ecs.soton.ac.uk> with ESMTP (valid=N/A) id o6QBJs04306241635l ret-id none; Fri, 27 Jul 2012 11:19:54 +0100
Received: from smurf.ecs.soton.ac.uk ([IPv6:2001:630:d0:f111:222:4dff:fe6b:45ed]) by gander.ecs.soton.ac.uk (8.13.8/8.13.8) with ESMTP id q6RAJoFb006584;  Fri, 27 Jul 2012 11:19:50 +0100
Message-ID: <EMEW3|0d6af10e701ec50a4d99234c93bc21cdo6QBJs08l.moreau|ecs.soton.ac.uk|50126B46.8030004@ecs.soton.ac.uk>
Date: Fri, 27 Jul 2012 11:19:50 +0100
From: Luc Moreau <l.moreau@ecs.soton.ac.uk>
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:13.0) Gecko/20120615 Thunderbird/13.0.1
MIME-Version: 1.0
To: ietf-types@ietf.org
References: <CAJCyKRopSJr=w3N2cgsDO=GLmGsNQ99kcy6W1whQHuAZ78b2KQ@mail.gmail.com> <50126B46.8030004@ecs.soton.ac.uk>
In-Reply-To: <CAJCyKRopSJr=w3N2cgsDO=GLmGsNQ99kcy6W1whQHuAZ78b2KQ@mail.gmail.com>
X-Forwarded-Message-Id: <CAJCyKRopSJr=w3N2cgsDO=GLmGsNQ99kcy6W1whQHuAZ78b2KQ@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------070702060508030300070606"
X-ECS-MailScanner: Found to be clean, Found to be clean
X-smtpf-Report: sid=o6QBJs043062416300; tid=o6QBJs04306241635l; client=relay,forged,no_ptr,ipv6; mail=; rcpt=; nrcpt=4:0; fails=0
X-ECS-MailScanner-Information: Please contact the ISP for more information
X-ECS-MailScanner-ID: q6RAJsSp022550
X-ECS-MailScanner-From: l.moreau@ecs.soton.ac.uk
Cc: "team-prov-chairs@w3.org" <team-prov-chairs@w3.org>, public-prov-comments@w3.org
Subject: [ietf-types] Mime Type registration (PROV Last Call)
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, 27 Jul 2012 10:45:00 -0000

This is a multi-part message in MIME format.
--------------070702060508030300070606
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit

Dear all,

The W3C Provenance Working has published a Last Call Working Draft for 
the PROV Notation.

We would be grateful for your feedback on the Media Type section of the 
specification.

1. Media Type Section: http://www.w3.org/TR/prov-n/#media-type
2. Text Version: 
http://dvcs.w3.org/hg/prov/raw-file/default/model/media-type-request.txt

We look forward to hearing your comments,

Text version is included below, and followed by the last call announcement.

Best regards,
Luc Moreau
W3C PROV-WG co-chair

--------------------------------------------------------

The media type of PROV-N is text/provenance-notation. The content 
encoding of PROV-N content is UTF-8.

Contact:
Ivan Herman
See also:
How to Register a Media Type for a W3C Specification
Internet Media Type registration, consistency of use
TAG Finding 3 June 2002 (Revised 4 September 2002)
The Internet Media Type / MIME Type for PROV-N is 
"text/provenance-notation".

It is recommended that PROV-N files have the extension ".provn" (all 
lowercase) on all platforms.

It is recommended that PROV-N files stored on Macintosh HFS file systems 
be given a file type of "TEXT".

This information that follows is being submitted to the IESG for review, 
approval, and registration with IANA.

Type name:
text

Subtype name:
provenance-notation

Required parameters:
None

Optional parameters:
charset â€” this parameter is mandatory. The value of charset is always UTF-8.

Encoding considerations:
The syntax of PROV-N is expressed over code points in Unicode 
[UNICODE5]. The encoding is always UTF-8 [UTF-8].
Unicode code points may also be expressed using an \uXXXX (U+0 to 
U+FFFF) or \UXXXXXXXX syntax (for U+10000 onwards) where X is a 
hexadecimal digit [0-9A-F]

Security considerations:
PROV-N is a general-purpose language for describing the provenance of 
things; applications may evaluate given data to infer more descriptions 
or to dereference URIs, invoking the security considerations of the 
scheme for that URI. Note in particular, the privacy issues in [RFC3023] 
section 10 for HTTP URIs. Data obtained from an inaccurate or malicious 
data source may lead to inaccurate or misleading conclusions, as well as 
the dereferencing of unintended URIs. Care must be taken to align the 
trust in consulted resources with the sensitivity of the intended use of 
the data.
PROV-N is used to express the provenance of arbitrary application data; 
security considerations will vary by domain of use. Security tools and 
protocols applicable to text (e.g. PGP encryption, MD5 sum validation, 
password-protected compression) may also be used on PROV-N documents. 
Security/privacy protocols must be imposed which reflect the sensitivity 
of the embedded information.
PROV-N can express data which is presented to the user, for example, by 
means of label attributes. Application rendering strings retrieved from 
untrusted PROV-N documents must ensure that malignant strings may not be 
used to mislead the reader. The security considerations in the media 
type registration for XML ([RFC3023] section 10) provide additional 
guidance around the expression of arbitrary data and markup.
PROV-N is a language for describing the provenance of things, and 
therefore a PROV-N document is metadata for other resources. Untrusted 
PROV-N documents may mislead its consumers by indicating that a 
third-party resource has a reputable lineage, when it has not. 
Provenance of PROV-N document should be sought.
PROV-N uses qualified names mappeable to IRIs as term identifiers. 
Applications interpreting data expressed in PROV-N should address the 
security issues of Internationalized Resource Identifiers (IRIs) 
[RFC3987] Section 8, as well as Uniform Resource Identifier (URI): 
Generic Syntax [RFC3986] Section 7.
Multiple IRIs may have the same appearance. Characters in different 
scripts may look similar (a Cyrillic "Ð¾" may appear similar to a Latin 
"o"). A character followed by combining characters may have the same 
visual representation as another character (LATIN SMALL LETTER E 
followed by COMBINING ACUTE ACCENT has the same visual representation as 
LATIN SMALL LETTER E WITH ACUTE). Any person or application that is 
writing or interpreting data in PROV-N must take care to use the IRI 
that matches the intended semantics, and avoid IRIs that make look 
similar. Further information about matching of similar characters can be 
found in Unicode Security Considerations [UNISEC] and Internationalized 
Resource Identifiers (IRIs) [RFC3987] Section 8.
Interoperability considerations:

There are no known interoperability issues.

Published specification:
PROV-N: The Provenance Notation, Moreau, Missier, (eds), Cheney, 
Soiland-Reyes http://www.w3.org/TR/prov-n/

Applications which use this media type:
No widely deployed applications are known to use this media type. It may 
be used by some web services and clients consuming their data.

Additional information:
Magic number(s):
PROV-N documents may have the strings 'bundle' near the beginning of the 
document.

File extension(s):
".provn"

Base URI:
There are no constructs in the PROV-N Syntax to change the Base IRI.

Macintosh file type code(s):
"TEXT"

Person & email address to contact for further information:
public-prov-comments@w3.org

Intended usage:
COMMON

Restrictions on usage:
None

Author/Change controller:
The PROV-N specification is the product of the World Wide Web 
Consortium's PROV Working Group. The W3C has change control over this 
specification.


-------- Original Message --------
Subject: 	PROV Last Call on three documents: Request for Review
Resent-Date: 	Tue, 24 Jul 2012 14:53:27 +0000
Resent-From: 	<team-prov-chairs@w3.org>
Date: 	Tue, 24 Jul 2012 16:52:57 +0200
From: 	Paul Groth <p.t.groth@vu.nl>
To: 	chairs@w3.org Chairs <chairs@w3.org>
CC: 	<team-prov-chairs@w3.org>



Dear All,

The Provenance Working has published the following three drafts as
Last Call Working Drafts:

- PROV-DM: The PROV Data Model [1]
- PROV-O: The PROV Ontology [2]
- PROV-N: The Provenance Notation [3]

We are looking for your feedback. To introduce you to the
specifications, we also have published an updated Primer [4]. You'll
also find an overview blog post at [5].

The Last Call period ends 18 September 2012. Comments can be sent to
public-prov-comments@w3.org

We are particularly looking for feedback from the following groups:

- Semantic Web Coordination Group
- RDFa Working Group
- RDF Working Group
- Internationalization Activity
- MultilingualWeb-LT Working Group

We will follow-up with the chairs of these groups individually
outlining specific areas where feedback will be useful.

We look forward to hearing your comments.

regards,
Paul


[1] http://www.w3.org/TR/2012/WD-prov-dm-20120724/
[2] http://www.w3.org/TR/2012/WD-prov-o-20120724/
[3] http://www.w3.org/TR/2012/WD-prov-n-20120724/
[4] http://www.w3.org/TR/2012/WD-prov-primer-20120724/
[5] http://www.w3.org/blog/SW/2012/07/24/last-call-3-working-drafts-for-provenance-interchange/

-- 
--
Dr. Paul Groth (p.t.groth@vu.nl)
http://www.few.vu.nl/~pgroth/
Assistant Professor
- Knowledge Representation & Reasoning Group |
   Artificial Intelligence Section | Department of Computer Science
- The Network Institute
VU University Amsterdam





--------------070702060508030300070606
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=UTF-8">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    Dear all,<br>
    <br>
    <div class="moz-forward-container">The W3C Provenance Working has
      published a
      Last Call Working Draft for the PROV Notation.<br>
      <br>
      We would be grateful for your feedback on the Media Type section
      of the specification.<br>
      <br>
      1. Media Type Section: <a class="moz-txt-link-freetext" href="http://www.w3.org/TR/prov-n/#media-type">http://www.w3.org/TR/prov-n/#media-type</a><br>
      2. Text Version:
      <a class="moz-txt-link-freetext" href="http://dvcs.w3.org/hg/prov/raw-file/default/model/media-type-request.txt">http://dvcs.w3.org/hg/prov/raw-file/default/model/media-type-request.txt</a><br>
      <br>
      We look forward to hearing your comments,<br>
      <br>
      Text version is included below, and followed by the last call
      announcement.<br>
      <br>
      Best regards,<br>
      Luc Moreau<br>
      W3C PROV-WG co-chair<br>
      <br>
      --------------------------------------------------------<br>
      <br>
      The media type of PROV-N is text/provenance-notation. The content
      encoding of PROV-N content is UTF-8.<br>
      <br>
      Contact:<br>
      Ivan Herman<br>
      See also:<br>
      How to Register a Media Type for a W3C Specification<br>
      Internet Media Type registration, consistency of use<br>
      TAG Finding 3 June 2002 (Revised 4 September 2002)<br>
      The Internet Media Type / MIME Type for PROV-N is
      "text/provenance-notation".<br>
      <br>
      It is recommended that PROV-N files have the extension ".provn"
      (all lowercase) on all platforms.<br>
      <br>
      It is recommended that PROV-N files stored on Macintosh HFS file
      systems be given a file type of "TEXT".<br>
      <br>
      This information that follows is being submitted to the IESG for
      review, approval, and registration with IANA.<br>
      <br>
      Type name:<br>
      text<br>
      <br>
      Subtype name:<br>
      provenance-notation<br>
      <br>
      Required parameters:<br>
      None<br>
      <br>
      Optional parameters:<br>
      charset â€” this parameter is mandatory. The value of charset is
      always UTF-8.<br>
      <br>
      Encoding considerations:<br>
      The syntax of PROV-N is expressed over code points in Unicode
      [UNICODE5]. The encoding is always UTF-8 [UTF-8].<br>
      Unicode code points may also be expressed using an \uXXXX (U+0 to
      U+FFFF) or \UXXXXXXXX syntax (for U+10000 onwards) where X is a
      hexadecimal digit [0-9A-F]<br>
      <br>
      Security considerations:<br>
      PROV-N is a general-purpose language for describing the provenance
      of things; applications may evaluate given data to infer more
      descriptions or to dereference URIs, invoking the security
      considerations of the scheme for that URI. Note in particular, the
      privacy issues in [RFC3023] section 10 for HTTP URIs. Data
      obtained from an inaccurate or malicious data source may lead to
      inaccurate or misleading conclusions, as well as the dereferencing
      of unintended URIs. Care must be taken to align the trust in
      consulted resources with the sensitivity of the intended use of
      the data.<br>
      PROV-N is used to express the provenance of arbitrary application
      data; security considerations will vary by domain of use. Security
      tools and protocols applicable to text (e.g. PGP encryption, MD5
      sum validation, password-protected compression) may also be used
      on PROV-N documents. Security/privacy protocols must be imposed
      which reflect the sensitivity of the embedded information.<br>
      PROV-N can express data which is presented to the user, for
      example, by means of label attributes. Application rendering
      strings retrieved from untrusted PROV-N documents must ensure that
      malignant strings may not be used to mislead the reader. The
      security considerations in the media type registration for XML
      ([RFC3023] section 10) provide additional guidance around the
      expression of arbitrary data and markup.<br>
      PROV-N is a language for describing the provenance of things, and
      therefore a PROV-N document is metadata for other resources.
      Untrusted PROV-N documents may mislead its consumers by indicating
      that a third-party resource has a reputable lineage, when it has
      not. Provenance of PROV-N document should be sought.<br>
      PROV-N uses qualified names mappeable to IRIs as term identifiers.
      Applications interpreting data expressed in PROV-N should address
      the security issues of Internationalized Resource Identifiers
      (IRIs) [RFC3987] Section 8, as well as Uniform Resource Identifier
      (URI): Generic Syntax [RFC3986] Section 7.<br>
      Multiple IRIs may have the same appearance. Characters in
      different scripts may look similar (a Cyrillic "Ð¾" may appear
      similar to a Latin "o"). A character followed by combining
      characters may have the same visual representation as another
      character (LATIN SMALL LETTER E followed by COMBINING ACUTE ACCENT
      has the same visual representation as LATIN SMALL LETTER E WITH
      ACUTE). Any person or application that is writing or interpreting
      data in PROV-N must take care to use the IRI that matches the
      intended semantics, and avoid IRIs that make look similar. Further
      information about matching of similar characters can be found in
      Unicode Security Considerations [UNISEC] and Internationalized
      Resource Identifiers (IRIs) [RFC3987] Section 8.<br>
      Interoperability considerations:<br>
      <br>
      There are no known interoperability issues.<br>
      <br>
      Published specification:<br>
      PROV-N: The Provenance Notation, Moreau, Missier, (eds), Cheney,
      Soiland-Reyes <a class="moz-txt-link-freetext" href="http://www.w3.org/TR/prov-n/">http://www.w3.org/TR/prov-n/</a><br>
      <br>
      Applications which use this media type:<br>
      No widely deployed applications are known to use this media type.
      It may be used by some web services and clients consuming their
      data.<br>
      <br>
      Additional information:<br>
      Magic number(s):<br>
      PROV-N documents may have the strings 'bundle' near the beginning
      of the document.<br>
      <br>
      File extension(s):<br>
      ".provn"<br>
      <br>
      Base URI:<br>
      There are no constructs in the PROV-N Syntax to change the Base
      IRI.<br>
      <br>
      Macintosh file type code(s):<br>
      "TEXT"<br>
      <br>
      Person &amp; email address to contact for further information:<br>
      <a class="moz-txt-link-abbreviated" href="mailto:public-prov-comments@w3.org">public-prov-comments@w3.org</a><br>
      <br>
      Intended usage:<br>
      COMMON<br>
      <br>
      Restrictions on usage:<br>
      None<br>
      <br>
      Author/Change controller:<br>
      The PROV-N specification is the product of the World Wide Web
      Consortium's PROV Working Group. The W3C has change control over
      this specification.<br>
      <br>
      <br>
      -------- Original Message --------
      <table class="moz-email-headers-table" border="0" cellpadding="0"
        cellspacing="0">
        <tbody>
          <tr>
            <th align="RIGHT" nowrap="nowrap" valign="BASELINE">Subject:
            </th>
            <td>PROV Last Call on three documents: Request for Review</td>
          </tr>
          <tr>
            <th align="RIGHT" nowrap="nowrap" valign="BASELINE">Resent-Date:
            </th>
            <td>Tue, 24 Jul 2012 14:53:27 +0000</td>
          </tr>
          <tr>
            <th align="RIGHT" nowrap="nowrap" valign="BASELINE">Resent-From:
            </th>
            <td><a class="moz-txt-link-rfc2396E" href="mailto:team-prov-chairs@w3.org">&lt;team-prov-chairs@w3.org&gt;</a></td>
          </tr>
          <tr>
            <th align="RIGHT" nowrap="nowrap" valign="BASELINE">Date: </th>
            <td>Tue, 24 Jul 2012 16:52:57 +0200</td>
          </tr>
          <tr>
            <th align="RIGHT" nowrap="nowrap" valign="BASELINE">From: </th>
            <td>Paul Groth <a class="moz-txt-link-rfc2396E" href="mailto:p.t.groth@vu.nl">&lt;p.t.groth@vu.nl&gt;</a></td>
          </tr>
          <tr>
            <th align="RIGHT" nowrap="nowrap" valign="BASELINE">To: </th>
            <td><a class="moz-txt-link-abbreviated" href="mailto:chairs@w3.org">chairs@w3.org</a> Chairs <a class="moz-txt-link-rfc2396E" href="mailto:chairs@w3.org">&lt;chairs@w3.org&gt;</a></td>
          </tr>
          <tr>
            <th align="RIGHT" nowrap="nowrap" valign="BASELINE">CC: </th>
            <td><a class="moz-txt-link-rfc2396E" href="mailto:team-prov-chairs@w3.org">&lt;team-prov-chairs@w3.org&gt;</a></td>
          </tr>
        </tbody>
      </table>
      <br>
      <br>
      <pre>Dear All,

The Provenance Working has published the following three drafts as
Last Call Working Drafts:

- PROV-DM: The PROV Data Model [1]
- PROV-O: The PROV Ontology [2]
- PROV-N: The Provenance Notation [3]

We are looking for your feedback. To introduce you to the
specifications, we also have published an updated Primer [4]. You'll
also find an overview blog post at [5].

The Last Call period ends 18 September 2012. Comments can be sent to
<a class="moz-txt-link-abbreviated" href="mailto:public-prov-comments@w3.org">public-prov-comments@w3.org</a>

We are particularly looking for feedback from the following groups:

- Semantic Web Coordination Group
- RDFa Working Group
- RDF Working Group
- Internationalization Activity
- MultilingualWeb-LT Working Group

We will follow-up with the chairs of these groups individually
outlining specific areas where feedback will be useful.

We look forward to hearing your comments.

regards,
Paul


[1] <a class="moz-txt-link-freetext" href="http://www.w3.org/TR/2012/WD-prov-dm-20120724/">http://www.w3.org/TR/2012/WD-prov-dm-20120724/</a>
[2] <a class="moz-txt-link-freetext" href="http://www.w3.org/TR/2012/WD-prov-o-20120724/">http://www.w3.org/TR/2012/WD-prov-o-20120724/</a>
[3] <a class="moz-txt-link-freetext" href="http://www.w3.org/TR/2012/WD-prov-n-20120724/">http://www.w3.org/TR/2012/WD-prov-n-20120724/</a>
[4] <a class="moz-txt-link-freetext" href="http://www.w3.org/TR/2012/WD-prov-primer-20120724/">http://www.w3.org/TR/2012/WD-prov-primer-20120724/</a>
[5] <a class="moz-txt-link-freetext" href="http://www.w3.org/blog/SW/2012/07/24/last-call-3-working-drafts-for-provenance-interchange/">http://www.w3.org/blog/SW/2012/07/24/last-call-3-working-drafts-for-provenance-interchange/</a>

-- 
--
Dr. Paul Groth (<a class="moz-txt-link-abbreviated" href="mailto:p.t.groth@vu.nl">p.t.groth@vu.nl</a>)
<a class="moz-txt-link-freetext" href="http://www.few.vu.nl/~pgroth/">http://www.few.vu.nl/~pgroth/</a>
Assistant Professor
- Knowledge Representation &amp; Reasoning Group |
  Artificial Intelligence Section | Department of Computer Science
- The Network Institute
VU University Amsterdam

</pre>
      <br>
      <br>
    </div>
    <br>
  </body>
</html>

--------------070702060508030300070606--


Return-Path: <ericw3c@gmail.com>
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 43D6F21F8678 for <ietf-types@ietfa.amsl.com>; Sat, 21 Jul 2012 03:10:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.076
X-Spam-Level: 
X-Spam-Status: No, score=-2.076 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, J_CHICKENPOX_41=0.6, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-1]
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 n6-kV0KTUvvt for <ietf-types@ietfa.amsl.com>; Sat, 21 Jul 2012 03:10:28 -0700 (PDT)
Received: from mail-vc0-f172.google.com (mail-vc0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id 67F3621F8539 for <ietf-types@ietf.org>; Sat, 21 Jul 2012 03:10:28 -0700 (PDT)
Received: by vcbfo14 with SMTP id fo14so3899353vcb.31 for <ietf-types@ietf.org>; Sat, 21 Jul 2012 03:11:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=UR44VvThg3nbBWLfta/lZ1poP+eWqOnDbDFXY+LBv0U=; b=IlLtDs/qRPHEZG+5ocp6d2YQd9h0L0Q3+Na8+B0eoHN0HWl2Pyf+XGI/jYz1yUJwiu r+gLR2l8xiWjdIq1GWrp4oKNi0Cgit+6AY5hGPfCPMBClMjt3u9RfBbclBEYisHpqDp0 ItkTCFxDmeX7TwWMKzIGa5rIeSs1zBrK+uonkh3Ge+8BMBN5JmAx2mqn+kKgg4ZtV8zA wnPXzu3wKXPMlw6WhBF87FQFa4BCU+3nY4eRo3vKwNpLnZEWy+plRQx9Wb/9GpTd1b+z Ggo59bYQkHdUgNAB32ZBYZbScysVl4u9jbwZvVcCi1iO7iVJmGyagJ3VRrIi5XyiUUNg eXug==
MIME-Version: 1.0
Received: by 10.52.93.194 with SMTP id cw2mr6299592vdb.9.1342865486258; Sat, 21 Jul 2012 03:11:26 -0700 (PDT)
Sender: ericw3c@gmail.com
Received: by 10.52.156.129 with HTTP; Sat, 21 Jul 2012 03:11:25 -0700 (PDT)
Received: by 10.52.156.129 with HTTP; Sat, 21 Jul 2012 03:11:25 -0700 (PDT)
In-Reply-To: <500A5199.7030705@it.aoyama.ac.jp>
References: <CAMHjJ=Sr+pVyqSCZeJw5ECjWHjSpeu1+womAxeAO6VQCv8aT6g@mail.gmail.com> <87k3y03q69.fsf@latte.josefsson.org> <50086D95.7080004@gmx.de> <87txx2yay1.fsf@latte.josefsson.org> <50093E36.1000107@gmx.de> <vmfi08t6tr0n8aisarmurigm7f8h4j484i@hive.bjoern.hoehrmann.de> <50094599.3090804@gmx.de> <nlii08hr4iatmckce26oh8fq9u9o1fv31k@hive.bjoern.hoehrmann.de> <CANfjZH3_6TjRWtuU5R6pdg3mUZf222R-+L17OVyeLLUnS4mngA@mail.gmail.com> <CAMHjJ=R3v4QGUBAKk035juyrYoBKgN36y5A=LfF0jDimEVHeTg@mail.gmail.com> <1F8E110D-6F65-442D-922A-C88090FC33F2@hoplahup.net> <CAMHjJ=QNGKyjPToz-Z_HDcymWWvwRWCh0zTbu69tkzrn1V_Bww@mail.gmail.com> <500A5199.7030705@it.aoyama.ac.jp>
Date: Sat, 21 Jul 2012 06:11:25 -0400
X-Google-Sender-Auth: kDOg7x3UT4uDf1z5_EaQHCZ0W4M
Message-ID: <CANfjZH1p4XmFKqCEYWs9p+H_20iiqOmc0UjpWMJ-GqHiRO=Vsg@mail.gmail.com>
From: "Eric Prud'hommeaux" <eric@w3.org>
To: =?UTF-8?Q?Martin_J=2E_D=C3=BCrst?= <duerst@it.aoyama.ac.jp>
Content-Type: multipart/alternative; boundary=20cf3071c6444a216404c5543cab
Cc: Julian Reschke <julian.reschke@gmx.de>, Simon Josefsson <simon@josefsson.org>, Bjoern Hoehrmann <derhoermi@gmx.net>, ietf-types@ietf.org
Subject: Re: [ietf-types] Status of application/patch or text/patch?
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: Sat, 21 Jul 2012 10:10:29 -0000

--20cf3071c6444a216404c5543cab
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Jul 21, 2012 8:53 AM, Martin J. D=C3=BCrst <duerst@it.aoyama.ac.jp> wrot=
e:
>
> On 2012/07/21 5:49, Jon Moore wrote:
>>
>> On Fri, Jul 20, 2012 at 2:46 PM, Paul Libbrecht<paul@hoplahup.net>
 wrote:
>>>
>>> Erm... source charset makes sense to me (this is "the charset of the
patch").
>>> But target charset makes no sense into a media-type... this is "after
applying a patch" which is beyond the scope of a single file.
>>
>>
>> No, the issue is that the patch file could have mixed charsets. If the
>> change is 'convert README from iso-8859-1 to utf-8', then the patch
>> file itself will have two character sets:
>>
>> 1. The lines that begin with '-' or ' ' will be iso-8859-1.
>> 2. The lines that begin with '+' will be utf-8.
>>
>> Since these are incompatible charsets (neither is a superset of the
>> other), we need two charset parameters to describe them, and this
>> patch is not capable of being a text/* document. I'm open to other
>> names besides 'source' and 'target', but I'm not sure how we get
>> around having two of them for this case.
>
>
> Just use application/patch. I don't think current diff programs are able
to deal with character encoding parameters. I don't think people
necessarily need to know the source/target encoding in the above example,
unless something weird happens and they need to debug (in which case,
they'll find out by themselves through trial and error anyway).
>
> I also don't think there is much of a use case for:
> - Originator: Has files in Latin-1, makes a diff in that encoding,
>   sends to receiver.
> - Receiver: Has files in UTF-8, wants to apply patch and wants a
>   conversion from Latin-1 to UTF-8 to happen automatically.

I'm not saying that any conventional tools do this (though it would be nice
for them to grow into this functionality), but as someone who manages
public input on a fair number of docs, I receive a lot of 1252 or 8859
undermining my precious UTF-8 docs. If these are properly labeled, I can
iconv them our pull them into emacs and transcode them before applying
them.i expect that the burgeoning popularity of distributed version control
will accentuate this need as people become more adept at managing diffs.

> So I very much agree with Bj=C3=B6rn here.
>
> Regards,   Martin.
>
> _______________________________________________
> ietf-types mailing list
> ietf-types@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-types

--20cf3071c6444a216404c5543cab
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<p>On Jul 21, 2012 8:53 AM, Martin J. D=C3=BCrst &lt;<a href=3D"mailto:duer=
st@it.aoyama.ac.jp">duerst@it.aoyama.ac.jp</a>&gt; wrote:<br>
&gt;<br>
&gt; On 2012/07/21 5:49, Jon Moore wrote:<br>
&gt;&gt;<br>
&gt;&gt; On Fri, Jul 20, 2012 at 2:46 PM, Paul Libbrecht&lt;<a href=3D"mail=
to:paul@hoplahup.net">paul@hoplahup.net</a>&gt; =C2=A0wrote:<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; Erm... source charset makes sense to me (this is &quot;the cha=
rset of the patch&quot;).<br>
&gt;&gt;&gt; But target charset makes no sense into a media-type... this is=
 &quot;after applying a patch&quot; which is beyond the scope of a single f=
ile.<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; No, the issue is that the patch file could have mixed charsets. If=
 the<br>
&gt;&gt; change is &#39;convert README from iso-8859-1 to utf-8&#39;, then =
the patch<br>
&gt;&gt; file itself will have two character sets:<br>
&gt;&gt;<br>
&gt;&gt; 1. The lines that begin with &#39;-&#39; or &#39; &#39; will be is=
o-8859-1.<br>
&gt;&gt; 2. The lines that begin with &#39;+&#39; will be utf-8.<br>
&gt;&gt;<br>
&gt;&gt; Since these are incompatible charsets (neither is a superset of th=
e<br>
&gt;&gt; other), we need two charset parameters to describe them, and this<=
br>
&gt;&gt; patch is not capable of being a text/* document. I&#39;m open to o=
ther<br>
&gt;&gt; names besides &#39;source&#39; and &#39;target&#39;, but I&#39;m n=
ot sure how we get<br>
&gt;&gt; around having two of them for this case.<br>
&gt;<br>
&gt;<br>
&gt; Just use application/patch. I don&#39;t think current diff programs ar=
e able to deal with character encoding parameters. I don&#39;t think people=
 necessarily need to know the source/target encoding in the above example, =
unless something weird happens and they need to debug (in which case, they&=
#39;ll find out by themselves through trial and error anyway).<br>

&gt;<br>
&gt; I also don&#39;t think there is much of a use case for:<br>
&gt; - Originator: Has files in Latin-1, makes a diff in that encoding,<br>
&gt; =C2=A0 sends to receiver.<br>
&gt; - Receiver: Has files in UTF-8, wants to apply patch and wants a<br>
&gt; =C2=A0 conversion from Latin-1 to UTF-8 to happen automatically.</p>
<p>I&#39;m not saying that any conventional tools do this (though it would =
be nice for them to grow into this functionality), but as someone who manag=
es public input on a fair number of docs, I receive a lot of 1252 or 8859 u=
ndermining my precious UTF-8 docs. If these are properly labeled, I can ico=
nv them our pull them into emacs and transcode them before applying them.i =
expect that the burgeoning popularity of distributed version control will a=
ccentuate this need as people become more adept at managing diffs.</p>

<p>&gt; So I very much agree with Bj=C3=B6rn here.<br>
&gt;<br>
&gt; Regards, =C2=A0 Martin.<br>
&gt;<br>
&gt; _______________________________________________<br>
&gt; ietf-types mailing list<br>
&gt; <a href=3D"mailto:ietf-types@ietf.org">ietf-types@ietf.org</a><br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/ietf-types">https://w=
ww.ietf.org/mailman/listinfo/ietf-types</a></p>

--20cf3071c6444a216404c5543cab--


Return-Path: <duerst@it.aoyama.ac.jp>
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 31D4811E808D for <ietf-types@ietfa.amsl.com>; Fri, 20 Jul 2012 23:51:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.295
X-Spam-Level: 
X-Spam-Status: No, score=-100.295 tagged_above=-999 required=5 tests=[AWL=-0.505, BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, MIME_8BIT_HEADER=0.3, USER_IN_WHITELIST=-100]
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 rAoSKPLuABB2 for <ietf-types@ietfa.amsl.com>; Fri, 20 Jul 2012 23:51:30 -0700 (PDT)
Received: from scintmta01.scbb.aoyama.ac.jp (scintmta01.scbb.aoyama.ac.jp [133.2.253.33]) by ietfa.amsl.com (Postfix) with ESMTP id 7C78C11E8073 for <ietf-types@ietf.org>; Fri, 20 Jul 2012 23:51:30 -0700 (PDT)
Received: from scmse01.scbb.aoyama.ac.jp ([133.2.253.231]) by scintmta01.scbb.aoyama.ac.jp (secret/secret) with SMTP id q6L6qL7G011622 for <ietf-types@ietf.org>; Sat, 21 Jul 2012 15:52:22 +0900
Received: from (unknown [133.2.206.133]) by scmse01.scbb.aoyama.ac.jp with smtp id 7597_7d48_9e92b5b2_d300_11e1_af80_001d096c566a; Sat, 21 Jul 2012 15:52:20 +0900
Received: from [IPv6:::1] ([133.2.210.1]:51107) by itmail.it.aoyama.ac.jp with [XMail 1.22 ESMTP Server] id <S15E5581> for <ietf-types@ietf.org> from <duerst@it.aoyama.ac.jp>;  Sat, 21 Jul 2012 15:52:23 +0900
Message-ID: <500A5199.7030705@it.aoyama.ac.jp>
Date: Sat, 21 Jul 2012 15:52:09 +0900
From: =?UTF-8?B?Ik1hcnRpbiBKLiBEw7xyc3Qi?= <duerst@it.aoyama.ac.jp>
Organization: Aoyama Gakuin University
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.9) Gecko/20100722 Eudora/3.0.4
MIME-Version: 1.0
To: Jon Moore <jonm@jjmoore.net>
References: <CAMHjJ=Sr+pVyqSCZeJw5ECjWHjSpeu1+womAxeAO6VQCv8aT6g@mail.gmail.com>	<87k3y03q69.fsf@latte.josefsson.org> <50086D95.7080004@gmx.de>	<87txx2yay1.fsf@latte.josefsson.org> <50093E36.1000107@gmx.de>	<vmfi08t6tr0n8aisarmurigm7f8h4j484i@hive.bjoern.hoehrmann.de>	<50094599.3090804@gmx.de>	<nlii08hr4iatmckce26oh8fq9u9o1fv31k@hive.bjoern.hoehrmann.de>	<CANfjZH3_6TjRWtuU5R6pdg3mUZf222R-+L17OVyeLLUnS4mngA@mail.gmail.com>	<CAMHjJ=R3v4QGUBAKk035juyrYoBKgN36y5A=LfF0jDimEVHeTg@mail.gmail.com>	<1F8E110D-6F65-442D-922A-C88090FC33F2@hoplahup.net> <CAMHjJ=QNGKyjPToz-Z_HDcymWWvwRWCh0zTbu69tkzrn1V_Bww@mail.gmail.com>
In-Reply-To: <CAMHjJ=QNGKyjPToz-Z_HDcymWWvwRWCh0zTbu69tkzrn1V_Bww@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Cc: Julian Reschke <julian.reschke@gmx.de>, Simon Josefsson <simon@josefsson.org>, Bjoern Hoehrmann <derhoermi@gmx.net>, ietf-types@ietf.org
Subject: Re: [ietf-types] Status of application/patch or text/patch?
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: Sat, 21 Jul 2012 06:51:31 -0000

On 2012/07/21 5:49, Jon Moore wrote:
> On Fri, Jul 20, 2012 at 2:46 PM, Paul Libbrecht<paul@hoplahup.net>  wrote:
>> Erm... source charset makes sense to me (this is "the charset of the patch").
>> But target charset makes no sense into a media-type... this is "after applying a patch" which is beyond the scope of a single file.
>
> No, the issue is that the patch file could have mixed charsets. If the
> change is 'convert README from iso-8859-1 to utf-8', then the patch
> file itself will have two character sets:
>
> 1. The lines that begin with '-' or ' ' will be iso-8859-1.
> 2. The lines that begin with '+' will be utf-8.
>
> Since these are incompatible charsets (neither is a superset of the
> other), we need two charset parameters to describe them, and this
> patch is not capable of being a text/* document. I'm open to other
> names besides 'source' and 'target', but I'm not sure how we get
> around having two of them for this case.

Just use application/patch. I don't think current diff programs are able 
to deal with character encoding parameters. I don't think people 
necessarily need to know the source/target encoding in the above 
example, unless something weird happens and they need to debug (in which 
case, they'll find out by themselves through trial and error anyway).

I also don't think there is much of a use case for:
- Originator: Has files in Latin-1, makes a diff in that encoding,
   sends to receiver.
- Receiver: Has files in UTF-8, wants to apply patch and wants a
   conversion from Latin-1 to UTF-8 to happen automatically.

So I very much agree with BjÃ¶rn here.

Regards,   Martin.


Return-Path: <paul@hoplahup.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 69E8C21F85E3 for <ietf-types@ietfa.amsl.com>; Fri, 20 Jul 2012 13:54:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.649
X-Spam-Level: 
X-Spam-Status: No, score=-1.649 tagged_above=-999 required=5 tests=[AWL=0.600,  BAYES_00=-2.599, HELO_EQ_DE=0.35]
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 S8tmXdTFiRzl for <ietf-types@ietfa.amsl.com>; Fri, 20 Jul 2012 13:54:58 -0700 (PDT)
Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.17.8]) by ietfa.amsl.com (Postfix) with ESMTP id A0F4221F847E for <ietf-types@ietf.org>; Fri, 20 Jul 2012 13:54:57 -0700 (PDT)
Received: from [192.168.178.32] (p5DDEC373.dip0.t-ipconnect.de [93.222.195.115]) by mrelayeu.kundenserver.de (node=mreu4) with ESMTP (Nemesis) id 0MFW2y-1T6fiX0Ve8-00ELcF; Fri, 20 Jul 2012 22:55:53 +0200
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=iso-8859-1
From: Paul Libbrecht <paul@hoplahup.net>
In-Reply-To: <CAMHjJ=QNGKyjPToz-Z_HDcymWWvwRWCh0zTbu69tkzrn1V_Bww@mail.gmail.com>
Date: Fri, 20 Jul 2012 22:55:52 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <7FE1D2F8-1893-497E-A40E-B69DE99A5184@hoplahup.net>
References: <CAMHjJ=Sr+pVyqSCZeJw5ECjWHjSpeu1+womAxeAO6VQCv8aT6g@mail.gmail.com> <87k3y03q69.fsf@latte.josefsson.org> <50086D95.7080004@gmx.de> <87txx2yay1.fsf@latte.josefsson.org> <50093E36.1000107@gmx.de> <vmfi08t6tr0n8aisarmurigm7f8h4j484i@hive.bjoern.hoehrmann.de> <50094599.3090804@gmx.de> <nlii08hr4iatmckce26oh8fq9u9o1fv31k@hive.bjoern.hoehrmann.de> <CANfjZH3_6TjRWtuU5R6pdg3mUZf222R-+L17OVyeLLUnS4mngA@mail.gmail.com> <CAMHjJ=R3v4QGUBAKk035juyrYoBKgN36y5A=LfF0jDimEVHeTg@mail.gmail.com> <1F8E110D-6F65-442D-922A-C88090FC33F2@hoplahup.net> <CAMHjJ=QNGKyjPToz-Z_HDcymWWvwRWCh0zTbu69tkzrn1V_Bww@mail.gmail.com>
To: Jon Moore <jonm@jjmoore.net>
X-Mailer: Apple Mail (2.1084)
X-Provags-ID: V02:K0:pQQxaD7ftxnQ7P+je+r5qcL9ZoyhHcv7/5FXeqc56X7 1RbgccVwYmneHI4YM7o2+Z1VwxEwqsIyDYUHDSL8RcpzEisnsy rarr2GWvtoYuN8AuNsxeAsxQu3SsDjzWpVQDV9oSss9EEaO0oi Ujb5IeH/GWdkZyKLLqNPrzZUZHF9MgdAWzamhh6mozNvcEQNCh BGuUbIKnXBr2xM1yjScjucNU4xIDFYaEsE/NcQXNZYG/GLYEYy us1l7Ks86rB7NmsGQWrvL5RPc4yEYZ2tKr743osBgPcQkzTSFa ZeiS8rvN2x3DVvw3csx7w27EFNAHh8QbieCtUo1qwI0zUlB+77 r1zn2wYk6nPYUu0MdlEDtdtv/+bjlAPzr/tGgGvu/TeBmtLWNH vtQlpzV2oML6Q==
Cc: Julian Reschke <julian.reschke@gmx.de>, Simon Josefsson <simon@josefsson.org>, Bjoern Hoehrmann <derhoermi@gmx.net>, ietf-types@ietf.org
Subject: Re: [ietf-types] Status of application/patch or text/patch?
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 Jul 2012 20:54:58 -0000

Le 20 juil. 2012 =E0 22:49, Jon Moore a =E9crit :

> On Fri, Jul 20, 2012 at 2:46 PM, Paul Libbrecht <paul@hoplahup.net> =
wrote:
>> Erm... source charset makes sense to me (this is "the charset of the =
patch").
>> But target charset makes no sense into a media-type... this is "after =
applying a patch" which is beyond the scope of a single file.
>=20
> No, the issue is that the patch file could have mixed charsets. If the
> change is 'convert README from iso-8859-1 to utf-8', then the patch
> file itself will have two character sets:
>=20
> 1. The lines that begin with '-' or ' ' will be iso-8859-1.
> 2. The lines that begin with '+' will be utf-8.
>=20
> Since these are incompatible charsets (neither is a superset of the
> other), we need two charset parameters to describe them, and this
> patch is not capable of being a text/* document. I'm open to other
> names besides 'source' and 'target', but I'm not sure how we get
> around having two of them for this case.

Thanks Jon,

that clarifies and makes sense.

I still believe you could ignore such a difference and expect the =
patch-application-engine to know the charset of its source and thus the =
normal (single) charset annotations would suffice.

Paul




Return-Path: <jonm@jjmoore.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 A230E21F852E for <ietf-types@ietfa.amsl.com>; Fri, 20 Jul 2012 13:48:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.377
X-Spam-Level: 
X-Spam-Status: No, score=-2.377 tagged_above=-999 required=5 tests=[AWL=0.600,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
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 cMCbcbmZEVnj for <ietf-types@ietfa.amsl.com>; Fri, 20 Jul 2012 13:48:23 -0700 (PDT)
Received: from mail-gh0-f172.google.com (mail-gh0-f172.google.com [209.85.160.172]) by ietfa.amsl.com (Postfix) with ESMTP id 0125D21F846B for <ietf-types@ietf.org>; Fri, 20 Jul 2012 13:48:22 -0700 (PDT)
Received: by ghbg16 with SMTP id g16so4831263ghb.31 for <ietf-types@ietf.org>; Fri, 20 Jul 2012 13:49:19 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=KbyNIXnqho81GLXuhuvJxlRLmu7iwtNO+HU1YTMf98g=; b=IaxARDIhByT1r+wxERcQkPM0LtkdwbfEpuDcol2Z7AzPdJoUuaPTRlB8I+agFUOdyq GaOp3UCP3vQZY8FrB3+lb9bSL1XWVKQzOKSzjQR0SwvJH0GT6KiG9HzMVofjNU/iSaEC 2hzf4OxsGi0gwB9P4maD+ScZt767OzFrRF4fKfHSv72rMabpu9Vv/CzUXth0lwhWKGAB VPW3G2KBmMURDGHesxOvb9GdirNC+zMwtyEEyxW7oNWaUtAbe/GnF3rv2FgsRzT0YHTr 6SVes8ZmQP1N6M6yX/lpGOf48q4pioroCZK5wacWexDyomhjSJb6Bi+LXigQIi15CRBm uaJA==
MIME-Version: 1.0
Received: by 10.50.182.231 with SMTP id eh7mr9379777igc.42.1342817358996; Fri, 20 Jul 2012 13:49:18 -0700 (PDT)
Received: by 10.64.57.4 with HTTP; Fri, 20 Jul 2012 13:49:18 -0700 (PDT)
X-Originating-IP: [75.149.106.130]
In-Reply-To: <1F8E110D-6F65-442D-922A-C88090FC33F2@hoplahup.net>
References: <CAMHjJ=Sr+pVyqSCZeJw5ECjWHjSpeu1+womAxeAO6VQCv8aT6g@mail.gmail.com> <87k3y03q69.fsf@latte.josefsson.org> <50086D95.7080004@gmx.de> <87txx2yay1.fsf@latte.josefsson.org> <50093E36.1000107@gmx.de> <vmfi08t6tr0n8aisarmurigm7f8h4j484i@hive.bjoern.hoehrmann.de> <50094599.3090804@gmx.de> <nlii08hr4iatmckce26oh8fq9u9o1fv31k@hive.bjoern.hoehrmann.de> <CANfjZH3_6TjRWtuU5R6pdg3mUZf222R-+L17OVyeLLUnS4mngA@mail.gmail.com> <CAMHjJ=R3v4QGUBAKk035juyrYoBKgN36y5A=LfF0jDimEVHeTg@mail.gmail.com> <1F8E110D-6F65-442D-922A-C88090FC33F2@hoplahup.net>
Date: Fri, 20 Jul 2012 16:49:18 -0400
Message-ID: <CAMHjJ=QNGKyjPToz-Z_HDcymWWvwRWCh0zTbu69tkzrn1V_Bww@mail.gmail.com>
From: Jon Moore <jonm@jjmoore.net>
To: Paul Libbrecht <paul@hoplahup.net>
Content-Type: text/plain; charset=ISO-8859-1
X-Gm-Message-State: ALoCoQlfQEQyNFbQK9g67zNGMKftutHcFYQwu8KVKWnJiWc1UHrjWzv087j/XJuiXTiNs72yY0xZ
Cc: Julian Reschke <julian.reschke@gmx.de>, Simon Josefsson <simon@josefsson.org>, Bjoern Hoehrmann <derhoermi@gmx.net>, ietf-types@ietf.org
Subject: Re: [ietf-types] Status of application/patch or text/patch?
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 Jul 2012 20:48:23 -0000

On Fri, Jul 20, 2012 at 2:46 PM, Paul Libbrecht <paul@hoplahup.net> wrote:
> Erm... source charset makes sense to me (this is "the charset of the patch").
> But target charset makes no sense into a media-type... this is "after applying a patch" which is beyond the scope of a single file.

No, the issue is that the patch file could have mixed charsets. If the
change is 'convert README from iso-8859-1 to utf-8', then the patch
file itself will have two character sets:

1. The lines that begin with '-' or ' ' will be iso-8859-1.
2. The lines that begin with '+' will be utf-8.

Since these are incompatible charsets (neither is a superset of the
other), we need two charset parameters to describe them, and this
patch is not capable of being a text/* document. I'm open to other
names besides 'source' and 'target', but I'm not sure how we get
around having two of them for this case.

Jon
-- 
........
Jon Moore


Return-Path: <ericw3c@gmail.com>
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 5679321F855F for <ietf-types@ietfa.amsl.com>; Fri, 20 Jul 2012 12:06:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.076
X-Spam-Level: 
X-Spam-Status: No, score=-2.076 tagged_above=-999 required=5 tests=[AWL=-0.300, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, J_CHICKENPOX_12=0.6, J_CHICKENPOX_48=0.6, RCVD_IN_DNSWL_LOW=-1]
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 NAE6BX7GtKGE for <ietf-types@ietfa.amsl.com>; Fri, 20 Jul 2012 12:06:55 -0700 (PDT)
Received: from mail-vb0-f44.google.com (mail-vb0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id 89A3921F8505 for <ietf-types@ietf.org>; Fri, 20 Jul 2012 12:06:54 -0700 (PDT)
Received: by vbbez10 with SMTP id ez10so3543104vbb.31 for <ietf-types@ietf.org>; Fri, 20 Jul 2012 12:07:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=1ViTAlaq65+VbDtiwELyTzP0gaqK+fiuWqp5V8OXGdY=; b=jYHoBk0v9V/r7/Np7kX2wYOGCIXXb6o16x3zyO40cU4QEKZLtS1WlgovDnxAt48OS/ dhuGTyqfNOxvp/XApm2REHNesunZmvPO/HjmZj96bZJPOT112+47ccrALBgOef94pmLr kGl9EmexgOuOKO/W7jeLo8Py0Z/Q8iUO32OWRJ7sN8x4yhyH7wcyHLnsOAWrdFohGzYa QuLglCmrEOt/QzzcitucVKFInbtgc2S9bqOSOfohm5BqQEskPK9llPi/LsGc4FGQ5wtr DRptf1ruEcZp0RxgRcbfEMjWvYyHz2PJmU0l2vtRwSa4VuJHn9qPIYX/luUGxcoq2EIy Em7Q==
MIME-Version: 1.0
Received: by 10.52.176.66 with SMTP id cg2mr4735333vdc.121.1342811270881; Fri, 20 Jul 2012 12:07:50 -0700 (PDT)
Sender: ericw3c@gmail.com
Received: by 10.52.156.129 with HTTP; Fri, 20 Jul 2012 12:07:50 -0700 (PDT)
Received: by 10.52.156.129 with HTTP; Fri, 20 Jul 2012 12:07:50 -0700 (PDT)
In-Reply-To: <1F8E110D-6F65-442D-922A-C88090FC33F2@hoplahup.net>
References: <CAMHjJ=Sr+pVyqSCZeJw5ECjWHjSpeu1+womAxeAO6VQCv8aT6g@mail.gmail.com> <87k3y03q69.fsf@latte.josefsson.org> <50086D95.7080004@gmx.de> <87txx2yay1.fsf@latte.josefsson.org> <50093E36.1000107@gmx.de> <vmfi08t6tr0n8aisarmurigm7f8h4j484i@hive.bjoern.hoehrmann.de> <50094599.3090804@gmx.de> <nlii08hr4iatmckce26oh8fq9u9o1fv31k@hive.bjoern.hoehrmann.de> <CANfjZH3_6TjRWtuU5R6pdg3mUZf222R-+L17OVyeLLUnS4mngA@mail.gmail.com> <CAMHjJ=R3v4QGUBAKk035juyrYoBKgN36y5A=LfF0jDimEVHeTg@mail.gmail.com> <1F8E110D-6F65-442D-922A-C88090FC33F2@hoplahup.net>
Date: Fri, 20 Jul 2012 15:07:50 -0400
X-Google-Sender-Auth: 2YHqliA1MQtHGcZKP93400Fb5ZY
Message-ID: <CANfjZH3CFhTexivfEEzLT3cFYmke6P41TgqAEzvCXAoyBaskCw@mail.gmail.com>
From: "Eric Prud'hommeaux" <eric@w3.org>
To: Paul Libbrecht <paul@hoplahup.net>
Content-Type: multipart/alternative; boundary=20cf307f34bacd241204c5479c85
Cc: Julian Reschke <julian.reschke@gmx.de>, Simon Josefsson <simon@josefsson.org>, Bjoern Hoehrmann <derhoermi@gmx.net>, ietf-types@ietf.org
Subject: Re: [ietf-types] Status of application/patch or text/patch?
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 Jul 2012 19:06:56 -0000

--20cf307f34bacd241204c5479c85
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Jul 20, 2012 8:46 PM, "Paul Libbrecht" <paul@hoplahup.net> wrote:
>
> Erm... source charset makes sense to me (this is "the charset of the
patch").
> But target charset makes no sense into a media-type... this is "after
applying a patch" which is beyond the scope of a single file.

Just to be clear, I am quite happy to write off the encoding transformation
use case. My argument was that, even without that use case, we need a
charset. Given that constraint, we may as well use the text tree.

> Paul
>
>
> Le 20 juil. 2012 =C3=A0 17:23, Jon Moore a =C3=A9crit :
>
> > On Fri, Jul 20, 2012 at 9:40 AM, Eric Prud'hommeaux <eric@w3.org> wrote=
:
> >> Writing off this use case means I don't need to know the *resulting*
> >> character encoding, but that doesn't mean I don't want to know the
character
> >> encoding of a patch which someone mails me or I encounter on the web.
> >> Presuming that the patch matches the target is unreliable and invites =
a
> >> proliferation of doubly-encoded =C3=85s and buried f'ed up authors' na=
mes
and
> >> math symbols.
> >
> > Yes, I was thinking about this too. I believe for the application/*
> > format, we might want to have two (optional) parameters defaulting to
> > us-ascii, perhaps "source-charset" and "target-charset", as a way to
> > describe the "mixed" character set case (where I'm converting from
> > iso-8859-1 to utf-8, for example). Perhaps "charset" as a shorthand
> > for specifying both when they match. We'll have to document what the
> > precedence is among these options if they are over-specified, but this
> > seems tractable.
> >
> >> If we then say that we need a charset parameters, a naive agent
already has
> >> what it needs to suss out line breaks and render text. I'd rather not
see
> >> two media types with no principled descriminator so I'd like to see
text/
> >> with the usual charset rules.
> >
> > Agreed. If a patch can be represented as a text/* type then it should
> > have a singular charset parameter describing the patch as a whole. The
> > draft I-D(*) I'm working up (https://github.com/jonm/text-diff)
> > already contemplates this.
> >
> > Jon
> >
> > (*) I don't think what I currently have there is a viable RFC
> > candidate, so I haven't formally submitted it as an I-D yet. On the
> > other hand, saying "draft Internet-Draft" begs a certain question, and
> > I don't have enough IETF experience to make the call. Is what's there
> > useful enough to start a conversation like this one (meaning I should
> > go ahead and issue version 00 of the I-D), or should I wait until I
> > think there's something closer to a "release candidate"? Any opinions?
> > ........
> > Jon Moore
> > _______________________________________________
> > ietf-types mailing list
> > ietf-types@ietf.org
> > https://www.ietf.org/mailman/listinfo/ietf-types
>

--20cf307f34bacd241204c5479c85
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<p><br>
On Jul 20, 2012 8:46 PM, &quot;Paul Libbrecht&quot; &lt;<a href=3D"mailto:p=
aul@hoplahup.net">paul@hoplahup.net</a>&gt; wrote:<br>
&gt;<br>
&gt; Erm... source charset makes sense to me (this is &quot;the charset of =
the patch&quot;).<br>
&gt; But target charset makes no sense into a media-type... this is &quot;a=
fter applying a patch&quot; which is beyond the scope of a single file.</p>
<p>Just to be clear, I am quite happy to write off the encoding transformat=
ion use case. My argument was that, even without that use case, we need a c=
harset. Given that constraint, we may as well use the text tree.</p>
<p>&gt; Paul<br>
&gt;<br>
&gt;<br>
&gt; Le 20 juil. 2012 =C3=A0 17:23, Jon Moore a =C3=A9crit :<br>
&gt;<br>
&gt; &gt; On Fri, Jul 20, 2012 at 9:40 AM, Eric Prud&#39;hommeaux &lt;<a hr=
ef=3D"mailto:eric@w3.org">eric@w3.org</a>&gt; wrote:<br>
&gt; &gt;&gt; Writing off this use case means I don&#39;t need to know the =
*resulting*<br>
&gt; &gt;&gt; character encoding, but that doesn&#39;t mean I don&#39;t wan=
t to know the character<br>
&gt; &gt;&gt; encoding of a patch which someone mails me or I encounter on =
the web.<br>
&gt; &gt;&gt; Presuming that the patch matches the target is unreliable and=
 invites a<br>
&gt; &gt;&gt; proliferation of doubly-encoded =C3=85s and buried f&#39;ed u=
p authors&#39; names and<br>
&gt; &gt;&gt; math symbols.<br>
&gt; &gt;<br>
&gt; &gt; Yes, I was thinking about this too. I believe for the application=
/*<br>
&gt; &gt; format, we might want to have two (optional) parameters defaultin=
g to<br>
&gt; &gt; us-ascii, perhaps &quot;source-charset&quot; and &quot;target-cha=
rset&quot;, as a way to<br>
&gt; &gt; describe the &quot;mixed&quot; character set case (where I&#39;m =
converting from<br>
&gt; &gt; iso-8859-1 to utf-8, for example). Perhaps &quot;charset&quot; as=
 a shorthand<br>
&gt; &gt; for specifying both when they match. We&#39;ll have to document w=
hat the<br>
&gt; &gt; precedence is among these options if they are over-specified, but=
 this<br>
&gt; &gt; seems tractable.<br>
&gt; &gt;<br>
&gt; &gt;&gt; If we then say that we need a charset parameters, a naive age=
nt already has<br>
&gt; &gt;&gt; what it needs to suss out line breaks and render text. I&#39;=
d rather not see<br>
&gt; &gt;&gt; two media types with no principled descriminator so I&#39;d l=
ike to see text/<br>
&gt; &gt;&gt; with the usual charset rules.<br>
&gt; &gt;<br>
&gt; &gt; Agreed. If a patch can be represented as a text/* type then it sh=
ould<br>
&gt; &gt; have a singular charset parameter describing the patch as a whole=
. The<br>
&gt; &gt; draft I-D(*) I&#39;m working up (<a href=3D"https://github.com/jo=
nm/text-diff">https://github.com/jonm/text-diff</a>)<br>
&gt; &gt; already contemplates this.<br>
&gt; &gt;<br>
&gt; &gt; Jon<br>
&gt; &gt;<br>
&gt; &gt; (*) I don&#39;t think what I currently have there is a viable RFC=
<br>
&gt; &gt; candidate, so I haven&#39;t formally submitted it as an I-D yet. =
On the<br>
&gt; &gt; other hand, saying &quot;draft Internet-Draft&quot; begs a certai=
n question, and<br>
&gt; &gt; I don&#39;t have enough IETF experience to make the call. Is what=
&#39;s there<br>
&gt; &gt; useful enough to start a conversation like this one (meaning I sh=
ould<br>
&gt; &gt; go ahead and issue version 00 of the I-D), or should I wait until=
 I<br>
&gt; &gt; think there&#39;s something closer to a &quot;release candidate&q=
uot;? Any opinions?<br>
&gt; &gt; ........<br>
&gt; &gt; Jon Moore<br>
&gt; &gt; _______________________________________________<br>
&gt; &gt; ietf-types mailing list<br>
&gt; &gt; <a href=3D"mailto:ietf-types@ietf.org">ietf-types@ietf.org</a><br=
>
&gt; &gt; <a href=3D"https://www.ietf.org/mailman/listinfo/ietf-types">http=
s://www.ietf.org/mailman/listinfo/ietf-types</a><br>
&gt;<br>
</p>

--20cf307f34bacd241204c5479c85--


Return-Path: <paul@hoplahup.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 2EF2411E8098 for <ietf-types@ietfa.amsl.com>; Fri, 20 Jul 2012 11:45:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.049
X-Spam-Level: 
X-Spam-Status: No, score=-1.049 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35, J_CHICKENPOX_12=0.6, J_CHICKENPOX_48=0.6]
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 GkLv-81wYkwP for <ietf-types@ietfa.amsl.com>; Fri, 20 Jul 2012 11:45:16 -0700 (PDT)
Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.17.8]) by ietfa.amsl.com (Postfix) with ESMTP id 29C4E11E807F for <ietf-types@ietf.org>; Fri, 20 Jul 2012 11:45:15 -0700 (PDT)
Received: from [192.168.178.32] (p5DDEC373.dip0.t-ipconnect.de [93.222.195.115]) by mrelayeu.kundenserver.de (node=mrbap0) with ESMTP (Nemesis) id 0Lxdlr-1TuHcX0wnr-017IDz; Fri, 20 Jul 2012 20:46:10 +0200
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset=iso-8859-1
From: Paul Libbrecht <paul@hoplahup.net>
In-Reply-To: <CAMHjJ=R3v4QGUBAKk035juyrYoBKgN36y5A=LfF0jDimEVHeTg@mail.gmail.com>
Date: Fri, 20 Jul 2012 20:46:09 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <1F8E110D-6F65-442D-922A-C88090FC33F2@hoplahup.net>
References: <CAMHjJ=Sr+pVyqSCZeJw5ECjWHjSpeu1+womAxeAO6VQCv8aT6g@mail.gmail.com> <87k3y03q69.fsf@latte.josefsson.org> <50086D95.7080004@gmx.de> <87txx2yay1.fsf@latte.josefsson.org> <50093E36.1000107@gmx.de> <vmfi08t6tr0n8aisarmurigm7f8h4j484i@hive.bjoern.hoehrmann.de> <50094599.3090804@gmx.de> <nlii08hr4iatmckce26oh8fq9u9o1fv31k@hive.bjoern.hoehrmann.de> <CANfjZH3_6TjRWtuU5R6pdg3mUZf222R-+L17OVyeLLUnS4mngA@mail.gmail.com> <CAMHjJ=R3v4QGUBAKk035juyrYoBKgN36y5A=LfF0jDimEVHeTg@mail.gmail.com>
To: Jon Moore <jonm@jjmoore.net>
X-Mailer: Apple Mail (2.1084)
X-Provags-ID: V02:K0:M6KajnFF9wyQ0Kl4Ms/zuaqnUoAROWrXXdYpUMWd9Co hdTGxc5XJdkCYgSEXVL++5sbp9IFCEGGp32NzrPu99v/HUGl2T 7Q4QCtBdI4FrmlNIEx28HD2viErUHSOhGRm+PyXSJSMOPVZOpW wnitZQRLgwTAYz7DRaL5NPjZ7A+dBv4fNmW10HJ/LllGtiSkem Bbkd8h+8krmGJc3qdHBFkMO11FzdDLs4v13bWJS+k7PzsOsyaH W2Cf+Xr89vLnx2WAh7baR6RVFrPaKCj5hW44i1FbaIWkxnNtKX JBmp9mG4ZTAgotvrGMhbHt/Q8RLGsoVL06K4N51WmbV4wH0sn4 HGvpATERwxVVzamJeJHpAAwXOHNseeT+tuL8wTfwbYxipTRK/h O8jzACktKbMXQ==
Cc: Julian Reschke <julian.reschke@gmx.de>, Simon Josefsson <simon@josefsson.org>, Bjoern Hoehrmann <derhoermi@gmx.net>, ietf-types@ietf.org
Subject: Re: [ietf-types] Status of application/patch or text/patch?
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 Jul 2012 18:45:17 -0000

Erm... source charset makes sense to me (this is "the charset of the =
patch").
But target charset makes no sense into a media-type... this is "after =
applying a patch" which is beyond the scope of a single file.

Paul


Le 20 juil. 2012 =E0 17:23, Jon Moore a =E9crit :

> On Fri, Jul 20, 2012 at 9:40 AM, Eric Prud'hommeaux <eric@w3.org> =
wrote:
>> Writing off this use case means I don't need to know the *resulting*
>> character encoding, but that doesn't mean I don't want to know the =
character
>> encoding of a patch which someone mails me or I encounter on the web.
>> Presuming that the patch matches the target is unreliable and invites =
a
>> proliferation of doubly-encoded =C5s and buried f'ed up authors' =
names and
>> math symbols.
>=20
> Yes, I was thinking about this too. I believe for the application/*
> format, we might want to have two (optional) parameters defaulting to
> us-ascii, perhaps "source-charset" and "target-charset", as a way to
> describe the "mixed" character set case (where I'm converting from
> iso-8859-1 to utf-8, for example). Perhaps "charset" as a shorthand
> for specifying both when they match. We'll have to document what the
> precedence is among these options if they are over-specified, but this
> seems tractable.
>=20
>> If we then say that we need a charset parameters, a naive agent =
already has
>> what it needs to suss out line breaks and render text. I'd rather not =
see
>> two media types with no principled descriminator so I'd like to see =
text/
>> with the usual charset rules.
>=20
> Agreed. If a patch can be represented as a text/* type then it should
> have a singular charset parameter describing the patch as a whole. The
> draft I-D(*) I'm working up (https://github.com/jonm/text-diff)
> already contemplates this.
>=20
> Jon
>=20
> (*) I don't think what I currently have there is a viable RFC
> candidate, so I haven't formally submitted it as an I-D yet. On the
> other hand, saying "draft Internet-Draft" begs a certain question, and
> I don't have enough IETF experience to make the call. Is what's there
> useful enough to start a conversation like this one (meaning I should
> go ahead and issue version 00 of the I-D), or should I wait until I
> think there's something closer to a "release candidate"? Any opinions?
> ........
> Jon Moore
> _______________________________________________
> ietf-types mailing list
> ietf-types@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-types



Return-Path: <jonm@jjmoore.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 9CF5221F8617 for <ietf-types@ietfa.amsl.com>; Fri, 20 Jul 2012 08:22:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.777
X-Spam-Level: 
X-Spam-Status: No, score=-1.777 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, J_CHICKENPOX_12=0.6, J_CHICKENPOX_48=0.6, RCVD_IN_DNSWL_LOW=-1]
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 sbQNQcDczXgo for <ietf-types@ietfa.amsl.com>; Fri, 20 Jul 2012 08:22:41 -0700 (PDT)
Received: from mail-yx0-f172.google.com (mail-yx0-f172.google.com [209.85.213.172]) by ietfa.amsl.com (Postfix) with ESMTP id 1287F21F84D5 for <ietf-types@ietf.org>; Fri, 20 Jul 2012 08:22:40 -0700 (PDT)
Received: by yenq13 with SMTP id q13so4485153yen.31 for <ietf-types@ietf.org>; Fri, 20 Jul 2012 08:23:30 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding:x-gm-message-state; bh=nmQC3y/n4tI+0VAtigKAKgkYZFeZPkj+tqOFGgAXjzo=; b=WQ0UoUmMPXhh0R1rkMO+Ity+5IaVOssvnZxWRRPGSAFYEsQdOArHNtySgH+41+hDj5 +YYn00MeAffJNmGBBDlrT+u8mXBJX5WxtlhY/81WBOl28BUNINscbEsobOGoKJ1086HR m1Q0btJfIYYPk9LSBHgRnZU5pNJS1CEUG2OzfCnatqrW8vC+buasXwWosnQYugQR8yvL J/wtgLw3F68+fguuYeBYIq1evc30COjOqMo0kTTtMpC4sU4RTj1xPeqCxo8OB/rYnmks XbkyrQCcuWYeIF2Frc24ee8hVk6XfTCYLNjPF4SDC4wrlWMPiKUCip7K+2jQnQdVvti6 OA9g==
MIME-Version: 1.0
Received: by 10.50.203.98 with SMTP id kp2mr4780418igc.42.1342797810210; Fri, 20 Jul 2012 08:23:30 -0700 (PDT)
Received: by 10.64.57.4 with HTTP; Fri, 20 Jul 2012 08:23:30 -0700 (PDT)
X-Originating-IP: [75.149.106.130]
In-Reply-To: <CANfjZH3_6TjRWtuU5R6pdg3mUZf222R-+L17OVyeLLUnS4mngA@mail.gmail.com>
References: <CAMHjJ=Sr+pVyqSCZeJw5ECjWHjSpeu1+womAxeAO6VQCv8aT6g@mail.gmail.com> <87k3y03q69.fsf@latte.josefsson.org> <50086D95.7080004@gmx.de> <87txx2yay1.fsf@latte.josefsson.org> <50093E36.1000107@gmx.de> <vmfi08t6tr0n8aisarmurigm7f8h4j484i@hive.bjoern.hoehrmann.de> <50094599.3090804@gmx.de> <nlii08hr4iatmckce26oh8fq9u9o1fv31k@hive.bjoern.hoehrmann.de> <CANfjZH3_6TjRWtuU5R6pdg3mUZf222R-+L17OVyeLLUnS4mngA@mail.gmail.com>
Date: Fri, 20 Jul 2012 11:23:30 -0400
Message-ID: <CAMHjJ=R3v4QGUBAKk035juyrYoBKgN36y5A=LfF0jDimEVHeTg@mail.gmail.com>
From: Jon Moore <jonm@jjmoore.net>
To: "Eric Prud'hommeaux" <eric@w3.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Gm-Message-State: ALoCoQm+IPx2woRb8f84OkHvr8n4ktBKfNmV4MwtqybsU38MTVtGCuyc413WqCVN1iVY91jj6Unt
Cc: Julian Reschke <julian.reschke@gmx.de>, Simon Josefsson <simon@josefsson.org>, Bjoern Hoehrmann <derhoermi@gmx.net>, ietf-types@ietf.org
Subject: Re: [ietf-types] Status of application/patch or text/patch?
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 Jul 2012 15:22:42 -0000

On Fri, Jul 20, 2012 at 9:40 AM, Eric Prud'hommeaux <eric@w3.org> wrote:
> Writing off this use case means I don't need to know the *resulting*
> character encoding, but that doesn't mean I don't want to know the charac=
ter
> encoding of a patch which someone mails me or I encounter on the web.
> Presuming that the patch matches the target is unreliable and invites a
> proliferation of doubly-encoded =C5s and buried f'ed up authors' names an=
d
> math symbols.

Yes, I was thinking about this too. I believe for the application/*
format, we might want to have two (optional) parameters defaulting to
us-ascii, perhaps "source-charset" and "target-charset", as a way to
describe the "mixed" character set case (where I'm converting from
iso-8859-1 to utf-8, for example). Perhaps "charset" as a shorthand
for specifying both when they match. We'll have to document what the
precedence is among these options if they are over-specified, but this
seems tractable.

> If we then say that we need a charset parameters, a naive agent already h=
as
> what it needs to suss out line breaks and render text. I'd rather not see
> two media types with no principled descriminator so I'd like to see text/
> with the usual charset rules.

Agreed. If a patch can be represented as a text/* type then it should
have a singular charset parameter describing the patch as a whole. The
draft I-D(*) I'm working up (https://github.com/jonm/text-diff)
already contemplates this.

Jon

(*) I don't think what I currently have there is a viable RFC
candidate, so I haven't formally submitted it as an I-D yet. On the
other hand, saying "draft Internet-Draft" begs a certain question, and
I don't have enough IETF experience to make the call. Is what's there
useful enough to start a conversation like this one (meaning I should
go ahead and issue version 00 of the I-D), or should I wait until I
think there's something closer to a "release candidate"? Any opinions?
........
Jon Moore


Return-Path: <ericw3c@gmail.com>
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 3A78D21F8608 for <ietf-types@ietfa.amsl.com>; Fri, 20 Jul 2012 06:39:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.376
X-Spam-Level: 
X-Spam-Status: No, score=-2.376 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, J_CHICKENPOX_12=0.6, RCVD_IN_DNSWL_LOW=-1]
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 Q1RC2sE-2rhR for <ietf-types@ietfa.amsl.com>; Fri, 20 Jul 2012 06:39:09 -0700 (PDT)
Received: from mail-vb0-f44.google.com (mail-vb0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id E905B21F8598 for <ietf-types@ietf.org>; Fri, 20 Jul 2012 06:39:08 -0700 (PDT)
Received: by vbbez10 with SMTP id ez10so3231802vbb.31 for <ietf-types@ietf.org>; Fri, 20 Jul 2012 06:40:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=qg3CVLdUWqhi19urIRpBdOcug78iUC8p23yictOi9cE=; b=lmbr83r+FzyuwjJF9HOs6tJlSJfUzFFK+arCraJ3cH2kFT+mqtBS72OihYQ0IiMhtf GvuC2HesMrJIHHhDOE9i663NXb88psiT72MtfQECvWgm/dfaYrCf86PIAFregC0M9nms tAi0y0vJVTeWOI2y745V6Rj4aW7JVBkeqmo8444yUL8PGCTRpEOUlSviDf9wgrcBhbIa mmTAS+S45zlLqALZ1Wg8wfjYxOJXGMlNdxbJK1ghVa52xfE3TQ/SrEfGrmIh0JBeO46J qlp/+65SkrFlp6O9IPwVZYbDw580Yr/gH6ke7K5PwdOVzsYzolVEZJKhiZHK9C3sJ3X4 pG1Q==
MIME-Version: 1.0
Received: by 10.220.223.201 with SMTP id il9mr4452762vcb.64.1342791602415; Fri, 20 Jul 2012 06:40:02 -0700 (PDT)
Sender: ericw3c@gmail.com
Received: by 10.52.156.129 with HTTP; Fri, 20 Jul 2012 06:40:01 -0700 (PDT)
Received: by 10.52.156.129 with HTTP; Fri, 20 Jul 2012 06:40:01 -0700 (PDT)
In-Reply-To: <nlii08hr4iatmckce26oh8fq9u9o1fv31k@hive.bjoern.hoehrmann.de>
References: <CAMHjJ=Sr+pVyqSCZeJw5ECjWHjSpeu1+womAxeAO6VQCv8aT6g@mail.gmail.com> <87k3y03q69.fsf@latte.josefsson.org> <50086D95.7080004@gmx.de> <87txx2yay1.fsf@latte.josefsson.org> <50093E36.1000107@gmx.de> <vmfi08t6tr0n8aisarmurigm7f8h4j484i@hive.bjoern.hoehrmann.de> <50094599.3090804@gmx.de> <nlii08hr4iatmckce26oh8fq9u9o1fv31k@hive.bjoern.hoehrmann.de>
Date: Fri, 20 Jul 2012 09:40:01 -0400
X-Google-Sender-Auth: d35lt8T67EZKcsSpbYWM9E_81vg
Message-ID: <CANfjZH3_6TjRWtuU5R6pdg3mUZf222R-+L17OVyeLLUnS4mngA@mail.gmail.com>
From: "Eric Prud'hommeaux" <eric@w3.org>
To: Bjoern Hoehrmann <derhoermi@gmx.net>
Content-Type: multipart/alternative; boundary=14dae9cdc47f78278f04c54308ed
Cc: Julian Reschke <julian.reschke@gmx.de>, Simon Josefsson <simon@josefsson.org>, ietf-types@ietf.org
Subject: Re: [ietf-types] Status of application/patch or text/patch?
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 Jul 2012 13:39:10 -0000

--14dae9cdc47f78278f04c54308ed
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On Jul 20, 2012 2:13 PM, "Bjoern Hoehrmann" <derhoermi@gmx.net> wrote:
>
> * Julian Reschke wrote:
> >So do you believe we need a variant that is encoding-agnostics except
> >for CRLF detection?
>
> Certainly. An "encoding-aware" variant seems much less necessary.

Writing off this use case means I don't need to know the *resulting*
character encoding, but that doesn't mean I don't want to know the
character encoding of a patch which someone mails me or I encounter on the
web. Presuming that the patch matches the target is unreliable and invites
a proliferation of doubly-encoded =C3=85s and buried f'ed up authors' names=
 and
math symbols.

If we then say that we need a charset parameters, a naive agent already has
what it needs to suss out line breaks and render text. I'd rather not see
two media types with no principled descriminator so I'd like to see text/
with the usual charset rules.

> --
> Bj=C3=B6rn H=C3=B6hrmann =C2=B7 mailto:bjoern@hoehrmann.de =C2=B7 http://=
bjoern.hoehrmann.de
> Am Badedeich 7 =C2=B7 Telefon: +49(0)160/4415681 =C2=B7 http://www.bjoern=
sworld.de
> 25899 Dageb=C3=BCll =C2=B7 PGP Pub. KeyID: 0xA4357E78 =C2=B7 http://www.w=
ebsitedev.de/
> _______________________________________________
> ietf-types mailing list
> ietf-types@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-types

--14dae9cdc47f78278f04c54308ed
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<p>On Jul 20, 2012 2:13 PM, &quot;Bjoern Hoehrmann&quot; &lt;<a href=3D"mai=
lto:derhoermi@gmx.net">derhoermi@gmx.net</a>&gt; wrote:<br>
&gt;<br>
&gt; * Julian Reschke wrote:<br>
&gt; &gt;So do you believe we need a variant that is encoding-agnostics exc=
ept<br>
&gt; &gt;for CRLF detection?<br>
&gt;<br>
&gt; Certainly. An &quot;encoding-aware&quot; variant seems much less neces=
sary.</p>
<p>Writing off this use case means I don&#39;t need to know the *resulting*=
 character encoding, but that doesn&#39;t mean I don&#39;t want to know the=
 character encoding of a patch which someone mails me or I encounter on the=
 web. Presuming that the patch matches the target is unreliable and invites=
 a proliferation of doubly-encoded =C3=85s and buried f&#39;ed up authors&#=
39; names and math symbols.</p>

<p>If we then say that we need a charset parameters, a naive agent already =
has what it needs to suss out line breaks and render text. I&#39;d rather n=
ot see two media types with no principled descriminator so I&#39;d like to =
see text/ with the usual charset rules.</p>

<p>&gt; --<br>
&gt; Bj=C3=B6rn H=C3=B6hrmann =C2=B7 mailto:<a href=3D"mailto:bjoern@hoehrm=
ann.de">bjoern@hoehrmann.de</a> =C2=B7 <a href=3D"http://bjoern.hoehrmann.d=
e">http://bjoern.hoehrmann.de</a><br>
&gt; Am Badedeich 7 =C2=B7 Telefon: +49(0)160/4415681 =C2=B7 <a href=3D"htt=
p://www.bjoernsworld.de">http://www.bjoernsworld.de</a><br>
&gt; 25899 Dageb=C3=BCll =C2=B7 PGP Pub. KeyID: 0xA4357E78 =C2=B7 <a href=
=3D"http://www.websitedev.de/">http://www.websitedev.de/</a><br>
&gt; _______________________________________________<br>
&gt; ietf-types mailing list<br>
&gt; <a href=3D"mailto:ietf-types@ietf.org">ietf-types@ietf.org</a><br>
&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/ietf-types">https://w=
ww.ietf.org/mailman/listinfo/ietf-types</a><br>
</p>

--14dae9cdc47f78278f04c54308ed--


Return-Path: <derhoermi@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 6D7D121F85D3 for <ietf-types@ietfa.amsl.com>; Fri, 20 Jul 2012 05:12:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 eTBUWKxhu-Em for <ietf-types@ietfa.amsl.com>; Fri, 20 Jul 2012 05:12:06 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by ietfa.amsl.com (Postfix) with SMTP id E3CD421F85C6 for <ietf-types@ietf.org>; Fri, 20 Jul 2012 05:12:02 -0700 (PDT)
Received: (qmail invoked by alias); 20 Jul 2012 12:12:57 -0000
Received: from p5B232442.dip.t-dialin.net (EHLO netb.fritz.box) [91.35.36.66] by mail.gmx.net (mp041) with SMTP; 20 Jul 2012 14:12:57 +0200
X-Authenticated: #723575
X-Provags-ID: V01U2FsdGVkX1+En7RFfP6EU3bDqEthWolqqzQGTBXiORH5dmQpCm EVvZ4PNMm7J5Jg
From: Bjoern Hoehrmann <derhoermi@gmx.net>
To: Julian Reschke <julian.reschke@gmx.de>
Date: Fri, 20 Jul 2012 14:13:01 +0200
Message-ID: <nlii08hr4iatmckce26oh8fq9u9o1fv31k@hive.bjoern.hoehrmann.de>
References: <CAMHjJ=Sr+pVyqSCZeJw5ECjWHjSpeu1+womAxeAO6VQCv8aT6g@mail.gmail.com> <87k3y03q69.fsf@latte.josefsson.org> <50086D95.7080004@gmx.de> <87txx2yay1.fsf@latte.josefsson.org> <50093E36.1000107@gmx.de> <vmfi08t6tr0n8aisarmurigm7f8h4j484i@hive.bjoern.hoehrmann.de> <50094599.3090804@gmx.de>
In-Reply-To: <50094599.3090804@gmx.de>
X-Mailer: Forte Agent 3.3/32.846
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Y-GMX-Trusted: 0
Cc: Simon Josefsson <simon@josefsson.org>, ietf-types@ietf.org
Subject: Re: [ietf-types] Status of application/patch or text/patch?
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 Jul 2012 12:12:08 -0000

* Julian Reschke wrote:
>So do you believe we need a variant that is encoding-agnostics except 
>for CRLF detection?

Certainly. An "encoding-aware" variant seems much less necessary.
-- 
Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de
Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de
25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/ 


Return-Path: <julian.reschke@gmx.de>
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 3773421F8593 for <ietf-types@ietfa.amsl.com>; Fri, 20 Jul 2012 04:47:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.323
X-Spam-Level: 
X-Spam-Status: No, score=-104.323 tagged_above=-999 required=5 tests=[AWL=-1.724, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 8bFSSYB6W-sD for <ietf-types@ietfa.amsl.com>; Fri, 20 Jul 2012 04:47:48 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by ietfa.amsl.com (Postfix) with SMTP id 46DED21F858A for <ietf-types@ietf.org>; Fri, 20 Jul 2012 04:47:48 -0700 (PDT)
Received: (qmail invoked by alias); 20 Jul 2012 11:48:43 -0000
Received: from mail.greenbytes.de (EHLO [192.168.1.140]) [217.91.35.233] by mail.gmx.net (mp012) with SMTP; 20 Jul 2012 13:48:43 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX19feaYAdjJfiSlcu3mq/fO7xqzo6Zvs+gFYx3a3wq ovMQ8jio4StKNH
Message-ID: <50094599.3090804@gmx.de>
Date: Fri, 20 Jul 2012 13:48:41 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: Bjoern Hoehrmann <derhoermi@gmx.net>
References: <CAMHjJ=Sr+pVyqSCZeJw5ECjWHjSpeu1+womAxeAO6VQCv8aT6g@mail.gmail.com> <87k3y03q69.fsf@latte.josefsson.org> <50086D95.7080004@gmx.de> <87txx2yay1.fsf@latte.josefsson.org> <50093E36.1000107@gmx.de> <vmfi08t6tr0n8aisarmurigm7f8h4j484i@hive.bjoern.hoehrmann.de>
In-Reply-To: <vmfi08t6tr0n8aisarmurigm7f8h4j484i@hive.bjoern.hoehrmann.de>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: Simon Josefsson <simon@josefsson.org>, ietf-types@ietf.org
Subject: Re: [ietf-types] Status of application/patch or text/patch?
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 Jul 2012 11:47:49 -0000

On 2012-07-20 13:22, Bjoern Hoehrmann wrote:
> * Julian Reschke wrote:
>> On 2012-07-20 12:38, Simon Josefsson wrote:
>>> * It can deal with diff's of files with different character sets,
>>>     e.g. converting ISO-8859-1 files to UTF-8.  Like the draft says now,
>>>     the text/* approach is unable to deal with this.
>>
>> I don't see that the problem is.
>>
>>  From a media type of view, the patch consists on instructions how to
>> patch certain lines in a text file. So to make this work properly, the
>> encoding of both the patch and the file-to-be-patched need to be known,
>> but they don't need to be the same.
>
> So, if you have a patch file that turns a ISO-8859-1 encoded file into
> a UTF-8 encoded file, what would be "the encoding" of the patch file?

Always these trick questions :-)

So do you believe we need a variant that is encoding-agnostics except 
for CRLF detection?

Best regards, Julian



Return-Path: <derhoermi@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 982A721F84B3 for <ietf-types@ietfa.amsl.com>; Fri, 20 Jul 2012 04:21:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 JYINhW2FDKtj for <ietf-types@ietfa.amsl.com>; Fri, 20 Jul 2012 04:21:51 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by ietfa.amsl.com (Postfix) with SMTP id 92AF521F84A0 for <ietf-types@ietf.org>; Fri, 20 Jul 2012 04:21:50 -0700 (PDT)
Received: (qmail invoked by alias); 20 Jul 2012 11:22:45 -0000
Received: from p5B232442.dip.t-dialin.net (EHLO netb.fritz.box) [91.35.36.66] by mail.gmx.net (mp001) with SMTP; 20 Jul 2012 13:22:45 +0200
X-Authenticated: #723575
X-Provags-ID: V01U2FsdGVkX18kHIAy6LwkjJS2k4j2Fk8W3po7tE3Fv1miJhNCZw qvS93cySSCbuVJ
From: Bjoern Hoehrmann <derhoermi@gmx.net>
To: Julian Reschke <julian.reschke@gmx.de>
Date: Fri, 20 Jul 2012 13:22:48 +0200
Message-ID: <vmfi08t6tr0n8aisarmurigm7f8h4j484i@hive.bjoern.hoehrmann.de>
References: <CAMHjJ=Sr+pVyqSCZeJw5ECjWHjSpeu1+womAxeAO6VQCv8aT6g@mail.gmail.com> <87k3y03q69.fsf@latte.josefsson.org> <50086D95.7080004@gmx.de> <87txx2yay1.fsf@latte.josefsson.org> <50093E36.1000107@gmx.de>
In-Reply-To: <50093E36.1000107@gmx.de>
X-Mailer: Forte Agent 3.3/32.846
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
X-Y-GMX-Trusted: 0
Cc: Simon Josefsson <simon@josefsson.org>, ietf-types@ietf.org
Subject: Re: [ietf-types] Status of application/patch or text/patch?
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 Jul 2012 11:21:56 -0000

* Julian Reschke wrote:
>On 2012-07-20 12:38, Simon Josefsson wrote:
>> * It can deal with diff's of files with different character sets,
>>    e.g. converting ISO-8859-1 files to UTF-8.  Like the draft says now,
>>    the text/* approach is unable to deal with this.
>
>I don't see that the problem is.
>
> From a media type of view, the patch consists on instructions how to 
>patch certain lines in a text file. So to make this work properly, the 
>encoding of both the patch and the file-to-be-patched need to be known, 
>but they don't need to be the same.

So, if you have a patch file that turns a ISO-8859-1 encoded file into
a UTF-8 encoded file, what would be "the encoding" of the patch file?
-- 
Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de
Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de
25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/ 


Return-Path: <julian.reschke@gmx.de>
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 0F9B021F855B for <ietf-types@ietfa.amsl.com>; Fri, 20 Jul 2012 04:16:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.346
X-Spam-Level: 
X-Spam-Status: No, score=-104.346 tagged_above=-999 required=5 tests=[AWL=-1.747, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 cUddrr0UYCWA for <ietf-types@ietfa.amsl.com>; Fri, 20 Jul 2012 04:16:20 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.22]) by ietfa.amsl.com (Postfix) with SMTP id 20B8921F84C4 for <ietf-types@ietf.org>; Fri, 20 Jul 2012 04:16:17 -0700 (PDT)
Received: (qmail invoked by alias); 20 Jul 2012 11:17:12 -0000
Received: from mail.greenbytes.de (EHLO [192.168.1.140]) [217.91.35.233] by mail.gmx.net (mp034) with SMTP; 20 Jul 2012 13:17:12 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX1+WEEpDd0WWaLI8ZqdRuaP9Zc7bbq+1wXYVd85mk7 cQBG3FVLycexOM
Message-ID: <50093E36.1000107@gmx.de>
Date: Fri, 20 Jul 2012 13:17:10 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: Simon Josefsson <simon@josefsson.org>
References: <CAMHjJ=Sr+pVyqSCZeJw5ECjWHjSpeu1+womAxeAO6VQCv8aT6g@mail.gmail.com> <87k3y03q69.fsf@latte.josefsson.org> <50086D95.7080004@gmx.de> <87txx2yay1.fsf@latte.josefsson.org>
In-Reply-To: <87txx2yay1.fsf@latte.josefsson.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: ietf-types@ietf.org
Subject: Re: [ietf-types] Status of application/patch or text/patch?
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 Jul 2012 11:16:21 -0000

On 2012-07-20 12:38, Simon Josefsson wrote:
> ...
> Some reasons that I had in mind were:
>
> * There is no character set issues -- the encoder doesn't need to know
>    which character encoding was used.  The specification doesn't have to
>    talk about character sets (which makes up a big chunk of the current
>    spec.)
> ...

The encoder needs to be aware of lines, which implies that it knows that 
octet sequence(s) are line endings.

> * It can deal with diff's of files with different character sets,
>    e.g. converting ISO-8859-1 files to UTF-8.  Like the draft says now,
>    the text/* approach is unable to deal with this.

I don't see that the problem is.

 From a media type of view, the patch consists on instructions how to 
patch certain lines in a text file. So to make this work properly, the 
encoding of both the patch and the file-to-be-patched need to be known, 
but they don't need to be the same.

> * Sometimes text/* parts are modified by gateways, and this is usually
>    avoided by using an application/* type.  So the spec doesn't have to
>    talk about these concerns.

If a gateway every changed the charset, it would need to do it properly. 
Otherwise it's broken anyway (and I would be surprised if it handled 
PATCH properly).

> However I support doing both media types.  For some situations,
> text/patch is appropriate.
>
> /Simon

Best regards, Julian



Return-Path: <simon@josefsson.org>
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 879EC21F85C6 for <ietf-types@ietfa.amsl.com>; Fri, 20 Jul 2012 03:37:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.909
X-Spam-Level: 
X-Spam-Status: No, score=-99.909 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, HELO_MISMATCH_COM=0.553, HOST_EQ_STATICB=1.372, USER_IN_WHITELIST=-100]
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 RoXxtDFvly1z for <ietf-types@ietfa.amsl.com>; Fri, 20 Jul 2012 03:37:48 -0700 (PDT)
Received: from yxa-v.extundo.com (static-213-115-179-173.sme.bredbandsbolaget.se [213.115.179.173]) by ietfa.amsl.com (Postfix) with ESMTP id 887D621F85C2 for <ietf-types@ietf.org>; Fri, 20 Jul 2012 03:37:46 -0700 (PDT)
Received: from latte (static-213-115-179-130.sme.bredbandsbolaget.se [213.115.179.130]) (authenticated bits=0) by yxa-v.extundo.com (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id q6KAcFqM012468 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Fri, 20 Jul 2012 12:38:27 +0200
From: Simon Josefsson <simon@josefsson.org>
To: Julian Reschke <julian.reschke@gmx.de>
References: <CAMHjJ=Sr+pVyqSCZeJw5ECjWHjSpeu1+womAxeAO6VQCv8aT6g@mail.gmail.com> <87k3y03q69.fsf@latte.josefsson.org> <50086D95.7080004@gmx.de>
OpenPGP: id=B565716F; url=http://josefsson.org/key.txt
X-Hashcash: 1:22:120720:julian.reschke@gmx.de::kEQnJgYufcgT9/HH:7wqb
X-Hashcash: 1:22:120720:ietf-types@ietf.org::Zm/Yoe17JNuUxxQP:HFDq
Date: Fri, 20 Jul 2012 12:38:14 +0200
In-Reply-To: <50086D95.7080004@gmx.de> (Julian Reschke's message of "Thu, 19 Jul 2012 22:27:01 +0200")
Message-ID: <87txx2yay1.fsf@latte.josefsson.org>
User-Agent: Gnus/5.130006 (Ma Gnus v0.6) Emacs/23.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
X-Virus-Scanned: clamav-milter 0.97.3 at yxa-v
X-Virus-Status: Clean
Cc: ietf-types@ietf.org
Subject: Re: [ietf-types] Status of application/patch or text/patch?
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 Jul 2012 10:37:48 -0000

Julian Reschke <julian.reschke@gmx.de> writes:

> On 2012-07-19 14:12, Simon Josefsson wrote:
>> Jon Moore <jonm@jjmoore.net> writes:
>>
>>> Hi folks,
>>>
>>> Given the recent arrival of HTTP PATCH in RFC 5789[1], it seems like
>>> registering a media type for the output of the 'diff' utility would be
>>> a good idea. I found this thread from 2007 where Julian Reschke
>>> proposed this exact thing:
>>>
>>> http://www.ietf.org/mail-archive/web/ietf-types/current/msg00591.html
>>>
>>> Does anyone know where this landed? I'd like to pick up the torch and
>>> at least work on text/diff (using the unified diff format, and limited
>>> to those diffs that can be rendered as valid text/* types). I've
>>> started putting together an Internet Draft for it, but was wondering
>>> if this had actually run into technical trouble, or if it just ran out
>>> of steam in 2007.
>>
>> The issue of how to deal with different character encodings were
>> unresolved, and I think it is important to get right.  The approach to
>> specify an application/patch is the easy way out.  Trying to resolve it
>> for a text/patch may be possible, but I fear it will be problematic in
>> practice.  Thus I lean towards a application/patch.
>
> Could you elaborate of what exactly you think would be easier to
> specify using application/patch instead of text/patch?

Some reasons that I had in mind were:

* There is no character set issues -- the encoder doesn't need to know
  which character encoding was used.  The specification doesn't have to
  talk about character sets (which makes up a big chunk of the current
  spec.)

* It can deal with diff's of files with different character sets,
  e.g. converting ISO-8859-1 files to UTF-8.  Like the draft says now,
  the text/* approach is unable to deal with this.

* Sometimes text/* parts are modified by gateways, and this is usually
  avoided by using an application/* type.  So the spec doesn't have to
  talk about these concerns.

However I support doing both media types.  For some situations,
text/patch is appropriate.

/Simon


Return-Path: <julian.reschke@gmx.de>
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 14F8321F8685 for <ietf-types@ietfa.amsl.com>; Thu, 19 Jul 2012 13:26:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.104
X-Spam-Level: 
X-Spam-Status: No, score=-105.104 tagged_above=-999 required=5 tests=[AWL=-2.505, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 eVZSOUTNaiTg for <ietf-types@ietfa.amsl.com>; Thu, 19 Jul 2012 13:26:10 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by ietfa.amsl.com (Postfix) with SMTP id 1A6B621F8686 for <ietf-types@ietf.org>; Thu, 19 Jul 2012 13:26:09 -0700 (PDT)
Received: (qmail invoked by alias); 19 Jul 2012 20:27:03 -0000
Received: from p54BB27D6.dip.t-dialin.net (EHLO [192.168.178.36]) [84.187.39.214] by mail.gmx.net (mp033) with SMTP; 19 Jul 2012 22:27:03 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX18vLENsoocvcFiYKGJadUGAGC5Z9/p1fmvbMtgGL6 cHNlarDyen+R3i
Message-ID: <50086D95.7080004@gmx.de>
Date: Thu, 19 Jul 2012 22:27:01 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0
MIME-Version: 1.0
To: Simon Josefsson <simon@josefsson.org>
References: <CAMHjJ=Sr+pVyqSCZeJw5ECjWHjSpeu1+womAxeAO6VQCv8aT6g@mail.gmail.com> <87k3y03q69.fsf@latte.josefsson.org>
In-Reply-To: <87k3y03q69.fsf@latte.josefsson.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: ietf-types@ietf.org
Subject: Re: [ietf-types] Status of application/patch or text/patch?
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: Thu, 19 Jul 2012 20:26:11 -0000

On 2012-07-19 14:12, Simon Josefsson wrote:
> Jon Moore <jonm@jjmoore.net> writes:
>
>> Hi folks,
>>
>> Given the recent arrival of HTTP PATCH in RFC 5789[1], it seems like
>> registering a media type for the output of the 'diff' utility would be
>> a good idea. I found this thread from 2007 where Julian Reschke
>> proposed this exact thing:
>>
>> http://www.ietf.org/mail-archive/web/ietf-types/current/msg00591.html
>>
>> Does anyone know where this landed? I'd like to pick up the torch and
>> at least work on text/diff (using the unified diff format, and limited
>> to those diffs that can be rendered as valid text/* types). I've
>> started putting together an Internet Draft for it, but was wondering
>> if this had actually run into technical trouble, or if it just ran out
>> of steam in 2007.
>
> The issue of how to deal with different character encodings were
> unresolved, and I think it is important to get right.  The approach to
> specify an application/patch is the easy way out.  Trying to resolve it
> for a text/patch may be possible, but I fear it will be problematic in
> practice.  Thus I lean towards a application/patch.

Could you elaborate of what exactly you think would be easier to specify 
using application/patch instead of text/patch?

Best regards, Julian



Return-Path: <sla@ucolick.org>
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 1D30421F86E0 for <ietf-types@ietfa.amsl.com>; Thu, 19 Jul 2012 12:13:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
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 qicT59jJmf+Q for <ietf-types@ietfa.amsl.com>; Thu, 19 Jul 2012 12:13:58 -0700 (PDT)
Received: from smtp.ucolick.org (zilan.ucolick.org [128.114.23.234]) by ietfa.amsl.com (Postfix) with ESMTP id 157D021F86B6 for <ietf-types@ietf.org>; Thu, 19 Jul 2012 12:13:58 -0700 (PDT)
Received: from smtp.ucolick.org (localhost [127.0.0.1]) by smtp.ucolick.org (Postfix) with ESMTP id DB5AE2834; Thu, 19 Jul 2012 12:14:51 -0700 (PDT)
Received: from geneva.ucolick.org (geneva.ucolick.org [128.114.23.183]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.ucolick.org (Postfix) with ESMTP id CD54B199D; Thu, 19 Jul 2012 12:14:51 -0700 (PDT)
Received: from geneva.ucolick.org (localhost [127.0.0.1]) by geneva.ucolick.org (8.13.8/8.13.8) with ESMTP id q6JJEpd0007234; Thu, 19 Jul 2012 12:14:51 -0700
Received: (from sla@localhost) by geneva.ucolick.org (8.13.8/8.13.8/Submit) id q6JJEoHn007233; Thu, 19 Jul 2012 12:14:50 -0700
Date: Thu, 19 Jul 2012 12:14:50 -0700
From: Steve Allen <sla@ucolick.org>
To: ietf-types@ietf.org
Message-ID: <20120719191450.GJ14844@ucolick.org>
References: <mailman.163.1342724471.22142.ietf-types@ietf.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <mailman.163.1342724471.22142.ietf-types@ietf.org>
User-Agent: Mutt/1.4.2.2i
Subject: Re: [ietf-types] Status of application/patch or text/patch?
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: Thu, 19 Jul 2012 19:13:59 -0000

> From: Jon Moore <jonm@jjmoore.net>
> Date: Thu, 19 Jul 2012 09:24:15 -0400
> Subject: Re: [ietf-types] Status of application/patch or text/patch?

> Does anyone have opinions regarding whether this should be one or two RFCs?

RFC 4047 gives precedent for describing multiple MIME media types.

--
Steve Allen                 <sla@ucolick.org>                WGS-84 (GPS)
UCO/Lick Observatory--ISB   Natural Sciences II, Room 165    Lat  +36.99855
1156 High Street            Voice: +1 831 459 3046           Lng -122.06015
Santa Cruz, CA 95064        http://www.ucolick.org/~sla/     Hgt +250 m


Return-Path: <simon@josefsson.org>
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 ABFFD21F8715 for <ietf-types@ietfa.amsl.com>; Thu, 19 Jul 2012 06:38:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.909
X-Spam-Level: 
X-Spam-Status: No, score=-99.909 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, HELO_MISMATCH_COM=0.553, HOST_EQ_STATICB=1.372, USER_IN_WHITELIST=-100]
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 xBrlNXOlWA54 for <ietf-types@ietfa.amsl.com>; Thu, 19 Jul 2012 06:38:55 -0700 (PDT)
Received: from yxa-v.extundo.com (static-213-115-179-173.sme.bredbandsbolaget.se [213.115.179.173]) by ietfa.amsl.com (Postfix) with ESMTP id BFB6321F8700 for <ietf-types@ietf.org>; Thu, 19 Jul 2012 06:38:54 -0700 (PDT)
Received: from latte (static-213-115-179-130.sme.bredbandsbolaget.se [213.115.179.130]) (authenticated bits=0) by yxa-v.extundo.com (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id q6JDdadr022651 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Thu, 19 Jul 2012 15:39:38 +0200
From: Simon Josefsson <simon@josefsson.org>
To: Jon Moore <jonm@jjmoore.net>
References: <CAMHjJ=Sr+pVyqSCZeJw5ECjWHjSpeu1+womAxeAO6VQCv8aT6g@mail.gmail.com> <87k3y03q69.fsf@latte.josefsson.org> <F39036BC-C76B-42C3-AE5D-AE67A820316E@jjmoore.net>
OpenPGP: id=B565716F; url=http://josefsson.org/key.txt
X-Hashcash: 1:22:120719:jonm@jjmoore.net::LVWsiHoU3vRl6ihH:4lpT
X-Hashcash: 1:22:120719:ietf-types@ietf.org::pGTakgRog7dnBUOn:Jt0e
Date: Thu, 19 Jul 2012 15:39:36 +0200
In-Reply-To: <F39036BC-C76B-42C3-AE5D-AE67A820316E@jjmoore.net> (Jon Moore's message of "Thu, 19 Jul 2012 09:24:15 -0400")
Message-ID: <87eho73m5j.fsf@latte.josefsson.org>
User-Agent: Gnus/5.130006 (Ma Gnus v0.6) Emacs/23.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
X-Virus-Scanned: clamav-milter 0.97.3 at yxa-v
X-Virus-Status: Clean
Cc: "ietf-types@ietf.org" <ietf-types@ietf.org>
Subject: Re: [ietf-types] Status of application/patch or text/patch?
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: Thu, 19 Jul 2012 13:38:55 -0000

Jon Moore <jonm@jjmoore.net> writes:

> I think application/{diff,patch} and text/{diff,patch} both have their
> places. The application/* version will be easier to specify, for
> sure. However, a very, very common use case for diff is exchanging
> source code diffs against ASCII-encoded files; being able to have a
> text/* version means, for example, that many clients will be able to
> treat them as generic text files--for example, a browser could just
> display the diff rather than downloading it. So the text/* version
> might be more generally consumable.
>
> There are probably some very simple rules by which a producer could
> run 'diff' and know that the output could be labelled 'text/diff'
> without much extra work (for example, if the two documents given as
> arguments to diff have the same encoding, and it is one of us-ascii,
> iso-8859-*, or utf-8,then you're good).

Agreed.

> My intent would be to document both media types. Does anyone have opinions regarding whether this should be one or two RFCs?

I would prefer one document, for easier review and less text
duplication.

/Simon


Return-Path: <jonm@jjmoore.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 682D421F8606 for <ietf-types@ietfa.amsl.com>; Thu, 19 Jul 2012 06:23:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.203
X-Spam-Level: 
X-Spam-Status: No, score=-2.203 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_LOW=-1]
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 0fk+zsEh2dLM for <ietf-types@ietfa.amsl.com>; Thu, 19 Jul 2012 06:23:32 -0700 (PDT)
Received: from mail-qc0-f182.google.com (mail-qc0-f182.google.com [209.85.216.182]) by ietfa.amsl.com (Postfix) with ESMTP id CB70521F8672 for <ietf-types@ietf.org>; Thu, 19 Jul 2012 06:23:31 -0700 (PDT)
Received: by qcsg15 with SMTP id g15so2175524qcs.27 for <ietf-types@ietf.org>; Thu, 19 Jul 2012 06:24:24 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=references:in-reply-to:mime-version:content-type:message-id :content-transfer-encoding:cc:x-mailer:from:subject:date:to :x-gm-message-state; bh=8vJYzgt7Qru7MsQ7aJr8PGuGAGZ6EjbFUOmkO8Ktzws=; b=j9vndMiub1TCr0K+1lsEaKHL5eOvLnni9kwQLI0AwPRMJ0aIxN2u0ac57rDq/2wt6U 8iWtNlfBPUCmiVOjXEGHNkv4mzHMCNtwijSd2XiraxZyAa+hD7zb9ubdjRIIrbhBXrea G3aDvnoWgrbzaOxpn565lqxbQV85D1OUptdqrBPOTAnqcimM5SmVh/QjD8YAhqe2I0So nwca2CFG88BhFhfLurWQYY4JQHpmXp4oEk44em37A4+l5I/weiyAooy5NOxvDfWJSoKB tb0Y7S8Ff4R0UE1bjcaa4FUoZBbmWEoDZIbEMAG4/igoSn0Qzbt3kR1TX0M8U0Q8C6Om Asxw==
Received: by 10.224.191.138 with SMTP id dm10mr3626373qab.94.1342704264550; Thu, 19 Jul 2012 06:24:24 -0700 (PDT)
Received: from [10.141.53.217] (mobile-198-228-197-206.mycingular.net. [198.228.197.206]) by mx.google.com with ESMTPS id f14sm3067033qak.20.2012.07.19.06.24.21 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 19 Jul 2012 06:24:23 -0700 (PDT)
References: <CAMHjJ=Sr+pVyqSCZeJw5ECjWHjSpeu1+womAxeAO6VQCv8aT6g@mail.gmail.com> <87k3y03q69.fsf@latte.josefsson.org>
In-Reply-To: <87k3y03q69.fsf@latte.josefsson.org>
Mime-Version: 1.0 (iPhone Mail 8J2)
Content-Type: text/plain; charset=us-ascii
Message-Id: <F39036BC-C76B-42C3-AE5D-AE67A820316E@jjmoore.net>
Content-Transfer-Encoding: quoted-printable
X-Mailer: iPhone Mail (8J2)
From: Jon Moore <jonm@jjmoore.net>
Date: Thu, 19 Jul 2012 09:24:15 -0400
To: Simon Josefsson <simon@josefsson.org>
X-Gm-Message-State: ALoCoQnH9eLCjkkcOoOf5pSYS8Ekw8KR9mV6ruZODcpCqVDS3sP9nXvR1iw1sPlNPe156OITXgM4
Cc: "ietf-types@ietf.org" <ietf-types@ietf.org>
Subject: Re: [ietf-types] Status of application/patch or text/patch?
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: Thu, 19 Jul 2012 13:23:32 -0000

I think application/{diff,patch} and text/{diff,patch} both have their place=
s. The application/* version will be easier to specify, for sure. However, a=
 very, very common use case for diff is exchanging source code diffs against=
 ASCII-encoded files; being able to have a text/* version means, for example=
, that many clients will be able to treat them as generic text files--for ex=
ample, a browser could just display the diff rather than downloading it. So t=
he text/* version might be more generally consumable.=20

There are probably some very simple rules by which a producer could run 'dif=
f' and know that the output could be labelled 'text/diff' without much extra=
 work (for example, if the two documents given as arguments to diff have the=
 same encoding, and it is one of us-ascii, iso-8859-*, or utf-8,then you're g=
ood).=20

My intent would be to document both media types. Does anyone have opinions r=
egarding whether this should be one or two RFCs?

Jon
........
Jon Moore


On Jul 19, 2012, at 8:12 AM, Simon Josefsson <simon@josefsson.org> wrote:

> Jon Moore <jonm@jjmoore.net> writes:
>=20
>> Hi folks,
>>=20
>> Given the recent arrival of HTTP PATCH in RFC 5789[1], it seems like
>> registering a media type for the output of the 'diff' utility would be
>> a good idea. I found this thread from 2007 where Julian Reschke
>> proposed this exact thing:
>>=20
>> http://www.ietf.org/mail-archive/web/ietf-types/current/msg00591.html
>>=20
>> Does anyone know where this landed? I'd like to pick up the torch and
>> at least work on text/diff (using the unified diff format, and limited
>> to those diffs that can be rendered as valid text/* types). I've
>> started putting together an Internet Draft for it, but was wondering
>> if this had actually run into technical trouble, or if it just ran out
>> of steam in 2007.
>=20
> The issue of how to deal with different character encodings were
> unresolved, and I think it is important to get right.  The approach to
> specify an application/patch is the easy way out.  Trying to resolve it
> for a text/patch may be possible, but I fear it will be problematic in
> practice.  Thus I lean towards a application/patch.
>=20
> /Simon


Return-Path: <simon@josefsson.org>
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 0449321F8769 for <ietf-types@ietfa.amsl.com>; Thu, 19 Jul 2012 05:12:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.909
X-Spam-Level: 
X-Spam-Status: No, score=-99.909 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FH_HOST_EQ_D_D_D_D=0.765, HELO_MISMATCH_COM=0.553, HOST_EQ_STATICB=1.372, USER_IN_WHITELIST=-100]
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 vKM2VnVBJfXM for <ietf-types@ietfa.amsl.com>; Thu, 19 Jul 2012 05:12:04 -0700 (PDT)
Received: from yxa-v.extundo.com (static-213-115-179-173.sme.bredbandsbolaget.se [213.115.179.173]) by ietfa.amsl.com (Postfix) with ESMTP id 1312C21F8759 for <ietf-types@ietf.org>; Thu, 19 Jul 2012 05:12:03 -0700 (PDT)
Received: from latte (static-213-115-179-130.sme.bredbandsbolaget.se [213.115.179.130]) (authenticated bits=0) by yxa-v.extundo.com (8.14.3/8.14.3/Debian-5+lenny1) with ESMTP id q6JCClLw018806 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Thu, 19 Jul 2012 14:12:48 +0200
From: Simon Josefsson <simon@josefsson.org>
To: Jon Moore <jonm@jjmoore.net>
References: <CAMHjJ=Sr+pVyqSCZeJw5ECjWHjSpeu1+womAxeAO6VQCv8aT6g@mail.gmail.com>
OpenPGP: id=B565716F; url=http://josefsson.org/key.txt
X-Hashcash: 1:22:120719:jonm@jjmoore.net::BfGgYWGnf+5je7QQ:ZkIZ
X-Hashcash: 1:22:120719:ietf-types@ietf.org::nfS914lVuwPRpz8S:iW63
Date: Thu, 19 Jul 2012 14:12:46 +0200
In-Reply-To: <CAMHjJ=Sr+pVyqSCZeJw5ECjWHjSpeu1+womAxeAO6VQCv8aT6g@mail.gmail.com> (Jon Moore's message of "Tue, 10 Jul 2012 21:12:22 -0400")
Message-ID: <87k3y03q69.fsf@latte.josefsson.org>
User-Agent: Gnus/5.130006 (Ma Gnus v0.6) Emacs/23.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain
X-Virus-Scanned: clamav-milter 0.97.3 at yxa-v
X-Virus-Status: Clean
Cc: ietf-types@ietf.org
Subject: Re: [ietf-types] Status of application/patch or text/patch?
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: Thu, 19 Jul 2012 12:12:05 -0000

Jon Moore <jonm@jjmoore.net> writes:

> Hi folks,
>
> Given the recent arrival of HTTP PATCH in RFC 5789[1], it seems like
> registering a media type for the output of the 'diff' utility would be
> a good idea. I found this thread from 2007 where Julian Reschke
> proposed this exact thing:
>
> http://www.ietf.org/mail-archive/web/ietf-types/current/msg00591.html
>
> Does anyone know where this landed? I'd like to pick up the torch and
> at least work on text/diff (using the unified diff format, and limited
> to those diffs that can be rendered as valid text/* types). I've
> started putting together an Internet Draft for it, but was wondering
> if this had actually run into technical trouble, or if it just ran out
> of steam in 2007.

The issue of how to deal with different character encodings were
unresolved, and I think it is important to get right.  The approach to
specify an application/patch is the easy way out.  Trying to resolve it
for a text/patch may be possible, but I fear it will be problematic in
practice.  Thus I lean towards a application/patch.

/Simon


Return-Path: <jonm@jjmoore.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 C925A21F8683 for <ietf-types@ietfa.amsl.com>; Wed, 11 Jul 2012 02:02:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.502
X-Spam-Level: 
X-Spam-Status: No, score=-2.502 tagged_above=-999 required=5 tests=[AWL=-0.299, BAYES_00=-2.599, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_LOW=-1]
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 0LSvtM+36Nov for <ietf-types@ietfa.amsl.com>; Wed, 11 Jul 2012 02:02:04 -0700 (PDT)
Received: from mail-qa0-f51.google.com (mail-qa0-f51.google.com [209.85.216.51]) by ietfa.amsl.com (Postfix) with ESMTP id 0455321F8680 for <ietf-types@ietf.org>; Wed, 11 Jul 2012 02:02:03 -0700 (PDT)
Received: by qaea16 with SMTP id a16so729549qae.10 for <ietf-types@ietf.org>; Wed, 11 Jul 2012 02:02:33 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=references:in-reply-to:mime-version:content-type:message-id :content-transfer-encoding:cc:x-mailer:from:subject:date:to :x-gm-message-state; bh=xF77/b4foGGi2K9kFx9N3vTda1l7CyU95hdyvm7VKGU=; b=dv1wHVSI9WBm5+knIWfyswM+MLWa9u6pe3+VyPd35lIbNakgf/klmYHrG/iZBWwpGx y7/z3C09TvIR8k3uQYzayzuX2NOCaAJvYiXy8T0A24CXIGW5TaXTqbrES2Sg1frDuo4I uhQybz1zmzwmUvM85I0amWRyKYaelZhLi3gAB75vJnkSmYeA/nHXv+wVsBcZjjQU7MY3 lwU3wHpdGK9AquQO/4RNLXLoyrLNeAWzbrOVSzLn2JM+2NUTOBQVj2sw0YicdqokCJCk Xt/RaJFQdFbtO8FuLq2fYkiHVY1kTnMR3oF8Oy9Q7bR8HGEyOkLybyYXedOpxFU/yR/F 9c/g==
Received: by 10.229.136.200 with SMTP id s8mr25387871qct.46.1341997353478; Wed, 11 Jul 2012 02:02:33 -0700 (PDT)
Received: from [192.168.154.100] (c-68-32-29-233.hsd1.pa.comcast.net. [68.32.29.233]) by mx.google.com with ESMTPS id t6sm2492882qal.18.2012.07.11.02.02.30 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 11 Jul 2012 02:02:31 -0700 (PDT)
References: <CAMHjJ=Sr+pVyqSCZeJw5ECjWHjSpeu1+womAxeAO6VQCv8aT6g@mail.gmail.com> <4FFD2A49.8030709@gmx.de>
In-Reply-To: <4FFD2A49.8030709@gmx.de>
Mime-Version: 1.0 (iPhone Mail 8J2)
Content-Type: text/plain; charset=us-ascii
Message-Id: <7CB5C4AB-E6CD-4357-9DA0-8A541DE333CA@jjmoore.net>
Content-Transfer-Encoding: quoted-printable
X-Mailer: iPhone Mail (8J2)
From: Jon Moore <jonm@jjmoore.net>
Date: Wed, 11 Jul 2012 05:02:26 -0400
To: Julian Reschke <julian.reschke@gmx.de>
X-Gm-Message-State: ALoCoQnvulCJ3bqAmyy/zai7hsK61ea8Ux0WoMN3KTXwgPvqSooPeQUg0XpUJZwzbUuY00+TYhgu
Cc: "ietf-types@ietf.org" <ietf-types@ietf.org>
Subject: Re: [ietf-types] Status of application/patch or text/patch?
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: Wed, 11 Jul 2012 09:02:05 -0000

Well, 2+ years is pretty recent in IETF time. :)

Thanks for the guidance, I'll follow up with APPSAWG.=20

Jon
........
Jon Moore


On Jul 11, 2012, at 3:24 AM, Julian Reschke <julian.reschke@gmx.de> wrote:

> On 2012-07-11 03:12, Jon Moore wrote:
>> Hi folks,
>>=20
>> Given the recent arrival of HTTP PATCH in RFC 5789[1], it seems like
>=20
> 2+ years :-)
>=20
>> registering a media type for the output of the 'diff' utility would be
>> a good idea. I found this thread from 2007 where Julian Reschke
>> proposed this exact thing:
>>=20
>> http://www.ietf.org/mail-archive/web/ietf-types/current/msg00591.html
>>=20
>> Does anyone know where this landed? I'd like to pick up the torch and
>=20
> Nowhere, as far as I can tell.
>=20
>> at least work on text/diff (using the unified diff format, and limited
>> to those diffs that can be rendered as valid text/* types). I've
>> started putting together an Internet Draft for it, but was wondering
>> if this had actually run into technical trouble, or if it just ran out
>> of steam in 2007.
>>=20
>> Any guidance would be appreciated!
>=20
> My recollection is that I got lost in the output format variations and pot=
ential copyrights.
>=20
> So please go ahead; the IETF APPSAWG mailing list probably is a good place=
 to get feedback.
>=20
> Best regards, Julian


Return-Path: <julian.reschke@gmx.de>
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 D298B21F85D8 for <ietf-types@ietfa.amsl.com>; Wed, 11 Jul 2012 00:24:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.107
X-Spam-Level: 
X-Spam-Status: No, score=-105.107 tagged_above=-999 required=5 tests=[AWL=-2.508, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 3HapXGYUOz60 for <ietf-types@ietfa.amsl.com>; Wed, 11 Jul 2012 00:24:32 -0700 (PDT)
Received: from mailout-de.gmx.net (mailout-de.gmx.net [213.165.64.23]) by ietfa.amsl.com (Postfix) with SMTP id 20B0E21F85D5 for <ietf-types@ietf.org>; Wed, 11 Jul 2012 00:24:29 -0700 (PDT)
Received: (qmail invoked by alias); 11 Jul 2012 07:24:58 -0000
Received: from p5DD94F16.dip.t-dialin.net (EHLO [192.168.178.36]) [93.217.79.22] by mail.gmx.net (mp071) with SMTP; 11 Jul 2012 09:24:58 +0200
X-Authenticated: #1915285
X-Provags-ID: V01U2FsdGVkX18z2pMOMWYzxpm9DVONyi7Z/Kzl9i5oV3+Ty9ZXlv lVkzLWVBEN5OKj
Message-ID: <4FFD2A49.8030709@gmx.de>
Date: Wed, 11 Jul 2012 09:24:57 +0200
From: Julian Reschke <julian.reschke@gmx.de>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: Jon Moore <jonm@jjmoore.net>
References: <CAMHjJ=Sr+pVyqSCZeJw5ECjWHjSpeu1+womAxeAO6VQCv8aT6g@mail.gmail.com>
In-Reply-To: <CAMHjJ=Sr+pVyqSCZeJw5ECjWHjSpeu1+womAxeAO6VQCv8aT6g@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Y-GMX-Trusted: 0
Cc: ietf-types@ietf.org
Subject: Re: [ietf-types] Status of application/patch or text/patch?
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: Wed, 11 Jul 2012 07:24:34 -0000

On 2012-07-11 03:12, Jon Moore wrote:
> Hi folks,
>
> Given the recent arrival of HTTP PATCH in RFC 5789[1], it seems like

2+ years :-)

> registering a media type for the output of the 'diff' utility would be
> a good idea. I found this thread from 2007 where Julian Reschke
> proposed this exact thing:
>
> http://www.ietf.org/mail-archive/web/ietf-types/current/msg00591.html
>
> Does anyone know where this landed? I'd like to pick up the torch and

Nowhere, as far as I can tell.

> at least work on text/diff (using the unified diff format, and limited
> to those diffs that can be rendered as valid text/* types). I've
> started putting together an Internet Draft for it, but was wondering
> if this had actually run into technical trouble, or if it just ran out
> of steam in 2007.
>
> Any guidance would be appreciated!

My recollection is that I got lost in the output format variations and 
potential copyrights.

So please go ahead; the IETF APPSAWG mailing list probably is a good 
place to get feedback.

Best regards, Julian


Return-Path: <jonm@jjmoore.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 0717311E80A1 for <ietf-types@ietfa.amsl.com>; Tue, 10 Jul 2012 18:11:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.977
X-Spam-Level: 
X-Spam-Status: No, score=-2.977 tagged_above=-999 required=5 tests=[AWL=0.000,  BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1]
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 gb3sbw1D2k71 for <ietf-types@ietfa.amsl.com>; Tue, 10 Jul 2012 18:11:54 -0700 (PDT)
Received: from mail-gg0-f172.google.com (mail-gg0-f172.google.com [209.85.161.172]) by ietfa.amsl.com (Postfix) with ESMTP id 3EF9B11E8079 for <ietf-types@ietf.org>; Tue, 10 Jul 2012 18:11:54 -0700 (PDT)
Received: by ggnc4 with SMTP id c4so705506ggn.31 for <ietf-types@ietf.org>; Tue, 10 Jul 2012 18:12:23 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:date:message-id:subject:from:to :content-type:x-gm-message-state; bh=GVYTu/iNCPBa33p3aAfWm9BXdAlh1oDygb44j0UxyNw=; b=nV9+21wiOM8+xN1NFUeFNcSx9QLQQaH8vr3p10Dv8biU+hv0IK9ZLNXXvQTZ6lhXJ7 luL8VwMJCHCZWz+EjEOjYphpdrFgfxaQVlGfQDhi8ZIijI4+CjkMHOjieXnFbJ/K+4y8 MaCQ7/aGT23rELqKtEl45aMA3aUgbhbWQ2fbJ7Hi2YU3mkwNLLjOJvR8lFZwzwg48dCb 6AL9U7TKQN1iBbHVCRxZW+LY9SsDzS4XhmBRqhFengcG7iAZ+5uTszw0W9wnIDRRZ5+f 0TOFFF5Z1vo5b5r7acpOcWGbM6EQ407xYQoGfEmT00ydKCb4bKlAyPxXB8TCiAOUDvTk 6ZNg==
MIME-Version: 1.0
Received: by 10.50.237.72 with SMTP id va8mr12872823igc.17.1341969142760; Tue, 10 Jul 2012 18:12:22 -0700 (PDT)
Received: by 10.64.137.200 with HTTP; Tue, 10 Jul 2012 18:12:22 -0700 (PDT)
X-Originating-IP: [68.32.29.233]
Date: Tue, 10 Jul 2012 21:12:22 -0400
Message-ID: <CAMHjJ=Sr+pVyqSCZeJw5ECjWHjSpeu1+womAxeAO6VQCv8aT6g@mail.gmail.com>
From: Jon Moore <jonm@jjmoore.net>
To: ietf-types@ietf.org
Content-Type: text/plain; charset=ISO-8859-1
X-Gm-Message-State: ALoCoQklASFVFDwPOURxLHQCo5tpqIW5LTcRsHolYgxE1DPomaFwcPgmlFZq5cWxoZyapCgb7k4W
Subject: [ietf-types] Status of application/patch or text/patch?
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: Wed, 11 Jul 2012 01:12:28 -0000

Hi folks,

Given the recent arrival of HTTP PATCH in RFC 5789[1], it seems like
registering a media type for the output of the 'diff' utility would be
a good idea. I found this thread from 2007 where Julian Reschke
proposed this exact thing:

http://www.ietf.org/mail-archive/web/ietf-types/current/msg00591.html

Does anyone know where this landed? I'd like to pick up the torch and
at least work on text/diff (using the unified diff format, and limited
to those diffs that can be rendered as valid text/* types). I've
started putting together an Internet Draft for it, but was wondering
if this had actually run into technical trouble, or if it just ran out
of steam in 2007.

Any guidance would be appreciated!

Thanks,
Jon
--
........
Jon Moore

