Revision Summary Date Revision History Revision Class Comments 4/8/2008 0.1 New Version 0.1 release 6/20/2008 0.1.1 Editorial Changed language and formatting in the technical content. 7/25/2008 0.1.2 Editorial Changed language and formatting in the technical content. 8/29/2008 1.0 Major Updated and revised the technical content. 10/24/2008 1.0.1 Editorial Changed language and formatting in the technical content. 12/5/2008 1.1 Minor Clarified the meaning of the technical content. 1/16/2009 1.1.1 Editorial Changed language and formatting in the technical content. 2/27/2009 1.1.2 Editorial Changed language and formatting in the technical content. 4/10/2009 1.1.3 Editorial Changed language and formatting
in the technical content. 5/22/2009 1.1.4 Editorial Changed language and formatting in the technical content. 7/2/2009 1.1.5 Editorial Changed language and formatting in the technical content. 8/14/2009 2.0 Updated and revised the technical content. 9/25/2009 3.0 Major Updated and revised the technical content. 11/6/2009 3.0.1 Editorial Changed language and formatting in the technical content. 12/18/2009 3.0.2 Editorial Changed language and formatting in the technical content. 1/29/2010 4.0 Major Updated and revised the technical content. 3/12/2010 4.0.1 Editorial Changed language and formatting in the technical content.
4/23/2010 5.0 Major Updated and revised the technical content. 6/4/2010 5.0.1 Editorial Changed language and formatting in the technical content. 7/16/2010 5.0.1 None No changes to the meaning, language, or formatting of the technical content. 8/27/2010 5.0.1 None No changes to the meaning, language, or formatting of the technical content. 10/8/2010 5.0.1 None No changes to the meaning, language, or formatting of the technical content. 11/19/2010 5.0.1 None No changes to the meaning, language, or formatting of the technical content. 1/7/2011 5.0.1 None No changes to the meaning, language, or formatting of the
5/15/2014 6.0 None No changes to the meaning, language, or formatting of the technical content. 6/30/2015 7.0 Major Significantly changed the technical content. 10/16/2015 7.0 None No changes to the meaning, language, or formatting of the technical content. 7/14/2016 7.0 None No changes to the meaning, language, or formatting of the technical content.
Miscellaneous OLE2.0 Streams In addition to the OLE2.0 streams mentioned in sections and , a container document can also include another OLE2.0 stream: (section 2.3.7). Clipboard Formats The users of container applications and creating applications can use the system to transfer data between applications. All data copied to a system clipboard has to conform to a format specification, known as a . Each Clipboard Format is identified by a unique numeric format ID. Standard Clipboard Formats This specification uses a number of called the Standard Clipboard Formats. These are specified in section 2.1.1. A standard Clipboard Format is identified by a numeric ID as specified in section 2.1.1. Relationship to Protocols and Other Structures The OLE2.0 Format uses the OLE Compound File Streams (as specified in ) to linked object and embedded object data in container documents. Applicability Statement The OLE File Format specification is appropriate when creating a single container document that contains data from multiple applications. It is applicable when one of the applications is the primary of the document and that application will always be asked to process the document first. It is not applicable if there are no applications with primary ownership of the document. Versioning and Localization There is only one version of the OLE File Format Data Structure. This data structure does not define locale-specific processes or data. This document specifies two types of OLE File Formats: the OLE1.0 Format and the OLE2.0 Format. These two formats are independent and are not differentiated using a versioning mechanism. Vendor-Extensible Fields The Object Linking and Embedding Data Structures use HRESULT error codes. These are taken from the Windows error number space as specified in . Vendors SHOULD<1> reuse those values with their indicated meaning. Choosing any other value runs the risk of a collision in the future. Registered Clipboard Formats Vendors can create their own , called Registered Clipboard Formats. A Registered Clipboard Format is identified by a string that contains the name of the Clipboard Format (as specified in section 2.1.1). Vendors can define their own Registered Clipboard Formats provided that the string that identifies the Registered Clipboard Format is prefixed with the "OleExternal" string literal.
Index A 12 B 22 C 48 11 23 28 28 13 13 13 36 36 D 13 13 Details 13 15 22 18 E 9 EmbeddedObject packet ( 26, 27) Examples 44 42 39 39 43 39 F 12 14 Format 11 OLE1.0 ( 11, 20) OLE2.0 ( 11, 28) G 6 I 45 8 6 L 14 15 10 12 M 21 31 N 8 O 25 Objects 9 10 OLE1.0 Format ( 11, 20) OLE2.0 Format ( 11, 28) 11 35 44 32 42 29 39 39 13 9 P 20 46 R 8 8 8 24 11 S 45 45 24 20 11 Structures 13 T 34 43