[media-types] Potential media type registration for OASIS XLIFF 2.0

"Dr. David Filip" <David.Filip@ul.ie> Thu, 16 January 2014 20:28 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 []) by ietfa.amsl.com (Postfix) with ESMTP id 2953F1ABBB1 for <media-types@ietfa.amsl.com>; Thu, 16 Jan 2014 12:28:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.805
X-Spam-Status: No, score=-1.805 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RP_MATCHES_RCVD=-0.538, T_HK_NAME_DR=0.01] autolearn=ham
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id wQFxdWM06kwF for <media-types@ietfa.amsl.com>; Thu, 16 Jan 2014 12:28:06 -0800 (PST)
Received: from MARSHAL4.ul.ie (marshal4.ul.ie []) by ietfa.amsl.com (Postfix) with ESMTP id 3853B1A16F0 for <media-types@ietf.org>; Thu, 16 Jan 2014 12:28:06 -0800 (PST)
Received: from staffexchange7.ul.campus (Not Verified[]) by MARSHAL4.ul.ie with MailMarshal (v6, 8, 4, 9558) id <B52d840c90000>; Thu, 16 Jan 2014 20:27:53 +0000
Received: from mail-ie0-f171.google.com ([]) by staffexchange7.ul.campus over TLS secured channel with Microsoft SMTPSVC(6.0.3790.4675); Thu, 16 Jan 2014 20:27:52 +0000
Received: by mail-ie0-f171.google.com with SMTP id to1so4491617ieb.16 for <media-types@ietf.org>; Thu, 16 Jan 2014 12:27:51 -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:from:date:message-id:subject:to :content-type; bh=dmpiJsvV6gIIASuLS3ucVKBjEEbt1BhccPblkh7Ezqo=; b=B33NiOY92fT1qsAIf7nAoyJ0hJHdEXEMmnhi7xKuN73CEVLBc/z1QKoEB4rJ6+KWx7 1RyFkcIP/Gg5f8quGuQDLTEtwo127t5omA1e1r/u8pQ+05i9nF6+sGvCBJ9akIp00min h81GoDGG/uMrt9jj2KjXOBQ7RNA1k+ULSfBlzwnNMHfg/TwlKBtWyeCCwl3gP/I+HyCx 2V7Fotdj9I0NYMP7QdYyKZ4i5gD+iZD/uCgTDzo+VJc3z8WO1eccEhwIMpdEXpRrgKRp YWFhw02oLlTZKQFtG5ePkvXvzm4PUryr34+ff+clwoFanAKY+WeVbXncLyA0EBPC57DX 4b+A==
X-Gm-Message-State: ALoCoQlV83H0VawM39JaEsDxT5sViB+H/TWQJA1Mh9Ce1YTPZ16BH+1KHYQKjc1WtMP3PsJKOIfO
X-Received: by with SMTP id wx4mr10096838icb.6.1389904071176; Thu, 16 Jan 2014 12:27:51 -0800 (PST)
MIME-Version: 1.0
Received: by with HTTP; Thu, 16 Jan 2014 12:27:11 -0800 (PST)
X-Originating-IP: []
From: "Dr. David Filip" <David.Filip@ul.ie>
Date: Thu, 16 Jan 2014 20:27:11 +0000
Message-ID: <CANw5LK=z2YeUtYFUNtbFmKSGGmoYLwa1Ahvax5TbbmO_W7CkEw@mail.gmail.com>
To: media-types@ietf.org
Content-Type: multipart/alternative; boundary=bcaec51dd1f16f4bfe04f01c4286
X-OriginalArrivalTime: 16 Jan 2014 20:27:52.0984 (UTC) FILETIME=[6EAA3980:01CF12F9]
Subject: [media-types] Potential media type registration for OASIS 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: Thu, 16 Jan 2014 20:55:49 -0000

Hello Reviewers,

as Secretary of the OASIS XLIFF TC

I have been mandated by the said TC and OASIS TC administration to run by
this list our provisionally completed media type registration template.

All comments in square brackets are not meant as part of the future
submission but rather as explanattory notes for the reviewers within OASIS
and on this list.

XLIFF TC is looking forward to receiving your feedback

See the filled out template copy-pasted down below:

Best regards

Dr. David Filip
University of Limerick, Ireland
telephone: +353-6120-2781
*cellphone: +353-86-0222-158*
facsimile: +353-6120-2734
mailto: david.filip@ul.ie

----start of the registration form

Registration Template

   Type name: application
[not text, because end users do not like markup]

   Subtype name: xml

   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)

The relevant publsihed version at the time of submission will be most

likely this:]
XLIFF Version 2.0 (CSD03)

[the above will not resolve until the thrird public review call become s

public, the csd03 will be largely based on this current working draft:
wd03: https://tools.oasis-open.org/version-


   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,

however should be irrelevant for this current registration of XLIFF 2.0]
Intended usage:
Restrictions on usage: N/A

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
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
[the review comments will be monitored by david.filip@ul.ie on this list]

----end of the registration form