5 Appendix A: Product Behavior
The information in this specification is applicable to the following Microsoft products or supplemental software. References to product versions include updates to those products.
Microsoft OneNote 2010
Microsoft OneNote 2013
Microsoft SharePoint Foundation 2010
Microsoft SharePoint Foundation 2013
Microsoft SharePoint Server 2010
Microsoft SharePoint Server 2013
Windows 8.1 Update
Microsoft SharePoint Server 2016
Microsoft OneNote 2016
Microsoft SharePoint Server 2019
Windows 10 operating system
Microsoft OneNote 2021
Microsoft SharePoint Server Subscription Edition
Microsoft OneNote 2024 Preview
Exceptions, if any, are noted in this section. If an update version, service pack or Knowledge Base (KB) number appears with a product name, the behavior changed in that update. The new behavior also applies to subsequent updates unless otherwise specified. If a product edition appears with the product version, behavior is different in that product edition.
Unless otherwise specified, any statement of optional behavior in this specification that is prescribed using the terms "SHOULD" or "SHOULD NOT" implies product behavior in accordance with the SHOULD or SHOULD NOT prescription. Unless otherwise specified, the term "MAY" implies that the product does not follow the prescription.
<1> Section 1.5: This persistence format provides interoperability with applications that create or read documents conforming to this structure, including Microsoft OneNote 2010.
<2> Section 2.1.12: OneNote 2010 also specifies Revision Role 0x00000004 in some revision manifests. Until the revision is also associated with Revision Role 0x00000001, it is not the active content of the object space.
<3> Section 2.3.1: Sometimes OneNote 2010 writes an incorrect sum of the total size of the free space in the Free Chunk List.
<4> Section 2.3.1: OneNote 2010 writes its own application build number.
<5> Section 2.3.1: OneNote 2010 writes its own application build number.
<6> Section 2.3.1: OneNote 2010 writes its own application build number.
<7> Section 2.3.1: OneNote 2010 writes its own application build number.
<8> Section 2.3.3.2: For .onetoc2 file, the running CRC algorithm will include all bytes except any that is flushed with the end of the TransactionLogFragment.
<9> Section 2.7.2: Microsoft OneNote Online generates an Extended GUID not following this algorithm.
<10> Section 2.8.1: This field is ignored by OneNote 2013.
<11> Section 3: In cases, where this document specifies that a field can only have one value, or that its value can be ignored, the examples might show the actual value written by OneNote 2010, but will not further explain them.