zilongwang/ReadingBank huggingface dataset:
Revision Summary Date Revision History Revision Comments 4/4/2008 0.1 Major Initial Availability. 4/25/2008 0.2 Editorial Changed language and formatting in the technical content. 6/27/2008 1.0 Editorial Changed language and formatting in the technical content. 12/12/2008 1.01 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.2 Minor Clarified the meaning of the technical content. 4/21/2010 1.2.1 Editorial Changed language and formatting in the technical content. 6/4/2010 1.2.2 Editorial Changed language and formatting
meaning, language, or formatting of the technical content. 5/24/2012 1.3.2 None No changes to the meaning, language, or formatting of the technical content. 6/29/2012 1.3.2 None No changes to the meaning, language, or formatting of the technical content. 7/16/2012 1.3.2 None No changes to the meaning, language, or formatting of the technical content. 10/8/2012 1.3.2 None No changes to the meaning, language, or formatting of the technical content. 10/23/2012 1.3.2 None No changes to the meaning, language, or formatting of the technical content. 3/26/2013 1.3.2 None No changes to the meaning, language,
or formatting of the technical content. 6/11/2013 1.3.2 None No changes to the meaning, language, or formatting of the technical content. 8/8/2013 1.3.2 None No changes to the meaning, language, or formatting of the technical content. 12/5/2013 2.0 Major Updated and revised the technical content. 2/11/2014 3.0 Major Updated and revised the technical content. 5/20/2014 3.0 None No changes to the meaning, language, or formatting of the technical content. 5/10/2016 4.0 Major Significantly changed the technical content. 8/16/2017 5.0 Major Significantly changed the technical content.
Structure Examples Document This example illustrates a simple document encoded in Binary XML format. The textual XML for this example is: <root> <?pi text?> <!--comment--> </root> Binary XML: Token Binary Description Signature DF FF Version 01 Encoding B0 04 4 "root" F0 04 72 00 6F 00 6F 00 74 00 Name "root" id 1 0 0 1 EF 00 00 01 "root" id 1 1 F8 01 <root> 2 "\n\t" 11 02 0A 00 09 00 new-line and tab 2 "pi" F0 02 70 00 69 00 Name "pi" id 2 2 4 "text" F4 02 04 74 00 65 00 78 00 74 00 <?pi text?> 2 "\n\t" 11 02 0A 00 09 00 new-line and tab 7 "comment" F3 07 63 00 6F 00 6D 00 6D 00 65 00
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.5 Minor Clarified the meaning of the
technical content. 1/20/2012 3.0 Major 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.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.0 None No changes to the meaning, language, or formatting of the technical content. 2/11/2013 3.0 None No changes to the meaning, language, or formatting of the technical content. 7/30/2013 3.1 Clarified the meaning of the
technical content. 11/18/2013 3.1 None No changes to the meaning, language, or formatting of the technical content. 2/10/2014 3.1 None No changes to the meaning, language, or formatting of the technical content. 4/30/2014 3.1 None No changes to the meaning, language, or formatting of the technical content. 7/31/2014 3.1 None No changes to the meaning, language, or formatting of the technical content. 10/30/2014 3.1 None No changes to the meaning, language, or formatting of the technical content. 6/23/2016 3.1 None No changes to the meaning, language, or formatting of the technical content.
Index A Abstract data model client ( 18, 20, 22) server ( 16, 18, 20) 9 B 13 C 9 36 Client abstract data model ( 18, 20, 22) 20 22 18 initialization ( 18, 20, 22) local events ( 20, 22) message processing ( 20, 22) 16 sequencing rules ( 20, 22) timer events ( 20, 22) timers ( 18, 20, 22) Common data types 10 configInfo parameter 30 31 33 31 30 conversion applications 30 31 32 31 33 30 25 11 12 13 D Data model - abstract client ( 18, 20, 22) server ( 16, 18, 20) Data types 13 10 11 12 13 E Events local - client ( 20, 22) local - server ( 20, 22) timer - client ( 20, 22) timer - server ( 20, 22) 33 Examples 25 24 23 23 23 25 F 9 G 6 I 20 18 22 20 18 16 27 27 7 Initialization client ( 18, 20, 22) server ( 16, 19, 21) 28 6 L 24 Local events client ( 20, 22) server ( 20, 22) M Message processing client ( 20, 22) server ( 16, 19, 21) Messages 13 10 11 12 13 10 N 7
12 25 25 differentiateMultirowTableHeaders element ( 14, 15) 35 23 35 13 E Elements 21 21 31 32 22 22 22 15 conflictDel ( 32, 32) 33 32 33 33 34 34 34 23 35 differentiateMultirowTableHeaders ( 14, 15) 35 23 35 13 14 36 37 37 38 38 overrideTableStyleFontSizeAndJustification ( 13, 13) 24 38 38 24 24 39 39 39 40 40 25 25 14 36 Examples 79 79 Extensions 12 12 16 12 12 12 13 11 11 13 11 12 F 10 82 G 7 37 79 I 81 8 7 L 37 10 N 7 40 16 38 38 O 12 overrideTableStyleFontSizeAndJustification element ( 13, 13) 8 P 12 41 24 11 12 13 92 38 R References 8 7
38 9 24 24 11 S 39 11 13 Security 81 81 11 39 Simple types 63 64 64 65 66 68 68 69 69 70 70 71 74 75 76 77 31 63 64 64 65 66 68 68 69 69 70 70 71 74 75 76 77 31 Structures 40 21 12 21 31 32 22 22 22 11 15 13 12 32 32 33 32 33 42 42 43 26 27 43 43 44 45 45 46 46 47 47 48 48 49 49 49 50 27 50 28 51 51 28 52 52 53 54 55 55 29 56 57 30 57 59 59 60 61 61 62 33 34 34 34 23 35 differentiateMultirowTableHeaders element ( 14, 15) 35 23 35 13 14 36 37
37 40 16 38 38 12 overrideTableStyleFontSizeAndJustification element ( 13, 13) 12 41 11 24 12 13 38 38 24 24 11 39 11 13 11 39 63 64 64 65 66 68 68 69 69 70 70 71 74 75 76 77 31 11 39 40 41 40 12 25 25 11 79 39 T 40 41 40 12 94 V 10 10 W 25 25 X 82
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 change (Y or N) Change type Numbering Definition Extensions Added section describing the restartNumberingAfterBreak attribute, a numbering definition extension. Y New content added. 2.2.10 Numbering Definition Extensions Added a product behavior note for this extension. N New product behavior note added. r Extensions Added section describing the SymEx element, an extension to the r element. Y New content added. 2.2.11 r Extensions Added a product behavior note for this extension. N New product behavior note restartNumberingAfterBreak Added section describing the restartNumberingAfterBreak attribute. Y New content 2.5.2.1 restartNumberingAfterBreak Added a product behavior note for this attribute. N New product behavior note added. CT_SymEx Added a new section for this complex type. Y New content
Index A 43 24 10 Attributes 43 43 43 44 C 13 100 24 34 35 25 25 25 12 16 14 Complex types 44 45 45 29 30 46 46 47 47 48 48 49 49 50 50 51 51 51 52 52 31 53 31 53 54 54 54 55 56 57 58 32 59 59 33 60 61 61 62 63 63 64 13 35 35 36 35 36 44 45 45 29 30 46 46 47 47 48 48 49 49 50 50 51 51 51 52 52 31 53 31 53 54 32 54 54 55 56 57 58 32 59 59 33 60 61 61 62 63 63 64 36 37 37 37
D 26 37 Details 43 24 13 24 34 35 25 25 25 12 16 14 13 35 35 36 35 36 44 45 45 29 30 46 46 47 47 48 48 49 49 50 50 51 51 51 52 52 31 53 31 53 54 32 54 54 55 56 57 58 32 59 59 33 60 61 61 62 63 63 64 36 37 37 37 26 37 differentiateMultirowTableHeaders ( 15, 17) 38 26 38 15 15 38 40 40 43 14 17 40 41 13 overrideTableStyleFontSizeAndJustification ( 14, 15) 13 43 27 12 13 14 41 14 41 27 27 12 41 12 13 12 42 65 66 66 68 69 70 71 72 72 73 73 74 77 78 79 80 34 12 42 42 44 43 13 28
28 differentiateMultirowTableHeaders element ( 15, 17) 38 26 38 15 E Elements 24 24 34 35 25 25 25 16 conflictDel ( 35, 35) 36 35 36 36 37 37 37 26 37 differentiateMultirowTableHeaders ( 15, 17) 38 26 38 15 15 38 40 40 40 41 overrideTableStyleFontSizeAndJustification ( 14, 15) 27 41 41 27 27 41 42 42 42 43 28 28 15 38 Examples 84 84 Extensions 13 13 17 13 13 13 14 14 14 12 12 13 12 13 F 11 87 G 8 40 84 I 86 9 8 L 40 11 N 8 43 14 17 40 41 O 13 overrideTableStyleFontSizeAndJustification element ( 14, 15) 9 P 13 43 27 12 13 14 98 41 R 14 8 9 8
41 10 27 27 12 S 41 12 13 Security 86 86 12 42 Simple types 65 66 66 68 69 70 71 72 72 73 73 74 77 78 79 80 34 65 66 66 68 69 70 71 72 72 73 73 74 77 78 79 80 34 Structures 43 24 13 24 34 35 25 25 25 12 16 14 13 35 35 36 35 36 44 45 45 29 30 46 46 47 47 48 48 49 49 50 50 51 51 51 52 52 31 53 31 53 54 32 54 54 55 56 57 58 32 59 59 33 60 61 61 62 63 63 64 36 37 37 37 26 37 differentiateMultirowTableHeaders element ( 15, 17) 38 26 38 15 15 38 40 40 43
Revision Summary Date Revision History Revision Class Comments 3/17/2010 0.1 New Released new document. 3/26/2010 1.0 None Introduced no new technical or language changes. 5/26/2010 1.2 None Introduced no new technical or language changes. 9/8/2010 1.3 Major Significantly changed the technical content. 10/13/2010 1.4 Minor Clarified the meaning of the technical content. 2/10/2011 2.0 Minor Clarified the meaning of the technical content. 2/22/2012 3.0 Significantly changed the technical content. 7/25/2012 3.1 Clarified the meaning of the technical content. 6/26/2013 4.0 Major Significantly changed the technical content. 3/31/2014 4.0 None No changes to the meaning, language, or formatting of the
Quirks Mode, IE7 Mode, and IE8 Mode (All Versions) The contentDocument attribute is not supported on the HTMLObjectElement interface. V0040: The specification states: Interface HTMLParamElement Parameters fed to the OBJECT element. See the PARAM element definition in HTML 4.01. IDL Definition interface HTMLParamElement : HTMLElement { attribute DOMString name; attribute DOMString type; attribute DOMString value; attribute DOMString valueType; }; Quirks Mode, IE7 Mode, and IE8 Mode (Internet Explorer 7 and Internet Explorer 8) All attributes of the HTMLParamElement interface are defined only when they are defined in the markup. For an undefined attribute, HTMLParamElement returns undefined. V0041: The specification states: valueType of type DOMString Information about the meaning of the value attribute value. See the valuetype attribute definition in HTML 4.01. Quirks Mode and IE7 Mode (All Versions) The valueType attribute of the HTMLParamElement interface returns undefined, not the default value data. If the valuetype attribute of a PARAM element is not specified in HTML, the valueType attribute of the HTMLParamElement interface returns undefined as the default value. The specification states: Interface HTMLAppletElement An embedded Java applet. See the APPLET element definition in HTML 4.01. This element is deprecated in HTML 4.01. IDL Definition interface HTMLAppletElement : HTMLElement { attribute DOMString align; attribute DOMString alt; attribute DOMString archive; attribute DOMString code; attribute DOMString codeBase; attribute DOMString height; // Modified in DOM Level 2: attribute long hspace; attribute DOMString name; // Modified in DOM Level 2: attribute DOMString object; // Modified in DOM Level 2: attribute long vspace; attribute DOMString width; };
Revision Summary Date Revision History Revision Class Comments 9/3/2010 0.1 New Released new document. 2/9/2011 0.1 None No changes to the meaning, language, or formatting of the technical content. 7/7/2011 0.1 None No changes to the meaning, language, or formatting of the technical content. 11/3/2011 0.1 None No changes to the meaning, language, or formatting of the technical content. 1/19/2012 0.1 None No changes to the meaning, language, or formatting of the technical content. 2/23/2012 0.1 None No changes to the meaning, language, or formatting of the technical content. 3/27/2012 0.1 None No changes to the meaning, language, or
formatting of the technical content. 5/24/2012 0.1 None No changes to the meaning, language, or formatting of the technical content. 6/29/2012 0.1 None No changes to the meaning, language, or formatting of the technical content. 7/16/2012 0.1 None No changes to the meaning, language, or formatting of the technical content. 10/8/2012 0.1 None No changes to the meaning, language, or formatting of the technical content. 10/23/2012 0.1 None No changes to the meaning, language, or formatting of the technical content. 3/26/2013 0.1 None No changes to the meaning, language, or formatting of the
technical content. 6/11/2013 0.1 None No changes to the meaning, language, or formatting of the technical content. 8/8/2013 0.1 None No changes to the meaning, language, or formatting of the technical content. 12/5/2013 0.1 None No changes to the meaning, language, or formatting of the technical content. 2/11/2014 0.1 None No changes to the meaning, language, or formatting of the technical content. 5/20/2014 0.1 None No changes to the meaning, language, or formatting of the technical content. 5/10/2016 1.0 Major Significantly changed the technical content. 8/16/2017 1.0 None No changes to the meaning,
<xs:element name="metadata" nillable="true" xmlns:q4="http://schemas.microsoft.com/sqlserver/masterdataservices/2009/09" type="q4:Metadata" /> <xs:element name="settings" nillable="true" type="tns:PackageSettings" /> </xs:sequence> </xs:complexType> <xs:element name="Package" nillable="true" type="tns:Package" /> <xs:complexType name="PackageSettings"> <xs:sequence> <xs:element name="assemblyVersion" nillable="true" type="xs:string" /> <xs:element name="containsData" type="xs:boolean" /> <xs:element name="createdBy" nillable="true" type="xs:string" /> <xs:element name="createdDate" type="xs:dateTime" /> <xs:element name="deploymentType" type="tns:DeploymentType" /> <xs:element name="productVersion" nillable="true" type="xs:string" /> <xs:element name="version" type="xs:int" /> </xs:sequence> </xs:complexType> <xs:element name="PackageSettings" nillable="true" type="tns:PackageSettings" /> <xs:simpleType name="DeploymentType"> <xs:restriction base="xs:string"> <xs:enumeration value="Complete" /> </xs:restriction> </xs:simpleType> <xs:element name="DeploymentType" nillable="true" type="tns:DeploymentType" /> </xs:schema>
Revision Summary Date Revision History Revision Class Comments 2/9/2011 0.1 New Release new document 7/7/2011 0.1 None No changes to the meaning, language, or formatting of the technical content. 11/3/2011 0.1 None No changes to the meaning, language, or formatting of the technical content. 1/19/2012 0.1 None No changes to the meaning, language, or formatting of the technical content. 2/23/2012 0.1 None No changes to the meaning, language, or formatting of the technical content. 3/27/2012 0.1 None No changes to the meaning, language, or formatting of the technical content. 5/24/2012 0.1 None No changes to the meaning, language, or
8/8/2013 2.0 Updated and revised the technical content. 12/5/2013 2.0 None No changes to the meaning, language, or formatting of the technical content. 2/11/2014 2.0 None No changes to the meaning, language, or formatting of the technical content. 5/20/2014 2.0 None No changes to the meaning, language, or formatting of the technical content. 5/10/2016 2.0 None No changes to the meaning, language, or formatting of the technical content. 8/16/2017 2.1 Minor Clarified the meaning of the technical content.
identifies the users the particular item is shared with. pi The pi (published items) complex type is an envelope that contains the description of shared files and folders. <xs:element name="pi"> <xs:complexType> <xs:element name="usersFilesDescription" type="usersFilesDescription" /> <xs:complexType> </xs:element> usersFilesDescription: A description of the HomeGroup user's files. Defines the resources shared by a HomeGroup user on a HomeGroup machine. usersFilesDescription The usersFilesDescription complex type describes shared files and folders per HomeGroup user, per HomeGroup machine in the HomeGroup. <xs:element name="usersFilesDescription"> <xs:complexType> <xs:all> <xs:element name="o" type="o" /> <xs:element name="il" type="il" minOccurs="0" /> <xs:element name="dil" type="dil" minOccurs="0" /> </xs:all> </xs:complexType> </xs:element> o: The owner of the shared resource. The owner is typically the HomeGroup user who designates a resource for sharing. il: Optional element. When present, contains a sequence of one or more items (the item list). dil: Optional element. When present, contains a sequence of one or more (the item list), which are shared with specific other members of the HomeGroup using discretionary access. The usersFilesDescription MUST contain at least an il or a dil element. If both the il and dil elements are missing, the message will be discarded. o The o complex type describes a HomeGroup user in the HomeGroup machine that is sharing the files and folders on the HomeGroup. <xs:element name="o"> <xs:complexType> <xs:annotation>
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 Appendix A: Product Behavior Added Windows 10 to applicability list. Y Content update.
Index A 6 B 17 17 C 22 Complex types 10 11 10 9 8 9 11 9 D Data 12 12 8 Details 8 data 12 12 10 11 10 8 9 9 12 8 12 11 9 10 E Encryption rules - data 12 12 Examples 17 17 15 15 16 F Fields 20 7 20 7 G 5 I 11 10 20 20 6 5 L 6 N 8 6 O 9 6 P 9 21 R
Revision Summary Date Revision History Revision Comments 1/29/2010 0.1 First Release. 3/12/2010 0.1.1 Editorial Changed language and formatting in the technical content. 4/23/2010 0.1.2 Editorial Changed language and formatting in the technical content. 6/4/2010 1.0 Updated and revised the technical content. 7/16/2010 1.0 None No changes to the meaning, language, or formatting of the technical content. 8/27/2010 1.0 None No changes to the meaning, language, or formatting of the technical content. 10/8/2010 1.0 None No changes to the meaning, language, or formatting of the technical content. 11/19/2010 1.0 None No changes to the meaning, language,
or formatting of the technical content. 1/7/2011 1.0 None No changes to the meaning, language, or formatting of the technical content. 2/11/2011 1.0 None No changes to the meaning, language, or formatting of the technical content. 3/25/2011 1.0 None No changes to the meaning, language, or formatting of the technical content. 5/6/2011 1.0 None No changes to the meaning, language, or formatting of the technical content. 6/17/2011 1.1 Clarified the meaning of the technical content. 9/23/2011 1.1 None No changes to the meaning, language, or formatting of the technical content.
12/16/2011 2.0 Major Updated and revised the technical content. 3/30/2012 2.0 None No changes to the meaning, language, or formatting of the technical content. 7/12/2012 2.0 None No changes to the meaning, language, or formatting of the technical content. 10/25/2012 2.1 Minor Clarified the meaning of the technical content. 1/31/2013 2.1 None No changes to the meaning, language, or formatting of the technical content. 8/8/2013 3.0 Major Updated and revised 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,
Index A 6 B 17 17 C 22 Complex types 10 11 10 9 8 9 11 9 D Data 12 12 8 Details 8 data 12 12 10 11 10 8 9 9 12 8 12 11 9 10 E Encryption - data 12 12 Examples 17 17 15 15 16 F Fields 20 7 20 7 G 5 I 11 10 20 20 6 5 L 6 N 8 6 O 9 6 P 9 21 R 5 6 6 6 S Security 20 20 12 Shell Publishing data 8 15 15 16 Simple types 12 12 Structures 8 12
Revision Summary Date Revision History Revision Class Comments 3/2/2007 1.0 Updated and revised the technical content. 4/3/2007 1.1 Minor Clarified the meaning of the technical content. 5/11/2007 2.0 Updated and revised the technical content. 6/1/2007 2.1 Minor Clarified the meaning of the technical content. 7/3/2007 3.0 Changed to unified format; updates to technical content 8/10/2007 4.0 Major Updated and revised the technical content. 9/28/2007 5.0 Major Updated and revised the technical content. 10/23/2007 5.1 Clarified the meaning of the technical content. 1/25/2008 5.1.1 Editorial Changed language and formatting in the technical content. 3/14/2008 6.0 Major Major update to
technical content. 6/20/2008 7.0 Updated and revised the technical content. 7/25/2008 7.0.1 Editorial Changed language and formatting in the technical content. 8/29/2008 7.0.2 Editorial Changed language and formatting in the technical content. 10/24/2008 8.0 Major Updated and revised the technical content. 12/5/2008 9.0 Updated and revised the technical content. 1/16/2009 10.0 Major Updated and revised the technical content. 2/27/2009 10.0.1 Editorial Changed language and formatting in the technical content. 4/10/2009 11.0 Major Updated and revised the technical content. 5/22/2009 11.0.1 Editorial Changed language and formatting in the
technical content. 7/2/2009 11.0.2 Editorial Changed language and formatting in the technical content. 8/14/2009 11.0.3 Editorial Changed language and formatting in the technical content. 9/25/2009 11.1 Minor Clarified the meaning of the technical content. 11/6/2009 11.1.1 Editorial Changed language and formatting in the technical content. 12/18/2009 11.2 Minor Clarified the meaning of the technical content. 1/29/2010 11.2.1 Editorial Changed language and formatting in the technical content. 3/12/2010 12.0 Major Updated and revised the technical content. 4/23/2010 12.0.1 Editorial Changed language and formatting in the technical content.
6/1/2017 20.1 None No changes to the meaning, language, or formatting of the technical content. 9/15/2017 21.0 Significantly changed the technical content. 9/12/2018 22.0 Major Significantly changed the technical content.
Revision Summary Date Revision History Revision Class Comments 12/5/2008 0.1 Initial Availability. 1/16/2009 0.1.1 Editorial Changed language and formatting in the technical content. 2/27/2009 0.1.2 Editorial Changed language and formatting in the technical content. 4/10/2009 0.1.3 Editorial Changed language and formatting in the technical content. 5/22/2009 0.1.4 Editorial Changed language and formatting in the technical content. 7/2/2009 1.0 Updated and revised the technical content. 8/14/2009 1.0.1 Editorial Changed language and formatting in the technical content. 9/25/2009 1.1 Minor Clarified the meaning of the technical content. 11/6/2009 1.1.1 Editorial Changed language and formatting
in the technical content. 12/18/2009 2.0 Updated and revised the technical content. 1/29/2010 2.1 Minor Clarified the meaning of the technical content. 3/12/2010 2.1.1 Editorial Changed language and formatting in the technical content. 4/23/2010 2.1.2 Editorial Changed language and formatting in the technical content. 6/4/2010 2.1.3 Editorial Changed language and formatting in the technical content. 7/16/2010 2.1.3 None No changes to the meaning, language, or formatting of the technical content. 8/27/2010 2.1.3 None No changes to the meaning, language, or formatting of the technical content. 10/8/2010 2.1.3 None No changes to the
meaning, language, or formatting of the technical content. 11/19/2010 2.1.3 None No changes to the meaning, language, or formatting of the technical content. 1/7/2011 2.1.3 None No changes to the meaning, language, or formatting of the technical content. 2/11/2011 2.1.3 None No changes to the meaning, language, or formatting of the technical content. 3/25/2011 2.1.3 None No changes to the meaning, language, or formatting of the technical content. 5/6/2011 2.1.3 None No changes to the meaning, language, or formatting of the technical content. 6/17/2011 2.2 Clarified the meaning of the
Index A Abstract data model 14 13 13 9 12 11 C 9 20 Client 14 14 14 14 14 14 14 Common message syntax 12 11 11 11 12 11 10 10 11 11 D 13 14 13 E Elements 11 Events 14 13 14 13 Examples 15 15 15 15 F 9 18 G 6 12 I 17 17 7 Initialization 14 13 13 6 L 11 15 Local events 14 13 13 M Message processing 14 13 13 Messages 12 11 11 11 11 12 11 10 11 10 12 11 11 11 12 11 10 10 11 10 N 10 7 O 8
Revision Summary Date Revision History Revision Class Comments 12/5/2008 0.1 Major Initial Availability. 1/16/2009 0.1.1 Editorial Changed language and formatting in the technical content. 2/27/2009 0.1.2 Editorial Changed language and formatting in the technical content. 4/10/2009 0.1.3 Editorial Changed language and formatting in the technical content. 5/22/2009 0.1.4 Editorial Changed language and formatting in the technical content. 7/2/2009 1.0 Major Updated and revised the technical content. 8/14/2009 1.0.1 Editorial Changed language and formatting in the technical content. 9/25/2009 1.1 Minor Clarified the meaning of the technical content. 11/6/2009 1.1.1 Editorial Changed language and formatting
in the technical content. 12/18/2009 2.0 Major Updated and revised the technical content. 1/29/2010 2.1 Minor Clarified the meaning of the technical content. 3/12/2010 2.1.1 Editorial Changed language and formatting in the technical content. 4/23/2010 2.1.2 Editorial Changed language and formatting in the technical content. 6/4/2010 2.1.3 Editorial Changed language and formatting in the technical content. 7/16/2010 2.1.3 None No changes to the meaning, language, or formatting of the technical content. 8/27/2010 2.1.3 None No changes to the meaning, language, or formatting of the technical content. 10/8/2010 2.1.3 None No changes to the
technical content. 11/14/2013 4.0 None No changes to the meaning, language, or formatting of the technical content. 2/13/2014 4.0 None No changes to the meaning, language, or formatting of the technical content. 5/15/2014 4.0 None No changes to the meaning, language, or formatting of the technical content. 6/30/2015 5.0 Major Significantly changed the technical content. 10/16/2015 5.0 None No changes to the meaning, language, or formatting of the technical content. 7/14/2016 5.0 None No changes to the meaning, language, or formatting of the technical content. 6/1/2017 6.0 Major Significantly changed the
A Abstract data model 14 13 13 9 12 11 C 9 20 Client 14 14 14 14 14 14 14 Common message syntax 12 11 11 11 12 11 10 10 11 11 D 13 14 13 E Elements 11 Events 14 13 14 13 Examples 15 15 15 15 F 9 18 G 6 12 I 17 17 7 Initialization 14 13 13 6 L 11 15 events 14 13 13 M Message processing 14 13 13 Messages 12 11 11 11 11 12 11 10 11 10 12 11 11 11 12 11 10 10 11 10 N 10 7 O 8
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 Appendix A: Product Behavior Added Windows 10 to applicability list. Y Content update. 6 Appendix A: Product Behavior Updated product behavior notes for Windows 10 and Windows Server 2016 Technical Preview. Y Product behavior note updated.
L 23 24 Licenses 37 37 38 41 19 41 Local events 60 69 M 50 Message processing 56 62 Messages 16 20 49 25 16 16 42 N 9 O 42 42 42 43 38 60 60 69 11 11 P 75 18 19 14 43 44 14 46 76 46 19 R 9 10 9 14 53 46 S 75 75 75 29 47 Sequencing rules 56 62 Server 60 62 61 61 61 69 62 69 62 69 61 47 47 15 29 29 16 T Timer events 60 69 Timers 55 61 78 16 16 Triggered events - higher-layer 56 62
Revision Summary Date Revision History Revision Class Comments 5/10/2016 1.0 New Initial Availability 8/16/2017 1.0 None No changes to the meaning, language, or formatting of the technical content. 3/16/2018 1.0 None No changes to the meaning, language, or formatting of the technical content.
Index A 9 C 60 10 E Examples 47 47 46 46 51 46 46 49 50 51 48 48 F 9 54 G GetAction 20 20 20 20 22 22 20 47 Getaction versions 1.0 and 1.1 20 20 20 20 22 22 20 GetConfiguration 14 14 14 14 17 17 14 46 Getconfiguration version 2.0 28 28 28 28 31 31 28 Getconfiguration versions 1.0 and 1.1 14 14 14 14 17 17 14 Getdscaction version 2.0 34 35 34 35 37 37 34 GetModule 17 17 17 17 20 20 17 46 Getmodule version 2.0 31 31 31 32 34 34 31 Getmodule versions 1.0 and 1.1 17 17 17 17 20 20 17 Getreports version 2.0 43 43 43 43 45 45 43 Getstatusreport versions 1.0 and 1.1 25 26 25 26 28 27 25 7
H 10 I 53 53 8 7 J 54 M Messages 10 10 N 10 8 O 8 P 53 8 8 58 Protocol Details 20 20 14 28 14 34 17 31 17 43 25 37 40 22 22 Protocol examples 47 46 51 46 49 50 51 48 R References 8 8 Registerdscagent version 2 37 37 37 37 40 39 37 8 S 54 Security 53 53 53 Sendreport version 2.0 40 40 40 40 43 42 40 SendStatusReport 22 23 23 23 23 48 Sendstatusreport versions 1.0 and 1.1 22 23 23 23 25 25 23 9 7 T 60 10 10 10 U 12 V 9
DSC-GetConfigurationResp-Headers DSC-GetConfigurationResp-Body DSC-GetConfigurationResp-Headers = *( DSC-GetConfigurationResp-Header-REQ / DSC-GetConfigurationResp-Header-OPT / DSC-GetConfigurationResp-Body) DSC-GetConfigurationResp-Header-REQ = Content-Length ; section 14.13 of [RFC2616] / Content-Type ; section / Checksum ; section / ChecksumAlgorithm ; section DSC-GetConfigurationResp-Header-OPT = Server ; section 14.38 of [RFC2616] DSC-GetConfigurationResp-Body = Configuration ; section The response message for this operation contains the following HTTP headers. Response header Usage Value Checksum Required See section 2.2.2.2. ChecksumAlgorithm Required See section 2.2.2.3. ProtocolVersion Required See section The response message for this method can result in the following status codes. Status code Description 200 Request completed. 400 Bad request. 401 Not authorized. 404 The resource is not found. Request Body None. Response Body In the response body, the configuration represents a BLOB. Processing Details The client gets the configuration from the server as content-type in the response body for the GetConfiguration request. The server MUST send the checksum in the response headers as specified in section . The server MUST send the ChecksumAlgorithm in the response headers as specified in section . The server MUST send the ProtocolVersion in the response headers as specified in section . The server generates the checksum using the following algorithm: Use the algorithm specified in section 2.2.2.3 to compute the hash of the response body as specified in section 4.1.
Index A 9 C 9 Certificaterotation 45 46 45 46 47 47 45 62 10 E Examples 49 49 48 48 53 48 48 51 52 53 50 50 F 9 56 G GetAction 20 20 20 20 22 22 20 49 Getaction versions 1.0 and 1.1 20 20 20 20 22 22 20 GetConfiguration 14 14 14 14 17 17 14 48 Getconfiguration version 2.0 28 28 28 28 31 31 28 Getconfiguration versions 1.0 and 1.1 14 14 14 14 17 17 14 Getdscaction version 2.0 34 35 34 35 37 37 34 GetModule 17 17 17 17 20 20 17 48 Getmodule version 2.0 31 31 31 32 34 34 31 Getmodule versions 1.0 and 1.1 17 17 17 17 20 20 17 Getreports version 2.0 43 43 43 43 45 45
Revision Summary Date Revision History Revision Comments 8/8/2013 1.0 New Released new document. 11/14/2013 2.0 Major Updated and revised the technical content. 2/13/2014 2.1 Minor Clarified the meaning of the technical content. 5/15/2014 2.1 None No changes to the meaning, language, or formatting of the technical content. 6/30/2015 3.0 Major Significantly changed the technical content. 10/16/2015 4.0 Major Significantly changed the technical content. 7/14/2016 5.0 Major Significantly changed the technical content. 6/1/2017 5.0 None No changes to the meaning, language, or formatting of the technical content. 9/15/2017 6.0 Major Significantly changed the technical content.
Figure 3: Message sequence with a single GetAction request SendStatusReport Sequence The following sequence occurs between a client and a server during a SendStatusReport request. The client sends a SendStatusReport request. If the server requires the client to be authenticated, the server and client exchange access authentication HTTP headers as specified in section 11. If authentication is not required, or if authentication has succeeded, the server responds with a HTTP 200 (OK) response. The client closes the TCP connection to the server. The following figure shows a message sequence with a single SendStatusReport request. Figure 4: Message sequence with a single SendStatusReport GetStatusReport Sequence The following sequence occurs between a client and a server during a GetStatusReport request. The client sends a GetStatusReport request. If the server requires the client to be authenticated, the server and client exchange access authentication HTTP headers as specified in section 11. If authentication is not required, or if authentication has succeeded, the server responds with a HTTP 200 (OK) response. The client closes the TCP connection to the server. The following figure shows a message sequence with a single GetStatusReport request. Figure 5: Message sequence with a single GetStatusReport RegisterDscAgent Sequence The following sequence occurs between a client and a server during a RegisterDscAgent request. The client sends a RegisterDscAgent request. If the server requires the client to be authenticated, the server and client exchange access authentication HTTP headers as specified in section 11. If authentication is not required, or if authentication has succeeded, the server responds with a HTTP 200 (OK) response. The client closes the TCP connection to the server.
Index A 9 C 9 Certificaterotation 45 45 45 45 47 47 45 62 10 E Examples 49 49 48 48 53 48 48 51 52 53 50 50 F 9 56 G GetAction 20 20 20 20 22 22 20 49 Getaction versions 1.0 and 1.1 20 20 20 20 22 22 20 GetConfiguration 14 14 14 14 17 17 14 48 Getconfiguration version 2.0 28 28 28 28 31 31 28 Getconfiguration versions 1.0 and 1.1 14 14 14 14 17 17 14 Getdscaction version 2.0 34 34 34 34 37 37 34 GetModule 17 17 17 17 20 20 17 48 Getmodule version 2.0 31 31 31 31 34 34 31 Getmodule versions 1.0 and 1.1 17 17 17 17 20 20 17 Getreports version 2.0 42 43 43 43 45 45
DSLR_E_OUTOFHANDLES 0x88170106 No more request handles are available. DSLR_E_SERVICERELEASED 0x88170107 The service was released. DSLR_E_INVALIDCALLCONVENTION 0x88170108 Unsupported calling convention. DSLR_E_INVALIDREQUESTHANDLE 0x88170109 Invalid request handle. DSLR_E_INVALIDSTUBHANDLE 0x8817010a Invalid stub handle. DSLR_E_ABORT 0x8817010b DSLR operation aborted. Transport Specific Codes: Value Meaning DSLR_E_INVALIDOPERATION 0x8817010c Invalid operation. DSLR_E_INVALIDTAGOPERATION 0x8817010d Invalid operation on this tag. DSLR_E_TAGHASNOMORECHILDREN 0x8817010e There are no more children to this tag. DSLR_E_TAGSEEKERROR 0x8817010f Tag operation is out of bounds. DSLR_E_SENDBUFFERTOOSMALL 0x88170110 Buffer is too small for this tag. DSLR_E_DISCONNECTED 0x88170111L The transport was disconnected unexpectedly. The CreateService and DeleteService messages have no additional out parameters. Generic Service Request Payload The purpose of the DSLR protocol is to allow DSLR consumers to define remote services and requests (or function calls) on those services. To that end, all DSLR service requests follow the same convention. The message tag and payload is a child of the DSLR Dispatch Request tag defined in section , and includes the input parameters for the specific function being called. The format for a generic service request message payload (the function's input parameters) is as follows: 0 1 2 3 4 5 6 7 8 9 1 0 1 2 3 4 5 6 7 8 9 2 0 1 2 3 4 5 6 7 8 9 3 0 1
Index A Abstract data 25 30 13 C 13 39 Client 25 26 25 local events 29 29 26 24 26 29 25 31 16 D Data model - abstract 25 30 34 17 14 16 E 35 F 13 G 20 22 6 H Higher-layer triggered events 26 31 I 37 37 7 Initialization 25 31 6 L Local events client 29 29 34 34 M Message processing 26 31 Messages 12 12 12 12 14 11 14 14 14 N 7 O OSI layers 10 10 9
FACILITY_DSLR 0x8817 Facility for all DSLR HRESULT errors. Generic Error Codes: Value Meaning DSLR_E_OUTOFMEMORY 0x8817000e Ran out of memory. DSLR_E_INVALIDARG 0x88170057 One or more arguments are invalid. DSLR_E_POINTER 0x88174003 Invalid pointer. DSLR_E_FAIL 0x88174005 Unspecified DSLR_E_UNEXPECTED 0x8817ffff Catastrophic failure. Dispenser-Specific Error Codes: Value Meaning DSLR_E_PROXYNOTFOUND 0x88170100 Cannot find a for this service. DSLR_E_STUBNOTFOUND 0x88170101 Cannot find a stub for this service. DSLR_E_INVALIDSETTINGS 0x88170102 Invalid DSLR settings. Serializer/Deserializer-Specific Error Codes: Meaning DSLR_E_CHILDCOUNT 0x88170103 Tag has too many children. DSLR_E_INVALIDFUNCTION 0x88170104 Unknown function. DSLR_E_TOOLONG 0x88170105 The tag's payload is too long. Dispatcher-Specific Error Codes: Value Meaning
DSLR_E_OUTOFHANDLES 0x88170106 No more request handles are available. DSLR_E_SERVICERELEASED 0x88170107 The service was released. DSLR_E_INVALIDCALLCONVENTION 0x88170108 Unsupported calling convention. DSLR_E_INVALIDREQUESTHANDLE 0x88170109 Invalid request handle. DSLR_E_INVALIDSTUBHANDLE 0x8817010a Invalid stub handle. DSLR_E_ABORT 0x8817010b DSLR operation aborted. Transport Specific Codes: Value Meaning DSLR_E_INVALIDOPERATION 0x8817010c Invalid operation. DSLR_E_INVALIDTAGOPERATION 0x8817010d Invalid operation on this tag. DSLR_E_TAGHASNOMORECHILDREN 0x8817010e There are no more children to this tag. DSLR_E_TAGSEEKERROR 0x8817010f Tag operation is out of bounds. DSLR_E_SENDBUFFERTOOSMALL 0x88170110 Buffer is too small for this tag. DSLR_E_DISCONNECTED 0x88170111L The transport was disconnected unexpectedly. The CreateService and DeleteService messages have no additional out parameters. Generic Service Request Payload The purpose of the DSLR protocol is to allow DSLR consumers to define remote services and requests (or function calls) on those services. To that end, all DSLR service requests follow the same convention. The message tag and payload is a child of the DSLR Dispatch Request tag defined in section , and includes the input parameters for the specific function being called. The format for a generic service request message payload (the function's input parameters) is as follows: 0 1 2 3 4 5 6 7 8 9 1 0 1 2 3 4 5 6 7 8 9 2 0 1 2 3 4 5 6 7 8 9 3 0 1
A Abstract data model 25 30 13 C 13 39 Client 25 26 25 events 29 29 26 24 26 29 25 31 16 D Data - abstract 25 30 34 17 14 16 E 35 F 13 G 20 22 6 H triggered events 26 31 I 37 37 7 Initialization 25 31 6 L Local events client 29 29 proxy 34 34 M Message processing 26 31 Messages 12 12 12 12 14 11 14 14 14 N 7 O OSI layers 10 10 9 8 10 10 10 11 11 8 P 37 13 13 38 Protocol Details 24 local events 34 34 R
Revision Summary Date Revision History Revision Class Comments 6/20/2008 0.1 New Version 0.1 release 7/25/2008 0.1.1 Editorial Changed language and formatting in the technical content. 8/29/2008 0.1.2 Editorial Changed language and formatting in the technical content. 10/24/2008 0.1.3 Editorial Changed language and formatting in the technical content. 12/5/2008 0.2 Minor Clarified the meaning of the technical content. 1/16/2009 1.0 Major Updated and revised the technical content. 2/27/2009 1.1 Minor Clarified the meaning of the technical content. 4/10/2009 1.2 Minor Clarified the meaning of the technical content. 5/22/2009 1.2.1 Editorial Changed language and formatting in the technical content.
7/2/2009 1.2.2 Editorial Changed language and formatting in the technical content. 8/14/2009 1.2.3 Editorial Changed language and formatting in the technical content. 9/25/2009 1.3 Minor Clarified the meaning of the technical content. 11/6/2009 1.3.1 Editorial Changed language and formatting in the technical content. 12/18/2009 1.4 Minor Clarified the meaning of the technical content. 1/29/2010 2.0 Major Updated and revised the technical content. 3/12/2010 3.0 Major Updated and revised the technical content. 4/23/2010 3.0.1 Editorial Changed language and formatting in the technical content. 6/4/2010 3.0.2 Editorial Changed language and formatting in the
formatting of the technical content. 6/17/2011 5.3 Clarified the meaning of the technical content. 9/23/2011 5.3 None No changes to the meaning, language, or formatting of the technical content. 12/16/2011 6.0 Major Updated and revised the technical content. 3/30/2012 6.0 None No changes to the meaning, language, or formatting of the technical content. 7/12/2012 6.0 None No changes to the meaning, language, or formatting of the technical content. 10/25/2012 6.0 None No changes to the meaning, language, or formatting of the technical content. 1/31/2013 6.0 None No changes to the meaning, language, or
Index A Abstract data model 16 16 9 15 15 15 15 15 B BeginSession 13 11 13 C 9 28 14 D Data model - abstract 16 16 E Elements 13 13 14 14 14 14 EndSession 14 12 14 Events 20 20 21 F 9 25 G 6 15 I 24 24 8 Initialization 16 16 6 L Local events 20 20 M Message processing 17 17 Messages 15 15 11 13 11 13 11 14 13 12 14 12 14 12 10 15 10 11 14 11 14 11 15 15 15 15 15 10 10 N 10 7 O Operations 17 18 19 18 8
Revision Summary Date Revision History Revision Class Comments 11/6/2009 0.1 Release. 12/18/2009 0.1.1 Editorial Changed language and formatting in the technical content. 1/29/2010 1.0 Major Updated and revised the technical content. 3/12/2010 1.0.1 Editorial Changed language and formatting in the technical content. 4/23/2010 1.0.2 Editorial Changed language and formatting in the technical content. 6/4/2010 2.0 Major Updated and revised the technical content. 7/16/2010 3.0 Major Updated and revised the technical content. 8/27/2010 4.0 Major Updated and revised the technical content. 10/8/2010 4.0 None No changes to the meaning, language, or formatting of the
the technical content. 2/13/2014 7.0 None No changes to the meaning, language, or formatting of the technical content. 5/15/2014 7.0 None No changes to the meaning, language, or formatting of the technical content. 6/30/2015 7.0 None No changes to the meaning, language, or formatting of 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
Revision Summary Date Revision History Revision Comments 7/7/2011 0.1 New Released new document. 11/3/2011 0.1 None No changes to the meaning, language, or formatting of the technical content. 1/19/2012 0.1 None No changes to the meaning, language, or formatting of the technical content. 2/23/2012 0.1 None No changes to the meaning, language, or formatting of the technical content. 3/27/2012 0.1 None No changes to the meaning, language, or formatting of the technical content. 5/24/2012 0.1 None No changes to the meaning, language, or formatting of the technical content. 6/29/2012 0.1 None No changes to the meaning, language, or
version identification. CACHEDEFERRED 0x00001000 Set if the data for the column is currently in a local cache. ISCHAPTER 0x00002000 Set if the column contains a chapter value. The DataType property can have one of the following values. For more information, see Name Value Description EMPTY 0 No type specified for the value. NULL 1 A NULL value. I2 2 A two-byte, signed integer. For more information, see . I4 3 A four-byte, signed integer. For more information, see . R4 4 A floating value. For more information, see . R8 5 A floating point value. For more information, see . CY 6 A currency value, stored in an 8-byte signed integer. For more information, see CURRENCY ([MS-OAUT] section ).
Index A 7 C 58 48 8 8 52 52 51 D 8 Details 8 14 13 14 7 22 39 E Example 52 52 Examples 52 52 F 7 7 G 47 5 I 54 6 5 L 7 47 N 6 O 14 other protocols and structures 7 7 7 P 52 52 Package structure ( 9, 16) 8 8 13 55 R 6 6 6 7 S Security 54 19 Structures 8 T 58 41 39 V 7 10 10 7
Index A 7 C 7 18 E Examples 14 14 14 F 7 16 G 5 I Ihttpdiscoveryservice server 12 12 12 12 13 13 12 15 15 6 5 M Messages 8 N 8 5 O 6 P 15 7 7 17 Protocol examples 14 14 14 R References 6 5 6 S Security 15 15 7 T 18 8 8 V 7 7 X 16
Revision Summary Date Revision History Revision Comments 8/8/2013 1.0 New Released new document. 11/14/2013 1.0 None No changes to the meaning, language, or formatting of the technical content. 2/13/2014 1.0 None No changes to the meaning, language, or formatting of the technical content. 5/15/2014 2.0 Major Significantly changed the technical content. 6/30/2015 3.0 Major Significantly changed the technical content. 10/16/2015 3.0 None No changes to the meaning, language, or formatting of the technical content. 7/14/2016 4.0 Major Significantly changed the technical content. 6/1/2017 5.0 Major Significantly changed the technical content.
Index A 7 C 8 27 E Examples 19 20 19 F 8 23 G 5 I Ihttpdiscoveryservice server 16 16 16 16 18 18 16 22 22 6 5 M Messages 9 N 9 6 O 6 P 22 7 7 26 Protocol examples 19 20 19 R References 6 6 7 S Security 22 22 8 T 27 9 9 V 8 8 X 23
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 For more information, please contact . Section Tracking number (if applicable) and description Major change (Y or N) Change type Appendix B: Product Behavior Updated the product applicability list to include Windows Server 2016 Technical Preview. Y Content update.
Index A Abstract data model 15 10 12 12 C 10 34 12 12 D Data - abstract 15 12 E 12 Events 24 24 F 10 31 G 5 12 I 30 30 8 Initialization 15 5 L Local events 24 M Message processing 15 Messages 12 12 12 12 12 11 12 11 12 11 11 N 11 6 O Operations 23 15 8 P 30 9 9 33 R 6 8 6 8 S
Revision Summary Date Revision History Revision Class Comments 8/8/2013 1.0 New Released new document. 11/14/2013 1.0 None No changes to the meaning, language, or formatting of the technical content. 2/13/2014 2.0 Major Significantly changed the technical content. 5/15/2014 3.0 Major Significantly changed 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 5.0 Major Significantly changed the technical content.
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 Normative References Added [MS-ADTS] to list of normative references. Y New content added. Added a reference for the OCTET_STRING attribute. Y Content update. a reference for the UNICODE_STRING attribute. Y Content update.
Index A Abstract data model 16 10 12 12 C 10 35 12 12 D Data - abstract 16 12 E 12 Events 25 25 F 10 32 G 5 12 I 31 31 8 Initialization 16 5 L events 25 M Message processing 16 Messages 12 12 12 12 12 11 12 11 12 11 11 N 11 6 O Operations 23 16 8 P 31 9 9 34 R 6 8 6 8 S 12 Security 31 31 Sequencing rules 16 Server 16 16 25 16 23 16 16 25 16 12 10 Syntax 11 T Timer events