| | 189 | |
| | 190 | A CMDI file contains the actual metadata of one specific resource (hereafter referred to as the described resource), and might also be referred to as a CMDI record. All CMDI files have the same structure at the top level. At a lower level, parts of its structure are defined by the CMDI profile upon which it is based. |
| | 191 | == The main structure == |
| | 192 | A CMDI file has the root element CMD with 4 subelements: |
| | 193 | * The Header element, containing certain administrative information about the CMDI file, i.e. metadata about the file itself |
| | 194 | * The Resources element, listing resource proxies and their interrelations, by the following subelements |
| | 195 | * ResourceProxyList, containing a list of ResourceProxy elements, each referencing a file contained in or closely related to the described resource |
| | 196 | * JournalFileProxyList, containing a list of JournalFileProxy elements, each referencing a file (“journal file”) containing provenance information about the described resource |
| | 197 | * ResourceRelationList, containing a list of ResourceRelation elements, each representing a relationship between 2 resource files (as listed in the ResourceProxyList) |
| | 198 | * IsPartOf list, containing a list of IsPartOf elements, each referencing a larger external resource of which the described resource (as a whole) forms a part |
| | 199 | * Components, containing one subelement corresponding to – and in turn structured according to - the CMDI profile applied. |
| | 200 | |
| | 201 | The profile substructure exist in the profile-specific namespace, all the rest within the cmd namespace. |
| | 202 | |
| | 203 | <About local attributes here> |
| | 204 | |
| | 205 | In the following the main parts are described in detail |
| | 206 | |
