Microsoft Technology Licensing, LLC

Natasha Harish Jethanandani

Stefan Harrington Pharies

Douglas M Purdy

Sowmyanarayanan K Srinivasan

Erik B Christensen

Donald F Box

Sowmy Srinivasan

Kenneth David Wolf

Gopala Krishna R Kakivaya

David Wortendyke

Tirunelveli R Vishwanath

Stephen Jared Maine

Michael James Coulson

Michael Marucheck

Yann Christensen

Michael Steven Vernal

Stephen T Swartz

Ryan Thomas Sturgell

Evgeny Osovetsky

Elena A Kharitidi

Krishnan R Rangachari

Christopher G Kaler

Steven E Lucco

Stephen James Millet

Giovanni Moises Della-Libera

Bradford H Lovering

James Ernest Johnson

Lance Olson

Richard Douglas Hill

Michael John Hillberg

Geoffrey M Kizer

Stefan R Batres

Jeffrey C Schlimmer

Umesh Madan

John David Doty

Craig Andrew Critchley

Uday Sooryakant Hegde

Charles P Jazdzewski

Vijay Gajjala

Robert A Relyea

Elliot Lee Waingold

Krishnan Srinivasan

Tomasz Janczuk

Geary L Eppley

Matthew Thomas Tavis

David Edwin Levin

Shy Cohen

Martin James Gudgin

Max A Feingold

Richard Dievendorff

David Owen Driver

Saurab Nog

Aaron Stern

Siddhartha Puri

Douglas A Walter

Jesus Ruiz-Scougall

Anastasios Kasiolas

Kapil Gupta

Vipul A Modi

Alexander Martin DeJarnatt

Scott Christopher Seely

Jonathan T Wheeler

Mohammad Makarechian

Chaitanya Dutt Upadhyay

Michael Thomas Dice

Yaniv Pessach

Mauro Ottaviani

Erin Honeycutt

Alfred M Lee, Iv

Eugene Shvets

Eugene Osovetsky

Brian Faris Chapman

Yasser Shohoud

Joel David West

Vaithiakingam B Balayoghan

Anand Rjagopalan

Mohamed-Hany Essam Ramadan

Serge Sverdlov

Vaithialingam B Balayogan

Sowmy K Srinivasan

The present invention extends to using Simple Object Access Protocol ('SOAP') to exchange typed objects, such as, for example, parameters for invoking methods. A computer system accesses typed object parameters corresponding to a typed object. The typed object is annotated with one or more message contract attributes of a message contract model defining a mapping between typed object parameters and corresponding SOAP elements. The computer system utilizes the message contract attributes to map the typed object parameters into a SOAP element and inserts the SOAP element into a SOAP envelope. A receiving computer system accessing the SOAP element and utilizes the message contract attributes to map the SOAP element back into the typed object parameters.

Flexibly transferring typed application data

Encoding and/or decoding of messages. On the encoding end, a composite encoder encodes message from an internal format that is used by internal system components into an external format. However, the composite encoder may encode the outgoing messages into different external formats on a per-message basis. For incoming message, a composite decoder decodes incoming messages from any one of a plurality of external formats into the internal format also on a per-message basis. A per-message report mechanism permits internal system components and the encoding/decoding components to communicate information regarding the encoding or decoding on a per message basis. This permits a higher level of collaboration and complexity in the encoding and decoding process.

Encoding/decoding while allowing varying message formats per message

Determining compatibility of data structures. A method may be practiced in a computing environment. The method includes accessing a first type defined in a mark-up object. The first type includes a first structure including a first plurality of fields. A second type defined in a mark-up object is accessed. The second type includes a second structure including a second plurality of fields. The first structure and the second structure are compared. Based on the comparison, a determination is made that the first type is compatible with the second type.

Data description language for record based systems

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

Methods, systems, and computer program products for converting an object of one type to an object of another type that allow for the runtime operation of the conversion process to be altered or customized. The conversion may occur within an extensible serialization engine that serializes, deserializes, and transforms objects of various types. The runtime operation of the serialization engine is altered by one or more extension routines that implement the desired customizations or extensions, without requiring replacement of other existing routines. Based on type information, identified for an initial object, the object is converted to an intermediate representation which permits runtime modification, including modification of object names, object types, and object data. The intermediate representation of the initial object is modified in accordance with extension routines that alter the runtime operation of the serialization engine, and the intermediate representation is converted to a final object and type.

Type bridges

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 versionable schema is both backward-compatible and forward-compatible. Such a schema is able to receive data expected by multiple versions of the schema; tolerates the absence of optional data, in accordance with other versions, and accept wildcard data in accordance with still further versions. Thus, a message or message may be validated by the versionable schema.

Type evolution

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

Seattle, WA, United States of America

Natasha Harish Jethanandani