Implementation Date : 2003.03.19
Revision Date : 2012.07.22
Review Date : 2012.08.01
Next Review : 2017.08
- identification: Yes, by parsing the entire file or the first 65536 characters for large files. Plain Text can only contain octets with hexadecimal value in the range of [0x07, 0x0d], [0x20, 0x7e], [0x80, 0xfe], and 0x1b.
- validation: Yes. Same rules as identification.
- characterization: Yes. Extracted format metadata are described in Section 2.1 of Plain Text Action Plan Background.
- migration: No
- normalization: No
Plain text exhibits the following significant properties (note 1). It is intended to preserve and evaluate these significant properties when adopting migration or normalization policy in the future.
- content: All content, including every character, will be preserved.
- context: N/A. Plain Text does not contain metadata to describe the environment where it was originally created or used.
- behavior: N/A. Plain Text does not provide interactive characteristics.
- structure: The location of every linebreak will be preserved. There is no other predefined structure for Plain Text.
- appearance: N/A. Plain Text does not store appearance attributes such as font (including font size or font style), color, alignment, etc.
Long-term Preservation Strategy
Long-term Preservation Strategy for the original
Plain text files will be preserved “as is”.
Long-term Preservation Strategy for the normalized
- No actions
1. “From digital volatility to digital permanence, Preserving text documents”, Jacqueline Slats, The Hague, November 2003, http://www.digitaleduurzaamheid.nl/bibliotheek/docs/volatility-permanence-textdocs-en.pdf