Microsoft Technology Licensing, LLC

Yasser Shohoud

Christopher G Kaler

Erik B Christensen

Kenneth David Wolf

Stephen James Millet

David Wortendyke

Giovanni Moises Della-Libera

James Ernest Johnson

Tirunelveli R Vishwanath

Lance Olson

Richard Douglas Hill

Umesh Madan

Stefan R Batres

Michael James Coulson

John David Doty

Stefan Harrington Pharies

Craig Andrew Critchley

Vijay Gajjala

Uday Sooryakant Hegde

Michael Marucheck

Krishnan Srinivasan

Elliot Lee Waingold

Geary L Eppley

Matthew Thomas Tavis

Tomasz Janczuk

Michael Steven Vernal

Stephen T Swartz

David Edwin Levin

Shy Cohen

Max A Feingold

Richard Dievendorff

Douglas M Purdy

Natasha Harish Jethanandani

David Owen Driver

Siddhartha Puri

Saurab Nog

Aaron Stern

Jesus Ruiz-Scougall

Anastasios Kasiolas

Douglas A Walter

Kapil Gupta

Vipul A Modi

Ryan Thomas Sturgell

Sowmyanarayanan K Srinivasan

Scott Christopher Seely

Evgeny Osovetsky

Jonathan T Wheeler

Mohammad Makarechian

Alexander Martin DeJarnatt

Mauro Ottaviani

Elena A Kharitidi

Erin Honeycutt

Chaitanya Dutt Upadhyay

Michael Thomas Dice

Yaniv Pessach

Eugene Shvets

Alfred M Lee, Iv

John Koropchak

Anand Rjagopalan

Mohamed-Hany Essam Ramadan

Serge Sverdlov

Vaithialingam B Balayogan

XML schema types can be identified and compared for equivalence so as to avoid unnecessary and undesirable creation of multiple classes for equivalent schema types. XML schema types having the same name are identified and normalized according to a unified system for representing schema types. The step for normalizing schema types can include any writing and/or rewriting at least a portion of the schema types into a common unifying format so that they can be compared. Once the schema types have been normalized, they are then compared for equivalence. One technique for comparing the schema types is to create and compare hash numbers of all or only selected portions of the normalized schema types. Equivalent schema types can then be indexed to share a single class, thereby avoiding the creation of multiple classes for equivalent schema types.

Determining XML schema type equivalence

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

Sammamish, WA, United States of America

Yasser Shohoud