Kazuyuki Ashimura | 10 May 2012 19:12
Picon
Favicon

Request for review of EmotionML media type: application/emotionml+xml


Dear list,
# sorry but resending because I used wrong address for my previous post.

W3C has just published a Candidate Recommendation for "Emotion Markup
Language (EmotionML)" at:

  http://www.w3.org/TR/2012/CR-emotionml-20120510/

I am sending this request to ask the Ietf-types list for comments on
the Media Type section of the EmotionML specification following the
procedure defined at:

  http://www.w3.org/2002/06/registering-mediatype

---
The Media Type section of the EmotionML specification is available
at:

  http://www.w3.org/TR/2012/CR-emotionml-20120510/#MIME-type

and a plain text copy is also available below.

MIME media type name:
---------------------
     application

MIME subtype name:
------------------
     emotionml+xml
(Continue reading)

Kazuyuki Ashimura | 10 May 2012 18:28
Picon
Favicon

Request for review of EmotionML media type: application/emotionml+xml


Dear list,

W3C has just published a Candidate Recommendation for "Emotion Markup
Language (EmotionML)" at:

  http://www.w3.org/TR/2012/CR-emotionml-20120510/

I am sending this request to ask the Ietf-types list for comments on
the Media Type section of the EmotionML specification following the
procedure defined at:

  http://www.w3.org/2002/06/registering-mediatype

---
The Media Type section of the EmotionML specification is available
at:

  http://www.w3.org/TR/2012/CR-emotionml-20120510/#MIME-type

and a plain text copy is also available below.

MIME media type name:
---------------------
     application

MIME subtype name:
------------------
     emotionml+xml

(Continue reading)

Chris Lilley | 17 Jun 2010 16:26
Picon
Favicon

Registration of media typeimage/svg+xml


   Type name:
          image

   Subtype name:
          svg+xml

   Required parameters:
          None.

   Optional parameters:
          charset

          Same as application/xml media type, as specified in
          RFC3023 or it's successor.

   Encoding considerations:
          Same as for application/xml. See RFC3023, section 3.2.

   Security considerations:
          As with other XML types and as noted in RFC3023 section
          10, repeated expansion of maliciously constructed XML
          entities can be used to consume large amounts of memory,
          which may cause XML processors in constrained environments to
          fail.

          SVG documents may be transmitted in compressed form using
          gzip compression. For systems which employ MIME-like
          mechanisms, such as HTTP, this is indicated by the
          Content-Transfer-Encoding header; for systems which do not,
(Continue reading)

Paul Libbrecht | 24 Nov 2009 17:02

Re: please comment on media-type registrations for MathML


Dear media-types-expert,
Dear Björn,

> Forwarded-from : member-math <at> w3.org
> From : "Robert Miner" <robertm <at> dessci.com>
> Date : 24 novembre 2009 03:43:50 GMT+01:00
> To : <member-math <at> w3.org>
> Archived-At:
<http://www.w3.org/mid/D1EFB337111B674B8F1BE155B01C6DD6034CCA68 <at> franklin.corp.dessci 
> >
>
> Dear Björn,
>
> I am writing in response to your comments on the media-type
> registrations for MathML given in Appendix B of the Last Call draft of
> the MathML 3 Specification.  Your original comments are recorded at
> http://www.alvestrand.no/pipermail/ietf-types/2009-October/ 
> 002268.html.
>
> We have modified Appendix B, and believe we have addressed the issues
> you noted. The changes are explained below, and you can see the draft
> changes in an editor's draft of the spec located at
>
> http://monet.nag.co.uk/~dpc/draft-spec/appendixb.html
>
> Since we need to record the resolution of all Last Call comments,
> could we ask you to let us know whether you accept these changes as
> addressing your comments?  Thanks in advance.
>
(Continue reading)

Chris Lilley | 24 Sep 2009 18:12
Picon
Favicon

Fwd: New Version Notification for draft-murata-kohn-lilley-xml-03


This is a forwarded message
From: IETF I-D Submission Tool <idsubmission <at> ietf.org>
To: chris <at> w3.org
Date: Thursday, September 24, 2009, 5:56:50 PM
Subject: New Version Notification for draft-murata-kohn-lilley-xml-03

===8<==============Original message text===============

A new version of I-D, draft-murata-kohn-lilley-xml-03.txt has been successfuly submitted by Chris
Lilley and posted to the IETF repository.

Filename:        draft-murata-kohn-lilley-xml
Revision:        03
Title:           XML Media Types
Creation_date:   2009-09-24
WG ID:           Independent Submission
Number_of_pages: 49

Abstract:
This document standardizes three media types -- application/xml,
application/xml-external-parsed-entity, and application/xml-dtd --
for use in exchanging network entities that are related to the
Extensible Markup Language (XML) while deprecating text/xml and text/
xml-external-parsed-entity.  This document also standardizes a
convention (using the suffix '+xml') for naming media types outside
of these five types when those media types represent XML MIME
entities.  XML MIME entities are currently exchanged via the
HyperText Transfer Protocol on the World Wide Web, are an integral
part of the WebDAV protocol for remote web authoring, and are
(Continue reading)

Sandro Hawke | 21 Jul 2009 02:11
Picon
Favicon
Gravatar

please review "text/rif+xml" media type registration


The following media type registration has been recently published as
part of a W3C Last Call Working Draft [1], and will soon be submitted to
the IESG for review, approval, and registration with IANA (as per [2]).
An earlier version of this registration was posted here for review about
a year ago [3].  The changes made since then reflect changes in the
organization of the RIF family of dialects; there were no changes
suggested by reviewers of that posting.

At this point, we would appreciate comments on this registration
information.  If you see any problems, please let us know; I'll act as
a liason between these IETF lists and the W3C Working Group
responsible for these specifications.

      -- Sandro

[1] http://www.w3.org/TR/rif-core/#Appendix:_RIF_Media_Type_Registration
[2] http://www.w3.org/2002/06/registering-mediatype
[3] http://lists.w3.org/Archives/Public/www-archive/2008Sep/0023.html

================================================================

   Type name: application

   Subtype name: rif+xml

   Required parameters: none

   Optional parameters: charset, as per RFC 3023 (XML Media Types)

(Continue reading)

Sandro Hawke | 6 Jan 2009 01:03
Picon
Favicon
Gravatar

please review "text/owl-functional" and "application/owl+xml"


The following two media type registrations are currently published, each
as part a of W3C Last Call Working Draft ([1] [2]), and will soon be
submitted to the IESG for review, approval, and registration with IANA
(as per [3]).

At this point, we would appreciate comments on this registration
information.  If you see any problems, please let us know; I'll act as a
liason between these IETF lists and the W3C Working Group responsible
for these specifications.

      -- Sandro

[1] http://www.w3.org/TR/owl2-syntax/#Appendix:_Internet_Media_Type.2C_File_Extension.2C_and_Macintosh_File_Type
[2] http://www.w3.org/TR/owl2-xml-serialization/#Appendix:_Internet_Media_Type.2C_File_Extension.2C_and_Macintosh_File_Type
[3] http://www.w3.org/2002/06/registering-mediatype

================================================================

Type name

    text 

Subtype name

    owl-functional 

Required parameters

    None 
(Continue reading)

Phil Archer | 8 Dec 2008 15:37

Media Type Registration request for POWDER and POWDER-S

To whom it may concern,

This e-mail is sent in line with "How to Register an Internet Media Type 
for a W3C Spec" [1] and follows an earlier attempt to follow the IANA 
process (see 2, 3).

Having taken advice [4], the W3C POWDER Working Group requests that 
consideration be given to registering two Media types for POWDER and 
POWDER-S documents.

POWDER: application/powder+xml
==============================

POWDER is a constrained dialect of XML that transports RDF properties 
and objects that can be associated with multiple subjects. The media 
type details are included in Appendix B of POWDER: Description Resources 
[5] which has just completed its (second) Last Call period. The version 
cited here includes changes made in response to last call comments and 
is not yet published, however, it is the one (or very close to the one) 
the working group will present as the Proposed Recommendation. It is 
anticipated that this happen within the next 2 weeks. The relevant 
section of the Description Resources document is as follows:

Appendix B: POWDER Internet Media Type and Macintosh File Type

The following Media Type has been submitted to the IESG for review, 
approval, and registration with IANA

contact:
   Phil Archer or Matt Womer
(Continue reading)

Sandro Hawke | 16 Sep 2008 13:21
Picon
Favicon
Gravatar

please review "application/rif+xml"


The following media type registration is currently published as part of
a W3C Last Call Working Draft [1] and will soon be submitted to the IESG
for review, approval, and registration with IANA (as per [2]).

At this point, we would appreciate comments on this registration
information.  If you see any problems, please let us know.

(It's tempting to say a few words about RIF here, but I suppose I should
let the registration stand on its own.  It does includes links to the
specification and to the Working Group home page.)

      -- Sandro

[1] http://www.w3.org/TR/2008/WD-rif-bld-20080730/#Appendix:_RIF_Media_Type_Registration
[2] http://www.w3.org/2002/06/registering-mediatype

================================================================

   Type name: application

   Subtype name: rif+xml

   Required parameters: none

   Optional parameters: charset, as per RFC 3023 (XML Media Types)

   Encoding considerations: same as RFC 3023 (XML Media Types)

   Security considerations: 
(Continue reading)

Kazuyuki Ashimura | 29 Jan 2008 20:44
Picon
Favicon

[Fwd: Re: Request for review of InkML media type: application/inkml+xml]


forwarding the response from Ietf-types list for archival purpose.

Kazuyuki

-------- Original Message --------
Subject: 	Re: Request for review of InkML media type: application/inkml+xml
Date: 	Mon, 28 Jan 2008 20:45:15 +0100
From: 	Frank Ellermann <nobody <at> xyzzy.claranet.de>
Reply-To: 	Frank Ellermann <hmdmhdfmhdjmzdtjmzdtzktdkztdjz <at> gmail.com>
Organization: 	
To: 	ietf-types <at> alvestrand.no
References: 
<479E211E.7060406__48586.1079571352$1201547498$gmane$org <at> w3.org>

Kazuyuki Ashimura wrote:

> the security issues of RFC1738, section 6, should be considered.

Please s/RFC1738, section 6/RFC3986, section 7/ if you have no
special reasons to use the almost completely obsolete RFC 1738.

> Published specification:
> -------------------------
> 
> This media type registration is for InkML documents as described
> by this specification.

IMO you need a reference for "this" specification, IANA publishes
only your registration template, where "this" would make no sense.
(Continue reading)

Kazuyuki Ashimura | 28 Jan 2008 19:35
Picon
Favicon

[resent] Request for review of EMMA media type: application/emma+xml


Dear list,

# terribly sorry but resending this message, because apparently I used wrong
# email address in my previous message...

W3C published a Candidate Recommendation for "EMMA: Extensible
MultiModal Annotation markup language" at:

http://www.w3.org/TR/2007/CR-emma-20071211/

I am sending this request to ask the Ietf-types list for comments on
the Media Type section of the EMMA specification following the
procedure defined at:

http://www.w3.org/2002/06/registering-mediatype

---
The Media Type section of the EMMA specification is available at:

http://www.w3.org/TR/2007/CR-emma-20071211/#appB

and a plaintext copy is also available below.

MIME media type name:
----------------------

application

MIME subtype name:
(Continue reading)


Gmane