ࡱ > q t n o p a bjbj͚ I\I\] p p p p p D 4 ؝ , }$ P T @ ܩ 4 # # # # # # # $ O' * * # Q p ܩ ܩ # p p H 7$ f p p # # w
0| " . & # M$ 0 }$ Z /* P < /* " 0 /* p D h # # }$ /* > 6 : [MC-NBFSE]: .NET Binary Format: SOAP Extension
Intellectual Property Rights Notice for Open Specifications Documentation
Technical Documentation. Microsoft publishes Open Specifications documentation for protocols, file formats, languages, standards as well as overviews of the interaction among each of these technologies.
Copyrights. This documentation is covered by Microsoft copyrights. Regardless of any other terms that are contained in the terms of use for the Microsoft website that hosts this documentation, you may make copies of it in order to develop implementations of the technologies described in the Open Specifications and may distribute portions of it in your implementations using these technologies or your documentation as necessary to properly document the implementation. You may also distribute in your implementation, with or without modification, any schema, IDLs, or code samples that are included in the documentation. This permission also applies to any documents that are referenced in the Open Specifications.
No Trade Secrets. Microsoft does not claim any trade secret rights in this documentation.
Patents. Microsoft has patents that may cover your implementations of the technologies described in the Open Specifications. Neither this notice nor Microsoft's delivery of the documentation grants any licenses under those or any other Microsoft patents. However, a given Open Specification may be covered by Microsoft HYPERLINK "http://go.microsoft.com/fwlink/?LinkId=214445" Open Specification Promise or the HYPERLINK "http://go.microsoft.com/fwlink/?LinkId=214448" Community Promise. If you would prefer a written license, or if the technologies described in the Open Specifications are not covered by the Open Specifications Promise or Community Promise, as applicable, patent licenses are available by contacting HYPERLINK "mailto:iplg@microsoft.com" iplg@microsoft.com.
Trademarks. The names of companies and products contained in this documentation may be covered by trademarks or similar intellectual property rights. This notice does not grant any licenses under those rights. For a list of Microsoft trademarks, visit HYPERLINK "http://www.microsoft.com/trademarks" www.microsoft.com/trademarks.
Fictitious Names. The example companies, organizations, products, domain names, email addresses, logos, people, places, and events depicted in this documentation are fictitious. No association with any real company, organization, product, domain name, email address, logo, person, place, or event is intended or should be inferred.
Reservation of Rights. All other rights are reserved, and this notice does not grant any rights other than specifically described above, whether by implication, estoppel, or otherwise.
Tools. The Open Specifications do not require the use of Microsoft programming tools or programming environments in order for you to develop an implementation. If you have access to Microsoft programming tools and environments you are free to take advantage of them. Certain Open Specifications are intended for use in conjunction with publicly available standard specifications and network programming art, and assumes that the reader either is familiar with the aforementioned material or has immediate access to it.
Revision Summary
DateRevision HistoryRevision ClassComments08/10/20070.1MajorInitial Availability09/28/20070.2MinorUpdated the technical content.10/23/20070.2.1EditorialRevised and edited the technical content.11/30/20070.2.2EditorialRevised and edited the technical content.01/25/20080.2.3EditorialRevised and edited the technical content.03/14/20080.2.4EditorialRevised and edited the technical content.05/16/20080.2.5EditorialRevised and edited the technical content.06/20/20080.2.6EditorialRevised and edited the technical content.07/25/20080.2.7EditorialRevised and edited the technical content.08/29/20080.2.8EditorialRevised and edited the technical content.10/24/20080.2.9EditorialRevised and edited the technical content.12/05/20080.3MinorUpdated the technical content.01/16/20090.3.1EditorialRevised and edited the technical content.02/27/20090.3.2EditorialRevised and edited the technical content.04/10/20090.4MinorUpdated the technical content.05/22/20090.5MinorUpdated the technical content.07/02/20090.5.1EditorialRevised and edited the technical content.08/14/20090.5.2EditorialRevised and edited the technical content.09/25/20090.6MinorUpdated the technical content.11/06/20090.6.1EditorialRevised and edited the technical content.12/18/20090.6.2EditorialRevised and edited the technical content.01/29/20100.7MinorUpdated the technical content.03/12/20100.7.1EditorialRevised and edited the technical content.04/23/20101.0MajorUpdated and revised the technical content.06/04/20101.0.1EditorialRevised and edited the technical content.07/16/20102.0MajorSignificantly changed the technical content.08/27/20102.0No changeNo changes to the meaning, language, or formatting of the technical content.10/08/20102.0No changeNo changes to the meaning, language, or formatting of the technical content.11/19/20102.0No changeNo changes to the meaning, language, or formatting of the technical content.01/07/20112.0No changeNo changes to the meaning, language, or formatting of the technical content.02/11/20112.0No changeNo changes to the meaning, language, or formatting of the technical content.03/25/20112.0No changeNo changes to the meaning, language, or formatting of the technical content.05/06/20112.0No changeNo changes to the meaning, language, or formatting of the technical content.06/17/20112.1MinorClarified the meaning of the technical content.09/23/20112.1No changeNo changes to the meaning, language, or formatting of the technical content.12/16/20113.0MajorSignificantly changed the technical content.03/30/20123.0No changeNo changes to the meaning, language, or formatting of the technical content.07/12/20123.0No changeNo changes to the meaning, language, or formatting of the technical content.10/25/20123.0No changeNo changes to the meaning, language, or formatting of the technical content.01/31/20133.0No changeNo changes to the meaning, language, or formatting of the technical content.08/08/20133.0No changeNo changes to the meaning, language, or formatting of the technical content.11/14/20133.0No changeNo changes to the meaning, language, or formatting of the technical content.
Contents
TOC \f \h \t "DSTOC1-1,1,DSTOC1-2,2,DSTOC1-3,3,DSTOC1-4,4,DSTOC1-5,5,DSTOC1-6,6,DSTOC1-7,7,DSTOC1-8,8,DSTOC1-9,9,DSTOC2-2,2,DSTOC2-3,3,DSTOC2-4,4,DSTOC2-5,5,DSTOC2-6,6,DSTOC2-7,7,DSTOC2-8,8,DSTOC2-9,9,DSTOC3-3,3,DSTOC3-4,4,DSTOC3-5,5,DSTOC3-6,6,DSTOC3-7,7,DST HYPERLINK \l "_Toc370465780" 1 Introduction PAGEREF _Toc370465780 \h 5
HYPERLINK \l "_Toc370465781" 1.1 Glossary PAGEREF _Toc370465781 \h 5
HYPERLINK \l "_Toc370465782" 1.2 References PAGEREF _Toc370465782 \h 5
HYPERLINK \l "_Toc370465783" 1.2.1 Normative References PAGEREF _Toc370465783 \h 6
HYPERLINK \l "_Toc370465784" 1.2.2 Informative References PAGEREF _Toc370465784 \h 6
HYPERLINK \l "_Toc370465785" 1.3 Overview PAGEREF _Toc370465785 \h 6
HYPERLINK \l "_Toc370465786" 1.4 Relationship to Protocols and Other Structures PAGEREF _Toc370465786 \h 6
HYPERLINK \l "_Toc370465787" 1.5 Applicability Statement PAGEREF _Toc370465787 \h 6
HYPERLINK \l "_Toc370465788" 1.6 Versioning and Localization PAGEREF _Toc370465788 \h 6
HYPERLINK \l "_Toc370465789" 1.7 Vendor-Extensible Fields PAGEREF _Toc370465789 \h 6
HYPERLINK \l "_Toc370465790" 2 Structures PAGEREF _Toc370465790 \h 7
HYPERLINK \l "_Toc370465791" 2.1 StringTable PAGEREF _Toc370465791 \h 7
HYPERLINK \l "_Toc370465792" 2.2 DictionaryString PAGEREF _Toc370465792 \h 7
HYPERLINK \l "_Toc370465793" 3 Structure Examples PAGEREF _Toc370465793 \h 9
HYPERLINK \l "_Toc370465794" 4 Security Considerations PAGEREF _Toc370465794 \h 11
HYPERLINK \l "_Toc370465795" 5 Appendix A: Product Behavior PAGEREF _Toc370465795 \h 12
HYPERLINK \l "_Toc370465796" 6 Change Tracking PAGEREF _Toc370465796 \h 13
HYPERLINK \l "_Toc370465797" 7 Index PAGEREF _Toc370465797 \h 14
1 Introduction
In many types of communication, there are often repeated HYPERLINK "[MS-DTYP].pdf" strings, both within a document and within the context of related documents. For example, a request for a record set yields a list of records in one document or a series of documents, each bearing a record. Each record uses the same application-defined HYPERLINK "[MS-GLOS].pdf" XML tags. This pattern of repeated custom XML tags would be repeated each time as a fully expanded string using HYPERLINK "[MC-NBFS].pdf" [MC-NBFS].
This specification defines the .NET Binary Format: SOAP Extension, which is a new format built by extending the format specified in [MC-NBFS]. [MC-NBFS] specifies a way to efficiently encode strings that are common to many HYPERLINK "[MS-GLOS].pdf" SOAP messages, but it does not specify a way to efficiently encode repeated strings that are custom to applications. The purpose of this specification is to define a mechanism by which strings may be transmitted once and referred to by subsequent documents. Thus, applications with some recurrence of strings may result in documents that are smaller using [MC-NBFSE].
The .NET Binary Format: SOAP Extension does not specify a context in which documents are related. Rather, it is designed to work within the .NET Message Framing Protocol, as specified in HYPERLINK "[MC-NMF].pdf" [MC-NMF], which provides a context that defines related documents.
Sections 1.7 and 2 of this specification are normative and can contain the terms MAY, SHOULD, MUST, MUST NOT, and SHOULD NOT as defined in RFC 2119. All other sections and examples in this specification are informative.
1.1 Glossary
The following terms are defined in HYPERLINK "[MS-GLOS].pdf" [MS-GLOS]:
.NET FrameworkXML
The following terms are defined in HYPERLINK "[MC-NBFX].pdf" [MC-NBFX]:
DictionaryStringMultiByteInt31recordString
The following terms are specific to this document:
MAY, SHOULD, MUST, SHOULD NOT, MUST NOT: These terms (in all caps) are used as described in HYPERLINK "http://go.microsoft.com/fwlink/?LinkId=90317" [RFC2119]. All statements of optional behavior use either MAY, SHOULD, or SHOULD NOT.
1.2 References
References to Microsoft Open Specifications documentation do not include a publishing year because links are to the latest version of the documents, which are updated frequently. References to other documents include a publishing year when one is available.
A reference marked "(Archived)" means that the reference document was either retired and is no longer being maintained or was replaced with a new document that provides current implementation details. We archive our documents online HYPERLINK "http://msdn.microsoft.com/en-us/library/jj633107.aspx" [Windows Protocol].
1.2.1 Normative References
We conduct frequent surveys of the normative references to assure their continued availability. If you have any issue with finding a normative reference, please contact HYPERLINK "mailto:dochelp@microsoft.com" dochelp@microsoft.com. We will assist you in finding the relevant information. Please check the archive site, HYPERLINK "http://msdn2.microsoft.com/en-us/library/E4BD6494-06AD-4aed-9823-445E921C9624" http://msdn2.microsoft.com/en-us/library/E4BD6494-06AD-4aed-9823-445E921C9624, as an additional source.
[MC-NBFS] Microsoft Corporation, " HYPERLINK "[MC-NBFS].pdf" .NET Binary Format: SOAP Data Structure".
[MC-NBFX] Microsoft Corporation, HYPERLINK "[MC-NBFX].pdf" .NET Binary Format: XML Data Structure".
[MC-NMF] Microsoft Corporation, " HYPERLINK "[MC-NMF].pdf" .NET Message Framing Protocol".
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997, HYPERLINK "http://go.microsoft.com/fwlink/?LinkId=90317" http://www.rfc-editor.org/rfc/rfc2119.txt
[SOAP1.2-1/2007] Gudgin, M., Hadley, M., Mendelsohn, N., et al., "SOAP Version 1.2 Part 1: Messaging Framework (Second Edition) ", W3C Recommendation 27, April 2007, HYPERLINK "http://go.microsoft.com/fwlink/?LinkId=94664" http://www.w3.org/TR/2007/REC-soap12-part1-20070427/
1.2.2 Informative References
[MS-GLOS] Microsoft Corporation, " HYPERLINK "[MS-GLOS].pdf" Windows Protocols Master Glossary".
1.3 Overview
This .NET Binary Format: SOAP Extension is used to efficiently represent SOAP documents, as specified in HYPERLINK "http://go.microsoft.com/fwlink/?LinkId=94664" [SOAP1.2-1/2007]. When multiple documents are being processed, this format may be more efficient than the .NET Binary Format: SOAP Data Structure, as specified in HYPERLINK "[MC-NBFS].pdf" [MC-NBFS].
1.4 Relationship to Protocols and Other Structures
The .NET Binary Format: SOAP Extension uses the .NET Binary Format: SOAP Data Structure, as specified in HYPERLINK "[MC-NBFS].pdf" [MC-NBFS].
The .NET Message Framing Protocol, as specified in HYPERLINK "[MC-NMF].pdf" [MC-NMF], uses the .NET Binary Format: SOAP Extension.
1.5 Applicability Statement
The .NET Binary Format: SOAP Extension is a general-purpose way to process a series of SOAP documents, and is applied in the same way as specified in HYPERLINK "[MC-NBFS].pdf" [MC-NBFS] section 1.5. Additionally, the format is particularly well-suited for environments where a series of SOAP documents that share a common or repetitive vocabulary are processed.
1.6 Versioning and Localization
For information on versioning and localization, see HYPERLINK "[MC-NBFS].pdf" [MC-NBFS] section 1.6.
1.7 Vendor-Extensible Fields
The .NET Binary Format: SOAP Extension has no vendor-extensible fields.
2 Structures
The structures in the .NET Binary Format: SOAP Extension are identical to those specified in HYPERLINK "[MC-NBFS].pdf" [MC-NBFS], except for the addition of one new structure and a further extension of the HYPERLINK "[MC-NBFS].pdf" DictionaryString structure, as specified in HYPERLINK "[MC-NBFS].pdf" [MC-NBFS] section 2.1.
The format is identical to the .NET Binary Format: SOAP Data Structure, as specified in [MC-NBFS], except that the document MUST be preceded by a HYPERLINK \l "za161304c1a8a4f31beecb96ebc9b1919" StringTable structure, as specified in section HYPERLINK \l "za161304c1a8a4f31beecb96ebc9b1919" 2.1.
2.1 StringTable
The StringTable structure describes a set of new HYPERLINK "[MC-NBFX].pdf" strings to which subsequent HYPERLINK "[MC-NBFX].pdf" records can refer. As specified in HYPERLINK "[MC-NBFS].pdf" [MC-NBFS] (section HYPERLINK \l "zc84fb6f434c842e29a291208758c0940" 2.2), the static DictionaryStrings defined by [MC-NBFS] map even integers to a static set of characters, leaving odd integers for extension. The StringTable structure takes advantage of the extensibility point by defining a mapping of odd integers to strings.
01234567891012345678920123456789301Size (variable)...Strings (variable)...Size (variable): An integer value that is encoded by using the HYPERLINK "[MC-NBFX].pdf" MultiByteInt31 structure that indicates the overall size in bytes of the HYPERLINK "[MC-NBFX].pdf" String structures that follow.
Strings (variable): A series of strings. The Strings MUST fit exactly within the Size specified. Each String MUST be unique and MUST NOT have been present in a prior StringTable.
The first String of the first StringTable is assigned an ID of 1, and each subsequent String is assigned the next-higher odd number. A consumer of this format MUST maintain this mapping until there are no further documents to process. Subsequent records and documents will refer to this String by this ID, as specified in section HYPERLINK \l "zc84fb6f434c842e29a291208758c0940" 2.2.
2.2 DictionaryString
The DictionaryString structure describes a reference to a set of characters.
01234567891012345678920123456789301Value (variable)...Value (variable): An integer value that is encoded by using the HYPERLINK "[MC-NBFX].pdf" MultiByteInt31 structure. If this value is even, then it MUST be interpreted as specified in HYPERLINK "[MC-NBFS].pdf" [MC-NBFS] section 2. If this value is odd, then it MUST refer to a String from a HYPERLINK \l "za161304c1a8a4f31beecb96ebc9b1919" StringTable structure that has been processed and MUST be interpreted as the set of characters identified by that String.
3 Structure Examples
The following example is of a SOAP document that uses the .NET Binary Format: SOAP Extension format.
Note that the document is the same document that is encoded in HYPERLINK "[MC-NBFS].pdf" [MC-NBFS] section 3.
action
0
Because the content "action" in the element is not present in the HYPERLINK "[MC-NBFX].pdf" string structure as specified in HYPERLINK "[MC-NBFS].pdf" [MC-NBFS] section 2, the string was written out fully.
Bytes (hex) Records Characters represented 99 06 61 63 74 69 6F 6E Chars8TextWithEndElementactionSimilarly, because the Inventory string was also not present, the element was written out verbosely.
Bytes (hex) Records Characters represented 40 09 49 6E 76 65 6E 74 6F 72 79ShortElementIf this document, or a similar document, is processed repeatedly, then it is advantageous not to have to repeat these bytes.
Using the .NET Binary Format: SOAP Extension, a HYPERLINK \l "za161304c1a8a4f31beecb96ebc9b1919" StringTable (section HYPERLINK \l "za161304c1a8a4f31beecb96ebc9b1919" 2.1 HYPERLINK \l "za161304c1a8a4f31beecb96eb c 9 b 1 9 1 9 " ) i s u s e d f i r s t t o d e s c r i b e t h e t w o s t r i n g s .
a c t i o n
I n v e n t o r y
A c c o r d i n g t o t h e S t r i n g T a b l e s t r u c t u r e , t h e s e s t r i n g s M U S T b e e n c o d e d a s s h o w n i n t h e f o l l o w i n g t a b l e . T h e B y t e s c o l u m n c o n t a i n s t h e b y t e s o f t h e s t r u c t u r e s h o w n i n h e x , w h i l e t h e Chars column contains the same bytes shown as characters.
Bytes (hex) Chars 11 06 61 63 74 69 6F 6E 09 49 6E 76 65 6E 74 6F 72 79..action.InventoryThe bolded items in the preceding table are the size (0x11) of the overall structure encoded using MultiByteInt31 and the start of the two strings (0x06, 0x09) encoded using MultiByteInt31 as well. The string "action" is assigned a value of 1 and Inventory is assigned a value of 3, as specified in section HYPERLINK \l "z9c4265fa7ce743cb8067bce285bbccdb" 2.
Now, the two preceding HYPERLINK "[MC-NBFX].pdf" records can be encoded more compactly, as shown in the following tables.
Bytes (hex) Records Characters represented AB 01DictionaryTextWithEndElementaction
Bytes (hex) Records Characters represented 42 03ShortDictionaryElementThe references to the string from the StringTable are in bold.
4 Security Considerations
The .NET Binary Format: SOAP Extension has the same security considerations as the .NET Binary Format: SOAP Data Structure, as specified in HYPERLINK "[MC-NBFS].pdf" [MC-NBFS] section 4, and the .NET Binary Format: XML Data Structure, as specified in HYPERLINK "[MC-NBFX].pdf" [MC-NBFX] section HYPERLINK \l "z391c1720e3e4427aaa4c2abb3abf93fe" 4.
Consumers of this format should consider limiting the size of the HYPERLINK \l "za161304c1a8a4f31beecb96ebc9b1919" StringTable (section HYPERLINK \l "za161304c1a8a4f31beecb96ebc9b1919" 2.1 HYPERLINK \l "za161304c1a8a4f31beecb96ebc9b1919" ) structures that are processed. In addition to requiring the consumer to allocate memory to store the information, StringTable structures represent a way to refer to a potentially large piece of information by using a small piece of information. Without any limits, it might be possible for a malicious producer to leverage this behavior and devise a document that causes an unsuspecting consumer to use significantly more memory than expected.
5 Appendix A: Product Behavior
This document specifies version-specific details in the Microsoft.NET Framework. The following versions of .NET Framework are available in the following released Windows product or as supplemental software, see HYPERLINK "[MS-GLOS].pdf" .NET Framework.
The information in this specification is applicable to the following Microsoft products or supplemental software. References to product versions include released service packs:
M i c r o s o f t . N E T F r a m e w o r k 3 . 0
M i c r o s o f t . N E T F r a m e w o r k 3 . 5
M i c r o s o f t . N E T F r a m e w o r k 4 . 0
M i c r o s o f t . N E T F r a m e w o r k 4 . 5
E x c e p t i o n s , i f a n y , a r e n o t e d b e l o w . I f a s e r v i c e p a c k o r Q u i c k F i x E n g i n e e r i n g ( Q F E ) n u m b e r a p p e a r s w i t h t h e p r o d u c t v e r s i o n , b e h a v ior changed in that service pack or QFE. The new behavior also applies to subsequent service packs of the product unless otherwise specified. If a product edition appears with the product version, behavior is different in that product edition.
Unless otherwise specified, any statement of optional behavior in this specification that is prescribed using the terms SHOULD or SHOULD NOT implies product behavior in accordance with the SHOULD or SHOULD NOT prescription. Unless otherwise specified, the term MAY implies that the product does not follow the prescription.
6 Change Tracking
No table of changes is available. The document is either new or has had no changes since its last release.
7 Index
A
HYPERLINK \l "zdd7b06368d8049a98cc4d0694b6c2944" Applicability 6
C
HYPERLINK \l "z3c92158a76434f99a275c6351a560382" Change tracking 13
HYPERLINK \l "z9c4265fa7ce743cb8067bce285bbccdb" Common data types and fields 7
D
HYPERLINK \l "z9c4265fa7ce743cb8067bce285bbccdb" Data types and fields - common 7
HYPERLINK \l "z9c4265fa7ce743cb8067bce285bbccdb" Details - common data types and fields 7
HYPERLINK \l "zc84fb6f434c842e29a291208758c0940" DictionaryString packet 7
E
HYPERLINK \l "z0f3354271b804b5da32ee339e8acf376" Example 9
F
HYPERLINK \l "z672e9716f94548ddb5094ea7fb0f484b" Fields - vendor-extensible 6
G
HYPERLINK \l "z86e31626eb2b48d4a9775705c8640f02" Glossary 5
I
HYPERLINK \l "zec9a6500bd224b32aafb87375f2cabe3" Informative references 6
HYPERLINK \l "z517e2034aee640d3ac252c1532c39c64" Introduction 5
L
HYPERLINK \l "z4754e6e66d6148d6b240e82c461952ce" Localization 6
N
HYPERLINK \l "z19c72c4ed96c4137a4b3ede12c5d6572" Normative references 6
O
HYPERLINK \l "zdc4aeb7007f84027a004b926225a10bc" Overview (synopsis) 6
P
HYPERLINK \l "zf8a1891fee284608a0b9eeee481d9863" Product behavior 12
R
References
HYPERLINK \l "zec9a6500bd224b32aafb87375f2cabe3" informative 6
HYPERLINK \l "z19c72c4ed96c4137a4b3ede12c5d6572" normative 6
HYPERLINK \l "z88f08d7fe8f641a384c99e416fad0988" Relationship to protocols and other structures 6
S
HYPERLINK \l "zb6ea4d2997094329b9f1c8d661364a73" Security considerations 11
HYPERLINK \l "za161304c1a8a4f31beecb96ebc9b1919" StringTable packet 7
HYPERLINK \l "z9c4265fa7ce743cb8067bce285bbccdb" Structures - overview 7
T
HYPERLINK \l "z3c92158a76434f99a275c6351a560382" Tracking changes 13
V
HYPERLINK \l "z672e9716f94548ddb5094ea7fb0f484b" Vendor-extensible fields 6
HYPERLINK \l "z4754e6e66d6148d6b240e82c461952ce" Versioning 2 { | H S ( q y
L M ^ _ H I p q ! 7 ! ! " " " " # # # # "# ## *j" hO hy 0J UmH nH u hy mH nH uhO hy 0J mH nH u$j hO hy 0J UmH nH u hy hy 5j h7 hy 0J U
hy 0J j hy U
hy 0Jh hy 8 1 2 | H q ! $If gdQ gdy [ gdy gdy gdy gdy ! , 0 , # # $If gdQ kd $$If V 4 \
oE#
t ( 0 (#6 4 4
a p( yty 0 6 K L W [ a ? kd$ $$If V \
oE#
t 0 (#6 4 4
a p( yty $If gdQ H ? ? ? ? $If gdQ kd $$If V \
oE#
t 0 (#6 4 4
a p( yty H ? ? ? ? $If gdQ kd $$If V \
oE#
t 0 (#6 4 4
a p( yty
( R H ? ? ? ? $If gdQ kd $$If V \
oE#
t 0 (#6 4 4
a p( yty R S ^ d n H ? ? ? ? $If gdQ kdH $$If V \
oE#
t 0 (#6 4 4
a p( yty H ? ? ? ? $If gdQ kd $$If V \
oE#
t 0 (#6 4 4
a p( yty $ H ? ? ? ? $If gdQ kd $$If V \
oE#
t 0 (#6 4 4
a p( yty $ % 0 6 @ j H ? ? ? ? $If gdQ kd $$If V \
oE#
t 0 (#6 4 4
a p( yty j k v | H ? ? ? ? $If gdQ kdl $$If V \
oE#
t 0 (#6 4 4
a p( yty H ? ? ? ? $If gdQ kd5 $$If V \
oE#
t 0 (#6 4 4
a p( yty + H ? ? ? ? $If gdQ kd $$If V \
oE#
t 0 (#6 4 4
a p( yty + , 7 = G q H ? ? ? ? $If gdQ kd $$If V \
oE#
t 0 (#6 4 4
a p( yty q r } H ? ? ? ? $If gdQ kd
$$If V \
oE#
t 0 (#6 4 4
a p( yty H ? ? ? ? $If gdQ kdY $$If V \
oE#
t 0 (#6 4 4
a p( yty ! H ? ? ? ? $If gdQ kd" $$If V \
oE#
t 0 (#6 4 4
a p( yty ! " - 3 = g H ? ? ? ? $If gdQ kd $$If V \
oE#
t 0 (#6 4 4
a p( yty g h s y H ? ? ? ? $If gdQ kd
$$If V \
oE#
t 0 (#6 4 4
a p( yty H ? ? ? ? $If gdQ kd} $$If V \
oE#
t 0 (#6 4 4
a p( yty ( H ? ? ? ? $If gdQ kdF $$If V \
oE#
t 0 (#6 4 4
a p( yty ( ) 4 : D n H ? ? ? ? $If gdQ kd $$If V \
oE#
t 0 (#6 4 4
a p( yty n o z ~ H ? ? ? ? $If gdQ kd $$If V \
oE#
t 0 (#6 4 4
a p( yty H ? ? ? ? $If gdQ kd $$If V \
oE#
t 0 (#6 4 4
a p( yty * H ? ? ? ? $If gdQ kdj $$If V \
oE#
t 0 (#6 4 4
a p( yty * + 6 < F p H ? ? ? ? $If gdQ kd3 $$If V \
oE#
t 0 (#6 4 4
a p( yty p q | H ? ? ? ? $If gdQ kd $$If V \
oE#
t 0 (#6 4 4
a p( yty H ? ? ? ? $If gdQ kd $$If V \
oE#
t 0 (#6 4 4
a p( yty & * 4 H ? ? ? ? $If gdQ kd $$If V \
oE#
t 0 (#6 4 4
a p( yty H ? ? ? ? $If gdQ kdW $$If V \
oE#
t 0 (#6 4 4
a p( yty O H ? ? ? ? $If gdQ kd $$If V \
oE#
t 0 (#6 4 4
a p( yty O P [ _ i H ? ? ? ? $If gdQ kd $$If V \
oE#
t 0 (#6 4 4
a p( yty H ? ? ? ? $If gdQ kd $$If V \
oE#
t 0 (#6 4 4
a p( yty ) - 7 H ? ? ? ? $If gdQ kd{ $$If V \
oE#
t 0 (#6 4 4
a p( yty H ? ? ? ? $If gdQ kdD $$If V \
oE#
t 0 (#6 4 4
a p( yty 1 H ? ? ? ? $If gdQ kd
$$If V \
oE#
t 0 (#6 4 4
a p( yty 1 2 = A G t H ? ? ? ? $If gdQ kd $$If V \
oE#
t 0 (#6 4 4
a p( yty t u H ? ? ? ? $If gdQ kd $$If V \
oE#
t 0 (#6 4 4
a p( yty B H ? ? ? ? $If gdQ kdh $$If V \
oE#
t 0 (#6 4 4
a p( yty B C N R \ H ? ? ? ? $If gdQ kd1 $$If V \
oE#
t 0 (#6 4 4
a p( yty ! H ? ? ? ? $If gdQ kd $$If V \
oE#
t 0 (#6 4 4
a p( yty ! ! ! ! *! w! H ? ? ? ? $If gdQ kd $$If V \
oE#
t 0 (#6 4 4
a p( yty w! x! ! ! ! ! H ? ? ? ? $If gdQ kd $$If V \
oE#
t 0 (#6 4 4
a p( yty ! ! ! ! ! D# # H C > > <