Return to Home Page
Overview
    History
    Acknowledgements
    Podcasts
    Notification Form
    Feedback Form
    Press Release #1
    Press Release #2
    Press Release #3

Master SOA Design
Pattern Catalog
    Master Pattern List (alphabetical)
    Master Pattern List (by category)
    Master Pattern List (Text)
    Pattern Notation
    Pattern Profiles
    Symbol Legend
    Pattern Contribution Form

SOA Candidate Patterns
    SOA Patterns Review Committee
    Candidate Patterns Overview
    Candidate Patterns List
    Candidate Pattern Contribution Form
    Candidate Pattern
Feedback Form
    SOA Pattern Template

Design Pattern Basics
    What's a Design Pattern?
    What's a Design Pattern Language?
    What's a Compound Pattern?

Supplemental
    SOA Patterns and Application Technologies
    SOA Design Patterns Historical Influences
    SOA Design Patterns and Design Principles
    SOA Design Patterns and Design Granularity
    Legal

Resources
    Design Patterns Publications
    Reference Posters
    SOAPrinciples.com
    WhatIsSOA.com
    SOA Visio Stencil


Canonical Expression (Erl)


Home > Inventory Governance Patterns > Canonical Expression
How can service contracts be consistently understood and
interpreted? 		 

Problem

Service contracts may express similar capabilities in different ways, leading to inconsistency and risking misinterpretation.

Solution

Service contracts are standardized using naming conventions.

Application

Naming conventions are applied to service contracts as part of formal analysis and design processes.
Impacts

The use of global naming conventions introduces enterprisewide standards
that need to be consistently
used and enforced.

Principles

Standardized Service Contract, Service Discoverability

Architecture

Enterprise, Inventory, Service




The expression of service contracts is aligned across services.


Related Patterns in This Catalog

Agnostic Capability (Erl), Agnostic Context (Erl), Canonical Versioning (Erl), Concurrent Contracts (Erl), Contract Centralization (Erl), Contract Denormalization (Erl), Entity Abstraction (Erl), Metadata Centralization (Erl), Non Agnostic Context (Erl), Process Abstraction (Erl), Service Layers (Erl), Utility Abstraction (Erl)


Related Service-Oriented Computing Goals

Increased Federation, Increased ROI, Reduced IT Burden


SOA Design Patterns This page contains excerpts from:

SOA Design Patterns by Thomas Erl

Foreword by Grady Booch

With contributions from David Chappell, Jason Hogg, Anish Karmarkar, Mark Little, David Orchard, Satadru Roy,
Thomas Rischbeck, Arnaud Simon, Clemens Utschig, Dennis Wisnosky, and others.

(ISBN: 0136135161, Hardcover, Full-Color, 400+ Illustrations, 865 pages)

For more information about this book, visit www.soabooks.com.
Web Service Contract Design and Versioning for SOA This pattern is also discussed in the following title:

Web Service Contract Design and Versioning for SOA
by Thomas Erl, Anish Karmarkar, Priscilla Walmsley, Hugo Haas, Umit Yalcinalp, Canyang Kevin Liu,
David Orchard, Andre Tost, James Pasley

Foreword by David Chappell

(ISBN: 013613517X, Hardcover, 826 pages)

For more information about this book, visit www.soabooks.com.
The Prentice Hall Service-Oriented Computing Series from Thomas Erl
Home    SOA Books    SOA Magazine    What is SOA?    SOA Principles    SOASchool.com    SOA Glossary Copyright © 2007-2011
SOA Systems Inc.