Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n97Frl36006258 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 7 Oct 2009 08:53:47 -0700 (MST) (envelope-from owner-ietf-xml-mime@mail.imc.org) Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id n97FrljX006257; Wed, 7 Oct 2009 08:53:47 -0700 (MST) (envelope-from owner-ietf-xml-mime@mail.imc.org) X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-xml-mime@mail.imc.org using -f Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by balder-227.proper.com (8.14.2/8.14.2) with SMTP id n97FrjeK006250 for ; Wed, 7 Oct 2009 08:53:46 -0700 (MST) (envelope-from derhoermi@gmx.net) Received: (qmail invoked by alias); 07 Oct 2009 15:53:44 -0000 Received: from dslb-094-223-180-186.pools.arcor-ip.net (EHLO hive) [94.223.180.186] by mail.gmx.net (mp001) with SMTP; 07 Oct 2009 17:53:44 +0200 X-Authenticated: #723575 X-Provags-ID: V01U2FsdGVkX19r/SUOBzVreU5RagD0lDMKyiJnwsRc0KpVO5cIag GEPGptypbEB4L5 From: Bjoern Hoehrmann To: Paul Libbrecht Cc: ietf-types@iana.org, ietf-xml-mime@imc.org, Math Working Group WG Subject: Re: please comment on media-type registrations for MathML Date: Wed, 07 Oct 2009 17:53:51 +0200 Message-ID: References: <1D5BF002-117F-499C-A845-5C777D7E76E1@activemath.org> <824BB76F-58B4-46FF-9899-92BDEE42754F@activemath.org> In-Reply-To: <824BB76F-58B4-46FF-9899-92BDEE42754F@activemath.org> X-Mailer: Forte Agent 3.3/32.846 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Y-GMX-Trusted: 0 X-FuHaFi: 0.61 Sender: owner-ietf-xml-mime@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: * Paul Libbrecht wrote: >> The first problem I have with this is that there is no word on what >> exactly the various types are for, like if there are any restrictions >> on what should be in a mathml-content+xml vs a mathml-presentation+xml >> document, or if the types can be used with MathML 2.0. > >that is defined in chapter 6: > http://www.w3.org/TR/2009/WD-MathML3-20090924/chapter6.html#encoding-names >should it be repeated in our appendix hence in this registration then? That does not say whether I can use these types with MathML 2.0 or not. I would rather say that the contents of 6.2.3 should be kept together with the registration information, and it would not hurt to elaborate a little bit more than the proposal does at the moment. Personally I can- not tell, for example, when I'd ever use mathml-content+xml. >Wouldn't it be wishable to reference draft-murata-kohn-lilley-xml-03 >instead? Does anyone know when it'd be authoritative. There have been proposals under that name for over five years now, it is not very likely that consensus around proposed changed will be found and reflected in updated drafts in the near future. >> The security considerations are missing (in fact the specification >> as a whole does not have a security considerations section either). > >Can you suggest something? >MathML entities exchanged on the web have the same risks as any >document that could contain relative references. Is this the kind of >sentence that could be there? MathML implementers will know better what kind of security problems they have addressed in their implementations, so perhaps they could contribute something to this. Yes, that would be the kind of sentence except that it's a bit too obvious perhaps. An actual issue that may have security implications is, for example, what if you get a MathML document that's labeled as "content" but actually has "presentation" markup or vice versa? >> I believe the text you have under "interoperability considerations" >> is misplaced there in all three cases. > >misplaced like it's wrongly formulated? Formatted? As in, it does not belong there. Interoperability considerations are for known and anticipated interoperability problems. To take the first entities with this media type also have the media type application/xml and may also have the media types application/presentation-mathml+xml or application/content-mathml+xml. That does not mention a problem, but makes a somewhat redundant state- ment, and then a misleading statement about the relationship of this type to other types (I would say both are in fact incorrect, entities are labeled with media types, they do not intrinsically "have" them). This is something I would expect in a discussion of the type that pre- cedes the template information. >> Under "Person & email address to contact for further information" >> the proposal fails to properly separate name and email address, use >> something like "Name
" instead. > >this appears clear If you mean that you disagree, then regardless of whether it is clear or not, it is common practise to do so. >> I do not think having a generic W3C / W3C Webmaster combination >> there is a good practise. > >Should there be an email? (there's one three lines above) >Should there be a group? That is easy to add. I would be fine with a pointer to the authorship and contact infor- mation in the specification. -- Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de 25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/ Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n97F9OlX002994 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 7 Oct 2009 08:09:24 -0700 (MST) (envelope-from owner-ietf-xml-mime@mail.imc.org) Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id n97F9OAf002993; Wed, 7 Oct 2009 08:09:24 -0700 (MST) (envelope-from owner-ietf-xml-mime@mail.imc.org) X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-xml-mime@mail.imc.org using -f Received: from smtp.dfki.de (lnv-106.sb.dfki.de [134.96.191.147]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n97F9LoK002982 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 7 Oct 2009 08:09:22 -0700 (MST) (envelope-from paul@activemath.org) Received: from smtp.dfki.de (localhost [127.0.0.1]) by imss.7 (Postfix) with ESMTP id 6CDAF317B2; Wed, 7 Oct 2009 17:09:00 +0200 (CEST) Received: from mail.dfki.de (lnv-104.sb.dfki.de [134.96.191.146]) by smtp.dfki.de (Postfix) with ESMTP id 5951A31702; Wed, 7 Oct 2009 17:09:00 +0200 (CEST) Received: from bledsoe.dfki.uni-sb.de (bledsoe.dfki.uni-sb.de [134.96.184.151]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mail.dfki.de (Postfix) with ESMTPSA id D56583111D; Wed, 7 Oct 2009 17:09:19 +0200 (CEST) Cc: ietf-types@iana.org, ietf-xml-mime@imc.org, Math Working Group WG Message-Id: <824BB76F-58B4-46FF-9899-92BDEE42754F@activemath.org> From: Paul Libbrecht To: Bjoern Hoehrmann In-Reply-To: Content-Type: multipart/signed; boundary=Apple-Mail-9--404430391; micalg=sha1; protocol="application/pkcs7-signature" Mime-Version: 1.0 (Apple Message framework v936) Subject: Re: please comment on media-type registrations for MathML Date: Wed, 7 Oct 2009 17:09:16 +0200 References: <1D5BF002-117F-499C-A845-5C777D7E76E1@activemath.org> X-Mailer: Apple Mail (2.936) Sender: owner-ietf-xml-mime@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: --Apple-Mail-9--404430391 Content-Type: text/plain; charset=ISO-8859-1; format=flowed; delsp=yes Content-Transfer-Encoding: quoted-printable thank you Bjoern, =09 Le 07-oct.-09 =E0 16:14, Bjoern Hoehrmann a =E9crit : >> In this specification draft, one can find three registrations for >> media-types related to MathML in the appendix B: >> http://www.w3.org/TR/2009/WD-MathML3-20090924/appendixb.html > > The first problem I have with this is that there is no word on what > exactly the various types are for, like if there are any restrictions > on what should be in a mathml-content+xml vs a mathml-presentation+xml > document, or if the types can be used with MathML 2.0. that is defined in chapter 6: = http://www.w3.org/TR/2009/WD-MathML3-20090924/chapter6.html#encoding-names= should it be repeated in our appendix hence in this registration then? > As per RFC 3023, the charset definition and encoding considerations > should be referenced as follows, which the proposals fails to do: > > Registrations for new XML-based media types under top-level types > other than "text" SHOULD, in specifying the charset parameter and > encoding considerations, define them as: "Same as [charset parameter > / encoding considerations] of application/xml as specified in RFC > 3023." I can change this. Wouldn't it be wishable to reference draft-murata-kohn-lilley-xml-03 =20 instead? Does anyone know when it'd be authoritative. > The security considerations are missing (in fact the specification > as a whole does not have a security considerations section either). Can you suggest something? MathML entities exchanged on the web have the same risks as any =20 document that could contain relative references. Is this the kind of =20 sentence that could be there? > I believe the text you have under "interoperability considerations" > is misplaced there in all three cases. misplaced like it's wrongly formulated? Formatted? > I note that under "Applications that use this media type" you have > "(todo)". Going to Last Call with "todo" markers left is not a good > practise. I note that the purpose of this field is to give a general > idea of what kind of applications use it, not to list individual > software products. thanks, will do. > Under "Person & email address to contact for further information" > the proposal fails to properly separate name and email address, use > something like "Name
" instead. this appears clear > I do not think having a generic W3C / W3C Webmaster combination =20 > there is a good practise. Should there be an email? (there's one three lines above) Should there be a group? That is easy to add. paul --Apple-Mail-9--404430391 Content-Disposition: attachment; filename=smime.p7s Content-Type: application/pkcs7-signature; name=smime.p7s Content-Transfer-Encoding: base64 MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIDDzCCAwsw ggJ0oAMCAQICECfgYPDm3JFN4mPGdyWyyVgwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UEBhMCWkEx JTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQ ZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA5MDUyNjA3MzIzNloXDTEwMDUyNjA3MzIz NlowcDEaMBgGA1UEBBMRTGliYnJlY2h0IEdvdXJkZXQxDTALBgNVBCoTBFBhdWwxHzAdBgNVBAMT FlBhdWwgTGliYnJlY2h0IEdvdXJkZXQxIjAgBgkqhkiG9w0BCQEWE3BhdWxAYWN0aXZlbWF0aC5v cmcwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDeZiQTdNavFBrVY7WMNWscajCzBRZF cWhrkQyh2V0CCrwx7ElHEM0asrD/FbmK+eor0aeav4u/3RKj3qOsV/HV8VRiM2zHaaErrp+/boPw FapmxhPk0TXLceFJAgL5ZA1RsfpcIxGzE/AQ5ic+MqZXp2tZkH6RNeOwoUTURZb2bOZWX5fA1G+L G+IVs20vAN6i/Kdud3JUe9ElfHWfJTl2eO42Hea5MVLnk2IkmCqzxC3CcEchOgOzIrnEjaj/JLPB ZZkDv6sTyEouG4qQHr4trSZCe5anTM2HoPVtmAoaz+Acyt2+0cwIUIPGDjk1K0mvrnCbVIOUNlUe FVJu0svnAgMBAAGjMDAuMB4GA1UdEQQXMBWBE3BhdWxAYWN0aXZlbWF0aC5vcmcwDAYDVR0TAQH/ BAIwADANBgkqhkiG9w0BAQUFAAOBgQDC0P6qlhvM4E2XepLgrDWLj7yp9obwKr2tZBvM3lXGCIyx edzPOMRQABPH3eBbvhKyMb64AoCttJ0vt+QcBLLtc9TkBxPyHyaRHmi4NUMlJJyy1z6pLNc0Ipec U+qv5ck7Cl2SUs7ZQps9ZSW++s4LKKrcdsEs9HD4myt1YusWKTGCAxAwggMMAgEBMHYwYjELMAkG A1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMT I1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBAhAn4GDw5tyRTeJjxnclsslYMAkG BSsOAwIaBQCgggFvMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTA5 MTAwNzE1MDkxNlowIwYJKoZIhvcNAQkEMRYEFIIIvBFfsRZJYqIQCtAS+EpbYHAZMIGFBgkrBgEE AYI3EAQxeDB2MGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5 KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQQIQJ+Bg 8ObckU3iY8Z3JbLJWDCBhwYLKoZIhvcNAQkQAgsxeKB2MGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQK ExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwg RnJlZW1haWwgSXNzdWluZyBDQQIQJ+Bg8ObckU3iY8Z3JbLJWDANBgkqhkiG9w0BAQEFAASCAQBe uuGAOyo4JTDfW32y8gLRovWjRkL21A/Ko4eyUkfeuwW2/qznByJARWmEu1YCLUm1zVYfa9F65rGa 1VKMe++CPcYhEdgBZ7kX/CQ6qGGuzzamJaVk7ORPwlbShhwlyTt0ShF43BR+gLkDpCMONvdel4+4 7c5BCzJoD/v2n1hAW2z5rBWpWCDssWIaJ8fUXAhRPdASnQX1g7je/zcHR+MDSzKTrGEXc7WjkyfR hcUbN37IvCV6E6dFLPAnulifXpbqV8Mtz6UAzYZ6XlscIwHgbZDohv/92xEwGsGzoBy7aSBF/2CC iSfS+wRCybOeDALVmjXaI3PAeTE5RPzLEZt3AAAAAAAA --Apple-Mail-9--404430391-- Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n97EEExA098637 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 7 Oct 2009 07:14:14 -0700 (MST) (envelope-from owner-ietf-xml-mime@mail.imc.org) Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id n97EEEU8098636; Wed, 7 Oct 2009 07:14:14 -0700 (MST) (envelope-from owner-ietf-xml-mime@mail.imc.org) X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-xml-mime@mail.imc.org using -f Received: from mail.gmx.net (mail.gmx.net [213.165.64.20]) by balder-227.proper.com (8.14.2/8.14.2) with SMTP id n97EE9Lm098627 for ; Wed, 7 Oct 2009 07:14:10 -0700 (MST) (envelope-from derhoermi@gmx.net) Received: (qmail invoked by alias); 07 Oct 2009 14:14:06 -0000 Received: from dslb-094-223-180-186.pools.arcor-ip.net (EHLO hive) [94.223.180.186] by mail.gmx.net (mp056) with SMTP; 07 Oct 2009 16:14:06 +0200 X-Authenticated: #723575 X-Provags-ID: V01U2FsdGVkX19C2fEBZZpCAYFFaqAzZVz0olr00+Efj/UWqfbFux ugpG36cpme+jpJ From: Bjoern Hoehrmann To: Paul Libbrecht Cc: ietf-types@iana.org, ietf-xml-mime@imc.org Subject: Re: please comment on media-type registrations for MathML Date: Wed, 07 Oct 2009 16:14:13 +0200 Message-ID: References: <1D5BF002-117F-499C-A845-5C777D7E76E1@activemath.org> In-Reply-To: <1D5BF002-117F-499C-A845-5C777D7E76E1@activemath.org> X-Mailer: Forte Agent 3.3/32.846 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Y-GMX-Trusted: 0 X-FuHaFi: 0.58 Sender: owner-ietf-xml-mime@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: * Paul Libbrecht wrote: >In this specification draft, one can find three registrations for >media-types related to MathML in the appendix B: > http://www.w3.org/TR/2009/WD-MathML3-20090924/appendixb.html The first problem I have with this is that there is no word on what exactly the various types are for, like if there are any restrictions on what should be in a mathml-content+xml vs a mathml-presentation+xml document, or if the types can be used with MathML 2.0. As per RFC 3023, the charset definition and encoding considerations should be referenced as follows, which the proposals fails to do: Registrations for new XML-based media types under top-level types other than "text" SHOULD, in specifying the charset parameter and encoding considerations, define them as: "Same as [charset parameter / encoding considerations] of application/xml as specified in RFC 3023." The security considerations are missing (in fact the specification as a whole does not have a security considerations section either). I believe the text you have under "interoperability considerations" is misplaced there in all three cases. I note that under "Applications that use this media type" you have "(todo)". Going to Last Call with "todo" markers left is not a good practise. I note that the purpose of this field is to give a general idea of what kind of applications use it, not to list individual software products. Under "Person & email address to contact for further information" the proposal fails to properly separate name and email address, use something like "Name
" instead. I do not think having a generic W3C / W3C Webmaster combination there is a good practise. -- Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de 25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/ Received: from balder-227.proper.com (localhost [127.0.0.1]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n97Dgnu4096040 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Wed, 7 Oct 2009 06:42:50 -0700 (MST) (envelope-from owner-ietf-xml-mime@mail.imc.org) Received: (from majordom@localhost) by balder-227.proper.com (8.14.2/8.13.5/Submit) id n97Dgn5G096039; Wed, 7 Oct 2009 06:42:49 -0700 (MST) (envelope-from owner-ietf-xml-mime@mail.imc.org) X-Authentication-Warning: balder-227.proper.com: majordom set sender to owner-ietf-xml-mime@mail.imc.org using -f Received: from smtp.dfki.de (lnv-106.sb.dfki.de [134.96.191.147]) by balder-227.proper.com (8.14.2/8.14.2) with ESMTP id n97DgjN8096032 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Wed, 7 Oct 2009 06:42:48 -0700 (MST) (envelope-from paul@activemath.org) Received: from smtp.dfki.de (localhost [127.0.0.1]) by imss.7 (Postfix) with ESMTP id 7EEBD317D6; Wed, 7 Oct 2009 15:42:22 +0200 (CEST) Received: from mail.dfki.de (lnv-104.sb.dfki.de [134.96.191.146]) by smtp.dfki.de (Postfix) with ESMTP id 6EA033125D; Wed, 7 Oct 2009 15:42:22 +0200 (CEST) Received: from bledsoe.dfki.uni-sb.de (bledsoe.dfki.uni-sb.de [134.96.184.151]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mail.dfki.de (Postfix) with ESMTPSA id 253AD310E9; Wed, 7 Oct 2009 15:42:42 +0200 (CEST) Message-Id: <1D5BF002-117F-499C-A845-5C777D7E76E1@activemath.org> From: Paul Libbrecht To: ietf-types@iana.org, ietf-xml-mime@imc.org Content-Type: multipart/signed; boundary=Apple-Mail-4--409625435; micalg=sha1; protocol="application/pkcs7-signature" Mime-Version: 1.0 (Apple Message framework v936) Subject: please comment on media-type registrations for MathML Date: Wed, 7 Oct 2009 15:42:44 +0200 X-Mailer: Apple Mail (2.936) Sender: owner-ietf-xml-mime@mail.imc.org Precedence: bulk List-Archive: List-ID: List-Unsubscribe: --Apple-Mail-4--409625435 Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Dear Media-types experts, the last-call period for MathML3 has now launched and is set to end Nov 11th. See the announce at: http://www.w3.org/mid/9F0A2A05-3BCD-4E00-8B63-0DE2419CB98E@ams.org In this specification draft, one can find three registrations for media-types related to MathML in the appendix B: http://www.w3.org/TR/2009/WD-MathML3-20090924/appendixb.html They are copied below. I would love comments on them until Nov 11th. Paul B.1 Media type for Generic MathML This registration is for community review and will be submitted to the IESG for review, approval, and registration with IANA. Type name: application Subtype name: mathml+xml Required parameters: none Optional parameters: charset as per [RFC3023] Encoding considerations: same as XML as specified in [RFC3023]. Security considerations: none Interoperability considerations: entities with this media type also have the media type application/xml and may also have the media types application/presentation-mathml+xml or application/content-mathml+xml. Published specification: MathML-3, draft at: http://www.w3.org/TR/MathML3/ Applications that use this media type: (todo) Additional information Magic number(s): see [RFC3023] File extension(s): .mml Windows Clipboard Name: MathML Macintosh file type code(s) MML Macintosh Universal Type Identifier code: public.mathml conforming to public.xml Person & email address to contact for further information: World Wide Web Consortium web-human@w3.org Intended usage: COMMON Restrictions on usage: None Author and Change controller: The MathML specification is the product of the World Wide Web Consortium's Math Working Group. The W3C has change control over this specification. B.2 Media type for Presentation MathML This registration is for community review and will be submitted to the IESG for review, approval, and registration with IANA. Type name: application Subtype name: mathml-presentation+xml Required parameters: none Optional parameters: charset as per [RFC3023] Encoding considerations: same as XML as specified in [RFC3023]. Security considerations: none Interoperability considerations: This media type is a more specific type than application/mathml+xml. Hence any entity of this type is also of the type application/mathml+xml as well as application/xml. An agent offering this specific media type MUST also offer the application/mathml+xml media type. An agent delivering an entity of this media type SHOULD only do so if it knows the receiving party supports it, for example thanks to the Accept http header, and should otherwise deliver the more generic type. Published specification: MathML-3, draft at: http://www.w3.org/TR/MathML3/ Applications that use this media type: (todo) Additional information: Magic number(s): see [RFC3023] File extension(s): none Windows Clipboard Name: MathML Presentation Macintosh file type code(s) MMLp Macintosh Universal Type Identifier code: public.mathml.presentation conforming to public.mathml (described above) conforming to public.xml Person & email address to contact for further information: World Wide Web Consortium web-human@w3.org Intended usage: COMMON Restrictions on usage: None Author and Change controller The MathML specification is the product of the World Wide Web Consortium's Math Working Group. The W3C has change control over this specification. B.3 Media type for Content MathML This registration is for community review and will be submitted to the IESG for review, approval, and registration with IANA. Type name: application Subtype name: mathml-content+xml Required parameters: none Optional parameters: charset as per [RFC3023] Encoding considerations: same as XML as specified in [RFC3023]. Security considerations: none Interoperability considerations: This media type is a more specific type than application/mathml+xml. Hence any entity of this type is also of the type application/mathml+xml as well as application/xml. An agent offering this specific media type MUST also offer the application/mathml+xml media type. An agent delivering an entity of this media type SHOULD only do so if it knows the receiving party supports it, for example thanks to the Accept http header, and should otherwise deliver the more generic type. Published specification: MathML-3, draft at: http://www.w3.org/TR/MathML3/ Applications that use this media type: (todo) Additional information: Magic number(s): see [RFC3023] File extension(s): none Windows Clipboard Name: MathML Content Macintosh file type code(s): MMLc Macintosh Universal Type Identifier code: public.mathml.content conforming to public.mathml (described above) conforming to public.xml Person & email address to contact for further information: World Wide Web Consortium web-human@w3.org Intended usage: COMMON Restrictions on usage: None Author and Change controller: The MathML specification is the product of the World Wide Web Consortium's Math Working Group. The W3C has change control over this specification. --Apple-Mail-4--409625435 Content-Disposition: attachment; filename=smime.p7s Content-Type: application/pkcs7-signature; name=smime.p7s Content-Transfer-Encoding: base64 MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIDDzCCAwsw ggJ0oAMCAQICECfgYPDm3JFN4mPGdyWyyVgwDQYJKoZIhvcNAQEFBQAwYjELMAkGA1UEBhMCWkEx JTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMTI1RoYXd0ZSBQ ZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBMB4XDTA5MDUyNjA3MzIzNloXDTEwMDUyNjA3MzIz NlowcDEaMBgGA1UEBBMRTGliYnJlY2h0IEdvdXJkZXQxDTALBgNVBCoTBFBhdWwxHzAdBgNVBAMT FlBhdWwgTGliYnJlY2h0IEdvdXJkZXQxIjAgBgkqhkiG9w0BCQEWE3BhdWxAYWN0aXZlbWF0aC5v cmcwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQDeZiQTdNavFBrVY7WMNWscajCzBRZF cWhrkQyh2V0CCrwx7ElHEM0asrD/FbmK+eor0aeav4u/3RKj3qOsV/HV8VRiM2zHaaErrp+/boPw FapmxhPk0TXLceFJAgL5ZA1RsfpcIxGzE/AQ5ic+MqZXp2tZkH6RNeOwoUTURZb2bOZWX5fA1G+L G+IVs20vAN6i/Kdud3JUe9ElfHWfJTl2eO42Hea5MVLnk2IkmCqzxC3CcEchOgOzIrnEjaj/JLPB ZZkDv6sTyEouG4qQHr4trSZCe5anTM2HoPVtmAoaz+Acyt2+0cwIUIPGDjk1K0mvrnCbVIOUNlUe FVJu0svnAgMBAAGjMDAuMB4GA1UdEQQXMBWBE3BhdWxAYWN0aXZlbWF0aC5vcmcwDAYDVR0TAQH/ BAIwADANBgkqhkiG9w0BAQUFAAOBgQDC0P6qlhvM4E2XepLgrDWLj7yp9obwKr2tZBvM3lXGCIyx edzPOMRQABPH3eBbvhKyMb64AoCttJ0vt+QcBLLtc9TkBxPyHyaRHmi4NUMlJJyy1z6pLNc0Ipec U+qv5ck7Cl2SUs7ZQps9ZSW++s4LKKrcdsEs9HD4myt1YusWKTGCAxAwggMMAgEBMHYwYjELMAkG A1UEBhMCWkExJTAjBgNVBAoTHFRoYXd0ZSBDb25zdWx0aW5nIChQdHkpIEx0ZC4xLDAqBgNVBAMT I1RoYXd0ZSBQZXJzb25hbCBGcmVlbWFpbCBJc3N1aW5nIENBAhAn4GDw5tyRTeJjxnclsslYMAkG BSsOAwIaBQCgggFvMBgGCSqGSIb3DQEJAzELBgkqhkiG9w0BBwEwHAYJKoZIhvcNAQkFMQ8XDTA5 MTAwNzEzNDI0NVowIwYJKoZIhvcNAQkEMRYEFGXSVLveR7RWigs6/7+SQjHB4XUGMIGFBgkrBgEE AYI3EAQxeDB2MGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQKExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5 KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwgRnJlZW1haWwgSXNzdWluZyBDQQIQJ+Bg 8ObckU3iY8Z3JbLJWDCBhwYLKoZIhvcNAQkQAgsxeKB2MGIxCzAJBgNVBAYTAlpBMSUwIwYDVQQK ExxUaGF3dGUgQ29uc3VsdGluZyAoUHR5KSBMdGQuMSwwKgYDVQQDEyNUaGF3dGUgUGVyc29uYWwg RnJlZW1haWwgSXNzdWluZyBDQQIQJ+Bg8ObckU3iY8Z3JbLJWDANBgkqhkiG9w0BAQEFAASCAQC4 9Cgq9ot3/HW/HA4kTkvGwQ7pAQZYL6zA9wLLRGyqR+lXtD/NqKvOVuQ1LVhyQwng+8sIzm70NVVe QkdHYDtEiGvW4shceOugp7Og4Y05vDsZ1OHcqvEbhiev5h8GRvhiI4pN1lqEVuSKxmhXub4MX8sb lj694Ii3kRv92SSnE9/9W4G+tgPf/MGHegWXkocr1/wlwjV/7pTFlsqULgcASS3Ye3eSgCd3KR0m W6C/BZajqQcngxfk43vC6fGGzi8O+9oLqXZI2Ej5t73PlFVRNI08iyHUflbiVaaDhuXNAZinsMhc wP46axa+lUbQLfJpvMzFKq8qK4P1YjKumUqcAAAAAAAA --Apple-Mail-4--409625435--