DR-09-0034 (was "Re: DR-09-0032 and DR-09-0034")
MURATA Makoto (FAMILY Given)
eb2m-mrt at asahi-net.or.jp
Wed Feb 25 14:43:13 CET 2009
Shawn,
I didn't know the web form you mentioned, but it is mentioned
in RFC 4288. Thank you for enlightening me.
Here is my first cut.
Required parameters
None.
Optional parameters
charset, as specified in 3.2 of RFC 3023.
Encoding considerations
The same as in application/xml (3.2 of RFC 3023).
Security considerations
The same as in application/xml (3.2 of RFC 3023).
Interoperability considerations
The same as in application/xml (3.2 of RFC 3023).
Published Specification
ISO/IEC 29500:2008, Part X, Clause X.X.X
Applications using this type
OOXML applications
Magic number(s)
None
File extension(s)
xml
Mac File Type(s)
"TEXT"
OID(s)
???? (I do not understand. Can we simply skip this field?)
Intended usage
Common
We might want to say that OOXML documents are zip files and that our
media types are labels for files within such zip files. By the way,
when the pack URI scheme is used to reference to files within OOXML
zip files, will our media types be returned?
Although we can directly contact IANA, I think we should first send a
proposal to the IETF-type ML.
Cheers,
--
MURATA Makoto (FAMILY Given) <EB2M-MRT at asahi-net.or.jp>
More information about the sc34wg4
mailing list