Re: [ietf-types] Registration for application/its+xml

"Martin J. Dürst" <duerst@it.aoyama.ac.jp> Fri, 07 December 2012 10:37 UTC

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 119D521F8624 for <ietf-types@ietfa.amsl.com>; Fri, 7 Dec 2012 02:37:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.562
X-Spam-Level:
X-Spam-Status: No, score=-100.562 tagged_above=-999 required=5 tests=[AWL=-0.272, BAYES_00=-2.599, HELO_EQ_JP=1.244, HOST_EQ_JP=1.265, J_CHICKENPOX_33=0.6, J_CHICKENPOX_35=0.6, MANGLED_WRLDWD=2.3, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4IYlwVrOoQFn for <ietf-types@ietfa.amsl.com>; Fri, 7 Dec 2012 02:37:58 -0800 (PST)
Received: from scintmta02.scbb.aoyama.ac.jp (scintmta02.scbb.aoyama.ac.jp [133.2.253.34]) by ietfa.amsl.com (Postfix) with ESMTP id 09A4821F860D for <ietf-types@ietf.org>; Fri, 7 Dec 2012 02:37:57 -0800 (PST)
Received: from scmse02.scbb.aoyama.ac.jp ([133.2.253.231]) by scintmta02.scbb.aoyama.ac.jp (secret/secret) with SMTP id qB7Abm44002529 for <ietf-types@ietf.org>; Fri, 7 Dec 2012 19:37:48 +0900
Received: from (unknown [133.2.206.133]) by scmse02.scbb.aoyama.ac.jp with smtp id 3150_206c_25108030_405a_11e2_8bda_001d096c5782; Fri, 07 Dec 2012 19:37:48 +0900
Received: from [IPv6:::1] ([133.2.210.1]:57812) by itmail.it.aoyama.ac.jp with [XMail 1.22 ESMTP Server] id <S161CD78> for <ietf-types@ietf.org> from <duerst@it.aoyama.ac.jp>; Fri, 7 Dec 2012 19:37:50 +0900
Message-ID: <50C1C6F5.908@it.aoyama.ac.jp>
Date: Fri, 07 Dec 2012 19:37:41 +0900
From: "\"Martin J. Dürst\"" <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: Felix Sasaki <fsasaki@w3.org>
References: <261b5c2124cb69a4d610adf684f1cce4@w3.org>
In-Reply-To: <261b5c2124cb69a4d610adf684f1cce4@w3.org>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: ietf-types@ietf.org
Subject: Re: [ietf-types] Registration for application/its+xml
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, 07 Dec 2012 10:37:59 -0000

Hello Felix,

This looks good to me. Glad to see this registration finally coming through.

Regards,   Martin.

On 2012/12/06 22:17, Felix Sasaki wrote:
> Hello,
>
> This is Appendix B of ITS 2.0
>
> http://www.w3.org/TR/2012/WD-its20-20121206/#its-mime-type
>
> Comments on this registration would be greatly appreciated.
>
> ==========
> This section defines a MIME type for Internationalization Tag Set (ITS)
> documents. It covers both ITS 1.0 and ITS 2.0.
>
> Type name: application
>
> Subtype name: its+xml
>
> Required parameters: none
>
> Optional parameters: charset
>
> This parameter has identical semantics to the charset parameter of the
> "application/xml" media type as specified in IETF RFC 3023.
>
> Encoding considerations: Identical to those of "application/xml" as
> described in IETF RFC 3023, section 3.2, as applied to an ITS document.
>
> Security considerations: An ITS 1.0 or ITS 2.0 document may cause
> arbitrary URIs or IRIs to be dereferenced, via the @xlink:href attribute
> at the its:rules element. Therefore, the security issues of [RFC3987]
> Section 8 should be considered. In addition, the contents of resources
> identified by file: URIs can in some cases be accessed, processed and
> returned as results. An implementation of ITS global rules requires the
> support of XPath 1.0 or its successor. Hence, processing of global rules
> might encompass dereferencing of URIs or IRIs during computation of
> XPath expressions. Arbitrary recursion is possible, as is arbitrarily
> large memory usage, and implementations may place limits on CPU and
> memory usage, as well as restricting access to system-defined functions.
> ITS 1.0 and ITS 2.0 permit extensions. Hence it is possible that
> application/its+xml may describe content that has security implications
> beyond those described here.
>
> Interoperability considerations: There are no known interoperability
> issues.
>
> Published specification: http://www.w3.org/TR/2007/REC-its-20070403/ and
> http://www.w3.org/TR/its20/.
>
> Any XML document containing ITS 1.0 "its:rules" elements
> http://www.w3.org/TR/its/#selection-global can be labeled with
> application/its+xml.
> http://www.w3.org/TR/its/EX-link-external-rules-2.xml Provides an
> example of a document linking to a file with ITS 1.0 and ITS 2.0
> "rules". The link target is at
> http://www.w3.org/TR/its/EX-link-external-rules-1.xml. There is no need
> that the link target has "its:rules" as a root element. The processing
> semantics is that rules are gathered in document order.
>
> Applications that use this media type: This new media type is being
> registered to allow for deployment of ITS 1.0 and ITS 2.0 on the World
> Wide Web., e.g. by localization tools.
>
> Additional information:
>
> Magic number(s): none
>
> File extension(s): its
>
> Macintosh file type code(s): TEXT
>
> Person & email address to contact for further information: World Wide
> Web Consortium <web-human at w3.org>
>
> Intended usage: COMMON
>
> Restrictions on usage: none
>
> Author / Change controller: The Internationalization Tag Set (ITS) 1.0
> and 2.0 specifications are a work product of the World Wide Web
> Consortium's Internationalization Tag Set Working Group. The W3C has
> change control over this specification.
> ==========
> _______________________________________________
> ietf-types mailing list
> ietf-types@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf-types
>