XML Protocol (XMLP)

XML Protocol (XMLP) provides simple protocols that can be ubiquitously deployed and easily programmed through scripting languages, XML tools, interactive Web development tools, etc. The goal is a layered system which will directly meet the needs of applications with simple interfaces (e.g. getStockQuote, validateCreditCard), and which can be incrementally extended to provide the security, scalability, and robustness required for more complex application interfaces.

Specifically, the XML Protocol Working Group is chartered to design the following four components:

1. An envelope for encapsulating XML data to be transferred in an interoperable manner that allows for distributed extensibility. 
2. A convention for the content of the envelope when used for RPC (Remote Procedure Call) applications. The protocol aspects of this should be coordinated closely with the IETF and make an effort to leverage any work they are doing, see below for details. 
3. A mechanism for serializing data representing non-syntactic data models such as object graphs and directed labeled graphs, based on the data types of XML Schema. 
4. A mechanism for using HTTP transport in the context of an XML Protocol. This does not mean that HTTP is the only transport mechanism that can be used for the technologies developed, nor that support for HTTP transport is mandatory. This component merely addresses the fact that HTTP transport is expected to be widely used, and so should be addressed by this Working Group. There will be coordination with the Internet Engineering Task Force (IETF), see Blocks Extensible Exchange Protocol (BEEP) (new window). 

Furthermore, the following two general requirements must be met by the work produced by this Working Group:

1. The envelope and the serialization mechanisms developed by the Working Group may not preclude any programming model nor assume any particular mode of communication between peers. 
2. Focus must be put on simplicity and modularity and must support the kind of extensibility actually seen on the Web. In particular, it must support distributed extensibility where the communicating parties do not have a priori knowledge of each other. 

The Working Group shall start by developing a requirements document, and then evaluate the technical solutions proposed in the SOAP/1.1 submission against these requirements. If in this process the Working Group finds solutions that are agreed to be improvements over solutions suggested by SOAP 1.1, those improved solutions should be used.

Organization: W3C

More information: XMLP page on the W3C Web site (new window)

Web Services and Service-Oriented Architectures Online articles > Consulting Mentoring Speaking Suggested programs Stencils for the Savvy Manager's Guide Links Mail list Privacy policy Sitemap Contact

Web Services articles > XML standards and vocabularies Application server articles Database concepts and standards Object database articles Relational database articles Object-relational mapping articles XML database articles XML middleware articles Article Sponsorship Reprint policy

Web Services definition Service-oriented architecture (SOA) definition Web Services explained Web Services specifications > Prior Service-Oriented Architecture specifications Organizations Article suggestions

Models and metamodels Repository Messaging > Service Security and authorization Federated network identity User interface Workflow Application servers Object programming languages

Messaging components Messaging specifications > Transaction specifications

Representational State Transfer (REST) SOAP Message Service Specification (MSS) RosettaNet Business Message Asynchronous Application Service Protocol (ASAP) for SOAP XML Protocol (XMLP) > Web Distributed Data Exchange (WDDX) Web Services Addressing (WS-Addressing) Web Services Eventing (WS-Eventing) Web Services Notification (WSN) Web Services Reliability (WS-Reliability) Web Services Reliable Messaging (WS-ReliableMessaging)

Blocks Extensible Exchange Protocol (BEEP)

Related books at Amazon.com

	ISO/TS 24530-1:2006, Traffic and Travel Information (TTI) - TTI via Transport Protocol Experts Group (TPEG) Extensible Markup Language (XML) - Part 1: Introduction, common data types and tpegML by ISO/TC 204 Publisher: Multiple. Distributed through American National Standards Institute (ANSI) Publication Date: August 2007
	ACCESS360/XRPM TO DEVELOP XML-BASED PROVISIONING PROTOCOL.(Technology Information): An article from: Computer Protocols Publisher: Worldwide Videotex Publication Date: June 2001
	NETWORK PROTOCOL FIREWALLS/ROUTERS NOT ADEQUATE FOR XML.(ZapThink's report): An article from: Computer Protocols Publisher: Worldwide Videotex Publication Date: September 2002
	Enhancing Network Communication in NPSNET-V Virtual Environments Using XML-Described Dynamic Behavior (DBP) Protocols Editorial Review: This is a NAVAL POSTGRADUATE SCHOOL MONTEREY CA report procured by the Pentagon and made available for public release. It has been reproduced in the best form available to the Pentagon. It is not spiral-bound, but rather assembled with Velobinding in a soft, white linen cover. The Storming Media report number is A843793. The abstract provided by the Pentagon follows: This thes...
	ISO/TS 24530-4:2006, Traffic and Travel Information (TTI) - TTI via Transport Protocol Experts Group (TPEG) Extensible Markup Language (XML) - Part 4: tpeg-ptiML by ISO/TC 204 Publisher: Multiple. Distributed through American National Standards Institute (ANSI) Publication Date: August 2007

More related books: Search Amazon.com for XMLP

Copyright © 2000-2008 Barry & Associates, Inc. All Rights Reserved.
You can use this material for your work or classes. Click here for our reprint policy.
www.service-architecture.com