ࡱ > " a ę bjbj͚ I\I\ ( ( D d \ O \ D @ | $ N N N N N N N $ Q T * N - 4 4 4 N H N 4 : N 4 N . 0 8 ` n . a2 kN N 0 O 4 T T T 8 8 T 9 h 4 4 4 4 4 4 4 N N 4 4 4 O 4 4 4 4 T 4 4 4 4 4 4 4 4 4 ( > f : [MC-NBFS]: .NET Binary Format: SOAP Data Structure
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.3MinorUpdated the technical content.01/25/20080.3.1EditorialRevised and edited the technical content.03/14/20080.3.2EditorialRevised and edited the technical content.05/16/20080.3.3EditorialRevised and edited the technical content.06/20/20080.3.4EditorialRevised and edited the technical content.07/25/20080.3.5EditorialRevised and edited the technical content.08/29/20080.3.6EditorialRevised and edited the technical content.10/24/20080.3.7EditorialRevised and edited the technical content.12/05/20080.4MinorUpdated the technical content.01/16/20090.4.1EditorialRevised and edited the technical content.02/27/20090.4.2EditorialRevised and edited the technical content.04/10/20090.4.3EditorialRevised and edited 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.6.3EditorialRevised and edited the technical content.03/12/20100.6.4EditorialRevised 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 "_Toc370465802" 1 Introduction PAGEREF _Toc370465802 \h 5
HYPERLINK \l "_Toc370465803" 1.1 Glossary PAGEREF _Toc370465803 \h 5
HYPERLINK \l "_Toc370465804" 1.2 References PAGEREF _Toc370465804 \h 5
HYPERLINK \l "_Toc370465805" 1.2.1 Normative References PAGEREF _Toc370465805 \h 6
HYPERLINK \l "_Toc370465806" 1.2.2 Informative References PAGEREF _Toc370465806 \h 6
HYPERLINK \l "_Toc370465807" 1.3 Overview PAGEREF _Toc370465807 \h 6
HYPERLINK \l "_Toc370465808" 1.4 Relationship to Protocols and Other Structures PAGEREF _Toc370465808 \h 6
HYPERLINK \l "_Toc370465809" 1.5 Applicability Statement PAGEREF _Toc370465809 \h 6
HYPERLINK \l "_Toc370465810" 1.6 Versioning and Localization PAGEREF _Toc370465810 \h 6
HYPERLINK \l "_Toc370465811" 1.7 Vendor-Extensible Fields PAGEREF _Toc370465811 \h 6
HYPERLINK \l "_Toc370465812" 2 Structures PAGEREF _Toc370465812 \h 7
HYPERLINK \l "_Toc370465813" 2.1 DictionaryString PAGEREF _Toc370465813 \h 7
HYPERLINK \l "_Toc370465814" 3 Structure Examples PAGEREF _Toc370465814 \h 24
HYPERLINK \l "_Toc370465815" 4 Security Considerations PAGEREF _Toc370465815 \h 26
HYPERLINK \l "_Toc370465816" 5 Appendix A: Product Behavior PAGEREF _Toc370465816 \h 27
HYPERLINK \l "_Toc370465817" 6 Change Tracking PAGEREF _Toc370465817 \h 28
HYPERLINK \l "_Toc370465818" 7 Index PAGEREF _Toc370465818 \h 29
1 Introduction
This specification defines the .NET Binary Format: SOAP Data Structure, which is a new format built by extending the format described in the .NET Binary Format: HYPERLINK "[MS-GLOS].pdf" XML Data Structure, as specified in HYPERLINK "[MC-NBFX].pdf" [MC-NBFX]. While the SOAP data structure is structurally identical to the XML data structure, should not be used where an XML data structure document is expected.
The XML Data Structure specifies a binary XML format to efficiently encode the structures that are common to any XML document. The SOAP protocol specifies an XML document with specific structures that are common to many SOAP messages. While using XML Data Structure alone to encode SOAP messages provides efficiencies for the structures of XML, one can observe that strings common to many SOAP messages are still encoded in their entirety. Furthermore, the XML data structure does not specify how a producer and a consumer of a document agree on the strings referenced within a document.
The purpose of the SOAP data structure is to extend the XML data structure format to further reduce the cost of generating SOAP documents by defining a shortened structure of strings to which a producer and a consumer can refer.
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-NBFSE] Microsoft Corporation, " HYPERLINK "[MC-NBFSE].pdf" .NET Binary Format: SOAP Extension".
[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
The .NET Binary Format: SOAP Data Structure is used to efficiently represent SOAP documents, as specified in HYPERLINK "http://go.microsoft.com/fwlink/?LinkId=94664" [SOAP1.2-1/2007].
1.4 Relationship to Protocols and Other Structures
The .NET Binary Format: SOAP Data Structure extends the .NET Binary Format: XML Data Structure, as specified in HYPERLINK "[MC-NBFX].pdf" [MC-NBFX]. The .NET Binary Format: SOAP Extension, as specified in HYPERLINK "[MC-NBFSE].pdf" [MC-NBFSE], and the .NET Message Framing Protocol, as specified in HYPERLINK "[MC-NMF].pdf" [MC-NMF], both use the .NET Binary Format: SOAP Data Structure.
1.5 Applicability Statement
The .NET Binary Format: SOAP Data Structure is a general-purpose way to represent an XML document and is applied as specified in HYPERLINK "[MC-NBFX].pdf" [MC-NBFX] section 1.3. Additionally, the format is particularly well-suited for SOAP documents as specified in HYPERLINK "http://go.microsoft.com/fwlink/?LinkId=94664" [SOAP1.2-1/2007] because it defines a fixed set of s from the SOAP vocabulary that a producer and a consumer of documents in this format may reference and results in smaller documents.
This specification extends the format described by [MC-NBFX], which describes an efficient encoding for general XML documents. This specification describes efficient encoding for strings that are specific to SOAP messages and does not supersede any of the structures defined in [MC-NBFX].
1.6 Versioning and Localization
For information on versioning and localization, see HYPERLINK "[MC-NBFX].pdf" [MC-NBFX] section 1.3.
1.7 Vendor-Extensible Fields
The .NET Binary Format: SOAP Data Structure has no vendor-extensible fields.
2 Structures
The structures in the .NET Binary Format: SOAP Data Structure are identical to those specified in HYPERLINK "[MC-NBFX].pdf" [MC-NBFX], except that the HYPERLINK "[MC-NBFX].pdf" DictionaryString structure, as defined in HYPERLINK "[MC-NBFX].pdf" [MC-NBFX] section 1.3, has an additional meaning, described in the following section.
2.1 DictionaryString
The DictionaryString structure describes a reference to a set of characters. This specification lists a static set of characters that both producer and consumer can map via the DictionaryString structure.
The DictionaryString structure MUST be an even integer value. This restriction exists such that another specification, namely HYPERLINK "[MC-NBFSE].pdf" [MC-NBFSE], may define the odd integers to reference another list of sets of characters.
01234567891012345678920123456789301Value (variable) Value: An even integer value encoded by using HYPERLINK "[MC-NBFX].pdf" MultiByteInt31. The value MUST be one of the values shown in the first column of the following table. The characters represented by this data structure MUST correspond to the charactersexactly as they are shownin the second column of the following table. Even values not appearing in the following table have no character representation and are reserved.
ValueCharacters0x00mustUnderstand0x02Envelope0x04http://www.w3.org/2003/05/soap-envelope0x06http://www.w3.org/2005/08/addressing0x08Header0x0AAction0x0CTo0x0EBody0x10Algorithm0x12RelatesTo0x14http://www.w3.org/2005/08/addressing/anonymous0x16URI0x18Reference0x1AMessageID0x1CId0x1EIdentifier0x20http://schemas.xmlsoap.org/ws/2005/02/rm0x22Transforms0x24Transform0x26DigestMethod0x28DigestValue0x2AAddress0x2CReplyTo0x2ESequenceAcknowledgement0x30AcknowledgementRange0x32Upper0x34Lower0x36BufferRemaining0x38http://schemas.microsoft.com/ws/2006/05/rm0x3Ahttp://schemas.xmlsoap.org/ws/2005/02/rm/SequenceAcknowledgement0x3CSecurityTokenReference0x3ESequence0x40MessageNumber0x42http://www.w3.org/2000/09/xmldsig#0x44http://www.w3.org/2000/09/xmldsig#enveloped-signature0x46KeyInfo0x48http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd0x4Ahttp://www.w3.org/2001/04/xmlenc#0x4Chttp://schemas.xmlsoap.org/ws/2005/02/sc0x4EDerivedKeyToken0x50Nonce0x52Signature0x54SignedInfo0x56CanonicalizationMethod0x58SignatureMethod0x5ASignatureValue0x5CDataReference0x5EEncryptedData0x60EncryptionMethod0x62CipherData0x64CipherValue0x66http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd0x68Security0x6ATimestamp0x6CCreated0x6EExpires0x70Length0x72ReferenceList0x74ValueType0x76Type0x78EncryptedHeader0x7Ahttp://docs.oasis-open.org/wss/oasis-wss-wssecurity-secext-1.1.xsd0x7CRequestSecurityTokenResponseCollection0x7Ehttp://schemas.xmlsoap.org/ws/2005/02/trust0x80http://schemas.xmlsoap.org/ws/2005/02/trust#BinarySecret0x82http://schemas.microsoft.com/ws/2006/02/transactions0x84s0x86Fault0x88MustUnderstand0x8Arole0x8Crelay0x8ECode0x90Reason0x92Text0x94Node0x96Role0x98Detail0x9AValue0x9CSubcode0x9ENotUnderstood0xA0qname0xA20xA4From0xA6FaultTo0xA8EndpointReference0xAAPortType0xACServiceName0xAEPortName0xB0ReferenceProperties0xB2RelationshipType0xB4Reply0xB6a0xB8http://schemas.xmlsoap.org/ws/2006/02/addressingidentity0xBAIdentity0xBCSpn0xBEUpn0xC0Rsa0xC2Dns0xC4X509v3Certificate0xC6http://www.w3.org/2005/08/addressing/fault0xC8ReferenceParameters0xCAIsReferenceParameter0xCChttp://www.w3.org/2005/08/addressing/reply0xCEhttp://www.w3.org/2005/08/addressing/none0xD0Metadata0xD2http://schemas.xmlsoap.org/ws/2004/08/addressing0xD4http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous0xD6http://schemas.xmlsoap.org/ws/2004/08/addressing/fault0xD8http://schemas.xmlsoap.org/ws/2004/06/addressingex0xDARedirectTo0xDCVia0xDEhttp://www.w3.org/2001/10/xml-exc-c14n#0xE0PrefixList0xE2InclusiveNamespaces0xE4ec0xE6SecurityContextToken0xE8Generation0xEALabel0xECOffset0xEEProperties0xF0Cookie0xF2wsc0xF4http://schemas.xmlsoap.org/ws/2004/04/sc0xF6http://schemas.xmlsoap.org/ws/2004/04/security/sc/dk0xF8http://schemas.xmlsoap.org/ws/2004/04/security/sc/sct0xFAhttp://schemas.xmlsoap.org/ws/2004/04/security/trust/RST/SCT0xFChttp://schemas.xmlsoap.org/ws/2004/04/security/trust/RSTR/SCT0xFERenewNeeded0x100BadContextToken0x102c0x104http://schemas.xmlsoap.org/ws/2005/02/sc/dk0x106http://schemas.xmlsoap.org/ws/2005/02/sc/sct0x108http://schemas.xmlsoap.org/ws/2005/02/trust/RST/SCT0x10Ahttp://schemas.xmlsoap.org/ws/2005/02/trust/RSTR/SCT0x10Chttp://schemas.xmlsoap.org/ws/2005/02/trust/RST/SCT/Renew0x10Ehttp://schemas.xmlsoap.org/ws/2005/02/trust/RSTR/SCT/Renew0x110http://schemas.xmlsoap.org/ws/2005/02/trust/RST/SCT/Cancel0x112http://schemas.xmlsoap.org/ws/2005/02/trust/RSTR/SCT/Cancel0x114http://www.w3.org/2001/04/xmlenc#aes128-cbc0x116http://www.w3.org/2001/04/xmlenc#kw-aes1280x118http://www.w3.org/2001/04/xmlenc#aes192-cbc0x11Ahttp://www.w3.org/2001/04/xmlenc#kw-aes1920x11Chttp://www.w3.org/2001/04/xmlenc#aes256-cbc0x11Ehttp://www.w3.org/2001/04/xmlenc#kw-aes2560x120http://www.w3.org/2001/04/xmlenc#des-cbc0x122http://www.w3.org/2000/09/xmldsig#dsa-sha10x124http://www.w3.org/2001/10/xml-exc-c14n#WithComments0x126http://www.w3.org/2000/09/xmldsig#hmac-sha10x128http://www.w3.org/2001/04/xmldsig-more#hmac-sha2560x12Ahttp://schemas.xmlsoap.org/ws/2005/02/sc/dk/p_sha10x12Chttp://www.w3.org/2001/04/xmlenc#ripemd1600x12Ehttp://www.w3.org/2001/04/xmlenc#rsa-oaep-mgf1p0x130http://www.w3.org/2000/09/xmldsig#rsa-sha10x132http://www.w3.org/2001/04/xmldsig-more#rsa-sha2560x134http://www.w3.org/2001/04/xmlenc#rsa-1_50x136http://www.w3.org/2000/09/xmldsig#sha10x138http://www.w3.org/2001/04/xmlenc#sha2560x13Ahttp://www.w3.org/2001/04/xmlenc#sha5120x13Chttp://www.w3.org/2001/04/xmlenc#tripledes-cbc0x13Ehttp://www.w3.org/2001/04/xmlenc#kw-tripledes0x140http://schemas.xmlsoap.org/2005/02/trust/tlsnego#TLS_Wrap0x142http://schemas.xmlsoap.org/2005/02/trust/spnego#GSS_Wrap0x144http://schemas.microsoft.com/ws/2006/05/security0x146dnse0x148o0x14APassword0x14CPasswordText0x14EUsername0x150UsernameToken0x152BinarySecurityToken0x154EncodingType0x156KeyIdentifier0x158http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary0x15Ahttp://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#HexBinary0x15Chttp://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Text0x15Ehttp://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509SubjectKeyIdentifier0x160http://docs.oasis-open.org/wss/oasis-wss-kerberos-token-profile-1.1#GSS_Kerberosv5_AP_REQ0x162http://docs.oasis-open.org/wss/oasis-wss-kerberos-token-profile-1.1#GSS_Kerberosv5_AP_REQ15100x164http://docs.oasis-open.org/wss/oasis-wss-saml-token-profile-1.0#SAMLAssertionID0x166Assertion0x168urn:oasis:names:tc:SAML:1.0:assertion0x16Ahttp://docs.oasis-open.org/wss/oasis-wss-rel-token-profile-1.0.pdf#license0x16CFailedAuthentication0x16EInvalidSecurityToken0x170InvalidSecurity0x172k0x174SignatureConfirmation0x176TokenType0x178http://docs.oasis-open.org/wss/oasis-wss-soap-message-security-1.1#ThumbprintSHA10x17Ahttp://docs.oasis-open.org/wss/oasis-wss-soap-message-security-1.1#EncryptedKey0x17Chttp://docs.oasis-open.org/wss/oasis-wss-soap-message-security-1.1#EncryptedKeySHA10x17Ehttp://docs.oasis-open.org/wss/oasis-wss-saml-token-profile-1.1#SAMLV1.10x180http://docs.oasis-open.org/wss/oasis-wss-saml-token-profile-1.1#SAMLV2.00x182http://docs.oasis-open.org/wss/oasis-wss-saml-token-profile-1.1#SAMLID0x184AUTH-HASH0x186RequestSecurityTokenResponse0x188KeySize0x18ARequestedTokenReference0x18CAppliesTo0x18EAuthenticator0x190CombinedHash0x192BinaryExchange0x194Lifetime0x196RequestedSecurityToken0x198Entropy0x19ARequestedProofToken0x19CComputedKey0x19ERequestSecurityToken0x1A0RequestType0x1A2Context0x1A4BinarySecret0x1A6http://schemas.xmlsoap.org/ws/2005/02/trust/spnego0x1A8http://schemas.xmlsoap.org/ws/2005/02/trust/tlsnego0x1AAwst0x1AChttp://schemas.xmlsoap.org/ws/2004/04/trust0x1AEhttp://schemas.xmlsoap.org/ws/2004/04/security/trust/RST/Issue0x1B0http://schemas.xmlsoap.org/ws/2004/04/security/trust/RSTR/Issue0x1B2http://schemas.xmlsoap.org/ws/2004/04/security/trust/Issue0x1B4http://schemas.xmlsoap.org/ws/2004/04/security/trust/CK/PSHA10x1B6http://schemas.xmlsoap.org/ws/2004/04/security/trust/SymmetricKey0x1B8http://schemas.xmlsoap.org/ws/2004/04/security/trust/Nonce0x1BAKeyType0x1BChttp://schemas.xmlsoap.org/ws/2004/04/trust/SymmetricKey0x1BEhttp://schemas.xmlsoap.org/ws/2004/04/trust/PublicKey0x1C0Claims0x1C2InvalidRequest0x1C4RequestFailed0x1C6SignWith0x1C8EncryptWith0x1CAEncryptionAlgorithm0x1CCCanonicalizationAlgorithm0x1CEComputedKeyAlgorithm0x1D0UseKey0x1D2http://schemas.microsoft.com/net/2004/07/secext/WS-SPNego0x1D4http://schemas.microsoft.com/net/2004/07/secext/TLSNego0x1D6t0x1D8http://schemas.xmlsoap.org/ws/2005/02/trust/RST/Issue0x1DAhttp://schemas.xmlsoap.org/ws/2005/02/trust/RSTR/Issue0x1DChttp://schemas.xmlsoap.org/ws/2005/02/trust/Issue0x1DEhttp://schemas.xmlsoap.org/ws/2005/02/trust/SymmetricKey0x1E0http://schemas.xmlsoap.org/ws/2005/02/trust/CK/PSHA10x1E2http://schemas.xmlsoap.org/ws/2005/02/trust/Nonce0x1E4RenewTarget0x1E6CancelTarget0x1E8RequestedTokenCancelled0x1EARequestedAttachedReference0x1ECRequestedUnattachedReference0x1EEIssuedTokens0x1F0http://schemas.xmlsoap.org/ws/2005/02/trust/Renew0x1F2http://schemas.xmlsoap.org/ws/2005/02/trust/Cancel0x1F4http://schemas.xmlsoap.org/ws/2005/02/trust/PublicKey0x1F6Access0x1F8AccessDecision0x1FAAdvice0x1FCAssertionID0x1FEAssertionIDReference0x200Attribute0x202AttributeName0x204AttributeNamespace0x206AttributeStatement0x208AttributeValue0x20AAudience0x20CAudienceRestrictionCondition0x20EAuthenticationInstant0x210AuthenticationMethod0x212AuthenticationStatement0x214AuthorityBinding0x216AuthorityKind0x218AuthorizationDecisionStatement0x21ABinding0x21CCondition0x21EConditions0x220Decision0x222DoNotCacheCondition0x224Evidence0x226IssueInstant0x228Issuer0x22ALocation0x22CMajorVersion0x22EMinorVersion0x230NameIdentifier0x232Format0x234NameQualifier0x236Namespace0x238NotBefore0x23ANotOnOrAfter0x23Csaml0x23EStatement0x240Subject0x242SubjectConfirmation0x244SubjectConfirmationData0x246ConfirmationMethod0x248urn:oasis:names:tc:SAML:1.0:cm:holder-of-key0x24Aurn:oasis:names:tc:SAML:1.0:cm:sender-vouches0x24CSubjectLocality0x24EDNSAddress0x250IPAddress0x252SubjectStatement0x254urn:oasis:names:tc:SAML:1.0:am:unspecified0x256xmlns0x258Resource0x25AUserName0x25Curn:oasis:names:tc:SAML:1.1:nameid-format:WindowsDomainQualifiedName0x25EEmailName0x260urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress0x262u0x264ChannelInstance0x266http://schemas.microsoft.com/ws/2005/02/duplex0x268Encoding0x26AMimeType0x26CCarriedKeyName0x26ERecipient0x270EncryptedKey0x272KeyReference0x274e0x276http://www.w3.org/2001/04/xmlenc#Element0x278http://www.w3.org/2001/04/xmlenc#Content0x27AKeyName0x27CMgmtData0x27EKeyValue0x280RSAKeyValue0x282Modulus0x284Exponent0x286X509Data0x288X509IssuerSerial0x28AX509IssuerName0x28CX509SerialNumber0x28EX509Certificate0x290AckRequested0x292http://schemas.xmlsoap.org/ws/2005/02/rm/AckRequested0x294AcksTo0x296Accept0x298CreateSequence0x29Ahttp://schemas.xmlsoap.org/ws/2005/02/rm/CreateSequence0x29CCreateSequenceRefused0x29ECreateSequenceResponse0x2A0http://schemas.xmlsoap.org/ws/2005/02/rm/CreateSequenceResponse0x2A2FaultCode0x2A4InvalidAcknowledgement0x2A6LastMessage0x2A8http://schemas.xmlsoap.org/ws/2005/02/rm/LastMessage0x2AALastMessageNumberExceeded0x2ACMessageNumberRollover0x2AENack0x2B0netrm0x2B2Offer0x2B4r0x2B6SequenceFault0x2B8SequenceTerminated0x2BATerminateSequence0x2BChttp://schemas.xmlsoap.org/ws/2005/02/rm/TerminateSequence0x2BEUnknownSequence0x2C0http://schemas.microsoft.com/ws/2006/02/tx/oletx0x2C2oletx0x2C4OleTxTransaction0x2C6PropagationToken0x2C8http://schemas.xmlsoap.org/ws/2004/10/wscoor0x2CAwscoor0x2CCCreateCoordinationContext0x2CECreateCoordinationContextResponse0x2D0CoordinationContext0x2D2CurrentContext0x2D4CoordinationType0x2D6RegistrationService0x2D8Register0x2DARegisterResponse0x2DCProtocolIdentifier0x2DECoordinatorProtocolService0x2E0ParticipantProtocolService0x2E2http://schemas.xmlsoap.org/ws/2004/10/wscoor/CreateCoordinationContext0x2E4http://schemas.xmlsoap.org/ws/2004/10/wscoor/CreateCoordinationContextResponse0x2E6http://schemas.xmlsoap.org/ws/2004/10/wscoor/Register0x2E8http://schemas.xmlsoap.org/ws/2004/10/wscoor/RegisterResponse0x2EAhttp://schemas.xmlsoap.org/ws/2004/10/wscoor/fault0x2ECActivationCoordinatorPortType0x2EERegistrationCoordinatorPortType0x2F0InvalidState0x2F2InvalidProtocol0x2F4InvalidParameters0x2F6NoActivity0x2F8ContextRefused0x2FAAlreadyRegistered0x2FChttp://schemas.xmlsoap.org/ws/2004/10/wsat0x2FEwsat0x300http://schemas.xmlsoap.org/ws/2004/10/wsat/Completion0x302http://schemas.xmlsoap.org/ws/2004/10/wsat/Durable2PC0x304http://schemas.xmlsoap.org/ws/2004/10/wsat/Volatile2PC0x306Prepare0x308Prepared0x30AReadOnly0x30CCommit0x30ERollback0x310Committed0x312Aborted0x314Replay0x316http://schemas.xmlsoap.org/ws/2004/10/wsat/Commit0x318http://schemas.xmlsoap.org/ws/2004/10/wsat/Rollback0x31Ahttp://schemas.xmlsoap.org/ws/2004/10/wsat/Committed0x31Chttp://schemas.xmlsoap.org/ws/2004/10/wsat/Aborted0x31Ehttp://schemas.xmlsoap.org/ws/2004/10/wsat/Prepare0x320http://schemas.xmlsoap.org/ws/2004/10/wsat/Prepared0x322http://schemas.xmlsoap.org/ws/2004/10/wsat/ReadOnly0x324http://schemas.xmlsoap.org/ws/2004/10/wsat/Replay0x326http://schemas.xmlsoap.org/ws/2004/10/wsat/fault0x328CompletionCoordinatorPortType0x32ACompletionParticipantPortType0x32CCoordinatorPortType0x32EParticipantPortType0x330InconsistentInternalState0x332mstx0x334Enlistment0x336protocol0x338LocalTransactionId0x33AIsolationLevel0x33CIsolationFlags0x33EDescription0x340Loopback0x342RegisterInfo0x344ContextId0x346TokenId0x348AccessDenied0x34AInvalidPolicy0x34CCoordinatorRegistrationFailed0x34ETooManyEnlistments0x350Disabled0x352ActivityId0x354http://schemas.microsoft.com/2004/09/ServiceModel/Diagnostics0x356http://docs.oasis-open.org/wss/oasis-wss-kerberos-token-profile-1.1#Kerberosv5APREQSHA10x358http://schemas.xmlsoap.org/ws/2002/12/policy0x35AFloodMessage0x35CLinkUtility0x35EHops0x360http://schemas.microsoft.com/net/2006/05/peer/HopCount0x362PeerVia0x364http://schemas.microsoft.com/net/2006/05/peer0x366PeerFlooder0x368PeerTo0x36Ahttp://schemas.microsoft.com/ws/2005/05/routing0x36CPacketRoutable0x36Ehttp://schemas.microsoft.com/ws/2005/05/addressing/none0x370http://schemas.microsoft.com/ws/2005/05/envelope/none0x372http://www.w3.org/2001/XMLSchema-instance0x374http://www.w3.org/2001/XMLSchema0x376nil0x378type0x37Achar0x37Cboolean0x37Ebyte0x380unsignedByte0x382short0x384unsignedShort0x386int0x388unsignedInt0x38Along0x38CunsignedLong0x38Efloat0x390double0x392decimal0x394dateTime0x396string0x398base64Binary0x39AanyType0x39Cduration0x39Eguid0x3A0anyURI0x3A2QName0x3A4time0x3A6date0x3A8hexBinary0x3AAgYearMonth0x3ACgYear0x3AEgMonthDay0x3B0gDay0x3B2gMonth0x3B4integer0x3B6positiveInteger0x3B8negativeInteger0x3BAnonPositiveInteger0x3BCnonNegativeInteger0x3BEnormalizedString0x3C0ConnectionLimitReached0x3C2http://schemas.xmlsoap.org/soap/envelope/0x3C4actor0x3C6faultcode0x3C8faultstring0x3CAfaultactor0x3CCdetail3 Structure Examples
Following is an example of how to encode a SOAP document in the SOAP data structure format by using the HYPERLINK "[MC-NBFX].pdf" strings specified in section HYPERLINK \l "z9447dee042d5458b902884536a515387" 2. White space (such as spaces, tab characters, and carriage returns) improves readability, but is not part of the encoded version of the document.
action
0
The following table divides the same SOAP document into HYPERLINK "[MC-NBFX].pdf" records. Each row in the table represents one record. The first column identifies the text, or record content. The second column identifies the type of SOAP record. The third column shows the record in its encoded form. For information on the structure of each record, see HYPERLINK "[MC-NBFX].pdf" [MC-NBFX].
String to encodeRecord typeEncoded bytes (hex)DictionaryXmlnsAttribute0B 01 73 04PrefixDictionaryElementS56 08PrefixDictionaryAttributeS1E 00 82actionChars8TextWithEndElement99 06 61 63 74 69 6F 6EEndElement01PrefixDictionaryElementS56 0EShortElement40 09 49 6E 76 65 6E 74 6F 72 790ZeroTextWithEndElement81EndElement01EndElement01Several of the records contain HYPERLINK \l "z9268bb1194bf451a8827955495e99c7b" DictionaryString entries, as specified in section HYPERLINK \l "z9447dee042d5458b902884536a515387" 2. The bytes that map to DictionaryString entries are highlighted in bold in records 1 through 6, and in record 9.
Finally, the following diagram shows the SOAP document as a byte stream.
56 02 0B 01 61 06 0B 01 73 04 56 08 44 0A 1E 00
82 99 06 61 63 74 69 6F 6E 01 56 0E 40 09 49 6E
76 65 6E 74 6F 72 79 81 01 01
4 Security Considerations
For information on security considerations, see HYPERLINK "[MC-NBFX].pdf" [MC-NBFX] section 1.3.
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 specificat i o n i s a p p l i c a b l e t o t h e f o l l o w i n g M i c r o s o f t p r o d u c t s o r s u p p l e m e n t a l s o f t w a r e . R e f e r e n c e s t o p r o d u c t v e r s i o n s i n c l u d e r e l e a s e d s e r v i c e p a c k s :
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 amework 4.5
Exceptions, if any, are noted below. If a service pack or Quick Fix Engineering (QFE) number appears with the product version, behavior 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 "z7652076433f74dc6aacbd67f2ea29bbe" Applicability 6
C
HYPERLINK \l "za63cc7a1c5f5495b802ffa5ef9006de5" Change tracking 28
HYPERLINK \l "z9447dee042d5458b902884536a515387" Common data types and fields 7
D
HYPERLINK \l "z9447dee042d5458b902884536a515387" Data types and fields - common 7
Details
HYPERLINK \l "z9447dee042d5458b902884536a515387" common data types and fields 7
HYPERLINK \l "z9268bb1194bf451a8827955495e99c7b" DictionaryString structure 7
HYPERLINK \l "z9268bb1194bf451a8827955495e99c7b" DictionaryString structure 7
E
HYPERLINK \l "z38195b75e82a4d17a358b79cec9d1f77" Example 24
F
HYPERLINK \l "zc95d984554c540789a3a7d239e5a90fb" Fields - vendor-extensible 6
G
HYPERLINK \l "z7fe31cc96cc64b83a4de24788d17f627" Glossary 5
I
HYPERLINK \l "z0495bec38e674cdc8debf157bb486f5f" Informative references 6
HYPERLINK \l "z7837d57a18e64c5f8ea5d80127b64148" Introduction 5
L
HYPERLINK \l "z948a0572cca948849980beb3db71e5dd" Localization 6
N
HYPERLINK \l "zae7fd8c18e6242ae80ae8121ab8c0322" Normative references 6
O
HYPERLINK \l "zabcf962d4fb74c3195a216ca7b9517f0" Overview (synopsis) 6
P
HYPERLINK \l "z27553681b1a14a32882444a2bda31511" Product behavior 27
R
References
HYPERLINK \l "z0495bec38e674cdc8debf157bb486f5f" informative 6
HYPERLINK \l "zae7fd8c18e6242ae80ae8121ab8c0322" normative 6
HYPERLINK \l "z111f2cf467c9477ea812ef88a5f50ab1" Relationship to protocols and other structures 6
S
HYPERLINK \l "z5ecc702fca464c4e8176521523e31a93" Security considerations 26
Structures
HYPERLINK \l "z9268bb1194bf451a8827955495e99c7b" DictionaryString 7
HYPERLINK \l "z9447dee042d5458b902884536a515387" overview 7
T
HYPERLINK \l "za63cc7a1c5f5495b802ffa5ef9006de5" Tracking changes 28
V
HYPERLINK \l "zc95d984554c540789a3a7d239e5a90fb" Vendor-extensible fields 6
HYPERLINK \l "z948a0572cca948849980beb3db71e5dd" Versioning 6
PAGE
PAGE
PAGE 2/ NUMPAGES 2
[MC-NBFS] v20131025
.NET Binary Format: SOAP Data Structure
Copyright 2013 Microsoft Corporation.
Release: Friday, October 25, 2013
6 L W , u }
P Q b c L M t u % ; $ % O P E F ] ^ d e % & k l hpu hr hr 5j h! hr 0J U
hr 0J j hr U
hr 0Jh hr R 5 6 L u % $ $If gd