service-oriented architecture

The phrase service-oriented architecture (abbreviated SOA) refers to a service economy model for the World Wide Web and some underlying Internet services including potentially Internet Governance services. It is the most specific and best supported vision of the so-called web 2.0 - an enterprise web 2.0 as ZDnet calls it(external link) - but may include many ill-advised extensions. More specific terms are advised:
  • client service computing? focuses on a real simple use of clients to consume services (or composite services)
  • service network computing? focuses on the plumbing that makes hokey Web 2.0 applications capable of performing 'business critical' applications.

According to Tim O'Reilly?, it simply means beyond page metaphors to an "architecture of participation." Effectively, the entire network is a single platform(external link).

until 3.1

Perhaps the only neutral way to define any "2.0" is as "the thing between 1.0 and 3.0". Thus Jeff Schneider?'s web 3.0 maturity model may be the only succinct statement until a widely accepted "version 3.1?":


The SOA expert podcast(external link) may be amusing.

See web 3.1? by Efficient Civics Guild for another technical vision? that's more specific.

too many terms

The phrases P2P?, Web 2.0, SaaS?, Web as platform?, SOA, convergence?, Enterprise Web 2.0, Global SOA, and even "business as a platform(external link)", social software and flash mob? likely converge over time if the vision is accurate, but no one convergence process makes all decisions - unlike the IETF and W3? visions. The ECG studies the process by which these decisions occur including especially contests such as(external link) the Game Design Challenge?, and "winning" applications like the Peace Bomb?. ECG proposes that all human command verbs related to nonviolent tactics?, especially those actually derived from municipal initiatives, will be the real convergent core ontology.

[+] too broad a path: enterprise versus public web views

[+] loose coupling, agile computing

standards efforts

However, it would be difficult to deviate much from the original architecture now being defined. Lawrence Lessig argues that this is the primary determiner of the services offered or not offered, and their ultimate subversion or reliability, and that after these definitions are accepted, there is little opportunity to fix them despite perhaps drastic effects on the polity?. See ICANN, IANA, Internet Governance and the difficulty of efforts to establish an Internet Governance Forum?.

OASIS called for public review of its reference model for SOA prior to 2006-04-14(external link), after which it was to become an OASIS standard?. This effort was expected to focus OASIS, W3? and ECG work on various aspects of the standards required, complement and incorporate some ISO standards while building on IETF standards.
The W3 standards effort is sometimes referred to as Web 2.0 and focuses on public World Wide Webtechnology. BACnet deals with infrastructural capital only.

The ECG and its Living Ontology Web take a broader living systems perspective to e-government and e-democracy problems, and focus on open politics itself. These more specialized efforts should require only some minor adaptations to the OASIS reference model. However, every political and journalistic problem arising from web 2.0 technology use(external link) contributes to case-based reasoning? about the ultimate form of web 3.1?.

what it does

OASIS provides the most useful definition(external link) from the point of view of vendors, larger organizations, and early corporate adopters who tend to drive such standards on their intranets.

According to OASIS, SOA "represents a collection of best practices, principles and patterns related to service-aware, enterprise-level, distributed computing. SOA standardization efforts at OASIS focus on workflow?s, translation coordination, orchestration?, collaboration, loose coupling, business process model?ing, and other concepts that support agile computing." This complements underlying SNMP MIB?s and skilled trades defined by BACnet and ECG respectively to keep green systems reliably operating and well monitored, which cover systems integration? and green procurement, for instance, to minimize use of electricity, creation of e-waste?, maximize telework.


A list of OASIS Technical Committee?s provides the best overall institutional guide to standards. The standards themselves are at a much lower level of detail(external link).

  • OASIS Electronic Business Service Oriented Architecture? (ebSOA) TC covers e-commerce? related software pattern?s - this complements e-government and e-democracy work by national governments and ECG
  • OASIS Framework for Web Services Implementation? (FWSI) TC defines "methods and functional components for broad, multi-platform, vendor-neutral cross-industry implementation of web services" which intersect strongly with W3 efforts, e.g. OWL
  • OASIS Semantic Execution Environment? TC develops guidelines, justifications, and implementation directions for deploying semantic web services in SOA" - this intersects with sociosemantic web standards proposed by ECG
  • OASIS SOA Adoption Blueprints? TC develops, publishes and maintains archetypal "blueprint" sets of "requirements and functions to serve as generic, vendor-neutral instances of service-oriented solutions for real business requirements." ECG developed Living Platform itself as an archetype for political party use of open politics itself
  • OASIS SOA Reference Model? TC develops a "core reference model to guide and foster the creation of specific, service-oriented architectures" similar to the ECG living ontology core ontology.
  • OASIS Web Services Quality Model? TC defines "common criteria to evaluate quality? levels for interoperability, security, and manageability of services", e.g. provisioning?, credentials, privacy. ECG similarly has set standards for what it means to put "open politics in force" and some Green web standards for the smooth interoperation of people cooperating politically.

Show php error messages