SOA patterns: proposal for exchanging non-XML data

At issue: how can services exchange data based on less common or non-standard formats?

Along with the established SOA patterns outlined at and in the book SOA Design Patterns (coordinated by Thomas Erl), there is a community process for submitting and reviewing candidate patterns.

The following is one of the candidate patterns now under consideration.

Candidate SOA pattern: Alternative Format

At issue: How can services exchange data based on less common or non-standard formats? Service consumers may have data exchange requirements based on non-XML formats.

Solution: Services can be designed to exchange data in alternative representation formats, thereby accommodating special consumer requirements.

Application: How this pattern is applied is dependent on the endpoint type of the service and technology required to support the desired data format.

Impact: This pattern can deviate from the goal of establishing Canonical Schema

Principles: Standardized Service Contract ("Services within the same service inventory are in compliance with the same contract design standards"); Service Reusability ("Services contain  and express agnostic logic and can be positioned as reusable enterprise resources.")

SOA proponents, enterprise architects, and IT professionals are invited to submit patterns they have identified for potential inclusion. SOA design patterns typically represent field-tested solutions, and organize intelligence into referenceable formats, and are intended to be repeatable by IT professionals.