- Ietf-types - example.com

RE: Proposed Registration of MIME media type application/vnd.wordperfect
by Kim Scarborough 21 Dec '03

21 Dec '03

> What is the relationship of this to > http://www.iana.org/assignments/media-types/application/wordperfect5.1 > ? Well, the problem with that was that they appended the version string on the end of the name, so nobody uses it anymore (WordPerfect is up to version 11 now--5.1 was only for DOS and Unix CLI). It's too bad it was registered that way, but it's too late now, so I figured I'd submit this. Also, RFC 2048 encourages re-registering grandfathered media types, so what the heck. -- ------------------------------------------------------------------------------- Kim Scarborough http://www.unknown.nu/kim/ -------------------------------------------------------------------------------

1 0

Proposed Registration of MIME media type application/vnd.wordperfect
by Kim Scarborough 21 Dec '03

21 Dec '03

MIME media type name: application MIME subtype name: vnd.wordperfect Required parameters: none Optional parameters: none Encoding Considerations: Wordperfect files are binary data and should be suitably encoded for protocols that do not handle binary data. Security Considerations: The security issues associated with this type have not been assessed. Interoperability considerations: As this is not an open standard, interoperability is left up to the discretion of the developer (currently Corel Corp.). Published specification: none Applications which use this media type: The WordPerfect suite of office applications. Additional information: Magic number(s): none File extension: .wpd Macintosh File Type Code(s): "WPC2" Person & email address to contact for further information: Questions about this proposal should be directed to Kim Scarborough <user(a)unknown.nu>. Intended usage: COMMON Author/Change controller: Corel Corporation 1600 Carling Avenue Ottawa, Ontario Canada K1Z 8R7

2 1

proposed media type registration: application/voicexml+xml
by Max Froumentin 20 Dec '03

20 Dec '03

Hi, Please consider the attached Internet Draft submission: "The application/voicexml+xml Media Type" (originating from the Voice Browser Working Group of the W3C), for review. Cheers, Max Froumentin, W3C

6 14

please review 'application/pdf'
by Larry Masinter 17 Dec '03

17 Dec '03

http://www.ietf.org/internet-drafts/draft-zilles-pdf-00.txt This draft updates the (9-year-old) application/pdf registration.

7 23

RE: proposed media type registration: application/voicexml+xml
by Francois Yergeau 16 Dec '03

16 Dec '03

Seconded, for all the reasons given by Martin. Please restore the charset parameter. Regards, -- François > -----Message d'origine----- > De : Martin Duerst [mailto:duerst@w3.org] > Envoyé : 16 décembre 2003 16:33 > À : Max Froumentin; ietf-types(a)iana.org > Cc : w3c-archive(a)w3.org; ietf-xml-mime(a)imc.org; Ben Kovitz; Linus > Walleij > Objet : Re: proposed media type registration: application/voicexml+xml > > > > Hello Max, others, > > I just by chance realized that you had removed the 'charset' > parameter from the registration for application/voicexml+xml, > and also for application/ssml+xml. I have found something similar > in other recent registration proposals. > > Here is why I think this is really not a good idea: > > First, we start to get into a patchwork where some types > allow the 'charset', and others don't. Assuming that there > is something like generic XML processors (e.g. parsers) > (which is the whole point of XML), how should such a parser > know whether the 'charset' parameter is allowed or not, > and keep up with new registrations? > > Second, there are various scenarios a charset parameter in > the header is automatically generated, or where it's much > easier to generate it than to avoid it. The following are > examples: > - The classical example of transcoding (converting from one > encoding to another). Not very frequent these days on the > Web in general, but still used for Russian/Cyrillic encodings > and in some mobile phone scenarios. > - Scripting technologies, for example JSP. With JSP, it is much > more straightforward to produce output with the right encoding > with a 'charset' parameter in the header than without. The > reason for this is that JSP allows to produce any kind of > output, not limited to XML, and has to know how to convert > from the Java-internal encoding to whatever is used on the > wire. Putting that information in the 'charset' parameter > in the header then is straightforward; anything else has > to be done by hand. Hopefully, excluding certain classes > of content production technologies is not what you want. > - Databases that store content as characters rather than bytes, > in a single encoding (in many cases e.g. uniformly UTF-8), > and transcode on output. Again, if they use generic technology, > getting the 'charset' into the header is much more straightforward > than putting it into the body. > > Given all these cases, I think it's not at all appropriate to > remove the 'charset' parameter from the registration, because > it would severely limit the use of technology that in good > faith, and with good reasons, is using it. > > In the long run, I think that an update to RFC 3023 should address > these issues in more detail to help content producers understand the > advantages and problems related to charset/encoding information. > > Regards, Martin. > > > At 17:15 03/08/21 +0200, Max Froumentin wrote: > > >Hi, > > > >Please consider the attached Internet Draft submission: "The > >application/voicexml+xml Media Type" (originating from the Voice > >Browser Working Group of the W3C), for review. > > > >Cheers, > > > >Max Froumentin, W3C >

1 0

Registration of MIME media type Application/EDI-Tradacoms
by Kyle Meadors 06 Dec '03

06 Dec '03

MIME media type name: Application MIME subtype name: IETF Tree - EDI-Tradacoms Required parameters: None Optional parameters: CHARSET, as defined for MIME Encoding considerations: May need BASE64 or QUOTED-PRINTABLE transfer encoding on transports not capable of handling 8 BIT text Security considerations: Refer to RFC 1767 Section 7 Interoperability considerations: None Published specification: Refer to RFC 1767 Applications which use this media type: EDI, EDIINT Additional information: Magic number(s): none File extension(s): none Macintosh File Type Code(s): none Person & email address to contact for further information: Name: Kyle Meadors Email: kyle(a)drummondgroup.com Intended usage: COMMON. UK EDI standard to support EDIINT AS2 in UK Author/Change controller: Drummond Group Inc.

3 2

application/rdf+xml
by Graham Klyne 20 Nov '03

20 Nov '03

Following review comments, the W3C RDFcore working group's draft for registering application/RDF+XML was updated some time ago, per [1]: [1] http://www.ietf.org/internet-drafts/draft-swartz-rdfcore-rdfxml-mediatype-0… (after a brief absence, this is draft is now back online) No further comments have been noted, either on <ietf-types(a)iana.org>, or on <www-rdf-comments(a)w3.org>. The RDF specification has just completed its second W3C last-call, and is requested [3] for consideration for advancement to a Proposed Recommendation (W3C-speak for approximately draft standard). The specification documents are linked from [2]. [2] http://www.w3.org/2001/sw/RDFCore/#documents [3] http://lists.w3.org/Archives/Public/w3c-rdfcore-wg/2003Nov/0146.html Accordingly, I think it is appropriate that in the near future we request IESG consideration of this draft for RFC publication and registration of the Content Type. If there are any remaining issues, please let us know on <mailto:www-rdf-comments@w3.org>. Thanks. #g ------------ Graham Klyne For email: http://www.ninebynine.org/#Contact

1 0

Please review application/shf+xml
by Linus Walleij 29 Oct '03

29 Oct '03

We have just published an I-D for the Standard Hex Format, and this announcement is to ask the types-list to review it from a transport type perspective. http://www.ietf.org/internet-drafts/draft-strombergson-shf-00.txt Yours, Linus Walleij on behalf of the author group

5 21

Internet draft for sbml+xml media type
by Ben Kovitz 24 Oct '03

24 Oct '03

Hi, I've just submitted an Internet Draft for the sbml+xml media type. I and the other folks responsible for SBML (the Systems Biology Markup Langage) have incorporated the comments and suggestions from the folks on this list, especially getting a definite, persistent, named organization in place to serve as the change owner. The draft is here: http://www.ietf.org/internet-drafts/draft-sbml-media-type-00.txt Your comments are solicited. Thanks! Ben Kovitz bkovitz at caltech.edu Control and Dynamical Systems Dept. California Institute of Technology http://sbml.org

5 8

update: application/mathml+xml media type submission
by Max Froumentin 03 Oct '03

03 Oct '03

Following the first submission at [1], the W3C Math Working Group is submitting a revised version of the application/mathml+xml media type registration. This version removes the charset parameter, considered dangerous as prone to conflicts with XML encoding declaration, and corrects a typo in the draft. Max.

1 0