Skip to main content

SOA Standards

 There are many standards related to SOA and SOA-related technologies. However, since multiple organizations and consortiums are working on these standards, it becomes challenging for people to determine which standard to follow. Additionally, interoperability issues remain unaddressed. Among the most prominent standardization bodies are OASIS, WS-I, and W3C, each at different stages of maturity in their standards.

There has long been confusion in the SOA space, primarily due to the lack of well-defined standards and governing bodies. Below is a list of standards that various organizations have been working on or have already established for SOA and related technologies:

Key SOA Standards and Organizations

Ongoing IEEE SOA Standardization Efforts

  1. IEEE SOA Solution Reference Architecture (SOA-SRA)
  2. IEEE SOA Services Composition Protocols (SOA-SCP)
  3. IEEE SOA Services Discovery Language (SOA-SDL) (Federated Discovery)
  4. IEEE SOA Requirements Model (SOA-RM)
  5. IEEE SOA Adaptive Services Invocation Model (SOA-ASIM)
  6. IEEE SOA Relationship Modeling Language (SOA-RML)
  7. IEEE SOA Services Ecosystem Exchange Protocols (SOA-SEEP)
  8. IEEE SOA Services Integration Protocol (SOA-SIP)
  9. IEEE SOA Service-Oriented Enterprise Project Management Model (SOA-PM)
  10. IEEE SOA Proactive Event Services Model (SOA-PESM)
  11. IEEE SOA for Manufacturing Execution System (SOA4MES)

Other Relevant SOA Standards and Resources

WS-I Specifications for Interoperability

The Web Services Interoperability Organization (WS-I) provides resources to help developers create interoperable web services and ensure compliance with WS-I guidelines. Key WS-I deliverables include:

  • Profiles
  • Sample Applications
  • Testing Tools

More details on WS-I deliverables can be found here: WS-I Deliverables Matrix

Additional Resources on Web Services Standards

  1. Poster of Web Services Standards (from innoQ)
  2. Web Services Specifications Index (MSDN)
  3. Web Services Standards Overview (IBM DeveloperWorks)
  4. List of Web Services Standards (Wikipedia)
Labels:

Comments

Post a Comment

Popular posts from this blog

Example 1: ArchiMate relationship in PlantUML code to demonstrate 15 relationship types

 Following section presents 15 types of relationships in ArchiMate and PlantUML to generate the diagram. Since this code is generated by GEN-AI it may require precision on aspects other than PlantUML syntax: Diagram Plant UML Code:  @startuml '!includeurl https://raw.githubusercontent.com/plantuml-stdlib/Archimate-PlantUML/master/Archimate.puml ' Another way of including Archimate Library (above is commented for following) !include <archimate/Archimate> !theme archimate-standard from https://raw.githubusercontent.com/plantuml-stdlib/Archimate-PlantUML/master/themes title ArchiMate Relationships Overview <style> element{     HorizontalAlignment: left;     MinimumWidth : 180;     Padding: 25; } </style> left to right direction rectangle Other {     Business_Role(Role_SeniorManager, "Senior Manager")     Business_Role(Role_Manager, "Manager") } rectangle Dynamic {     Business_Event(Event_CustomerReques...
Post a Comment
Read more

Mastering Trade-Off Analysis in System Architecture: A Strategic Guide for Architects

 In system architecture and design, balancing conflicting system qualities is both an art and a science. Trade-off analysis is a strategic evaluation process that enables architects to make informed decisions that align with business goals and technical constraints. By prioritizing essential system attributes while acknowledging inevitable compromises, architects can craft resilient and efficient solutions. This enhanced guide provides actionable insights and recommendations for architects aiming to master trade-off analysis for impactful architectural decisions. 1. Understanding Trade-Off Analysis Trade-off analysis involves identifying and evaluating the conflicting requirements and design decisions within a system. Architects must balance critical aspects like performance, scalability, cost, security, and maintainability. Since no system can be optimized for every quality simultaneously, prioritization based on project goals is essential. Actionable Insights: Define key quality ...
Post a Comment
Read more

Virtual environments in python

 Creating virtual environments is essential for isolating dependencies and ensuring consistency across different projects. Here are the main methods and tools available, along with their pros, cons, and recommendations : 1. venv (Built-in Python Virtual Environment) Overview: venv is a lightweight virtual environment module included in Python (since Python 3.3). It allows you to create isolated environments without additional dependencies. How to Use: python -m venv myenv source myenv/bin/activate # On macOS/Linux myenv\Scripts\activate # On Windows Pros: ✅ Built-in – No need to install anything extra. ✅ Lightweight – Minimal overhead compared to other tools. ✅ Works across all platforms . ✅ Good for simple projects . Cons: ❌ No dependency management – You still need pip and requirements.txt . ❌ Not as feature-rich as other tools . ❌ No package isolation per project directory (requires manual activation). Recommendation: Use venv if you need a simple, lightweight solut...
Post a Comment
Read more