Example Media Types for Use in Documentation
Extracted elements (10)
The 'example' media types are defined to provide a clearly illustrative placeholder in documentation and examples, avoiding the worst-case scenario where implementors mistake an example media type for a real protocol requirement.
Any attempt to negotiate or send the 'example' media type or any 'example' media subtype is bound to lead to interoperability problems.
IANA MUST NOT register any subtypes for the 'example' top-level media type.
The 'example' media subtypes (application/example, audio/example, etc.) MUST NOT be implemented. Their appearance in real code could lead to unpredictable results and therefore open up security holes.
The 'example' media type MUST NOT be implemented. Its appearance in real code could lead to unpredictable results and therefore open up security holes.
Eight 'example' subtypes are registered under standard top-level types: application/example, audio/example, image/example, message/example, model/example, multipart/example, text/example, and video/example, all for documentation use only.
The 'example' top-level media type is registered for documentation purposes; any subtype name may be used with it, and required/optional parameters and encoding considerations are defined by the user as needed.
IANA registers 'example' as a subtype within the 'application', 'audio', 'image', 'message', 'model', 'multipart', 'text', and 'video' media type trees, all intended for documentation use only.
IANA registers the 'example' top-level media type. IANA MUST NOT register any subtypes for the 'example' media type; subtypes may be freely invented by users for documentation purposes.
The 'example' media type and subtypes are defined for documentation only and MUST NOT be implemented. Any attempt to implement them in real code could lead to unpredictable results and potentially open security holes.