[MS-OMWWH]:
Office Mobile Word Web Handler Protocol
Intellectual Property Rights Notice for Open Specifications Documentation
§ Technical Documentation. Microsoft publishes Open Specifications documentation (“this documentation”) for protocols, file formats, data portability, computer languages, and standards support. Additionally, overview documents cover inter-protocol relationships and interactions.
§ 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 can make copies of it in order to develop implementations of the technologies that are described in this documentation and can distribute portions of it in your implementations that use these technologies or in your documentation as necessary to properly document the implementation. You can also distribute in your implementation, with or without modification, any schemas, IDLs, or code samples that are included in the documentation. This permission also applies to any documents that are referenced in the Open Specifications documentation.
§ No Trade Secrets. Microsoft does not claim any trade secret rights in this documentation.
§ Patents. Microsoft has patents that might cover your implementations of the technologies described in the Open Specifications documentation. Neither this notice nor Microsoft's delivery of this documentation grants any licenses under those patents or any other Microsoft patents. However, a given Open Specifications document might be covered by the Microsoft Open Specifications Promise or the Microsoft Community Promise. If you would prefer a written license, or if the technologies described in this documentation are not covered by the Open Specifications Promise or Community Promise, as applicable, patent licenses are available by contacting .
§ License Programs. To see all of the protocols in scope under a specific license program and the associated patents, visit the Patent Map.
§ Trademarks. The names of companies and products contained in this documentation might 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 www.microsoft.com/trademarks.
§ Fictitious Names. The example companies, organizations, products, domain names, email addresses, logos, people, places, and events that are 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 as specifically described above, whether by implication, estoppel, or otherwise.
Tools. The Open Specifications documentation does 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 documents are intended for use in conjunction with publicly available standards specifications and network programming art and, as such, assume that the reader either is familiar with the aforementioned material or has immediate access to it.
Support. For questions and support, please contact .
Revision Summary
Date / Revision History / Revision Class / 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 / Major / Significantly changed the technical content.
9/27/2010 / 1.05 / None / No changes to the meaning, language, or formatting of the technical content.
11/15/2010 / 1.05 / None / No changes to the meaning, language, or formatting of the technical content.
12/17/2010 / 1.05 / None / No changes to the meaning, language, or formatting of the technical content.
3/18/2011 / 1.05 / None / No changes to the meaning, language, or formatting of the technical content.
6/10/2011 / 1.05 / None / No changes to the meaning, language, or formatting of the technical content.
1/20/2012 / 1.6 / Minor / Clarified the meaning of the technical content.
4/11/2012 / 1.6 / None / No changes to the meaning, language, or formatting of the technical content.
7/16/2012 / 1.7 / Minor / Clarified the meaning of the technical content.
10/8/2012 / 1.7 / None / No changes to the meaning, language, or formatting of the technical content.
2/11/2013 / 1.7 / None / No changes to the meaning, language, or formatting of the technical content.
7/30/2013 / 1.7 / None / No changes to the meaning, language, or formatting of the technical content.
11/18/2013 / 1.7 / None / No changes to the meaning, language, or formatting of the technical content.
2/10/2014 / 1.7 / None / No changes to the meaning, language, or formatting of the technical content.
4/30/2014 / 1.8 / Minor / Clarified the meaning of the technical content.
7/31/2014 / 1.8 / None / No changes to the meaning, language, or formatting of the technical content.
10/30/2014 / 1.8 / None / No changes to the meaning, language, or formatting of the technical content.
6/23/2016 / 1.8 / None / No changes to the meaning, language, or formatting of the technical content.
9/14/2016 / 1.8 / None / No changes to the meaning, language, or formatting of the technical content.
9/19/2017 / 1.9 / Minor / Clarified the meaning of the technical content.
Table of Contents
1 Introduction 6
1.1 Glossary 6
1.2 References 7
1.2.1 Normative References 7
1.2.2 Informative References 7
1.3 Overview 8
1.4 Relationship to Other Protocols 8
1.5 Prerequisites/Preconditions 8
1.6 Applicability Statement 9
1.7 Versioning and Capability Negotiation 9
1.8 Vendor-Extensible Fields 9
1.9 Standards Assignments 9
2 Messages 10
2.1 Transport 10
2.2 Common Message Syntax 10
2.2.1 Namespaces 10
2.2.2 Messages 10
2.2.3 Elements 10
2.2.4 Complex Types 10
2.2.5 Simple Types 10
2.2.6 Attributes 10
2.2.7 Groups 10
2.2.8 Attribute Groups 10
2.2.9 Common Data Structures 11
3 Protocol Details 12
3.1 Server Details 12
3.1.1 Abstract Data Model 12
3.1.2 Timers 12
3.1.3 Initialization 12
3.1.4 Message Processing Events and Sequencing Rules 13
3.1.4.1 MobileDocHandler 13
3.1.4.1.1 GetMobileDoc 13
3.1.4.1.1.1 Return Values 13
3.1.4.1.1.2 Messages 14
3.1.4.1.1.3 Elements 14
3.1.4.1.1.3.1 mobileDoc 14
3.1.4.1.1.4 Complex Types 14
3.1.4.1.1.4.1 CT_PageSet 15
3.1.4.1.1.4.2 CT_Document 15
3.1.4.1.1.4.3 CT_PageXml 16
3.1.4.1.1.4.4 CT_PageImage 16
3.1.4.1.1.4.5 CT_DocData 17
3.1.4.1.1.4.6 CT_Ignorable 17
3.1.4.1.1.4.7 CT_MobileDoc 18
3.1.4.1.1.5 Simple Types 18
3.1.4.1.1.6 Attributes 18
3.1.4.1.1.7 Groups 18
3.1.4.1.1.8 Attribute Groups 18
3.1.4.1.2 GetLatestDocumentVersion 19
3.1.4.1.2.1 Return Values 19
3.1.4.1.3 PrepareThumbnail 19
3.1.4.1.3.1 Return Values 19
3.1.4.2 MobilePageHandler 20
3.1.4.2.1 GetMobilePageImage 20
3.1.4.2.1.1 Return Values 21
3.1.4.2.2 GetMobilePageXml 21
3.1.4.2.2.1 Return Values 21
3.1.4.2.2.2 Messages 22
3.1.4.2.2.3 Elements 22
3.1.4.2.2.3.1 Pages 22
3.1.4.2.2.4 Complex Types 22
3.1.4.2.2.4.1 CT_TextLine 23
3.1.4.2.2.4.2 CT_LinkTargetInternal 24
3.1.4.2.2.4.3 CT_Link 25
3.1.4.2.2.4.4 CT_Paragraph 26
3.1.4.2.2.4.5 CT_Image 27
3.1.4.2.2.4.6 CT_EndNote 27
3.1.4.2.2.4.7 CT_FootNote 28
3.1.4.2.2.4.8 CT_TableOfContents 28
3.1.4.2.2.4.9 CT_TextBox 28
3.1.4.2.2.4.10 CT_List 29
3.1.4.2.2.4.11 CT_TableDataCell 29
3.1.4.2.2.4.12 CT_TableHeaderCell 30
3.1.4.2.2.4.13 CT_TableRow 30
3.1.4.2.2.4.14 CT_Table 31
3.1.4.2.2.4.15 CT_Page 31
3.1.4.2.2.4.16 CT_Pages 32
3.1.4.2.2.5 Simple Types 32
3.1.4.2.2.5.1 ST_ImageType 33
3.1.4.2.2.5.2 ST_ParagraphType 33
3.1.4.2.2.5.3 ST_TextLineType 33
3.1.4.2.2.6 Attributes 34
3.1.4.2.3 GetThumbnail 34
3.1.4.2.3.1 Return Values 34
3.1.5 Timer Events 35
3.1.6 Other Local Events 35
4 Protocol Examples 36
4.1 Document Information 36
4.2 Page Image 36
4.3 Page Information 37
5 Security 43
5.1 Security Considerations for Implementers 43
5.2 Index of Security Parameters 43
6 Appendix A: Full WSDL 44
7 Appendix B: Product Behavior 45
8 Change Tracking 46
9 Index 47
1 Introduction
The Office Mobile Word Web Handler protocol retrieves document display information from the protocol server for a document that is optimized for viewing on a mobile device.
Sections 1.5, 1.8, 1.9, 2, and 3 of this specification are normative. All other sections and examples in this specification are informative.
1.1 Glossary
This document uses the following terms:
absolute URL: The full Internet address of a page or other World Wide Web resource. The absolute URL includes a protocol, such as "http," a network location, and an optional path and file name — for example, http://www.treyresearch.net/.
document: An object in a content database such as a file, folder, list, or site. Each object is identified by a URI.
endnote: A note that appears at the end of a section or document and that is referenced by text in the main body of the document. An endnote consists of two linked parts, a reference mark within the main body of text and the corresponding text of the note.
footnote: A note that appears at the end of a page, section, chapter, or publication. It explains, comments on, or provides references for text in the main body of a document. A footnote consists of two linked parts, a reference mark within the main body of the document and the corresponding text of the note.
front-end web server: A server that hosts webpages, performs processing tasks, and accepts requests from protocol clients and sends them to the appropriate back-end server for further processing.
header row: A row in a table, typically the first row, that contains labels for columns in the table.
HTTP GET: An HTTP method for retrieving a resource, as described in [RFC2616].
hyperlink: A relationship between two anchors, as described in [RFC1866].
Hypertext Transfer Protocol (HTTP): An application-level protocol for distributed, collaborative, hypermedia information systems (text, graphic images, sound, video, and other multimedia files) on the World Wide Web.
Hypertext Transfer Protocol Secure (HTTPS): An extension of HTTP that securely encrypts and decrypts web page requests. In some older protocols, "Hypertext Transfer Protocol over Secure Sockets Layer" is still used (Secure Sockets Layer has been deprecated). For more information, see [SSL3] and [RFC5246].
point: A unit of measurement for fonts and spacing. A point is equal to 1/72 of an inch.
Secure Sockets Layer (SSL): A security protocol that supports confidentiality and integrity of messages in client and server applications that communicate over open networks. SSL uses two keys to encrypt data-a public key known to everyone and a private or secret key known only to the recipient of the message. SSL supports server and, optionally, client authentication using X.509 certificates. For more information, see [X509]. The SSL protocol is precursor to Transport Layer Security (TLS). The TLS version 1.0 specification is based on SSL version 3.0 [SSL3].
site: A group of related pages and data within a SharePoint site collection. The structure and content of a site is based on a site definition. Also referred to as SharePoint site and web site.
SOAP: A lightweight protocol for exchanging structured information in a decentralized, distributed environment. SOAP uses XML technologies to define an extensible messaging framework, which provides a message construct that can be exchanged over a variety of underlying protocols. The framework has been designed to be independent of any particular programming model and other implementation-specific semantics. SOAP 1.2 supersedes SOAP 1.1. See [SOAP1.2-1/2003].
Uniform Resource Identifier (URI): A string that identifies a resource. The URI is an addressing mechanism defined in Internet Engineering Task Force (IETF) Uniform Resource Identifier (URI): Generic Syntax [RFC3986].
Uniform Resource Locator (URL): A string of characters in a standardized format that identifies a document or resource on the World Wide Web. The format is as specified in [RFC1738].
XML namespace: A collection of names that is used to identify elements, types, and attributes in XML documents identified in a URI reference [RFC3986]. A combination of XML namespace and local name allows XML documents to use elements, types, and attributes that have the same names but come from different sources. For more information, see [XMLNS-2ED].
MAY, SHOULD, MUST, SHOULD NOT, MUST NOT: These terms (in all caps) are used as defined in [RFC2119]. All statements of optional behavior use either MAY, SHOULD, or SHOULD NOT.
1.2 References
Links to a document in the Microsoft Open Specifications library point to the correct section in the most recently published version of the referenced document. However, because individual documents in the library are not updated at the same time, the section numbers in the documents may not match. You can confirm the correct section numbering by checking the Errata.
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 . We will assist you in finding the relevant information.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997, http://www.rfc-editor.org/rfc/rfc2119.txt
[RFC2616] Fielding, R., Gettys, J., Mogul, J., et al., "Hypertext Transfer Protocol -- HTTP/1.1", RFC 2616, June 1999, http://www.rfc-editor.org/rfc/rfc2616.txt
[XMLNS] Bray, T., Hollander, D., Layman, A., et al., Eds., "Namespaces in XML 1.0 (Third Edition)", W3C Recommendation, December 2009, http://www.w3.org/TR/2009/REC-xml-names-20091208/
[XMLSCHEMA1] Thompson, H., Beech, D., Maloney, M., and Mendelsohn, N., Eds., "XML Schema Part 1: Structures", W3C Recommendation, May 2001, http://www.w3.org/TR/2001/REC-xmlschema-1-20010502/
[XMLSCHEMA2] Biron, P.V., Ed. and Malhotra, A., Ed., "XML Schema Part 2: Datatypes", W3C Recommendation, May 2001, http://www.w3.org/TR/2001/REC-xmlschema-2-20010502/
1.2.2 Informative References
[RFC2818] Rescorla, E., "HTTP Over TLS", RFC 2818, May 2000, http://www.rfc-editor.org/rfc/rfc2818.txt
[SOAP1.1] Box, D., Ehnebuske, D., Kakivaya, G., et al., "Simple Object Access Protocol (SOAP) 1.1", W3C Note, May 2000, http://www.w3.org/TR/2000/NOTE-SOAP-20000508/
[SOAP1.2/1] Gudgin, M., Hadley, M., Mendelsohn, N., Moreau, J., and Nielsen, H.F., "SOAP Version 1.2 Part 1: Messaging Framework", W3C Recommendation, June 2003, http://www.w3.org/TR/2003/REC-soap12-part1-20030624