How element types map to item content types
Rational® ClearCase® elements have a type and a subtype that specify how versions of the element are constructed and merged. When an element is imported into a Rational Team Concert repository, its type provides the import process with guidance about how to set the MIME content-type of the resulting item.
When the synchronization process or the ClearCase Version Importer imports a file element into the repository, it maps the elements type to a MIME content type as displayed in Table 1.
Element type | MIME content-type |
---|---|
binary_delta_file | application/unknown |
compressed_file | application/unknown |
compressed_text_file | text/plain |
file | application/unknown |
file_system_object | application/unknown |
html | application/html |
msword | application/msword |
process_def_object | application/unknown |
rose | application/unknown |
rosert | application/unknown |
text_file | text/plain |
utf16be_file | text/plain |
utf16le_file | text/plain |
utf32be_file | text/plain |
utf32le_file | text/plain |
utf8_file | text/plain |
xde | application/unknown |
xml | application/xml |
If the element type is not included in Table 1, the closest match is used.