Registration of media type application/ttaf+xml
Philippe Le Hegaret
plh at w3.org
Wed Sep 30 21:46:15 CEST 2009
The following media type registration will be submitted to
the IESG for review, approval, and registration with IANA (as per [1]).
At this point, we would appreciate comments on this registration
information. If you see any problems, please let us know.
Regards,
Philippe
[1] http://www.w3.org/2002/06/registering-mediatype
[[
This appendix registers a new MIME media type, "application/ttaf+xml"
in conformance with [1144]BCP 13 and [1145]W3CRegMedia. The information
in this appendix is being submitted to the Internet Engineering
Steering Group (IESG) for review, approval, and registration with the
Internet Assigned Numbers Authority (IANA).
[1144] http://www.ietf.org/rfc/rfc4288.txt
[1145] http://www.w3.org/2002/06/registering-mediatype.html
MIME media type name:
application
MIME subtype name:
ttaf+xml
Required parameters:
None.
Optional parameters:
The encoding of a TT AF document must be determined by the
XML encoding declaration. This has identical semantics to the
application/xml media type in the case where the charset
parameter is omitted, as specified in [1146][XML Media],
Sections 8.9, 8.10 and 8.11.
The document profile of a TT AF document may be specified
using an optional profile parameter, which, if specified, the
value of which must adhere to the syntax and semantics of
ttp:profile parameter defined by Section [1147]6.2.8
ttp:profile of the published specification.
Encoding considerations:
Same for application/xml. See [1148][XML Media], Section 3.2.
Restrictions on usage:
None.
Security considerations:
As with other XML types and as noted in [1149][XML Media]
Section 10, repeated expansion of maliciously constructed XML
entities can be used to consume large amounts of memory,
which may cause XML processors in constrained environments to
fail.
In addition, because of the extensibility features for TT AF
and of XML in general, it is possible that
"application/ttaf+xml" may describe content that has security
implications beyond those described here. However, if the
processor follows only the normative semantics of the
published specification, this content will be outside TT AF
namespaces and may be ignored. Only in the case where the
processor recognizes and processes the additional content, or
where further processing of that content is dispatched to
other processors, would security issues potentially arise.
And in that case, they would fall outside the domain of this
registration document.
Interoperability considerations:
The published specification describes processing semantics
that dictate behavior that must be followed when dealing
with, among other things, unrecognized elements and
attributes, both in TT AF namespaces and in other namespaces.
Because TT AF is extensible, conformant
"application/ttaf+xml" processors must expect that content
received is well-formed XML, but it cannot be guaranteed that
the content is valid to a particular DTD or Schema or that
the processor will recognize all of the elements and
attributes in the document.
Published specification:
This media type registration is extracted from Appendix
[1150]D Media Type Registration of the [1151]Timed Text (TT)
Authoring Format 1.0 - Distribution Format Exchange Profile
(DFXP) specification.
[1151] http://www.w3.org/TR/ttaf1-dfxp/
Additional information:
None.
Person & email address to contact for further information:
Glenn Adams (public-tt at w3.org)
Intended usage:
COMMON
Author/Change controller:
The published specification is a work product of the World
Wide Web Consortium's Timed Text (TT) Working Group. The W3C
has change control over this specification.
]]
http://www.w3.org/TR/ttaf1-dfxp/#media-type-registration
More information about the Ietf-types
mailing list