Re: [media-types] Updated template for Potential media type registration for XLIFF 2.0
"Dr. David Filip" <David.Filip@ul.ie> Mon, 10 February 2014 12:59 UTC
Return-Path: <David.Filip@ul.ie>
X-Original-To: media-types@ietfa.amsl.com
Delivered-To: media-types@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3B30C1A05FA for <media-types@ietfa.amsl.com>; Mon, 10 Feb 2014 04:59:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.815
X-Spam-Level:
X-Spam-Status: No, score=-1.815 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.548, T_HK_NAME_DR=0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 0dnPidnNX0-2 for <media-types@ietfa.amsl.com>; Mon, 10 Feb 2014 04:59:34 -0800 (PST)
Received: from MARSHAL4.ul.ie (marshal4.ul.ie [193.1.100.137]) by ietfa.amsl.com (Postfix) with ESMTP id 14B551A05DF for <media-types@ietf.org>; Mon, 10 Feb 2014 04:59:33 -0800 (PST)
Received: from staffexchange7.ul.campus (Not Verified[193.1.101.32]) by MARSHAL4.ul.ie with MailMarshal (v6, 8, 4, 9558) id <B52f8cd340001>; Mon, 10 Feb 2014 12:59:32 +0000
Received: from staffexchange5.ul.campus ([10.220.1.55]) by staffexchange7.ul.campus with Microsoft SMTPSVC(6.0.3790.4675); Mon, 10 Feb 2014 12:59:19 +0000
Received: from EXCAS2.ul.campus ([193.1.97.102]) by staffexchange5.ul.campus with Microsoft SMTPSVC(6.0.3790.4675); Mon, 10 Feb 2014 12:59:14 +0000
Received: from mail-qc0-f182.google.com (209.85.216.182) by autodiscover.ul.ie (193.1.97.102) with Microsoft SMTP Server (TLS) id 14.3.174.1; Mon, 10 Feb 2014 12:59:13 +0000
Received: by mail-qc0-f182.google.com with SMTP id c9so10483057qcz.27 for <media-types@ietf.org>; Mon, 10 Feb 2014 04:59:12 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=mhRjIYtNC4cB3lX7aZ37I584g0pnPAykbVJdth+1gJI=; b=S2LkSd4Xaf4hCCu4hEvsPlnouVdiVZHyq+LaefSqeoDjkuaoBd5qhcbN8OybVeP3Gs nB7dnRO+9H8jqZhFGmw4lbXEvLxzQUOI+IPBb+nrkr1c7ajvQxKU7NMvEXa9WoOGzSZJ G/WgZrYtPkrZZiwg50KxKIbV6InHQNxbiqpi9RGUYM3VSSeCxXMqNdLmzqIP2VKrycQn 2ZHF2IeeEuhJDDQTddnakTBsBpk3hxxAHrqaVG42suNIAr1tzNZi3zgiYzGXHm4DjWHr jSnfcGXweFs0uHi93KxZikyW+qOKaoljJyQ3UTK2ZtpA7GweD+TNCL5rHorpfKHxnx9z 5/Og==
X-Gm-Message-State: ALoCoQkgYp11TpnZuonnlq9Y0Xg6o5y/lHepku5y/AXO+0ktVtaUcLyLGHQFCDh8kSI75I6k3NNc
X-Received: by 10.224.172.133 with SMTP id l5mr47721450qaz.25.1392037152728; Mon, 10 Feb 2014 04:59:12 -0800 (PST)
MIME-Version: 1.0
Received: by 10.224.210.137 with HTTP; Mon, 10 Feb 2014 04:58:32 -0800 (PST)
X-Originating-IP: [209.85.216.182]
In-Reply-To: <CANw5LK=sNvbXOQ9D3g2LUOb2xX3SX96BaOR8Z23Cc6gdVzNRkg@mail.gmail.com>
References: <CANw5LK=sNvbXOQ9D3g2LUOb2xX3SX96BaOR8Z23Cc6gdVzNRkg@mail.gmail.com>
From: "Dr. David Filip" <David.Filip@ul.ie>
Date: Mon, 10 Feb 2014 12:58:32 +0000
Message-ID: <CANw5LK=XjCf3rwBM5sWccu=SP5RUnD=zeQb1DvB0zJAaE-U=4w@mail.gmail.com>
To: "Dr. David Filip" <David.Filip@ul.ie>
Content-Type: multipart/alternative; boundary="001a11c22f0600d6d604f20ce8c2"
X-OriginalArrivalTime: 10 Feb 2014 12:59:14.0476 (UTC) FILETIME=[E64F9EC0:01CF265F]
Cc: media-types@ietf.org
Subject: Re: [media-types] Updated template for Potential media type registration for XLIFF 2.0
X-BeenThere: media-types@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "IANA mailing list for reviewing Media Type \(MIME Type, Content Type\) registration requests." <media-types.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/media-types>, <mailto:media-types-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/media-types/>
List-Post: <mailto:media-types@ietf.org>
List-Help: <mailto:media-types-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/media-types>, <mailto:media-types-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 10 Feb 2014 12:59:38 -0000
Hello, everyone, there seem to be no comments for the new version of our registration template, and AFAIK we've addressed all actionable comments from the first round. As a newbie on the list, I wonder, does that mean that our registration template is OK so or should we get an explicit OK from a senior reviewer who is now pondering some subtle points that might make our registration unlikely to succeed? Thanks again dF Dr. David Filip ======================= LRC | CNGL | LT-Web | CSIS University of Limerick, Ireland telephone: +353-6120-2781 *cellphone: +353-86-0222-158* facsimile: +353-6120-2734 http://www.cngl.ie/profile/?i=452 mailto: david.filip@ul.ie On Thu, Jan 23, 2014 at 12:31 PM, Dr. David Filip <David.Filip@ul.ie> wrote: > Thanks everyone, for commenting on the previous provisional template. > > I have changed the subtype to xliff+xml and corrected few typos. > > Please let us know if you think that the template would be in your opinion > ready for a IANA registration submission in its current state, ignoring any > content in square brackets that is provided just for context of the review. > > As soon as the template seems OK to the experts on this list I will take > it back to the XLIFF TC for registration approval. > > Thanks and regards > dF > > <start of the registration template> > > Registration Template > > Type name: application > [not text, because end users do not like markup] > > Subtype name: xliff+xml > [based on media-types list experts feedback] > > Required parameters: N/A > > Optional parameters: N/A > [charset declared in payload, hence charset parameter SHOULD NOT be > defined] > > > Encoding considerations: > Same as encoding considerations of application/xml as specified in RFC 3023 > [This media type MAY be encoded as appropriate for the charset and the > capabilities of the underlying MIME transport. For 7-bit transports, data > in UTF-8 MUST be encoded in quoted-printable or base64. For 8-bit clean > transport (e.g., 8BITMIME[RFC1652] ESMTP or NNTP[RFC0977]), UTF-8 does not > need to be encoded. Over HTTP[RFC2616], no content-transfer-encoding is > necessary and UTF-16 may also be used.] > > Security considerations: > All of the security considerations described in RFC 3023 > > Interoperability considerations: > Same as interoperability considerations described in RFC 3023 > [XML has proven to be interoperable across WebDAV clients and servers, and > for import and export from multiple XML authoring tools. For maximum > interoperability, > validating processors are recommended. Although non-validating > processors may be more efficient, they are not required to handle > all features of XML.] > Also, interoperability requirements are specified throughout the > specification and summarized in its Conformance section > > Published specification: > [the current latest published version is: > XLIFF Version 2.0 (CSD02) > > http://docs.oasis-open.org/xliff/xliff-core/v2.0/csd02/xliff-core-v2.0-csd02.html > The relevant published version at the time of submission will be most > likely this:] > XLIFF Version 2.0 (CSD03) > > http://docs.oasis-open.org/xliff/xliff-core/v2.0/csd02/xliff-core-v2.0-csd03.html > [the above will not resolve until the thrird public review call becomes > public, the csd03 will be largely based on this current working draft: > wd03: > https://tools.oasis-open.org/version-control/browse/wsvn/xliff/trunk/xliff-20/xliff-core.pdf > ] > > Applications that use this media type: > XLIFF conformant applications, according to the Conformance Section of the > specification. > > Fragment identifier considerations: > Generic XML processors won't be able to resolve XLIFF fragment > identifiers, as the fragment identification syntax is specific for XLIFF > and has been defined in its Fragment Identification section as of csprd03 > [wd03] of Version 2.0. [XLIFF 1.2 has never been registered as a media > type, I learn there is a xliff+xml type corresponding to XLIFF 1.2 in the > private x-tree, which seems to have been ill conceived for an OASIS > standard, however should be irrelevant for this current registration of > XLIFF 2.0] > Intended usage: > COMMON > Restrictions on usage: N/A > > Author: > OASIS XML Localisation Interchange File Format (XLIFF) TC > Editors: Tom Comerford, tom@supratext.com; David Filip, David.Filip@ul.ie; > Yves Savourel, ysavourel@enlaso.com > > Change controller: > OASIS XML Localisation Interchange File Format (XLIFF) TC > https://www.oasis-open.org/committees/xliff/ > Bryan Schnabel, bryan.s.schnabel@tektronix.com, Chair > Tom Comerford, tom@supratext.com, Secretary > David Filip, David.Filip@ul.ie, Secretary > > Provisional registration? (standards tree only): YES > [I assume that the registration becomes fix after we reach the OASIS > standard stage] > > > Additional information: > > Deprecated alias names for this type: N/A > Magic number(s): N/A > File extension(s): .xlf > Macintosh file type code(s): "TEXT" > > Person & email address to contact for further information: > OASIS Technical Committee administration > tc-admin@oasis-open.org > [the review comments will be monitored by david.filip@ul.ie on this list] > > </end of the registration template> > > > > > Dr. David Filip > ======================= > LRC | CNGL | LT-Web | CSIS > University of Limerick, Ireland > telephone: +353-6120-2781 > *cellphone: +353-86-0222-158 <%2B353-86-0222-158>* > facsimile: +353-6120-2734 > http://www.cngl.ie/profile/?i=452 > mailto: david.filip@ul.ie >
- [media-types] Updated template for Potential medi… Dr. David Filip
- Re: [media-types] Updated template for Potential … Dr. David Filip