XMind is the most professional and popular mind mapping tool. Millions of people use XMind to clarify thinking, manage complex information, run brainstorming and get work organized.
This document describes the general specification of an XMind file. Table of Contents. ZIP An XMind file (workbook) is actually a standard archive encapsulating multiple data files and asset files.
Supported compression methods include Store (no compression) and Deflate (compressed). Applications may choose between one of these two methods to store each archive component. Methods other than these two may or may not be supported by the official XMind app.
XMind files store encrypted contents using a for enhanced and flexible security. Note that this is NOT what.
XMind does NOT support ZIP's encryption methods and can NOT open files encrypted that way. Topic 1 Topic 2 xmap-content The root element of.
Attributes:. version: (required) the version of this document, currently 2.0. Elements:.: 1,n) the sheets of this workbook sheet A sheet element represents a mind map with a root topic.
Attributes:. id: (required) the unique identifier of this sheet.
style-id: the identifier of the style this sheet uses. theme: the identifier of the theme style this sheet uses.
Elements:.: 0,1 the title of this sheet.: 0,1 the root topic of this sheet.: 0,1 the relationship container of this sheet.: 0,1 the legend of this sheet topic A topic element represents a topic in a mind map. A topic may have children topics (or none), but must have only one parent (or none).
Xmap-styles The root element of. Attributes:. version: (required) the version of this document, currently 2.0. Elements:.: normal styles.: master styles.: automatic styles styles A styles element represents the normal style group of a style sheet. Elements:.: 0,n) styles in this group master-styles A master-styles element represents the master style group of a style sheet.
Elements:.: 0,n) styles in this group automatic-styles A automatic-styles element represents the automatic style group of a style sheet. Elements:.: 0,n) styles in this group style A style element represents a style. Attributes:. id: (required) the global identifier of this style. type: (required) the type of this style.
topic. map. boundary.
relationship. summary. theme.
name: the name of this style. Elements:.: 0,n) xxx must be the the type attribute of this style element xxx-properties This kind of elements represent sets of properties of a style. Foo Bar [email protected] Foo Bar Company Oct 14, 2016 4:38:14 PM XMind R3.6.42338 meta The root element of. Attributes:.
version: (required) the version of this document, currently 2.0. Elements: storing key-value metadata items in a hierarchical manner, e.g. An item with key Category/Foo and value Bar should be stored as Bar markers/markerSheet.xml The markers/markerSheet.xml contains marker information of this workbook, used to describe custom markers embedded in this workbook. System default markers will never be embedded. Marker-sheet The root element of. Attributes:. version: (required) the version of this document, currently 2.0.
Elements:.: 0,n) groups of markers marker-group A marker-group element represents a group of markers. Attributes:. id: (required) the unique identifier of this marker group.
name: the name of this marker group. singleton: whether this marker group is singleton. No more than one marker from a singleton group can be referenced by one single topic. Elements:.: 0,n) markers in this group marker A marker element represents a marker. Attributes:.
id: (required) the unique identifier of this marker. name: the name of this marker. resource: the location of the resource used to display this marker (e.g. An image file) META-INF/manifest.xml The META-INF/manifest.xml contains file entry information of this workbook archive.
Manifest The root element of. Attributes:.
version: (required) the version of this document, currently 2.0. Elements:.: 0,n) the file entries of this workbook file-entry A file-entry element represents a file entry in this workbook. Attributes:.
full-path: (required) the full path of this file entry within the archive. media-type: the media type of this file entry. Elements:.: 0,1 the encryption data of this file entry (if encrypted) encryption-data A encryption-data element contains encryption information of a file entry. See section for details. Attributes:.
checksum-type: name of the algorithm used to generate the file checksum. checksum: the checksum result generated using the algorithm defined by checksum-type against the content of the file entry. Elements:.: 1,1 the encryption algorithm and parameters.: 1,1 the key derivation algorithm and parameters algorithm An algorithm element contains information about the cipher algorithm used to encrypt the content of a file entry. Attributes:. algorithm-name: (required) the name of the cipher algorithm, e.g. AES/CBC/PKCS5Padding key-derivation A key-derivation element contains information about how to derive secret keys from the password.
Attributes:. key-derivation-name: (required) the name of the key-derivation algorithm, e.g. PBKDF2WithHmacSHA512. size: the length of the secret key (in bits), e.g. 128. iteration-count: iteration count of the key derivation, e.g. 1024.
iv: the initialization vector (IV) encoded by, random for each file entry. salt: the salt encoded by Base64, random for each file entry Encryption Creators of XMind files may choose to protect the file content by encrypting it against a password, and then any one who wants to read the content from the file have to use the same password and the same encryption methods to decrypt it in prior. Since an XMind file is composite content, the creator may choose which components to be encrypted and how they are encrypted. The encryption information of each file entry, EXCEPT the password, should be recorded in the file, and thus the META-INF/manifest.xml itself should never be encrypted. Recent versions of XMind applications (v3.6.50+) use the following two algorithms and parameters to do encryption/decryption:.
![]()
Cipher algorithm:. Key: derived from password using the following key-derivation algorithm. IV: 16 random bytes.
Key-derivation algorithm:. Password: the password given by the creator/reader.
Salt: 8 random bytes. Iteration Count: 1024 (times). Key Size: 128 (bits) However, versions before XMind 7.5 (v3.6.50) use a legacy key-derivation algorithm and a byte array of 16 0x00 (i.e. New byte16) as the IV. Newer versions of XMind applications can read these files, but saves them in the new format which can't be opened by older versions.
What steps will reproduce the problem? Add some markers to the topics, save the file 2.
Then delete all markers from topics 3. If you now look into xmind structure ('marker' folder), you will see that all initial markers from the group are still present, although they are not needed any more What is the expected output? What do you see instead? Software should remove marker groups from xmind file which are not referenced anywhere from the map, in order to optimize storage size and load time What version of the product are you using? On what operating system?
XMind 2012 SE (v3.3.1.29), Win7 32 bit Please provide any additional information below. Original issue reported on code.google.com by [email protected] on 22 Apr 2013 at 10:30.
Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |