A disclosure framework for service accountability in SOA

Joe Zou*, Christopher J. Pavlovski, Yan Wang

*Corresponding author for this work

Research output: Chapter in Book/Report/Conference proceedingConference proceeding contributionpeer-review

2 Citations (Scopus)


Accountability has become a key concern for management in recent years since the collapse of several large corporations in energy, communications and financial consulting industries. Traditionally, accountability has not been a significant concern in the IT literature. Recently, some protocols, models and frameworks that address certain aspects of accountability have emerged. However, an architecture framework that addresses the overall accountability requirements is nonetheless missing in a Service-Oriented computing environment. In this paper, we review the accountability literature in an IT context and argue that disclosure, as a crucial requirement of accountability, has been largely ignored in the current literature. Based on this proposition, we propose a new architectural framework to address the important disclosure requirement that extends and integrates the existing architecture models. The proposed framework can be used to build SOA solutions that support the key accountability requirements.

Original languageEnglish
Title of host publicationProceedings of the ICEBE 2008
Subtitle of host publicationIEEE International Conference on e-Business Engineering
Place of PublicationPiscataway, NJ
PublisherInstitute of Electrical and Electronics Engineers (IEEE)
Number of pages6
ISBN (Print)9780769533957
Publication statusPublished - 2008
EventIEEE International Conference on e-Business Engineering, ICEBE'08 - Xi'an, China
Duration: 22 Oct 200824 Oct 2008


OtherIEEE International Conference on e-Business Engineering, ICEBE'08


  • accountability
  • disclosure
  • SOA
  • web services
  • trust
  • reputation


Dive into the research topics of 'A disclosure framework for service accountability in SOA'. Together they form a unique fingerprint.

Cite this