Pure Data

A real service should produce a pure data representation, one built specifically for the service's intended clients.

As a result it is not always easy to classify a particular implementation as pure data or business service.

The role of a service implementation is to enforce the system of record's integrity, almost as a pure data access layer.

If your document is pure data, however, it still makes more sense to bring it into a relational database for manipulation.

Note: As with pure data-centric markup, beware of illegal characters weaseling into XML element names.

Pure data can be lost to hardware failures and disk crashes.

Decide whenever possible for a pure control-flow or a pure data-flow model.

In the real world, no such thing as pure data-centric, process-based, or policy interoperability exists.

For a long time e-business activities followed a pure data centric approach.

Sometimes it is easier to just return pure data from the server.

You are interested in the data but not the tags, and want to store pure data in your database.

This is pure data in action.

In a pure data flow system, there is no other interaction between processes

Pure data documents for information exchange between applications only