[media-types] Ideas for Multipart Media Types

Adam Sobieski <[email protected]>
Newsgroups gmane.ietf.types
Message-ID <DS4PPF69F41B22E0E5E9C889847903701AAC59FA@DS4PPF69F41B22E.NAMP223.PROD.OUTLOOK.COM>
IETF Media Type Maintenance Working Group,

Hello. Per Media Type Specifications and Registration Procedures, Section 5, Media Type Registration Procedures, I am writing this informal letter to "solicit comments and feedback on the choice of type/subtype name, the unambiguity of the references with respect to versions and external profiling information, and a review of any interoperability or security considerations."

I welcome any comments, feedback, and discussion about the following four ideas.



multipart/template

This multipart type would be for multiple parts which, together, could be used to create output resources using template-processing engines. The multiple input parts would be comprised of: (1) a required template resource, (2) an optional scripting-language resource for providing helper functions, and (3) an optional input data resource.

Examples of template formats include Handlebars ("text/x-handlebars-template"). Examples of scripting formats for providing optional helper functions include JavaScript ("text/javascript"). Examples of optional input data formats include JSON ("application/json").

As considered, this multipart type would have a parameter for specifying the media type of the resultant output content to be produced by a template-processing engine using the input parts.

For example: "multipart/template;output='application/xhtml+xml'"



multipart/difference

This multipart type would be for multiple parts which, together, could be used to apply differences or patches to input resource to create output resources using difference-applying engines. The multiple input parts would be comprised of: (1) a required input resource to apply a difference or patch to, and (2) a required difference or patch to apply.

Examples of difference or patch formats include: "text/x-diff" and "text/x-patch".

As considered, this multipart type would have a parameter for specifying the media type of the resultant output content to be produced by a difference-applying engine using the input parts.

For example: "multipart/difference;output='application/xhtml+xml'"



multipart/intersect

This multipart type would be for multiple parts capable of being intersected to create a resultant output resource. Examples of formats capable of being intersected include knowledge-graph formats such as "text/turtle".

As considered, this multipart type would have a parameter for specifying the media type of the resultant output content to be produced by an intersection algorithm using the input parts.

For example: "multipart/intersect;output='text/turtle'"



multipart/union

This multipart type would be for multiple parts capable of being unioned to create a resultant output resource. Examples of formats capable of being unioned include knowledge-graph formats such as "text/turtle".

As considered, this multipart type would have a parameter for specifying the media type of the resultant output content to be produced by a union algorithm using the input parts.

For example: "multipart/union;output='text/turtle'"



Thank you for any comments, feedback, or discussion about these ideas. Thank you for any information about guidelines for creating formal proposals or specifications for multipart media types.


Best regards,
Adam Sobieski
http://www.phoster.com

_______________________________________________
media-types mailing list -- [email protected]
To unsubscribe send an email to [email protected]
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.