Dear Frank Ellermann, I am really really sorry but I have just found apparently there was some email trouble and my reply was not distributed to the list... We W3C Multimodal Interaction Working Group completely agree with you. Could you please see below for the details? Frank Ellermann wrote:

Kazuyuki Ashimura wrote:

------------------------------------------ Comment1: Reference for "security issues" ------------------------------------------

...

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.

Yes, we agree with you and will refer RFC3986 instead of RFC1738. We will also add following reference to the spec: [[ [RFC3986] Uniform Resource Identifier (URI): Generic Syntax. IETF RFC 3986. http://www.ietf.org/rfc/rfc3986.txt ]] -------------------------------------------- Comment2: Text on "Published specification" --------------------------------------------

...

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.

Yes, we agree we should explicitly mention the spec name in the appendix B at: http://www.w3.org/TR/2006/WD-InkML-20061023/#media-type-registration We will modify above text to: [[ This media type registration is extracted from Appendix B of the Ink Markup Language (InkML) specification. ]] and add a link from the text "the Ink Markup Language (InkML) specification" to: http://www.w3.org/TR/2006/WD-InkML-20061023/ as the "Scalable Vector Graphics (SVG) Tiny 1.2 Specification" says at: http://www.w3.org/TR/SVGMobile12/mimereg.html Sincerely, Kazuyuki Ashimura -- Kazuyuki Ashimura / W3C Multimodal & Voice Activity Lead mailto: ashimura@w3.org voice: +81.466.49.1170 / fax: +81.466.49.1171