draft registration of application/vnd.kde.kpartgui+xml

[Marc Mutz]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Saturday 06 July 2002 20:54, David Faure wrote:
<snip>
> I think it's quite easy to add support for loading both, registering
> with <Gui> or with both, and starting to use <Gui> in CVS (for apps
> which rely on kdelibs-cvs anyway), or in KDE 4 for the other apps.
>
> I volunteer to do the change in the loading code, and to convert the
> CVS apps after some time (to avoid the breakage for those who
> partially updated ;). This (now nonsense) "KPartGui" element name has
> been bugging me for a while (e.g. it's hard to explain why it should
> be KPartGui when making an XMLGUI tutorial).

Ok, here's an updated draft. Both in complete and in diff form.

- --- kpartgui-mimetype.txt~	Thu Jul  4 00:13:43 2002
+++ kpartgui-mimetype.txt	Mon Jul  8 13:11:35 2002
@@ -1,10 +1,10 @@
 
 To: ietf-types at iana.org
- -Subject: Registration of MIME media type 
application/vnd.kde.kpartgui+xml
+Subject: Registration of MIME media type application/vnd.kde.gui+xml
 
 MIME media type name: application
 
- -MIME subtype name: vnd.kde.kpartgui+xml
+MIME subtype name: vnd.kde.gui+xml
 
 Required parameters: none
 
@@ -12,31 +12,31 @@
 
 Encoding considerations: (is there a std text for XML files?)
 
- -	Since KPartGui files are XML applications, 7bit is often
+	Since XMLGUI files are XML applications, 7bit is often
 	appropriate. For the rare case that identifiers are not
 	US-ASCII, 8bit should be used.
 
 Security considerations:
 
- -        KPartGui files can include personal toolbar layouts and
- -        keybinding definition.  To the extend that such metadata can
- -        be considered private, sending a KPartGui file could lead to
- -        leakage of this type of information.  A well-placed KPartGui
+        XMLGUI files can include personal toolbar layouts and
+        keybinding definitions.  To the extent that such metadata can
+        be considered private, sending a XMLGUI file could lead to
+        leakage of this type of information.  A well-placed XMLGUI
         file can be used to change the layout of toolbars and the
         binding of shortcut keys to application actions. This could
         potentially be used to trick the user in executing an action
         that she did not intend to execute.
 
 	Other than the above, it is believed that usage of this
- -        mimetype does not introduce security concerns other that those
+        mimetype does not introduce security concerns other than those
         already inherent in XML documents.
 
 Interoperability considerations: none
 
 Published specification:
 
- -        The DTD of the KPartGui XML application can be obtained from
- -        http://www.kde.org/DTD/kpartgui-current.dtd (### to be 
adjusted)
+        The DTD of the XMLGUI XML application can be obtained from
+        http://www.kde.org/DTD/xmlgui-current.dtd (### to be adjusted)
 
         A description of the format is contained in the DTD file in
         the form of comments.
@@ -48,7 +48,7 @@
 
 Additional information:
 
- -        Magic numbers: XML document with root node "kpartgui"
+        Magic numbers: XML document with root node "Gui"
         File extensions: none specific, usually rc
         Macintosh File Type Codes: n/a
 

Marc

- -- 
Marc Mutz <mutz at kde.org>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE9KXRi3oWD+L2/6DgRAmOEAJ9GRs4gE9RTYh8bEuFRg9BQV2oIUwCgiToy
bKAbtpwRYu/SQsI7kQ2gLLM=
=CRxm
-----END PGP SIGNATURE-----
-------------- next part --------------

To: ietf-types at iana.org
Subject: Registration of MIME media type application/vnd.kde.gui+xml

MIME media type name: application

MIME subtype name: vnd.kde.gui+xml

Required parameters: none

Optional parameters: none

Encoding considerations: (is there a std text for XML files?)

	Since XMLGUI files are XML applications, 7bit is often
	appropriate. For the rare case that identifiers are not
	US-ASCII, 8bit should be used.

Security considerations:

        XMLGUI files can include personal toolbar layouts and
        keybinding definitions.  To the extent that such metadata can
        be considered private, sending a XMLGUI file could lead to
        leakage of this type of information.  A well-placed XMLGUI
        file can be used to change the layout of toolbars and the
        binding of shortcut keys to application actions. This could
        potentially be used to trick the user in executing an action
        that she did not intend to execute.

	Other than the above, it is believed that usage of this
        mimetype does not introduce security concerns other than those
        already inherent in XML documents.

Interoperability considerations: none

Published specification:

        The DTD of the XMLGUI XML application can be obtained from
        http://www.kde.org/DTD/xmlgui-current.dtd (### to be adjusted)

        A description of the format is contained in the DTD file in
        the form of comments.

Applications which use this media type:

	All KDE applications that make use of the XMLGUI framework,
	esp. those using KParts technology.

Additional information:

        Magic numbers: XML document with root node "Gui"
        File extensions: none specific, usually rc
        Macintosh File Type Codes: n/a

Person & email address to contact for further information:

        <anyone?>

Intended usage: COMMON

Author/Change contoller: Marc Mutz <mutz at kde.org>