Microsoft Technology Licensing, LLC

Sowmyanarayanan K Srinivasan

Natasha Harish Jethanandani

Stefan Harrington Pharies

Douglas M Purdy

Erik B Christensen

Gopala Krishna R Kakivaya

Donald F Box

Stephen T Swartz

Christopher G Kaler

Kenneth David Wolf

Steven E Lucco

Stephen James Millet

Giovanni Moises Della-Libera

David Wortendyke

Bradford H Lovering

James Ernest Johnson

Tirunelveli R Vishwanath

Lance Olson

Richard Douglas Hill

Umesh Madan

Stefan R Batres

Stephen Jared Maine

Michael James Coulson

John David Doty

Craig Andrew Critchley

Vijay Gajjala

Michael Marucheck

Uday Sooryakant Hegde

Krishnan Srinivasan

Elliot Lee Waingold

Geary L Eppley

Matthew Thomas Tavis

Tomasz Janczuk

Michael Steven Vernal

David Edwin Levin

Shy Cohen

Max A Feingold

Richard Dievendorff

David Owen Driver

Aaron Stern

Siddhartha Puri

Saurab Nog

Jesus Ruiz-Scougall

Anastasios Kasiolas

Douglas A Walter

Kapil Gupta

Vipul A Modi

Ryan Thomas Sturgell

Scott Christopher Seely

Jonathan T Wheeler

Mohammad Makarechian

Evgeny Osovetsky

Alexander Martin DeJarnatt

Michael Thomas Dice

Yaniv Pessach

Mauro Ottaviani

Erin Honeycutt

Chaitanya Dutt Upadhyay

Eugene Shvets

Alfred M Lee, Iv

Eugene Osovetsky

Yasser Shohoud

Krishnan R Rangachari

Anand Rjagopalan

Mohamed-Hany Essam Ramadan

Serge Sverdlov

Vaithialingam B Balayogan

Converting data to an appropriate format for use with a service. An example method is illustrated where a message including data expressed using dynamic language data expressions is received. The dynamic language data expressions include a tree structure organization for the data. The data expressed using dynamic language data expressions is expressed in an XML data structure. The XML data structure preserves the original tree structure organization for the data.

Complete mapping between the XML infoset and dynamic language data expressions

Serialization and deserialization using data contracts. The data contract specifies data types that are serialized and deserialized for data objects that are associated with the data contract. During serialization, the data contract associated with the data object is identified. Then, the data fields that correspond to those specified data field types are extracted from the data object and serialized into a serialization format. During deserialization, the serialization mechanism receives a serialized data structure having a particular serialization format. A data contract is then identified as being associated with the serialized data structure. After deserialization of the serialized data structure into abstract data, a corresponding data object is populated with data fields that correspond only with those data field types specified in the data contract. Accordingly, data abstraction is enabled while serializing and deserializing.

Data abstraction based serialization

The transfer of raw data from a source data structure to a target data structure that represent the same item. During the data transfer, if there is a given field in the target data structure that does not correspond to a field supplied by the source data structure, the transfer mechanism determines whether or not it is mandatory that the source data structure supply the field. If it is mandatory, the transfer fails. Otherwise, the transfer continues. If there is field of the source data structure that does not correspond to a field of the target data structure, the transfer mechanism determines whether or not it is mandatory that the target data structure have the field. If it is mandatory, the transfer fails. Otherwise, the corresponding data may be provided to a residual field of the target data structure dedicated for unknown data.

Mechanisms for transferring raw data from one data structure to another representing the same item

A web services namespace pertains to an infrastructure for enabling creation of a wide variety of applications. The infrastructure provides a foundation for building message-based applications of various scale and complexity. The infrastructure or framework provides APIs for basic messaging, secure messaging, reliable messaging and transacted messaging. In some embodiments, the associated APIs are factored into a hierarchy of namespaces in a manner that balances utility, usability, extensibility and versionability.

Interface infrastructure for creating and interacting with web services

Growing community of inventors

Redmond, WA, United States of America

Sowmyanarayanan K Srinivasan