3.3 Root Object Space

In the preceding Root File Node List example, the root object space was identified as gosid set to "{{CFDC64CA-6425-4223-903F-0B7D8A6690F9},1}". Because this is a .one file, the root object space is the data for a Microsoft OneNote 2010 section.

To gather the data for this section, read the object space manifest list for that object space. That indicates the location of the active revision manifest list. The revision manifest list, in turn, indicates a collection of revision manifests, including references to object group lists that contain all the object nodes in the section. Finally, the objects have references to their properties.

The object space manifest list starts with an ObjectSpaceManifestListStartFND file node, which confirms the gosid of the object space. It then contains one or more RevisionManifestListReferenceFND file nodes. If there is more than one, ignore all but the last one. In this example, there is only one.

fnd[0].header: 0x0880600C specifies that the FileNode is of type "ObjectSpaceListStartFND", that it contains 20 bytes of data beyond the header, and that it does not contain a reference to another part of the file.

fnd[0].fnd.gosid: {{CFDC64CA-6425-4223-903F-0B7D8A6690F9},1} specifies the identity of the object space. It matches the gosid specified by the ObjectSpaceManifestListReferenceFND that directed it here.

fnd[1].header: 0x95001C10 specifies that the FileNode is of type "RevisionManifestListReferenceFND", that it contains 3 bytes of data beyond the header, that the data begins with a compressed reference to another part of the file, and that a file node list can be found at that other file location.

fnd[1].fnd.ref:  Specifies that the first fragment of the revision manifest list is located at offset 0xD20 in the file, and is 0x120 bytes in length.

Following the file offset to the object space’s revision manifest list, there is potentially a long list of FileNodes that create and manage multiple revisions of the object space. Some of the FileNodes might be grouped into sequences that together specify a revision. Other FileNodes might modify or extend an existing revision. In this example, there is just one sequence, which specifies a single revision for the section object space.

fnd[0].header: 0x80807014 specifies that the FileNode is of type "RevisionManifestListStartFND", that it contains 24 bytes of data beyond the header, and that it does not contain a reference to another part of the file.

fnd[0].fnd.gosid: {{CFDC64CA-6425-4223-903F-0B7D8A6690F9},1} specifies yet again the identity of the object space. It matches the gosid specified by the ObjectSpaceManifestListReferenceFND and ObjectSpaceManifestListStartFND that directed it here.

fnd[1].header: 0x8080C81E specifies that the FileNode is of type "RevisionManifestStart6FND", that it contains 46 bytes of data beyond the header, and that it does not contain a reference to another part of the file.

fnd[1].fnd.rid: {{082ED24F-9AA5-4DB8-875D-3E1FEE0AD4F4},1} specifies the identity of the revision formed by this revision manifest.

fnd[1].fnd.ridDependent: "{{00000000-0000-0000-0000-000000000000},0" specifies that there is no dependent revision. All of the objects needed to make a valid object space revision are declared in this FileNode sequence.

fnd[1].fnd.RevisionRole: 1 specifies that the revision created from this manifests labels itself the active content for this object space. It is all right if other revision manifests also specify RevisionRole 1. In that case, the actual active content is the last revision in the revision manifest list which receives that label.

fnd[1].fnd.odcsDefault: 0x0000 specifies that the object properties for objects declared by this revision manifest are not encrypted.

fnd[2].header: 0x95006CB0 specifies that the FileNode is of type "ObjectGroupListReferenceFND", that it contains 23 bytes of data beyond the header, that the data begins with a compressed reference to another part of the file, and that a file node list can be found at that other file location.

fnd[2].fnd.ref: Specifies that the first fragment of the object group list is located at offset 0xF48 in the file, and is 0x120 bytes in length

fnd[2].fnd.ObjectGroupID: {{2A83AE62-6754-4383-8E2B-4033FF3CFBA1},1} specifies the identity of the object group.

fnd[3].header: 0x8080705A specifies that the FileNode is of type "RootObjectReference3FND", that it contains 24 bytes of data beyond the header, and that the data does not contain a reference to another part of the file.

fnd[3].fnd.oidRoot: {{9A416C35-236A-49A1-91FE-BD73076400A4},11} specifies the identity of one of the root objects of this revision. The object might or might not be declared in this revision, because it could be declared in a dependent revision. In this example, the object is declared in the object group list referenced previously.

fnd[3].fnd.RootRole: 2 specifies that the object is the metadata root.

fnd[4].header: 0x8080705A specifies that the FileNode is of type "RootObjectReference3FND", that it contains 24 bytes of data beyond the header, and that the data does not contain a reference to another part of the file.

fnd[4].fnd.oidRoot: {{9A416C35-236A-49A1-91FE-BD73076400A4},10} specifies the identity of another root object for this revision.

fnd[4].fnd.RootRole: 1 specifies that the object is the default content root.

fnd[5].header: 0x8080101C specifies that the FileNode is of type "RevisionManifestEndFND", and that it contains zero bytes of data beyond the header. If there were more FileNodes in the list after this one, they would not be considered part of the revision manifest declared by fnd[1].