Begin with business processes and then progress into leading-edge technologies
IMO, services that only provide access to data, without functional operations that provide some sort of capability, is the wrong focus. The important thing about service orientation is doing something, not just reading or writing data. A service wrapper around data access is a data oriented approach, not an SO approach.
Presumably, one reads data in order to do something with it. The reading and the doing should be part of the same service, IMO. Segregating services by data vs. transaction is fundamentally flawed IMO.
Topic: SOA
SOA uses interoperable services grouped around business processes to ease data integration
Blog: Delivering Information as a Service
Article: The Best Cloud Case: What Functions You Should – and Shouldn't – Consider Moving
White Paper: Driving Business Agility Through SOA Connectivity and Integration
Related Topics
Data Integration, Master Data Management
Collaboration Without Boundaries: Enabling Innovation, Changing the WorkplaceIn today's competitive environment, sharing information and expertise can be critical in driving organizational success. To foster innovation, it's important to create collaboration communities of employees, as well as customers and partners "outside the firewall." Read this white paper to learn how to tap into both internal and external knowledge.

Service-Oriented Architecture is the catalyst that allows today’s companies to respond to business demands faster and more effectively than ever.

Learn more about this middleware layer that pools and dynamically provisions infrastruction application delivery resources to lower costs and improve efficiency.
IT Manager Development Library
Budget & Finance Toolkit for IT - 2010 EditionDownload a comprehensive collection of templates, forms, instruction and advice that will help you to plan and submit your 2010 IT Budget.
Loraine -
Yes, data can be service-enabled in the same way SOA service-enables business processes and transactions.
David Besemer provides a really good desciption of data services in "An Implementor's Guide to SOA" which can be freely downloaded at http://www.soaguidebook.com/chapters.html#chapter2
He nicely contrasts data and transaction services, clarifying key issues from a service design point of view.
From a governance point of view, typical SOA design and runtime governance needs to be enhanced with data governance. But in the long run, governing clearly defined, loosely-coupled, abstracted data services is a lot easier than governing siloed, old school FTPs and ELT scripts.
- Bob Eve