Chapter 3 from the book XSLT 2.0 Web Development.
The first part of the chapter deals with markup constructs commonly used in page documents, including headings,
paragraphs and paragraph-like elements, links, images and other non-XML objects,
tables, and forms.
Then we will analyze the master document to find out what data it needs to store and
what is the best XML representation for this data. The last section
presents complete summary examples of a page document, a master document, and a Schematron schema to validate them.
Service Oriented Mass Customization (SOMC) asks us to stop thinking of an application as an isolated island lacking a semantic bridge
to the rest of the user's world. Instead allow users to build bridges by explicitly mapping elements from your application domain
to others available in their burgeoning Service oriented architecture (SOA). Once these bridges are built, users can take
your application to strange and exotic places.
Excerpt from the book
Service-Oriented Architecture: A Field Guide to Integrating XML and Web Services.
In this article, perfectxml.com managing editor, Darshan Singh, responds to questions asked by
PerfectXML visitors. In this part:
The main goals of Web services are three-fold:
- Get programs talking to each other, because we want to leverage the existing technology.
- Be cheap, compact and scalable for all parties, because we want to have web services everywhere, providing services to everyone, using any device.
- Build on the infrastructure, because it's already paid for.
The best way to get there is to build an environment based on standards that everyone agrees on.
In this chapter, we will build a house of standards showing where each one fits, and how they relate to each other. It is only by using internationally recognized standards that you can create systems that can communicate with your trading partners around the world.
The integration models we have today are either loosely coupled or tightly
coupled. They are message-based or method-based. They are synchronous or
asynchronous. Putting these things together in an intelligent way is essential
if you are going to archive the promise of web services.
In this chapter,
we will discuss all of these models, and show which ones are used by web
services and why.
The Simple Object Access Protocol is a standard that has provided a simple solution to a complex problem. The problem is that integrating systems is difficult. That’s not really news, but it is a fact that many I.T. professionals are well aware of. The main area of incompatibility arises because information and objects are distributed all over the place.
The SOAP standard provides a set of tags and an environment that allows systems to request information from other systems by sending self-describing messages over any network.
SOAP is really just an envelope, but its simplicity means that it is easy to use and very flexible. In this chapter, you will learn about this most important standard for web services.