Revision Summary Date Revision History Revision 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 Major Updated and revised 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.05 Clarified the meaning of the technical content. 9/27/2010 1.06 Editorial Changed language and formatting in the technical content. 11/15/2010 1.06 None No changes to the meaning,
language, or formatting of the technical content. 10/8/2012 2.2 Minor Clarified the meaning of the technical content. 2/11/2013 3.0 Major Significantly changed the technical content. 7/30/2013 3.1 Minor Clarified the meaning of the technical content. 11/18/2013 3.2 Minor Clarified the meaning of the technical content. 2/10/2014 3.3 Minor Clarified the meaning of the technical content. 4/30/2014 3.4 Minor Clarified the meaning of the technical content. 7/31/2014 3.5 Minor Clarified the meaning of the technical content. 10/30/2014 3.6 Minor Clarified the meaning of the technical content. 3/16/2015 4.0 Significantly changed the technical content.
6/30/2015 5.0 Major Significantly changed the technical content. 2/26/2016 6.0 Major Significantly changed the technical content. 4/14/2016 7.0 Major Significantly changed the technical content. 7/15/2016 7.0 None No changes to the meaning, language, or formatting of the technical content. 8/23/2016 7.0 None No changes to the meaning, language, or formatting of the technical content. 9/7/2016 7.1 Minor Clarified the meaning of the technical content. 12/15/2016 7.2 Minor Clarified the meaning of the technical content. 3/28/2017 8.0 Major Significantly changed the technical content. 6/20/2017 9.0 Significantly changed the technical content.
2 Other authors detected in the same section where the protocol client is working. 3 Other authors detected outside the same page where the protocol client is working. E – Response Data View (2-bits): A 2-bit unsigned integer that specifies when the protocol client will present the response data to the user. Value Meaning 0 Future user action in a new session. 1 Future user action in the current session. 2 Automatically after a short delay. 3 Immediately. F – Time Since User View (2-bits): A 2-bit unsigned integer that specifies how long it has been since the user viewed data referenced by the Url. Value Meaning 0 Recently. 1 Within one week. 2 Within one 3 More than one month. G – Document Active State (1-bit): A bit that specifies if the protocol client considered the URL an active or inactive session at the time the request was triggered. Value Meaning 0 Active. 1 Inactive. H – Data Type (1-bit): A bit that specifies if the request data is recoverable by the protocol client. Value Meaning 0 The data is content and requires permanent reliable storage. 1 The data is recoverable. Less reliable stores can be used. I – Network Cost (2-bits): A 2-bit unsigned integer that specifies the cost of the network used to make the request. Meaning 0 Unspecified or unknown. 1 Low-cost network. 2 Medium-cost network. 3 High-cost network. J – Network Quota State (2-bits): A 2-bit unsigned integer that specifies the network quota state when a metered network is being used to make the request. Value Meaning 0 No system. 1 The quota system is active; the quota consumed is one half or less. 2 The quota system is active; the quota consumed is from one half through three quarters. 3 The system is active; the quota consumed is near or over the limit.
schema lock . The attributes in SchemaLockSubRequestDataOptionalAttributes are used as input parameters for processing the data associated with a schema lock subrequest. The definition of the SchemaLockSubRequestDataOptionalAttributes attribute group is as follows: <xs:attributeGroup name="SchemaLockSubRequestDataOptionalAttributes"> <xs:attribute name="SchemaLockRequestType" type="tns:SchemaLockRequestTypes" use="optional"/> </xs:attributeGroup> SchemaLockRequestType: A SchemaLockRequestTypes that specifies the type of schema lock subrequest. SchemaLockRequestTypes is defined in section . The following table shows a mapping between the type of schema lock subrequest and the attributes that MUST be specified for that SchemaLockRequestType. In the following Timeout, AllowFallbackToExclusive, and ExclusiveLockID release the lock on conversion failure, and ClientID, and SchemaLockID are attributes that MUST be specified for the SubRequestData element associated with the coauthoring subrequest, depending on the type of coauthoring subrequest. In the following table, “Yes” signifies that the attribute MUST be specified as part of the SubRequestData element associated with the schema lock subrequest. Value of ExclusiveLockID Release lock on failure ClientID "GetLock" (Get Lock) Yes If is set to true, the attribute for the exclusive lock identifier MUST be specified. Yes Yes "ReleaseLock" (Release Lock) Yes Yes "RefreshLock" (Refresh Lock) Yes Yes Yes (Convert To Exclusive Lock) Yes Yes Yes Yes Yes (Check Lock Availability) Yes WhoAmISubResponseDataOptionalAttributes The WhoAmISubResponseDataOptionalAttributes attribute group contains attributes that MUST be used only in SubResponseData elements associated with a subresponse for a Who Am I . The attributes in WhoAmISubResponseDataOptionalAttributes provide the data that was requested as part of the Who Am I subrequest. The schema definition of the WhoAmISubResponseDataOptionalAttributes attribute group is as follows: out
F 14 49 147 147 156 G 40 26 73 73 72 74 9 49 42 I 146 18 146 11 Initialization 103 9 L Local events 133 42 44 M Message processing 103 147 Messages attribute groups ( 49, 92) 49 86 92 57 58 94 58 59 87 37 95 59 61 61 62 54 complex types ( 26, 54) 37 38 17 15 39 ExclusiveLockRequestTypes simple type ( 88, 90, 91, 91) 39 97 63 ExclusiveLockSubRequestType complex type ( 64, 75, 77, 81, 82, 83) 64 65 49 40 26 73 73 72 74 49 42 18 42 44 45 15 48 26 16 18 16 22 22 16 23 16 24 24 SchemaLockRequestTypes simple type ( 88, 89) SchemaLockSubRequestDataOptionalAttributes attribute group ( 98, 99, 100, 101, 101) SchemaLockSubRequestDataType complex type ( 65, 70, 75, 76, 80, 83) 67 67 67 68 68 ServerTimeSubResponseType complex type ( 69, 76, 78, 81, 82, 84) simple ( 35, 85) 17 17 25 46 25 27 50 28 30 25 25 30 52 32 34
syntax ( 15, 54) 15 47 90 90 49 48 35 WhoAmISubRequestType complex type ( 69, 71, 74) 99 WhoAmISubResponseDataType complex type ( 69, 73, 77, 81, 82, 84) WhoAmISubResponseType complex type ( 70, 72, 74) 45 N 15 48 10 O Operations 131 105 107 104 125 119 130 127 128 131 132 114 125 129 124 11 P 146 14 14 167 26 Protocol Details 103 R 10 11 10 13 18 22 22 23 24 24 S SchemaLockRequestTypes simple type ( 88, 89) SchemaLockSubRequestDataOptionalAttributes attribute group ( 98, 99, 100, 101, 101) SchemaLockSubRequestDataType complex type ( 65, 70, 75, 76, 80, 83) 67 67 67 Security 146 146 Sequencing rules 103 Server 103 131 105 107 104 125 119 130 127 128 103 133 131 103 103 132 114 103 125 133 103 129 124 68 68 ServerTimeSubResponseType complex type ( 69, 76, 78, 81, 82, 84) Simple ( 35, 85) 86 87 37 37 38 39 ExclusiveLockRequestTypes ( 88, 90, 91, 91) 39 49 40 42 42 44 45 48 SchemaLockRequestTypes ( 88, 89) 46 47 90 90