Registration of media type FO and ZFO
Hello, I wanted to ask you whether there is any progress or comment on our registration proposal. Thank you in advance for you reply. Best regards, Jakub Hytka Product manager Software602 a.s. TEL: 222 011 296, 222 011 602 FAX: 222 011 218 hytka@602.cz http://www.602.cz ------------------------------------------------------------------------------------ Our company would like to apply for registration of two media types into the VENDOR tree. These two media types are bound with media files with the .fo and .zfo extensions - both files representing e-forms used by the 602XML technology. ---FO--- Type name: application Subtype name: Vendor Tree - vnd.software602.filler.xml+form Required parameters: None Optional parameters: None Encoding considerations: UTF-8 Security considerations: FO is a XML-based plain text format, secured by signing the file itself through the means of the XML Signature standard. Interoperability considerations: There are no special interoperability issues. Published specification: Not available yet. Applications that use this media type: The FO file is used by the Software602 602XML applications - 602XML Filler, 602XML Designer, 602XML Designer Express and 602XML FormServer Additional information: Magic number(s): NONE File extension(s): FO Macintosh file type code(s): - Person & email address to contact for further information: Jakub Hytka, hytka@602.cz Intended usage: Common Restrictions on usage: None Author: Jakub Hytka Change controller: Jakub Hytka ---ZFO--- Type name: application Subtype name: Vendor Tree - vnd.software602.filler.xml+zip+form Required parameters: None Optional parameters: None Encoding considerations: UTF-8 Security considerations: ZFO is a XML-based plain text format packed using the ZIP archive algorithms. The XML content is secured by signing the file itself through the means of the XML Signature standard. The ZIP file itself can be protected in the usual way by setting up a password. Interoperability considerations: There are no special interoperability issues. Published specification: Not available yet. Applications that use this media type: The ZFO file is used by the Software602 602XML applications - 602XML Filler, 602XML Designer, 602XML Designer Express and 602XML FormServer Additional information: Magic number(s): NONE File extension(s): FO Macintosh file type code(s): - Person & email address to contact for further information: Jakub Hytka, hytka@602.cz Intended usage: Common Restrictions on usage: None Author: Jakub Hytka Change controller: Jakub Hytka Best regards, Jakub Hytka Product manager Software602 a.s. TEL: 222 011 296, 222 011 602 FAX: 222 011 218 hytka@602.cz http://www.602.cz
Jakub Hytka wrote:
I wanted to ask you whether there is any progress or comment on our registration proposal.
Hi, apparently you are talking about registrations in the vendor's tree. If there was a comment it should be in one of the list archives, it's also possible that nobody commented on this list...
Published specification: Not available yet.
...without specification application/vnd.software602.filler.xml+zip+form is whatever you think it is. Maybe look in the list archives for other cases of "xml" and "zip" and uses of "+", IIRC folks here have certain preferences how to get this right and what to avoid. You are not obliged to adopt these preferences, following established conventions could be nevertheless a good idea. After the review (or if nobody has a helpful comment) if you've made up your mind submit the templates using the Web form specified in RFC 4288: <http://www.iana.org/cgi-bin/mediatypes.pl> This is a ticket system, you'll get an e-mail with the IANA ticket number. If nothing else happens for a few weeks you could ask iana@iana what the state of your ticket is. Frank
On Wed, Jun 4, 2008 at 9:27 AM, Jakub Hytka <hytka@602.cz> wrote:
Type name: application
Subtype name: Vendor Tree - vnd.software602.filler.xml+form
Required parameters: None
Optional parameters: None
Encoding considerations: UTF-8
Security considerations: FO is a XML-based plain text format, secured by signing the file itself through the means of the XML Signature standard.
So the file is digitally signed, but in what form? That you say UTF-8 suggests it's some sort of text based form, no? The "+" convention also isn't necessarily intended to be reused outside of the context of XML, so "xml+form" won't mean anything to anybody. You could save a few characters and just use "form".
Type name: application
Subtype name: Vendor Tree - vnd.software602.filler.xml+zip+form
Required parameters: None
Optional parameters: None
Encoding considerations: UTF-8
Security considerations: ZFO is a XML-based plain text format packed using the ZIP archive algorithms. The XML content is secured by signing the file itself through the means of the XML Signature standard. The ZIP file itself can be protected in the usual way by setting up a password.
Similar comments apply here: the inclusion of "xml" and "zip" add no value AFAICT. This one seems quite clearly a binary format though. You can just say there's no encoding considerations. Mark.
Mark Baker napsal(a):
On Wed, Jun 4, 2008 at 9:27 AM, Jakub Hytka <hytka@602.cz> wrote:
Type name: application
Subtype name: Vendor Tree - vnd.software602.filler.xml+form
Required parameters: None
Optional parameters: None
Encoding considerations: UTF-8
Security considerations: FO is a XML-based plain text format, secured by signing the file itself through the means of the XML Signature standard.
So the file is digitally signed, but in what form? That you say UTF-8 suggests it's some sort of text based form, no?
The "+" convention also isn't necessarily intended to be reused outside of the context of XML, so "xml+form" won't mean anything to anybody. You could save a few characters and just use "form".
As it is stated there, it's a UTF-8 encoded plain XML file, which is digitally protected using the XML signature standard, which means the XML structure is embedded in the XML Signature tags containing the digital signature description. The "+" convention we wanted to use just to make the mime subtype description a little bit clearer on what's really inside the "form", in this sense describing that it's a XML file.
Type name: application
Subtype name: Vendor Tree - vnd.software602.filler.xml+zip+form
Required parameters: None
Optional parameters: None
Encoding considerations: UTF-8
Security considerations: ZFO is a XML-based plain text format packed using the ZIP archive algorithms. The XML content is secured by signing the file itself through the means of the XML Signature standard. The ZIP file itself can be protected in the usual way by setting up a password.
Similar comments apply here: the inclusion of "xml" and "zip" add no value AFAICT.
This one seems quite clearly a binary format though. You can just say there's no encoding considerations.
This is indeed a binary zipped archive, which includes the FO file basically. Therefore the encoding coniderations here i also entered UTF-8, however as you say, this may be avoided.
Mark.
Jakub
participants (3)
-
Frank Ellermann -
Jakub Hytka -
Mark Baker