zilongwang/ReadingBank huggingface dataset:
Revision Summary Date Revision History Revision Class Comments 6/11/2013 1.0 New Released new document. 8/8/2013 1.0 None No changes to the meaning, language, or formatting of the technical content. 12/5/2013 1.0 None No changes to the meaning, language, or formatting of the technical content. 2/11/2014 1.0 None No changes to the meaning, language, or formatting of the technical content. 5/20/2014 2.0 Major Updated and revised the technical content. 5/10/2016 3.0 Major Significantly changed the technical content. 8/16/2017 3.0 None No changes to the meaning, language, or formatting of the technical content.
Revision Summary Date Revision History Revision Class Comments 6/27/2008 1.0 Major First release. 10/6/2008 1.01 Editorial Changed language and formatting in the technical content. 12/12/2008 1.02 Editorial Changed language and formatting in the technical content. 8/7/2009 1.1 Minor Clarified the meaning of the technical content. 11/6/2009 1.1.2 Editorial Changed language and formatting in the technical content. 3/5/2010 1.1.3 Editorial Changed language and formatting in the technical content. 4/21/2010 1.1.4 Editorial Changed language and formatting in the technical content. 6/4/2010 1.1.5 Editorial Changed language and formatting in the technical content. 9/3/2010 1.1.5 None No changes to the
meaning, language, or formatting of the technical content. 2/9/2011 1.1.5 None No changes to the meaning, language, or formatting of the technical content. 7/7/2011 1.1.5 None No changes to the meaning, language, or formatting of the technical content. 11/3/2011 1.1.5 None No changes to the meaning, language, or formatting of the technical content. 1/19/2012 1.1.5 None No changes to the meaning, language, or formatting of the technical content. 2/23/2012 1.1.5 None No changes to the meaning, language, or formatting of the technical content. 3/27/2012 1.1.5 None No changes to the meaning, language,
or formatting of the technical content. 5/24/2012 1.1.5 None No changes to the meaning, language, or formatting of the technical content. 6/29/2012 1.1.5 None No changes to the meaning, language, or formatting of the technical content. 7/16/2012 1.1.5 None No changes to the meaning, language, or formatting of the technical content. 10/8/2012 1.1.5 None No changes to the meaning, language, or formatting of the technical content. 10/23/2012 1.1.5 None No changes to the meaning, language, or formatting of the technical content. 3/26/2013 1.1.5 None No changes to the meaning, language, or formatting
of the technical content. 6/11/2013 2.0 Updated and revised the technical content. 8/8/2013 3.0 Major Updated and revised the technical content. 12/5/2013 4.0 Updated and revised the technical content. 2/11/2014 5.0 Major Updated and revised the technical content. 5/20/2014 5.0 None No changes to the meaning, language, or formatting of the technical content. 6/30/2015 6.0 Significantly changed the technical content. 5/10/2016 7.0 Major Significantly changed the technical content. 8/16/2017 8.0 Major Significantly changed the technical content. 9/15/2017 9.0 Major Significantly changed the technical content.
Revision Summary Date Revision History Revision Class Comments 6/27/2008 1.0 New Initial Availability 12/12/2008 1.01 Editorial Revised and edited the technical content 7/13/2009 1.02 Major Revised and edited the technical content 8/28/2009 1.03 Editorial Revised and edited the technical content 11/6/2009 1.04 Editorial Revised and edited the technical content 2/19/2010 2.0 Editorial Revised and edited the technical content 3/31/2010 2.01 Editorial Revised and edited the technical content 4/30/2010 2.02 Editorial Revised and edited the technical content 6/7/2010 2.03 Updated the technical content 6/29/2010 2.04 Editorial Changed language and formatting in the technical content. 7/23/2010 2.04 None No changes to the meaning, language, or formatting of the
technical content. 9/27/2010 2.04 None No changes to the meaning, language, or formatting of the technical content. 11/15/2010 2.04 None No changes to the meaning, language, or formatting of the technical content. 12/17/2010 2.04 None No changes to the meaning, language, or formatting of the technical content. 3/18/2011 2.04 None No changes to the meaning, language, or formatting of the technical content. 6/10/2011 2.04 None No changes to the meaning, language, or formatting of the technical content. 1/20/2012 3.0 Significantly changed the technical content. 4/11/2012 3.0 None No changes to the meaning,
language, or formatting of the technical content. 7/16/2012 3.1 Minor Clarified the meaning of the technical content. 10/8/2012 3.1 None No changes to the meaning, language, or formatting of the technical content. 2/11/2013 3.1 None No changes to the meaning, language, or formatting of the technical content. 7/30/2013 3.2 Minor Clarified the meaning of the technical content. 11/18/2013 3.2 None No changes to the meaning, language, or formatting of the technical content. 2/10/2014 3.2 None No changes to the meaning, language, or formatting of the technical content. 4/30/2014 3.2 None No changes to the meaning,
Spanish Venezuela es-VE Swahili Kenya sw-KE Swedish Finland sv-FI Swedish Sweden sv-SE Syriac Syria syr-SY (Cyrillic) Tajikistan tg-TJ-Cyrl Tamazight (Latin) Algeria tmz-DZ-Latn India ta-IN Tatar Russia tt-RU Telugu (Telugu Script) India te-IN Thai Thailand th-TH Tibetan PRC bo-CN Turkish Turkey tr-TR Turkmen Turkmenistan tk-TM Uighur PRC ug-CN Ukrainian Ukraine uk-UA Upper Sorbian Germany wen-DE Urdu Pakistan ur-PK Uzbek (Cyrillic) Uzbekistan uz-UZ-Cyrl (Latin) Uzbekistan uz-UZ-Latn Vietnamese Viet Nam vi-VN Welsh United Kingdom cy-GB Wolof Senegal wo-SN Yi PRC ii-CN Yoruba Nigeria yo-NG <4> Section 2.2.1: The 2007 Office system does not create this element.
Index A 8 B 7 C 32 15 Complex types 12 15 14 12 15 14 D 18 Details 15 12 15 14 18 15 15 15 18 17 10 10 11 15 16 17 22 E Examples 22 20 21 20 F 9 15 G 5 H 15 7 I 23 7 5 L 8 N 7 O 7 18 17 7 P 24 R 6 7 7 8 20 21 20 S Security 23 23 18 Simple types 10 10 11 10 10 11 Structures 12 15 14 10 10 11 T 32
Revision Summary Date Revision History Revision Class Comments 4/3/2007 1.0 New Version 1.0 release 7/3/2007 2.0 MLonghorn+90 7/20/2007 3.0 Major Updated and revised the technical content. 8/10/2007 3.0.1 Editorial Changed language and formatting in the technical content. 9/28/2007 4.0 Major Made a change to the IDL. 10/23/2007 5.0 Major Updated and revised the technical content. 11/30/2007 5.0.1 Editorial Changed language and formatting in the technical content. 1/25/2008 5.0.2 Editorial Changed language and formatting in the technical content. 3/14/2008 5.1 Minor Clarified the meaning of the technical content. 5/16/2008 5.1.1 Editorial Changed language and formatting in the technical content. 6/20/2008 6.0 Updated and revised the technical content. 7/25/2008 6.1 Minor Clarified the meaning of the technical content. 8/29/2008 7.0 Major Updated and revised the
technical content. 3/12/2010 14.0 Major Updated and revised the technical content. 4/23/2010 14.0.1 Editorial Changed language and formatting in the technical content. 6/4/2010 15.0 Major Updated and revised the technical content. 7/16/2010 15.0 None No changes to the meaning, language, or formatting of the technical content. 8/27/2010 15.0 None No changes to the meaning, language, or formatting of the technical content. 10/8/2010 15.0 None No changes to the meaning, language, or formatting of the technical content. 11/19/2010 15.0 None No changes to the meaning, language, or formatting of the technical content. 1/7/2011 16.0 Major Updated and revised the technical content. 2/11/2011 17.0 Major Updated and revised the technical content. 3/25/2011 18.0 Major Updated and revised the technical content.
5/6/2011 18.0 None No changes to the meaning, language, or formatting of the technical content. 6/17/2011 18.1 Minor Clarified the meaning of the technical content. 9/23/2011 18.1 None No changes to the meaning, language, or formatting of the technical content. 12/16/2011 19.0 Updated and revised the technical content. 3/30/2012 19.0 None No changes to the meaning, language, or formatting of the technical content. 7/12/2012 19.0 None No changes to the meaning, language, or formatting of the technical content. 10/25/2012 19.0 None No changes to the meaning, language, or formatting of the technical content. 1/31/2013 19.0 None No changes to the meaning, language, or formatting of the technical content. 8/8/2013 19.1 Clarified the meaning of the technical content. 11/14/2013 19.1 None No changes to the meaning, language, or formatting of
Revision Summary Date Revision History Revision Comments 6/27/2008 1.0 New Initial Availability 12/12/2008 1.01 Editorial Revised and edited the technical content 7/13/2009 1.02 Major Revised and edited the technical content 8/28/2009 1.03 Editorial Revised and edited the technical content 11/6/2009 1.04 Editorial Revised and edited the technical content 2/19/2010 2.0 Editorial Revised and edited the technical content 3/31/2010 2.01 Editorial Revised and edited the technical content 4/30/2010 2.02 Editorial Revised and edited the technical content 6/7/2010 2.03 Updated the technical content 6/29/2010 2.04 Editorial Changed language and formatting in the technical content. 7/23/2010 2.04 None No changes to the meaning, language, or formatting of the
technical content. 9/27/2010 2.04 None No changes to the meaning, language, or formatting of the technical content. 11/15/2010 2.04 None No changes to the meaning, language, or formatting of the technical content. 12/17/2010 2.04 None No changes to the meaning, language, or formatting of the technical content. 3/18/2011 2.04 None No changes to the meaning, language, or formatting of the technical content. 6/10/2011 2.04 None No changes to the meaning, language, or formatting of the technical content. 1/20/2012 3.0 Significantly changed the technical content. 4/11/2012 3.0 None No changes to the meaning,
language, or formatting of the technical content. 7/16/2012 3.1 Minor Clarified the meaning of the technical content. 10/8/2012 3.1 None No changes to the meaning, language, or formatting of the technical content. 2/11/2013 3.1 None No changes to the meaning, language, or formatting of the technical content. 7/30/2013 3.2 Clarified the meaning of the technical content. 11/18/2013 3.2 None No changes to the meaning, language, or formatting of the technical content. 2/10/2014 3.2 None No changes to the meaning, language, or formatting of the technical content. 4/30/2014 3.2 None No changes to the meaning,
technical content. 6/20/2017 5.0 None No changes to the meaning, language, or formatting of the technical content. 9/19/2017 5.1 Minor Clarified the meaning of the technical content. 4/27/2018 6.0 Major Significantly changed the technical content.
Index A 37 159 19 Attributes 159 159 48 85 B 38 141 C 180 35 44 85 216 21 175 21 43 Charts ( 15, 27) 108 126 108 44 Complex type 58 58 60 65 66 67 68 76 Complex types 100 CT_ApplicationNonVisualDrawingProps ( 83, 164) 143 127 104 104 49 93 94 111 112 49 CT_ContentPart ( 83, 164) 50 CT_ContentPartNonVisual ( 84, 165) 133 133 94 95 128 129 95 96 96 97 97 98 98 99 99 114 109 CT_FullRef ( 100, 101) 154 129 130 51 52 105 53 101 115 144 53 144 54 61 54 55 56 56 57 59 64 64 66 68 69 70 70 71 72 72 73 74 74 75 76 105 136 102 77 131 132 145 159 160 106
116 118 119 148 77 78 162 152 152 156 154 149 33 17 175 contentPart element ( 82, 151, 163) 44 132 100 CT_ApplicationNonVisualDrawingProps complex type ( 83, 164) 143 127 104 104 49 93 94 111 112 49 CT_ContentPart complex type ( 83, 164) 50 CT_ContentPartNonVisual complex type ( 84, 165) 133 133 94 95 85 128 86 129 95 96 96 97 97 98 98 99 99 114 109 CT_FullRef complex type ( 100, 101) 154 129 130 51 52 105 53 101 115 144 53 144 54 61 54 55 56 56 57 58 58 59 60 60 64 64 65 66 66 67 68 68 69 70 70 71 72 72 73 74 74 75 76 76 105 136 102 77 131 132 145 159 160 106 116 118 119 148 77 78 162 152 152 156 154 149 D 128 178 34 21 18
Drawing 18 18 128 40 41 40 39 E 159 Element 44 132 47 47 Elements 85 141 44 85 108 126 108 44 contentPart ( 82, 151, 163) 85 86 128 128 150 86 86 87 87 87 87 88 88 88 88 89 89 45 45 45 46 46 46 103 89 90 90 47 142 90 142 157 157 103 91 126 91 91 142 158 158 92 style ( 104, 150) 81 92 48 162 153 156 147 92 Examples 180 175 175 178 182 181 179 181 179 178 27 35 43 27 33 34 34 33 36 34 33 41 37 150 F 184 20 86 86 87 87 87 87 88 88 88 88 89 185 89 G 12 182 181
Revision Summary Date Revision History Revision Class Comments 5/16/2008 0.1 New Initial Availability 10/6/2008 0.2 Editorial Revised and edited the technical content 1/16/2009 1.0 Major Revised and edited the technical content 7/13/2009 1.01 Major Changes made for template compliance 8/28/2009 1.02 Editorial Revised and edited the technical content 11/6/2009 1.03 Editorial Revised and edited the technical content 2/19/2010 2.0 Editorial Revised and edited the technical content 3/31/2010 2.01 Editorial Revised and edited the technical content 4/30/2010 2.02 Editorial Revised and edited the technical content 6/7/2010 2.03 Editorial Revised and edited the technical content 6/29/2010 2.04 Minor Clarified the meaning of the technical content. 7/23/2010 2.04 None No changes to the meaning, language, or
formatting of the technical content. 9/27/2010 2.04 None No changes to the meaning, language, or formatting of the technical content. 11/15/2010 2.04 None No changes to the meaning, language, or formatting of the technical content. 12/17/2010 2.04 None No changes to the meaning, language, or formatting of the technical content. 3/18/2011 2.04 None No changes to the meaning, language, or formatting of the technical content. 6/10/2011 2.04 None No changes to the meaning, language, or formatting of the technical content. 1/20/2012 2.5 Minor Clarified the meaning of the technical content.
2/10/2014 2.7 None No changes to the meaning, language, or formatting of the technical content. 4/30/2014 2.7 None No changes to the meaning, language, or formatting of the technical content. 7/31/2014 2.7 None No changes to the meaning, language, or formatting of the technical content. 10/30/2014 2.7 None No changes to the meaning, language, or formatting of the technical content. 3/16/2015 3.0 Major Significantly changed the technical content. 6/30/2015 4.0 Major Significantly changed the technical content. 9/4/2015 5.0 Major Significantly changed the technical content. 4/14/2016 6.0 Major Significantly changed the
Index A Abstract data model 12 12 13 8 C 8 20 Client 12 13 13 13 13 12 13 13 12 Common 12 D Data model - abstract 12 13 Data model – abstract 12 E Examples 15 F 8 10 G 5 H triggered events 13 12 13 10 I 17 17 6 Initialization 13 12 13 5 L Local events 12 M Message processing 13 12 13 9 Messages 10 10 9 9 9 N 5 O Other local events 13 14 6 P 17 8 8 18 9 R 5 6 5 8 S Security 17 17 Sequencing rules 13 12 13 Server 13 13 13
1/20/2012 2.6 Minor Clarified the meaning of the technical content. 4/11/2012 2.6 None No changes to the meaning, language, or formatting of the technical content. 7/16/2012 2.6 None No changes to the meaning, language, or formatting of the technical content. 9/12/2012 2.6 None No changes to the meaning, language, or formatting of the technical content. 10/8/2012 2.7 Minor Clarified the meaning of the technical content. 2/11/2013 2.7 None No changes to the meaning, language, or formatting of the technical content. 7/30/2013 2.7 None No changes to the meaning, language, or formatting of the technical content.
DocumentRoutingResultType Namespace: http://schemas.microsoft.com/sharepoint/soap/recordsrepository/ Type of result. <xs:simpleType name="DocumentRoutingResultType" xmlns:xs="http://www.w3.org/2001/XMLSchema"> <xs:restriction base="xs:string"> <xs:enumeration value="Success"/> <xs:enumeration value="SuccessToDropOffLibrary"/> <xs:enumeration value="MissingRequiredProperties"/> <xs:enumeration value="NoMatchingRules"/> <xs:enumeration value="DocumentRoutingDisabled"/> <xs:enumeration value="PermissionDeniedAtDestination"/> <xs:enumeration value="ParsingDisabledAtDestination"/> <xs:enumeration <xs:enumeration value="NoEnforcementAtOriginalSaveLocation"/> <xs:enumeration value="UnknownFailure"/> </xs:restriction> </xs:simpleType> The following table specifies the allowable values for the DocumentRoutingResultType simple type. Value Meaning Success The operation was successful. SuccessToDropOffLibrary The operation was successful and the location determined by the protocol server is the temporary storage location. MissingRequiredProperties Additional data required from the protocol client. NoMatchingRules Reserved. Protocol server MUST not return this result. DocumentRoutingDisabled Routing is not enabled on the repository PermissionDeniedAtDestination validating permissions for the user at the storage location. ParsingDisabledAtDestination Parsing is not enabled on the repository. OriginalSaveLocationIsDocumentSet The originalSaveLocation
Revision Summary Date Revision History Revision Class Comments 7/13/2009 0.1 Major Initial Availability 8/28/2009 0.2 Editorial Revised and edited the technical content 11/6/2009 0.3 Editorial Revised and edited the technical content 2/19/2010 1.0 Updated the technical content 3/31/2010 1.01 Editorial Revised and edited the technical content 4/30/2010 1.02 Editorial Revised and edited the technical content 6/7/2010 1.03 Editorial Revised and edited the technical content 6/29/2010 1.04 Editorial Changed language and formatting in the technical content. 7/23/2010 1.04 None No changes to the meaning, language, or formatting of the technical content. 9/27/2010 1.04 None No changes to the meaning, language, or formatting of the
technical content. 11/15/2010 1.04 None No changes to the meaning, language, or formatting of the technical content. 12/17/2010 1.04 None No changes to the meaning, language, or formatting of the technical content. 3/18/2011 1.04 None No changes to the meaning, language, or formatting of the technical content. 6/10/2011 1.04 None No changes to the meaning, language, or formatting of the technical content. 1/20/2012 1.5 Clarified the meaning of the technical content. 4/11/2012 1.5 None No changes to the meaning, language, or formatting of the technical content. 7/16/2012 1.6 Minor Clarified the meaning of the
technical content. 10/30/2014 1.8 None No changes to the meaning, language, or formatting of the technical content. 3/16/2015 2.0 Major Significantly changed the technical content. 9/4/2015 2.1 Minor Clarified the meaning of the technical content. 7/15/2016 2.2 Minor Clarified the meaning of the technical content. 9/14/2016 2.2 None No changes to the meaning, language, or formatting of the technical content. 12/15/2016 2.3 Minor Clarified the meaning of the technical content. 12/12/2017 2.4 Minor Clarified the meaning of the technical content. 4/27/2018 3.0 Major Significantly changed the technical content.
O 9 P Part enumeration 15 16 11 23 VBA Project ( 11, 16, 23) 12 17 23 15 11 23 30 R 8 9 8 9 S Security 26 26 24 23 15 Structures 11 Structures – macro-enabled PresentationML 24 24 24 24 23 23 24 23 Structures – macro-enabled SpreadsheetML 21 22 22 21 18 18 17 17 18 15 16 17 15 23 16 17 Structures – macro-enabled WordprocessingML 12 13 14 14 12 12 11 11 15 11 12 12 T 31 V VBA Project - part enumeration ( 11, 16, 23) 12 25 12 10 10 W 17 X 27
Revision Summary Date Revision History Revision Class Comments 7/14/2016 1.0 New Released new document. 6/1/2017 2.0 Major Significantly changed the technical content. 6/13/2017 3.0 Major Significantly changed the technical content. 9/15/2017 4.0 Significantly changed the technical content. 12/1/2017 5.0 Major Significantly changed the technical content.
Processing Details Replaced OIDCSession, updating it with references to OIDCFrontChanLO. Major Message Processing Events and Sequencing Rules Replaced OIDCSession, updating it with references to OIDCFrontChanLO. Major Logout endpoint (/logout) Replaced OIDCSession, updating it with references to OIDCFrontChanLO. Request Body Replaced OIDCSession, updating it with references to OIDCFrontChanLO. Major Response Body Replaced OIDCSession, updating it with references to OIDCFrontChanLO. Major Processing Details Replaced OIDCSession, updating it with references to OIDCFrontChanLO. Major Example OpenID Provider Configuration Response Updated to include frontchannel logout support. Major
Index A Abstract data model 11 14 8 8 C 8 25 9 Client 11 11 11 11 14 11 11 14 11 D 9 E Examples 21 21 21 Extensions 9 9 F 8 G 5 H 9 Higher-layer triggered events 11 15 I 22 22 7 Initialization 11 15 5 L 8 M 9 Message processing 11 15 Messages 9 N 6 O Openid connect extension client 11 11 11 11 14 14 11 Openid connect extension server 14 15 15 15 20 20 14 Other local events 14 20 7 P 9 22 8 8 23 Protocol Details 11 11 14 14 Protocol examples 21 21 8 7 Q
of the technical content. 6/11/2013 2.0 Major Updated and revised the technical content. 8/8/2013 3.0 Updated and revised the technical content. 12/5/2013 4.0 Updated and revised the technical content. 2/11/2014 5.0 Updated and revised the technical content. 5/20/2014 5.0 None No changes to the meaning, language, or formatting of the technical content. 6/30/2015 6.0 Major Significantly changed the technical content. 5/10/2016 7.0 Major Significantly changed the technical content. 8/16/2017 8.0 Significantly changed the technical content.
Lock Owner Reserved. This key MUST NOT be used. Mode Specifies the mode in which the OLE DB consumer requests to open the data source. This key can have a compound value. The valid value components are the following: "Read": Read-only access permission. The corresponding numeric value is 0x1. "Write": Write-only access permission. The corresponding numeric value is 0x2. "ReadWrite": Read/write access permission. The corresponding numeric value is 0x3. "Share Deny Read": Prevents other data source open requests from opening a connection in read mode. The corresponding numeric value is 0x4. "Share Deny Write": Prevents other data source open requests from opening a connection in write mode. The corresponding numeric value is 0x8. "Share Exclusive": Prevents other data source open requests from opening a connection in read/write mode. The corresponding
"Negotiate": Negotiate authentication "Kerberos": authentication "NTLM": authentication "Anonymous": No authentication The default value is "Negotiate". Protocol Format Specifies the OLE DB encoding format for messages on this connection. The valid values are the following: "Default": Binary encoding "XML": Text encoding "Binary": Binary encoding Transport Compression Specifies whether the OLE DB consumer requests messages on this connection to be compressed. The valid values are the following: "Default": Messages are compressed. "None": Messages are not compressed. "Compressed": Messages are compressed. Compression Level Specifies the OLE DB of
Index A 12 B 22 C 49 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
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
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 Major 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.
5/15/2014 6.0 None No changes to the meaning, language, or formatting of the technical content. 6/30/2015 7.0 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. 6/1/2017 7.0 None No changes to the meaning, language, or formatting of the technical content.
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
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 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 Major 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.
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. 6/1/2017 7.0 None No changes to the meaning, language, or formatting of the technical content. 9/15/2017 8.0 Significantly changed the technical content.
Index A Abstract data 15 16 19 11 C 11 21 25 Client 15 15 15 message processing 15 16 16 sequencing rules 15 16 16 15 D Data model - abstract 15 16 E Examples 19 21 21 20 F 11 23 G 4 H Higher-layer triggered events 15 17 I 22 22 6 Initialization 15 16 4 21 M Message processing client 15 16 Messages 12 12 12 12 13 13 12 N 12 6 O Other local events 16 18 7 P 22 10 10 24
Index A Abstract data model 15 16 19 11 C 11 21 25 Client 15 15 15 message processing 15 16 16 sequencing rules 15 16 16 15 D Data model - abstract 15 16 E Examples 19 21 21 20 F 11 23 G 4 H Higher-layer triggered events 15 17 I 22 22 6 Initialization 15 16 4 21 M Message processing client 15 16 Messages 12 12 12 12 13 13 12 N 12 6 O Other local events 16 18 7 P 22 10 10 24 R 6 6 6 10 S Security 22 22 Sequencing client 15 16 Server 16 17 16 18 18 16
language, or formatting of the technical content. 5/15/2014 3.0 None No changes to the meaning, language, or formatting of the technical content. 6/30/2015 4.0 Major Significantly changed the technical content. 10/16/2015 4.0 None No changes to the meaning, language, or formatting of the technical content. 7/14/2016 4.0 None No changes to the meaning, language, or formatting of the technical content. 6/1/2017 5.0 Major Significantly changed the technical content. 9/15/2017 6.0 Major Significantly changed the technical content.
A Abstract data model 15 16 19 11 C 11 21 25 Client 15 15 15 message processing 15 16 16 sequencing rules 15 16 16 15 D Data model - abstract 15 16 E Examples 19 21 21 20 F 11 23 G 4 H Higher-layer triggered events 15 17 I 22 22 6 Initialization 15 16 4 21 M Message processing client 15 16 Messages 12 12 12 12 13 13 12 N 12 6 O Other local events 16 18 7 P 22 10 10 24 R 6 6 6 10 S Security 22 22 Sequencing rules client 15 16 Server 16 17 16 18
Revision Summary Date Revision History Revision Class Comments 12/16/2011 1.0 New Released new document. 3/30/2012 1.0 None No changes to the meaning, language, or formatting of the technical content. 7/12/2012 2.0 Major Significantly changed the technical content. 10/25/2012 2.0 None No changes to the meaning, language, or formatting of the technical content. 1/31/2013 2.0 None No changes to the meaning, language, or formatting of the technical content. 8/8/2013 3.0 Major Significantly changed the technical content. 11/14/2013 3.0 None No changes to the meaning, language, or formatting of the technical content. 2/13/2014 3.0 None No changes to the meaning,
language, or formatting of the technical content. 5/15/2014 3.0 None No changes to the meaning, language, or formatting of the technical content. 6/30/2015 4.0 Significantly changed the technical content. 10/16/2015 4.0 None No changes to the meaning, language, or formatting of the technical content. 7/14/2016 4.0 None No changes to the meaning, language, or formatting of the technical content. 6/1/2017 5.0 Significantly changed the technical content. 9/15/2017 6.0 Major Significantly changed the technical content. 12/1/2017 6.0 None No changes to the meaning, language, or formatting of the
Index A Abstract data model 15 16 19 11 C 11 21 25 Client 15 15 15 message processing 15 16 16 sequencing rules 15 16 16 15 D Data model - abstract 15 16 E Examples 19 21 21 20 F 11 23 G 4 H Higher-layer triggered events 15 17 I 22 22 6 Initialization 15 16 4 21 M Message processing client 15 16 Messages 12 12 12 12 13 13 12 N 12 6 O Other local events 16 18 7 P 22 10 10 24 R 6 6 6 10 S Security 22 22 Sequencing rules client 15 16 Server 16 17 16 18 18 16
authentication trust traversal boundaries to transform claims from sending authority into a form acceptable to the receiving authority . Windows Data Types This document contains the Windows data types and algorithms associated with authorization. DAC, CBAC,and COM+ roles Lightweight Directory Access Protocol (LDAP) In CBAC: This protocol enables the applications to configure the claim definitions and the user and devices claims on the Active Directory server. In RBAC: This protocol enables the retrieval of authorization policies from the Active Directory Policy Server. In DAC: section 5.1.3 specifies the authorization rules. DAC, CBAC, and AzMan RBAC Component Object Model Plus (COM+) Remote Administration Protocol With regards to authorization, this protocol enables the administration interface for the role-based security configuration for the COM+ applications. COM+ access control
Protocol syntax refers to data elements (such as packets, structures, enumerations, and methods) as well as interfaces. Protocol revision refers to changes made to a protocol that affect the bits that are sent over the wire. The changes made to this document are listed in the following table. For more information, please contact . Section Tracking number (if applicable) and description Major change (Y or N) Change type Security Descriptor 72216 : Clarified order of inherited ACEs. N Content update. Microsoft Implementations Added Windows 10 to the applicability list. Y Content update.
Index A 51 34 23 36 51 Azman rbac model 49 49 C 51 59 51 Communications 35 35 35 23 Considerations 51 51 D 6 7 37 Dependencies 35 35 35 Design intent 49 37 E 35 51 52 52 Extensibility 58 51 58 35 F 23 23 G 18 H 51 I 58 51 51 20 36 6 M 58 O Overview 34 34 23 37 6 P 36 58 R 52 20 Requirements 51 51 23 36 51
Revision Summary Date Revision History Revision Class Comments 4/4/2008 0.1 New Initial Availability 6/27/2008 1.0 Revised and edited the technical content 10/6/2008 1.01 Editorial Revised and edited the technical content 12/12/2008 1.02 Editorial Revised and edited the technical content 7/13/2009 1.03 Major Revised and edited the technical content 8/28/2009 1.04 Editorial Revised and edited the technical content 11/6/2009 1.05 Editorial Revised and edited the technical content 2/19/2010 2.0 Editorial Revised and edited the technical content 3/31/2010 2.01 Editorial Revised and edited the technical content 4/30/2010 2.02 Editorial Revised and edited the technical content 6/7/2010 2.03 Editorial Revised and edited the technical content 6/29/2010 2.04 Editorial Changed language and formatting in the
technical content. 4/11/2012 3.0 None No changes to the meaning, language, or formatting of the technical content. 7/16/2012 3.0 None No changes to the meaning, language, or formatting of the technical content. 9/12/2012 3.0 None No changes to the meaning, language, or formatting of the technical content. 10/8/2012 3.1 Minor Clarified the meaning of the technical content. 2/11/2013 4.0 Major Significantly changed the technical content. 7/30/2013 4.1 Minor Clarified the meaning of the technical content. 11/18/2013 4.1 None No changes to the meaning, language, or formatting of the technical content.
2/10/2014 4.1 None No changes to the meaning, language, or formatting of the technical content. 4/30/2014 4.1 None No changes to the meaning, language, or formatting of the technical content. 7/31/2014 4.1 None No changes to the meaning, language, or formatting of the technical content. 10/30/2014 5.0 Major Significantly changed the technical content. 3/16/2015 6.0 Major Significantly changed the technical content. 9/4/2015 6.0 None No changes to the meaning, language, or formatting of the technical content. 7/15/2016 6.0 None No changes to the meaning, language, or formatting of the technical content.
Index A Abstract data model 37 27 10 37 12 26 26 B 20 20 C 10 92 Client 37 37 40 65 65 40 Client details 37 39 39 39 65 43 65 40 39 67 26 11 12 13 12 13 14 18 18 18 39 D Data model - abstract 37 27 21 21 Details 37 39 39 39 65 43 65 40 39 39 39 E Events 65 37 65 37 22 Examples 67 67 69 70 69 71 F 10 22 73 G 23 7 26 I 72 23 72 9 Initialization 40 27 7 L events 65 37 65 M Message processing 27 Messages 12 26 26
20 20 26 11 21 21 11 11 22 22 23 26 23 11 24 24 13 12 13 14 19 24 11 18 18 18 11 25 25 N 11 8 O Operations 28 29 29 30 30 31 32 36 36 37 9 P 72 24 9 9 24 86 Protocol Details 27 R 13 12 13 8 9 8 9 14 S 43 Security 72 72 Sequencing rules 27 Server 27 28 29 29 27 30 30 31 32 36 36 27 37 27 27 37 27 37 65 19 20 20 21 21 22 22 23 23 24 24 24 25 25 10 40 24 Syntax 11 T 39 Timer events 65 37 Timers 40 27 18
Revision Summary Author Date Version Comments Microsoft Corporation 4, 2008 0.1 Initial Availability. Microsoft Corporation April 25, 2008 0.2 Revised and updated property names and other technical content. Microsoft Corporation June 27, 2008 1.0 Initial Release. Microsoft Corporation August 6, 2008 1.01 Revised and edited technical content. Microsoft Corporation September 3, 2008 1.02 Revised and edited technical content. Microsoft Corporation December 3, 2008 1.03 Revised and edited technical content. Microsoft Corporation February 4, 2009 1.04 Revised and edited technical content. Microsoft Corporation March 4, 2009 1.05 Editorial updates. Microsoft Corporation April 10, 2009 2.0 Updated technical content and applicable product releases. Table of Contents
Creates a FastTransfer download context for a snapshot of the checkpoint ICS state of the operation identified by the given synchronization context. The object output in OutputServerObject MUST be released by using RopRelease as soon as the client no longer needs it. Request: InputServerObject: MUST be a synchronization context, either download or upload. Response: ReturnValue: An unsigned 32-bit integer. This value represents the ROP execution status. OutputServerObject: MUST be the synchronization download context for the ICS state. MUST be present IFF ReturnValue equals Success. Upload The following steps MUST be taken by a client when uploading mailbox differences to a server: Obtain a handle to the Folder object (as specified in [MS-OXCFOLD]) that will be synchronized. Send a RopSynchronizationOpenCollector request to create a synchronization context on the server and to define parameters and the of an operation. [Optional] Send the RopSynchronizationUploadStateStreamBegin/-Continue/-End request to upload the initial ICS state information to the synchronization context. Upload changes, moves, and deletes of individual objects within the mailbox through RopSynchronizationImport* ROPs, while passing the synchronization context obtained in step 2. [Optional] Obtain the final ICS state by doing the following: Acquire a separate FastTransfer download context for a checkpoint ICS state by using RopSynchronizationGetTransferState and passing the synchronization upload context obtained in step 2 in the request buffer. Perform the FastTransfer download steps 4-5 (as specified in section 2.2.3.1.1) on the FastTransfer download context acquired in step (a). Release the FastTransfer download context obtained in step (a). Persist the ICS state. Send the RopRelease request to release the Folder object and the synchronization upload context obtained in steps 1 and 2. The client can not to upload/download the ICS states in steps 3 and 5. See section 3.3.4.2.2.1 for details on how that would impact responsibilities of the roles.
Protocol syntax refers to data elements (such as packets, structures, enumerations, and methods) as well as interfaces. Protocol revision refers to changes made to a protocol that affect the bits that are sent over the wire. The changes made to this document are listed in the following table. For more information, please contact . Section Tracking number (if applicable) and description Major change (Y or N) Change type AddressBookPropertyValue Structure Changed the value for TRUE in the description of the HasValue field from 0x01 to 0xFF. N Content update. AddressBookFlaggedPropertyValue Structure Revised the description of the flag value 0xA for clarity. N Content update. GetProps Request Type product behavior note for the GetProps request type when the type of the property is 0x000D. N New product behavior note added. Appendix A: Product Behavior Updated the list of applicable products. Y Content update.
A Abstract data model 81 84 12 C 12 94 Client 81 81 81 81 84 81 84 81 13 D Data model - abstract 81 84 91 E 88 Examples 91 88 88 90 90 F 12 G 7 H 18 Higher-layer triggered events 81 85 I 92 92 9 Initialization 81 84 7 88 M Message processing 81 Messages 13 18 80 17 23 80 13 N 9 O Other local events 84 87 10 P 92 80 17 12 12 93 R 90 9 9 9 90 11 32 23 80 S Security 92 92 Sequencing rules 81 Server 84 85 84
Revision Summary Date Revision History Revision Class Comments 11/18/2013 1.0 New Released new document. 2/10/2014 2.0 Significantly changed the technical content. 4/30/2014 2.1 Minor Clarified the meaning of the technical content. 7/31/2014 3.0 Major Significantly changed the technical content. 10/30/2014 4.0 Major Significantly changed the technical content. 3/16/2015 5.0 Major Significantly changed the technical content. 5/26/2015 5.0 None No changes to the meaning, language, or formatting of the technical content. 9/14/2015 6.0 Major Significantly changed the technical content. 6/13/2016 7.0 Significantly changed the technical content. 9/14/2016 7.0 None No changes to the meaning,
PING Indicates the PING request type for the mailbox server endpoint and address book server endpoint. Section Bind Indicates the Bind request type for the address book server endpoint. Section Unbind Indicates the Unbind request type for the address book server endpoint. Section CompareMIds Indicates the CompareMinIds request type for the address book server endpoint. Section DNToMId Indicates the DNToMinId request type for the address book server endpoint. Section GetMatches Indicates the GetMatches request type for the address book server endpoint. Section GetPropList Indicates the GetPropList request type for the address book server endpoint. Section GetProps Indicates the GetProps request type for the address book server endpoint. Section GetSpecialTable Indicates the GetSpecialTable request type for the address book server endpoint. Section GetTemplateInfo Indicates the GetTemplateInfo request type for the address book server endpoint. Section ModLinkAtt Indicates the ModLinkAtt request type for the address book server endpoint. Section ModProps Indicates the ModProps request type for the address book server endpoint. Section QueryColumns Indicates the QueryColumns request type for the address book server endpoint. Section QueryRows Indicates the QueryRows request type for the address book server endpoint. Section ResolveNames Indicates the ResolveNames request type for the address book server endpoint. Section ResortRestriction Indicates the ResortRestriction request type for the address book server endpoint. Section
Index A Abstract data 82 85 13 C 13 95 Client 82 82 82 82 85 82 85 82 14 D Data model - abstract 82 85 92 E 89 Examples 92 89 89 91 91 F 13 G 8 H 19 Higher-layer triggered events 82 86 I 93 93 10 Initialization 82 85 8 89 M Message processing 82 Messages 14 19 81 18 33 24 81 14 N 10 O Other local events 85 88 11 P 93 81 18 13 13 94 R 91 10 10 10 91 12 33 24 81 S Security 93 93 Sequencing rules 82 Server 85 86 85
Index A Abstract data model client ( 64, 76) server ( 38, 74) 13 74 18 C 13 92 Client abstract data model ( 64, 76) 73 74 73 initialization ( 64, 77) local events ( 74, 77) message processing ( 65, 77) 65 73 70 sequencing ( 65, 77) timer events ( 74, 77) timers ( 64, 77) 15 16 78 D Data model - abstract client ( 64, 76) server ( 38, 74) Data types 15 82 61 75 41 60 55 63 61 38 Events local - client ( 74, 77) local - server ( 64, 76) - client ( 74, 77) timer - server ( 64, 76) Examples 78 82 79 78 81 14 84 G 7 H 73 74 73 I 84 83 83 10 Initialization client ( 64, 77) server ( 39, 74) Interfaces - server 74 38 7 79 L Local events client ( 74, 77) server ( 64, 76) M Message processing client ( 65, 77) server ( 39, 75) Messages 15 15 Methods 61 75 41 60 55 63 61 73 74 73 63 64
64 63 63 63 63 64 64 65 73 70 N 10 O 63 64 64 63 63 63 63 64 64 11 P 83 13 13 86 Protocol Details 38 38 81 References 10 10 13 17 Security 83 83 65 73 70 Sequencing rules client ( 65, 77) server ( 39, 75) Server abstract data ( 38, 74) 74 61 75 41 60 55 63 61 38 initialization ( 39, 74) local events ( 64, 76) message processing ( 39, 75) 63 64 64 63 63 63 63 64 64 overview ( 38, 74) sequencing rules ( 39, 75) timer events ( 64, 76) timers ( 39, 74) 16 14 Structures 18 17 T Timer events client ( 74, 77) server ( 64, 76) Timers client ( 64, 77) server ( 39, 74) 92 15 V 14 13
Revision Summary Date Revision History Revision Comments 4/4/2008 0.1 New Initial Availability. 4/25/2008 0.2 Revised and updated property names and other technical content. 6/27/2008 1.0 Major Initial Release. 8/6/2008 1.01 Minor Revised and edited technical content. 9/3/2008 1.02 Minor Revised and edited technical content. 12/3/2008 1.03 Revised and edited technical content. 2/4/2009 1.04 Minor Revised and edited technical content. 4/10/2009 2.0 Major Updated technical content for new product releases. 7/15/2009 3.0 Major Revised and edited for technical content. 11/4/2009 4.0.0 Major Updated and revised the technical content. 2/10/2010 5.0.0 Major Updated and revised the technical content.
5/5/2010 6.0.0 Major Updated and revised the technical content. 8/4/2010 7.0 Major Significantly changed the technical content. 11/3/2010 8.0 Major Significantly changed the technical content. 3/18/2011 8.0 None No changes to the meaning, language, or formatting of the technical content. 8/5/2011 8.1 Minor Clarified the meaning of the technical content. 10/7/2011 8.2 Minor Clarified the meaning of the technical content. 1/20/2012 9.0 Major Significantly changed the technical content. 4/27/2012 10.0 Major Significantly changed the technical content. 7/16/2012 10.0 None No changes to the meaning, language, or formatting of the technical content.
10/8/2012 11.0 Major Significantly changed the technical content. 2/11/2013 12.0 Major Significantly changed the technical content. 7/26/2013 12.1 Minor Clarified the meaning of the technical content. 11/18/2013 13.0 Major Significantly changed the technical content. 2/10/2014 13.0 None No changes to the meaning, language, or formatting of the technical content. 4/30/2014 13.0 None No changes to the meaning, language, or formatting of the technical content. 7/31/2014 13.0 None No changes to the meaning, language, or formatting of the technical content. 10/30/2014 14.0 Major Significantly changed the technical content. 3/16/2015 15.0 Major Significantly changed
A Abstract data model 31 34 11 C 12 61 Client 31 31 34 34 31 Client - higher-layer triggered events:Converting between LongTermIDs and Folder or MessageIDs 31 Client - higher-layer triggered events:Logging on to a Store 31 Client - higher-layer triggered events:Registering for Notifications 32 Client - higher-layer triggered events:Syncing Read/Unread Data for Public Folders 32 Client - message Failure or Connection Failure 32 Client - message processing:Streaming of Per-User Read/Unread Data 33 D Data model - abstract 31 34 E 50 F 12 G 7 H Higher-layer triggered events 35 I 56 56 10 Initialization 31 35 7 L 27 M Message processing 35 Messages 27 13 13 N 10 O Other local events 34 49 P 56 11 11 10 57 R 9 10 10 11 13 RopGetPerUserLongTermIds example 54 RopGetReceiveFolder example 52 RopGetReceiveFolderTable example 53 RopIdFromLongTermId example 53 RopLogon for a Private Mailbox example 50 RopLogon for Public Folders example 51 RopReadPerUserInformation example 54 RopSetReceiveFolder example
Index A Abstract data model 15 17 11 21 14 C 11 25 Client 15 15 15 15 17 15 17 15 D Data model - abstract 15 17 13 E 14 Examples 21 20 F 11 G 7 H Higher-layer triggered events 15 19 13 I 23 23 10 Initialization 15 17 7 M Message processing 15 19 Messages 14 13 14 13 12 12 N 9 O local events 17 19 10 P 23 11 11 24 20 R 9 10
Security Security Considerations for Implementers The .msg File Format provides some mechanisms for ensuring that clients read the correct number of bytes from constituent streams. In the case of multiple-valued variable length properties, the length stream contains the lengths of each Clients can compare the lengths obtained from there with the actual length of the value streams. If they are not in sync, it can be assumed that there is data corruption. In case of the strings, stream entries are stored prefixed with their lengths; and if any inconsistency is detected, clients can assume that there is data corruption. However, are certain inherent security concerns with .msg files: Possible modification of properties, especially security-related flags. The .msg File Format does not provide for any encryption. Index of Security Parameters None.
Index . .msg file properties 11 11 A 10 15 C 37 8 33 D 24 Details 11 12 11 11 11 12 E Examples 33 27 30 F 10 11 27 G 6 H 22 I 35 35 8 6 L 10 M 12 N 30 30 17 8 O Overview 8 9 9 9 8 P 35 36 9 11 12 11 11 12 11 30 32 Property stream 24 22 21 R 15 References 8 8 9 S Security 35 35 Storages 15 17 9 15 Structures