- From: Felix Sasaki <felix.sasaki@fh-potsdam.de>
- Date: Thu, 16 Jul 2009 04:47:37 +0900
- To: Yves Savourel <yves@opentag.com>
- Cc: public-i18n-its-ig@w3.org
- Message-ID: <ba4134970907151247t7b29eb1dg119377152d3d087b@mail.gmail.com>
Thanks for the feedback. Two things to fix below. 2009/7/16 Yves Savourel <yves@opentag.com> > It looks good to me. > > Thanks for doing this. > > > > -ys > > > > *From:* public-i18n-its-ig-request@w3.org [mailto: > public-i18n-its-ig-request@w3.org] *On Behalf Of *Felix Sasaki > *Sent:* Wednesday, July 15, 2009 5:59 AM > *To:* public-i18n-its-ig@w3.org > *Subject:* Mime-type for ITS > > > > Hello all, > > below is a template for an ITS mime type. Comments are very welcome - > probably nothing important. At the end of the week I will send this in, > following > http://www.w3.org/2002/06/registering-mediatype > > Felix > > > MIME media type name: > application > > MIME 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 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 permits 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 specifications: > http://www.w3.org/TR/2007/REC-its-20070403/ > > Applications which use this media type: > This new media type is being registered to allow for deployment of ITS > 1.0 on the World Wide Web. > > Additional information: > > File extension: > its > > Fragment identifiers: > A syntax identical to that of "application/xml" as described in > IETF RFC 3023. > > Base URI: > As specified in IETF RFC 3023, section 6. > > Macintosh File Type code: > TEXT > > Person and email address to contact for further information: > World Wide Web Consortium <web-human@w3.org> > Intended usage: > > COMMON > > Author/Change controller: > > The Web Services Policy 1.5 specification set > s/Web Services Policy 1.5 specification set/Internationalization Tag Set (ITS) 1.0 specification/ > is a work product of the World Wide Web Consortium's Internationalization > Tag Set Working Group. > Here we have a problem - the WG does not exist anymore. Well, I will check with Philippe Le Hegaret. Felix > The W3C has change control over these specifications. >
Received on Wednesday, 15 July 2009 19:48:17 UTC