Fwd: [members] 60-day Public Review for OASIS Reference ArchitectureFoundation for Service Oriented Architecture (SOA-RAF)

Please excuse the duplications, folks,

    

    I wanted the emphasize the importance of this work, even if you have
    received the announcement through OASIS. 

    

    This work took more than five years and I think it will, over the
    years, become the checklist for those developing and deploying web
    services in a structured and intentionally long-lived way, e.g.
    governmental agencies and major corporations. It is not intended to
    be agile/nimble. People already do that quite well. It is the more
    long lasting, reliable and trustworthy purposes that it is aimed to
    provide for and help maintain. 

    

    It is at a level of abstraction between the purely abstract OASIS
    Reference Model for SOA and the more concrete SOA reference
    architectures such as that released by the Open Group last week and
    two steps more abstract than specific solution architectures. It is
    at a level of abstraction very close to our Reference Information
    Model; e.g. it is intended to provide a cookbook for more concrete
    architectures the same way our RIM is intended to provide the tools
    and common types for our functionally constrained specifications.

    

    We need the best feedback we can get.

    

    Cheers,

    Rex

    

    -------- Original Message --------
    
      
        

          Subject: 
          [members] 60-day Public Review for OASIS Reference
            Architecture Foundation for Service Oriented Architecture
            (SOA-RAF)
        

        

          Date: 
          Tue, 23 Aug 2011 19:50:54 -0400
        

        

          From: 
          
        

        

          To: 
          ,
            ,
            ,
            ,
            ,
            
        

      
    
    

    

    
The OASIS SOA Reference Model TC [1] members have recently
      approved a Committee Specification Draft (CSD) and submitted this
      specification for 60-day public review:

    
Reference Architecture Foundation for Service Oriented
      Architecture Version 1.0

      Committee Specification Draft 03 / Public Review Draft 02

      06 July 2011 

    
Specification Overview:

      This document specifies the OASIS Reference Architecture
      Foundation for

      Service Oriented Architecture (SOA-RAF). It follows from the
      concepts and relationships defined in the OASIS Reference Model
      for Service Oriented Architecture. While it remains abstract in
      nature, the current document describes the foundation upon which
      specific SOA concrete architectures can be built. 

    
The focus of the SOA-RAF is on an approach to integrating
      business with the information technology needed to support it.
      These issues are always present but are all the more important
      when business integration involves crossing ownership boundaries.
    

    
The SOA-RAF follows the recommended practice of describing
      architecture in terms of models, views, and viewpoints, as
      prescribed in the ANSI /IEEE 1471-2000, (now ISO /IEC 42010-2007)
      Standard. The SOA-RAF is of value to Enterprise Architects,
      Business and IT Architects as well as CIOs and other senior
      executives involved in strategic business and IT planning. 

    
TC Description:

      The OASIS Service Oriented Architecture TC was constituted to
      develop a

      Reference Model for Service Oriented Architecture (SOA-RM). This
      is primarily to address SOA being used as a term in many contexts
      and specific technology implementations, sometimes with differing
      - or worse, conflicting - understandings of implicit terminology
      and components. The Reference Model, which became an OASIS
      Standard, has provided

      a common layer of understanding about what is SOA. The continuing
      work on the Reference Architecture Foundation will document needs
      and considerations in applying SOA-RM concepts towards SOA
      realizations. 

    
Public Review Period:

      The public review starts today, 24 August 2011 and ends 24 October
      2011. The specification was previously submitted for public review
      on 13 November 2009 [2]. This review is limited in scope to
      changes made from the previous review. 

    
Changes are highlighted in the diff-marked PDF file: 

    
http://docs.oasis-open.org/soa-rm/soa-ra/v1.0/csprd02/soa-ra-v1.0-csprd02-diff.pdf

    
This is an open invitation to comment. OASIS solicits feedback
      from potential users, developers and others, whether OASIS members
      or not, for the sake of improving the interoperability and quality
      of its technical work.

    
URIs:

      The prose specification document and related files are available
      here:

    
PDF (Authoritative):

      http://docs.oasis-open.org/soa-rm/soa-ra/v1.0/csprd02/soa-ra-v1.0-csprd02.pdf

    
HTML:

      http://docs.oasis-open.org/soa-rm/soa-ra/v1.0/csprd02/soa-ra-v1.0-csprd02.html

    
Editable source:

      http://docs.oasis-open.org/soa-rm/soa-ra/v1.0/csprd02/soa-ra-v1.0-csprd02.doc

    
ZIP distribution file (complete):

      For your convenience, OASIS provides a complete package of the
      prose specification and related files in a ZIP distribution file.
      You can download the ZIP file here:

    
http://docs.oasis-open.org/soa-rm/soa-ra/v1.0/csprd02/soa-ra-v1.0-csprd02.zip

    
Additional information about the specification and the OASIS SOA
      Reference Model TC can be found at the TC's public home page:

    
http://www.oasis-open.org/committees/soa-rm/

    
Comments may be submitted to the TC by any person through the use
      of the OASIS TC Comment Facility which can be located via the
      button labeled "Send A Comment" at the top of the TC public home,
      or directly at:

    
http://www.oasis-open.org/committees/comments/index.php?wg_abbrev=soa-rm

    
Comments submitted by TC non-members for this work and for other
      work of this TC are publicly archived and can be viewed at:

    
http://lists.oasis-open.org/archives/soa-rm-comment/

    
All comments submitted to OASIS are subject to the OASIS Feedback
      License, which ensures that the feedback you provide carries the
      same obligations at least as the obligations of the TC members. In
      connection with this public review of for OASIS Reference
      Architecture Foundation for Service Oriented Architecture
      (SOA-RAF), we call your attention to the OASIS IPR Policy [3]
      applicable especially [4] to the work of this technical committee.
      All members of the TC should be familiar with this document, which
      may create obligations regarding the disclosure and availability
      of a member's patent, copyright, trademark and license rights that
      read on an approved OASIS specification. OASIS invites any persons
      who know of any such claims to disclose these if they may be
      essential to the implementation of the above specification, so
      that notice of them may be posted to the notice page for this TC's
      work.

    
========== Additional references:

    
[1] OASIS SOA Reference Model

      http://www.oasis-open.org/committees/soa-rm/

    
[2] Previous public review announcement

      http://lists.oasis-open.org/archives/tc-announce/200911/msg00010.html

    
[3] http://www.oasis-open.org/who/intellectualproperty.php

    
[4] http://www.oasis-open.org/committees/icom/ipr.php

      http://www.oasis-open.org/policies-guidelines/ipr#10.2.3

      RF on Limited Terms 

    
Best Regards,

    
/chet

      ----------------

      Chet Ensign

      Director of Standards Development and TC Administration

      OASIS: Advancing open standards for the information society

      http://www.oasis-open.org

    
Primary: +1 973-378-3472

      Mobile: +1 201-341-1393

    ---------------------------------------------------------------------

This

    email list is used solely by OASIS for official consortium
    communications. Opt-out requests may be sent to ,
    however, all members are strongly encouraged to maintain a
    subscription to this list.