On alternative format imports states that "plain text" is an accepted format. This part is ambiguous as there are numerous standard definitions of what "plain text" is. Also, this same section makes references to "Rich text format" which is a proprietary format owned by a single foreign company.

11.3.1

te

Proposed Disposition of DIS 29500 Comment PH-0006 (Modified: 2007-11-26) Agreed; these references are inappropriate; the following changes will be made in Part 1, §11.3.1: Page 28, Line 1, “Content Type” row Content Type: Any content, support for which is application-defined. [Note: Some examples of formats which might be supported include: Text = application/txt RTF = application/rtf HTML = application/html XML = application/xml end note] Page 28, lines 3-5 An alternative format import part allows content specified in an application-defined alternate format (HTML, MHTML, RTF, earlier versions of WordprocessingML, or plain text) to be embedded directly in a WordprocessingML document in order to allow that content to be migrated to the WordprocessingML format. Page 28, lines 15-17 A WordprocessingML consumer shall who understands the format of an instance of this part should treat the its contents of such legacy text files as if they were formatted using equivalent WordprocessingML, and if that consumer is also a WordprocessingML producer, it shall emit the legacy text contents of the part in WordprocessingML format. Similar Comments: CL-0040 , DE-0006 , DE-0150 , DK-0101 , DK-0151 , DK-0156 , FR-0014 , GB-0041 , KE-0004 , MT-0005 , US- 0033