\chapter{IANA Considerations}


%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
% Content-Type Registration
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
\section{Content-Type Registration}


\subsection{CMIS Query}

A CMIS Query Document, when serialized as XML 1.0, can be identified with the following media type:

\textbf{MIME media type name:} application

\textbf{MIME subtype name:} cmisquery +xml

\textbf{Mandatory parameters:} None

\textbf{Optional parameters:}
"charset": This parameter has semantics identical to the charset parameter of the "application/xml" media type as specified in \hyperref[intro:rfc3023]{[RFC3023]}.

\textbf{Encoding considerations:}
Identical to those of "application/xml" as described in \hyperref[intro:rfc3023]{[RFC3023]}, Section 3.2.

\textbf{Security considerations:}
As defined in this specification. In addition, as this media type uses the "+xml" convention, it shares the same security considerations as described in \hyperref[intro:rfc3023]{[RFC3023]}, Section 10. 

\textbf{Interoperability considerations:}
There are no known interoperability issues.

\textbf{Published specification:} This specification.

\textbf{Applications that use this media type:}
No known applications currently use this media type.

\textbf{Additional information:}

\textbf{Magic number(s):}
As specified for "application/xml" in \hyperref[intro:rfc3023]{[RFC3023]}, Section 3.2. 

\textbf{File extension:} .cmisquery

\textbf{Fragment identifiers:} 
As specified for "application/xml" in \hyperref[intro:rfc3023]{[RFC3023]}, Section 5.

\textbf{Base URI:}
As specified in \hyperref[intro:rfc3023]{[RFC3023]}, Section 6.

\textbf{Macintosh File Type code:} TEXT

\textbf{Person and email address to contact for further information:}
OASIS CMIS TC <cmis@lists.oasis-open.org>

\textbf{Intended usage:} COMMON

\textbf{Author/Change controller:} IESG


\subsection{CMIS AllowableActions}

 A CMIS Allowable Actions Document, when serialized as XML 1.0, can be identified with the following media type:

\textbf{MIME media type name:} application

\textbf{MIME subtype name:} cmisallowableactions +xml

\textbf{Mandatory parameters:} None.

\textbf{Optional parameters:}
"charset": This parameter has semantics identical to the charset parameter of the "application/xml" media type as specified in \hyperref[intro:rfc3023]{[RFC3023]}.

\textbf{Encoding considerations:}
Identical to those of "application/xml" as described in \hyperref[intro:rfc3023]{[RFC3023]}, Section 3.2.

\textbf{Security considerations:} As defined in this specification.
In addition, as this media type uses the "+xml" convention, it shares the same security considerations as described in \hyperref[intro:rfc3023]{[RFC3023]}, Section 10. 

\textbf{Interoperability considerations:}
There are no known interoperability issues.

\textbf{Published specification:} This specification.

\textbf{Applications that use this media type:}
No known applications currently use this media type.

\textbf{Additional information:}

\textbf{Magic number(s):}
As specified for "application/xml" in \hyperref[intro:rfc3023]{[RFC3023]}, Section 3.2. 

\textbf{File extension:} .cmisallowableactions

\textbf{Fragment identifiers:}
As specified for "application/xml" in \hyperref[intro:rfc3023]{[RFC3023]}, Section 5.

\textbf{Base URI:} As specified in \hyperref[intro:rfc3023]{[RFC3023]}, Section 6.

\textbf{Macintosh File Type code:} TEXT

\textbf{Person and email address to contact for further information:}
OASIS CMIS TC <cmis@lists.oasis-open.org>

\textbf{Intended usage:} COMMON

\textbf{Author/Change controller:} IESG


\subsection{CMIS Tree}

A CMIS Tree Document, when serialized as XML 1.0, can be identified with the following media type:

\textbf{MIME media type name:} application

\textbf{MIME subtype name:} cmistree +xml

\textbf{Mandatory parameters:} None.

\textbf{Optional parameters:}
"charset": This parameter has semantics identical to the charset parameter of the "application/xml" media type as specified in \hyperref[intro:rfc3023]{[RFC3023]}.

\textbf{Encoding considerations:} 
Identical to those of "application/xml" as described in \hyperref[intro:rfc3023]{[RFC3023]}, Section 3.2.

\textbf{Security considerations:} As defined in this specification.
In addition, as this media type uses the "+xml" convention, it shares the same security considerations as described in \hyperref[intro:rfc3023]{[RFC3023]}, Section 10. 

\textbf{Interoperability considerations:} 
There are no known interoperability issues.

\textbf{Published specification:} This specification.

\textbf{Applications that use this media type:}
No known applications currently use this media type.

\textbf{Additional information:}

\textbf{Magic number(s):}
As specified for "application/xml" in \hyperref[intro:rfc3023]{[RFC3023]}, Section 3.2. 

\textbf{File extension:} .cmistree

\textbf{Fragment identifiers:} 
As specified for "application/xml" in \hyperref[intro:rfc3023]{[RFC3023]}, Section 5.

\textbf{Base URI:} 
As specified in \hyperref[intro:rfc3023]{[RFC3023]}, Section 6.

\textbf{Macintosh File Type code:} TEXT

\textbf{Person and email address to contact for further information:} 
OASIS CMIS TC <cmis@lists.oasis-open.org>

\textbf{Intended usage:} COMMON

\textbf{Author/Change controller:} IESG


\subsection{CMIS Atom}

A CMIS Atom Document, when serialized as XML 1.0, can be identified with the following media type:


\textbf{MIME media type name:} application

\textbf{MIME subtype name:} cmisatom +xml

\textbf{Mandatory parameters:} None.

\textbf{Optional parameters:}
"charset": This parameter has semantics identical to the charset parameter of the "application/xml" media type as specified in \hyperref[intro:rfc3023]{[RFC3023]}.
"type": This parameter has semantics identical to the type parameter of the "application/atom+xml" as specified in 
\hyperref[intro:rfc4287]{[RFC4287]}

\textbf{Encoding considerations:} 
Identical to those of "application/xml" as described in \hyperref[intro:rfc3023]{[RFC3023]}, Section 3.2.

\textbf{Security considerations:} As defined in this specification.
In addition, as this media type uses the "+xml" convention, it shares the same security considerations as described in \hyperref[intro:rfc3023]{[RFC3023]}, Section 10. 

\textbf{Interoperability considerations:} 
There are no known interoperability issues.

\textbf{Published specification:} This specification.

\textbf{Applications that use this media type:} 
No known applications currently use this media type.

\textbf{Additional information:}

\textbf{Magic number(s):} 
As specified for "application/xml" in \hyperref[intro:rfc3023]{[RFC3023]}, Section 3.2. 

\textbf{File extension:} .cmisatom

\textbf{Fragment identifiers:} 
As specified for "application/xml" in \hyperref[intro:rfc3023]{[RFC3023]}, Section 5.

\textbf{Base URI:} 
As specified in \hyperref[intro:rfc3023]{[RFC3023]}, Section 6.

\textbf{Macintosh File Type code:} TEXT

\textbf{Person and email address to contact for further information:} 
OASIS CMIS TC <cmis@lists.oasis-open.org>

\textbf{Intended usage:} COMMON

\textbf{Author/Change controller:} IESG

Please see section \ref{atom:namespaces} on why this media type is needed above the Atom Media Type.


\subsection{CMIS ACL}

A CMIS ACL Document, when serialized as XML 1.0, can be identified with the following media type:


\textbf{MIME media type name:} application

\textbf{MIME subtype name:} cmisacl +xml

\textbf{Mandatory parameters:} None.

\textbf{Optional parameters:} 
"charset": This parameter has semantics identical to the charset parameter of the "application/xml" media type as specified in \hyperref[intro:rfc3023]{[RFC3023]}.

\textbf{Encoding considerations:} 
Identical to those of "application/xml" as described in \hyperref[intro:rfc3023]{[RFC3023]}, Section 3.2.

\textbf{Security considerations:} As defined in this specification.
In addition, as this media type uses the "+xml" convention, it shares the same security considerations as described in \hyperref[intro:rfc3023]{[RFC3023]}, Section 10. 

\textbf{Interoperability considerations:} 
There are no known interoperability issues.

\textbf{Published specification:} This specification.

\textbf{Applications that use this media type:} 
No known applications currently use this media type.

\textbf{Additional information:} 

\textbf{Magic number(s):} 
As specified for "application/xml" in \hyperref[intro:rfc3023]{[RFC3023]}, Section 3.2. 

\textbf{File extension:} .cmisacl

\textbf{Fragment identifiers:} 
As specified for "application/xml" in \hyperref[intro:rfc3023]{[RFC3023]}, Section 5.

\textbf{Base URI:} 
As specified in \hyperref[intro:rfc3023]{[RFC3023]}, Section 6.

\textbf{Macintosh File Type code:} TEXT

\textbf{Person and email address to contact for further information:} 
OASIS CMIS TC <cmis@lists.oasis-open.org>

\textbf{Intended usage:} COMMON

\textbf{Author/Change controller:} IESG

