technical content. 5/22/2009 2.0.5 Editorial Changed language and formatting in the technical content. 7/2/2009 2.0.6 Editorial Changed language and formatting in the technical content. 8/14/2009 2.0.7 Editorial Changed language and formatting in the technical content. 9/25/2009 2.1 Minor Clarified the meaning of the technical content. 11/6/2009 3.0 Major Updated and revised the technical content. 12/18/2009 3.1 Minor Clarified the meaning of the technical content. 1/29/2010 3.2 Minor Clarified the meaning of the technical content. 3/12/2010 3.2.1 Editorial Changed language and formatting in the technical content. 4/23/2010 3.2.2 Editorial Changed language and
formatting in the technical content. 6/4/2010 3.2.3 Editorial Changed language and formatting in the technical content. 7/16/2010 3.3 Minor Clarified the meaning of the technical content. 8/27/2010 3.3 None No changes to the meaning, language, or formatting of the technical content. 10/8/2010 4.0 Major Updated and revised the technical content. 11/19/2010 4.0 None No changes to the meaning, language, or formatting of the technical content. 1/7/2011 4.0 None No changes to the meaning, language, or formatting of the technical content. 2/11/2011 5.0 Updated and revised the technical content.
3/25/2011 5.0 None No changes to the meaning, language, or formatting of the technical content. 5/6/2011 6.0 Major Updated and revised the technical content. 6/17/2011 6.1 Minor Clarified the meaning of the technical content. 9/23/2011 6.1 None No changes to the meaning, language, or formatting of the technical content. 12/16/2011 7.0 Major Updated and revised the technical content. 3/30/2012 7.0 None No changes to the meaning, language, or formatting of the technical content. 7/12/2012 7.0 None No changes to the meaning, language, or formatting of the technical content. 10/25/2012 7.0 None No changes to the meaning, language,
or formatting of the technical content. 1/31/2013 8.0 Updated and revised the technical content. 8/8/2013 9.0 Updated and revised the technical content. 11/14/2013 10.0 Major Updated and revised the technical content. 2/13/2014 10.0 None No changes to the meaning, language, or formatting of the technical content. 5/15/2014 10.0 None No changes to the meaning, language, or formatting of the technical content. 6/30/2015 11.0 Major Significantly changed the technical content. 10/16/2015 11.0 None No changes to the meaning, language, or formatting of the technical content. 7/14/2016 11.0 None No changes to the
meaning, language, or formatting of the technical content. 6/1/2017 12.0 Major Significantly changed the technical content. 9/15/2017 13.0 Major Significantly changed the technical content. 12/1/2017 13.0 None No changes to the meaning, language, or formatting of the technical content. 9/12/2018 14.0 Major Significantly changed the technical content.
X T IB NORM IGNORESYMBOLS: Ignore symbols. U INS NORM IGNORENONSPACE: Ignore non-spacing characters. V IC NORM IGNORECASE: Ignore Case Permanent Entry ID GUID This value is associated with the NSPI Protocol and appears in . Name and Description GUID_NSPI {0xDC, 0xA7, 0x40, 0xC8, 0xC0, 0x42, 0x10, 0x1A, 0xB4, 0xB9, 0x08, 0x00, 0x2B, 0x2F, 0xE1, 0x82} Represents the NSPI Protocol in Permanent Entry IDs. Positioning Minimal Entry IDs These values are used to specify objects in the address book as a function of their positions in tables. They appear as in the CurrentRec field of the structure. Possible values are as follows. Name and value Description MID_BEGINNING_OF_TABLE 0x00000000 Specifies the position before the row in the current . MID_END_OF_TABLE 0x00000002 Specifies the position after the last row in
When returning string values as output parameters for methods where the method allows for both and 8-bit character representations, the server MUST follow these conversion rules. If the native type of a property is PtypString and the client has requested that property with the type PtypString8, the server MUST convert the Unicode representation to an 8-bit character representation in the specified by the CodePage of the pStat parameter prior to returning the value. If the native type of a property is PtypString and the client has requested that property with the type PtypString, the server MUST return the Unicode representation unmodified. If the native type of a property is PtypString8 and the client has requested that property with the type PtypString, the server MUST convert the 8-bit character representation to a Unicode representation prior to returning the value. The 8-bit character representation is considered to be in the codepage CP_TELETEX. If the native type of a property is PtypString8 and the client has requested that property with the type PtypString8, the server MUST return the 8-bit character representation unmodified. Servers MAY<7> undertake conversions and substitutions for specific properties. The following specifies methods, that are capable of returning string values in both Unicode and 8-bit character representations, and the methods for which the conversion rules are applicable. Method Description String values can be returned in the output parameter ppData. String values can be returned in the output parameter ppRows. String values can be returned in the output parameter ppRows. String values can be returned in the output parameter ppRows. String values can be returned in the output parameter ppRows. String values can be returned in the output parameter ppRows. String values can be returned in the output parameter ppRows. String values can be returned in the output parameter ppRows. Conversion Rules for String Values Specified by the Client to the Server When accepting strings as input parameters for methods where the method allows for both and 8-bit character representations, the server MUST follow these conversion rules: If the native type of a property is PtypString8 and the client has specified a property value with the type PtypString, the server MUST convert the Unicode representation to an 8-bit character representation in the specified by the CodePage field of the pStat parameter prior to processing the method.
A Abstract data model 82 40 29 11 B 24 26 31 C 11 101 Client 82 82 82 82 82 82 82 82 22 31 13 D Data model - abstract 82 40 22 26 E 37 83 F 12 24 26 90 G 7 I 90 88 89 10 Initialization 82 48 7 L 82 25 M Message processing 82 48 Messages 13 22 13 13 N 9 30 50 69 70 75 64 73 55 57 51 80 72 71 55 59 76 78 67 61 51 53 O 29 Other local events 82 82 10 10 P 17 89 37