2.7.4 Revisions

Office

When a revision store file is transmitted using the File Synchronization via SOAP over HTTP Protocol, revision manifests (section 2.1.9) are transmitted as Revision Manifest Data Element structures, as specified in [MS-FSSHTTPB] section 2.2.1.12.5.

  • Revision ID: MUST be equal to the revision store file revision identifier (section 2.1.8).

  • Base Revision ID: MUST be equal to the revision store file dependency revision identifier (section 2.1.9).

The value of RootObjectReference3FND.rootRole field of a root object (section 2.1.7) from a revision in a revision store specifies Root Extended GUID field in the Revision Manifest Data Element structure:

Value of RootObjectReference3FND.rootRole

Meaning

Root extended GUID

0x00000001

Default content root

{ { 4A3717F8- 1C14-49E7-9526-81D942DE1741 },  1}

0x00000002

Metadata root

{ { 4A3717F8- 1C14-49E7-9526-81D942DE1741 },  2}

0x00000003

Encryption Key root

{ 4A3717F8- 1C14-49E7-9526-81D942DE1741 },  3}

0x00000004

Version metadata root

{ { 4A3717F8- 1C14-49E7-9526-81D942DE1741 },  4}

The root object with RootObjectReference3FND.rootRole value set to 0x00000003 MUST be present only when the file is encrypted. (see section 2.7.7).

The Object Extended GUID field in the Revision Manifest Data Element structure MUST be equal to the identity of the corresponding root object in the revision in the revision store.

Show: