SOA for E-Government Conference Announcement and Launch

Last modified


  • Meetings:
    • First Meeting - Conference Call: February 22, 2006, 11 a.m. - 1 p.m. at Oracle, Reston, Virginia
    • Second Meeting - Conference Call: March 17, 2006, 10 a.m. - 12 noon
    • Third Meeting - Conference Call: June 8, 2006
    • Fourth Meeting - Conference Call: July 25 and/or July 31, 2006
  • Chronology/Calendar:
    • January 24, 2006, Collaborative Expedition Workshop COLAB, contained one or more presentations on the above three things as requested recently by the AIC Leadership:
      • SOA for E-Gov Initiatives Like E-Grants at the Federal and State Level and FHA Data Architecture
      • SOA Governance
      • SOA Best Practices
    • January 26, 2006, Announcement COLAB at the Chief Architects Forum Meeting
    • January 27, 2006, General Call for Participation (Very Positive Responses Received - See Below)
      • A special CAF meeting (planning and presentations)
      • Future Collaborative Expedition Workshops (planning and presentations)
      • The 4th Semantic Interoperability for E-Government Conference, February 9-10, 2006, where several Semantic (or Ontology-driven) SOA’s will be presented.
      • SOA for E-Government Conference, May 23-24, 2006, at MITRE, McLean, Virginia.
    • January 31, 2006, Greg Lomow, Bearing Point, and Co-Author of "Understanding SOA with Web Services" Invited to be Co-Chair with BrandNiemann, SICoP, Chair, for the initial phase of the CoP
    • February 9-10. 2006, Announcement of May 23-24, 2006, SOA for E-Government Conference at the Fourth Semantic Interoperability for E-Government Conference, MITRE, McLean, Virginia
    • February 16, 2006, EPA IT Contractors Forum on SOA - Presentations
    • February 16, 2006, Announcement of the new CIO Council Architecture & Infrastructure Committee's Services Subcommittee
    • February 22, 2006, First Meeting - Conference Call
    • February 24, 2006, Suggested May 23-24th Agenda Assignments Posted for Discussion
    • March 3, 2006, Wiki training COLAB, 10:30 a.m. - 12 noon
  • Some Resources:
    • SOA at OMG
    • FCW SOA Roundtable, January 25, 2006 (published March 28, 2006)
    • Ontology Driven Architectures and Potential Uses of the Semantic Web in Systems and Software Engineering
    • ZapThink’s SOA Roadmap
    • Model Driven Architecture in the U.S. Government, November 15, 2005, Workshop
    • Achieving Business Agility through Model-Driven SOA, Dr. Chris Harding, The Open Group, ebizQ, January 29, 2006
    • March 21, 2006, The XML SIG Steering Committee is pleased to sponsor a half day TEM on Tuesday morning, March 21st, for review and discussion of the Reference Model for Service Oriented Architectures (SOA-RM). The document has been developed under the auspices of OASIS and has just begun a 60-day public review; see for the review announcement and links to the SOA-RM. Ken Laskey, one of the editors of the draft, will present the key points of the document and provide additional rationale behind the descriptions in the document. The TEM will include ample time for questions and discussion. It will be open to MITRE employees and our sponsors. John Klingler is coordinating the TEM. Currently conference rooms and VTC are planned for Bedford and Washington. Those interested in additional VTC connections should contact John at 781-266-9113 or . More information will be provided in the coming days.
    • SOA, MDA, and Web Services Workshop: Integrating the Enterprise, and Beyond, March 27-30, 2006, Fairfax, VA
    • 3rd Service Oriented Architecture (SOA) & Web Services Best Practices Strategies for Governing the Implementation of SOA, Increasing Business Agility and Reducing IT Integration Costs, March 27 - 29, 2006, The Rosen Plaza Hotel, Orlando, FL
    • 2006 IEEE International Conference on Web Services (ICWS 2006), Celebrating the 60th Anniversary of IEEE Computer Society, September 18-22, 2006, Hyatt Regency at O'Hare Airport, Chicago, USA
    • Roadmap for Semantics in Netcentric Enterprise Architecture, Prepared for the Office of the CTO, US General Services Administration, February 2, 2006, Erick Von Schweber, Synsyta LLC
    • June 1, 2006, NASCIO's Service Oriented Architecture: an Enabler of the Agile Enterprise

Purpose and Suggested Structure

Purpose: SOA is already a common thread across the three AIC Subcommittees (SC) and Communities of Interest/Communities of Practice are becoming quite influential in government circles as the way diverse interests come together and break down the barriers between them. The SOA CoP would help align the many AIC initiatives around a given theme for both Enterprise SOA and Extended Enterprise SOA (John Dodd) and provide these SCs with expertise and coordination.

  • 1. Governance SC: SOA Governance and SOA in the Reference Model Maintenance Process.
  • 2. Services SC: Soon Services with SOA (new charter being drafted)
  • 3. Emerging Technology: SOA for Data (XML CoP and SICoP)- More agile than conventional data management and data standards approaches.
  • And elevating to serve all the SCs will promote collaboration and integration.
  • 4. And now a new Data Subcommittee just announced by Charlie Havekost at FOSE 2006: That sounds like it will also do SOA for Data! New charter also being drafted.

Suggested Structure (patterned after the very successful DRM 2.0 CoP):

  • SOA Reference Models, Specifications, and Standards
  • SOA Governance
  • SOA Implementation and Testing

Connections to the FEA Service Components Reference Model:

  • George Thomas is the FEA SRM process owner and GSA's SRM Reference Model submission on the SRM speaks to important SOA governance issues related to the following three points:
    • Better aligning the SRM with market-driven Service Oriented Architecture (SOA) through the W3C definition of Service
    • Better aligning the SRM with administration policy by specifying service providers and consumers
    • Better aligning DoD Net-centric Enterprise Services and the FEA
    • Note: This is an important change to the SRM that better reflects consistency between civilian and defense agencies.

Responses and Comments


  • AIC Leadership (Roy Mabry, GSC Co-Chair and Susan Turnbull, ETS Co-Chair)
  • Chief Architects Forum (Ira Grossman, Lead)
  • DoD CoI Forum (Michael Todd, Lead)
  • DoD OSD (Paul Grant and George Wauer)
  • GSA OSERA (Richard Murphy and George Thomas)
  • Industry Advisory Council (IAC)
  • John Dodd, EA SIG
  • SOA Committee: Greg Hauser, Chair, Gerry Anderson, Programs Chair, Bob Brogan, Software Focus Group Manager, and Jana Jackson, SOA Benefits & Cultural Change Focus Group Manager
  • IC EA CoP (Scott Mitchell)
  • MITRE (Rick Tucker)
  • DoNSOAWg (Bob Green, Tim Johnson, and John Weiland)
  • OASIS SOA-RM TC (Ken Laskey, MITRE, and Rebekah Metz, Booz Allen Hamilton)
  • SICoP (Brand Niemann, Chair)
  • SOA Leaders (Greg Lomow, Bearing Point, and Co-Author of "Understanding SOA with Web Services"
  • Ron Schmelzer, ZapThink and Service Orient or Be Doomed
  • Chris Harding, The Open Group, Forum Director for SOA and Semantic Interoperability
  • Benjamin Mosse, Vice President, Software, Services & Emerging Sectors, Enterprise Ireland
  • Eric Marks, President and CEO, AgilePath Corporation
  • Chris Gunderson, Executive Director, World Wide Consortium for the Grid (W2COG)
  • Brian Kahin, Computer & Communications Industry Association
  • Cory Casanave, CEO/President, Data Access Technologies, Inc.
  • Lois Fairclough, Department of Navy
  • David Allen, Booz Allen Hamilton
  • Chris Riley, Cape Clear
  • Mark O'Neill, Vordel
  • Federal Open Source Alliance at FOSE 2006 (JBOSS: Open Source Middleware and SOA in Government)
  • Joe Chiusano, Booz Allen Hamilton

Comments Received:

  • Large scale modifications to the Service Reference Model (SRM) as it relates to Service Oriented Architecture (SOA) seem to be emerging. See RMMP Update, February 16, 2006
  • I really think the FEA TRM and other parts have to be refreshed to reflect the SOA elements and we have to connect with the OASIS SOA groups. The TRM has to be treated as a forward looking document to be used for the target architecture and not stuck with legacy technologies. I am working on the TRM evaluation now and feel that there are a set of updates needed to reflect SOA Service Infrastructure. John C. Dodd, Principal Consultant- Federal Consulting Practice Strategic Programs, Enterprise Architecture and e-Government Services
  • DISA's Joint Interoperability Test Command has agreed to support my proposal to help them devise an approapriate T&E process for DOD SOA. My approach will be to do a disciplined inventory of best practice and cherry pick. Chris Gunderson, W2COG
  • Some notes for the Conference: The MDA & SOA Tutorial we do for OMG would work great for the conference, please put our hat in the ring. We would also bring in the GSA-FMEA architecture as the example; Tutorial Track 2: Model Driven Architecture, Web Services, and Service-Oriented Architecture in the Enterprise Cory Casanave, CEO/President, Data Access Technologies, Inc. Service Oriented Architectures (SOA) and Web services provide the technical basis for messaging, but are only part of the solution. Making a SOA solution for integration, collaboration and supply chain automation requires that multiple technologies be used and integrated. It requires new and legacy applications to be integrated into a seamless, maintainable and robust solution. The Model Driven Architecture provides the basis for a high-level and full life-cycle approach to web services. By combining web services and MDA we are able to drive our SOA solution from high-level business semantics, making sure our solution meets requirements and also making it easier to develop and maintain. We are also able to integrate web service and other technologies, providing a more cohesive environment. The presentation will show how to apply MDA to SOA and web services to achieve business goals. The result of applying these techniques can result in the enterprise Richard Soley, CEO, OMG as a Keynote. Do you want me to contact him? We discussed setting up an enterprise interoperability scenario and demo. I think this would be a great idea as a way to validate & demonstrate application of SOA to wide-scale and agile interoperability. Lets set up a workgroup to get this started. We would be happy to serve on the program committee, or, perhaps organize the Interoperability Demo. Let me know. Cory Casanave
  • Brand Niemann's comments on the AIC's new Services Subcommittee is: Elevating the Component SC to do SOA with Services aligns it with the Governance SC already doing Governance for SOA and SOA in the RMMP and aligns it with the Emerging Technology SC already doing SOA for Data (XML CoP and SICoP) and elevating to serve all the SCs will promote collaboration and integration.
    • John Dodd Comment: Very good idea that would align the many AIC initiatives around a give theme for both Enterprise SOA and Extended Enterprise SOA. Did you look at my TRM slides?(See TRM Evaluation Check List)
  • I thought I would comment that your approach to focus the AIC around SOA will give a theme to the year. The actions of all the groups can be integrated from governance-components to emerging technology. Charlie Havecost has shown great interest in this as well as Dick Burk. An integrated "yearly plan" could show how to update all reference models, make some of SOA Service Life Cycle processes, foster pilots and focus on SOA implementations and share lessons learned including gaps that are need to be filled with "next practices". A set of Service Data Scenarios and common shared data services can be defined an put in The FEA RM can be related to OASIS SOA initiatives and other standards and the government could provide input and involvement to these critical 2nd generation standards efforts. We can show how semantics is integrated and ontology-based development offers a strong operations approach and can be linked to community-based governance from the business governance, service infrastructure governance, and governance aspects to each project. Putting some summary together and a very high level schedule could be very important. John C. Dodd


Notes: A Work in Progress and Initial Source: Capability Cases: A Solution Envisioning Approach, Polikoff, Coyne, and Hodgson, 2006, pp. 437-445, Addison Wesley.

Agile Methods:

Lightweight software development methodologies that emphasize close collaboration between the programmer team and business experts; face-to-face communication (as more efficient than written documentation); frequent delivery of new deployable business value; tight, self-organizing teams; and ways to craft the code and the team such that the inevitable requirements churn is not a crisis.

See the Agile Alliance Website

Component-Based Development:

An approach to the design and implementation of software applications where systems are assembled using components from one or more sources. The components may be written in different programming languages and run on different platforms. Components exist at different levels of granularity - from a re-usable calendar gadget to fully featured CRM (Customer Relationship Management)) module. What is common is their ability to be composable. A software component is any self-contained, independently viable, and deployable grouping of services whose services can be involked by many different types of clients.

See Componenttechnology.Org Website

Model Driven Architecture (MDA):

An approach to system specification, portability, and interoperability based on the use of formal and semi-formal models. The MDA derives all executable code from models of the system using UML and other associated OMG (Object Management Group) standards.

See the OMG MDA Website


A model of how to specify a subject area of interest in which concepts, their attributes, and relationships (associations between concepts) are explicitily named and distinguished. Constraints stipulate distinctions that differentiate concepts, governing how they participate in relationships, and how implicit knowledge is made explicit through qualifiers that allow inferencing over relationships properties. A standard language for representing an ontology on the web is the W3C standard OWL.

See W3C Semantic Web Website

Semantic Model:

Another way of referring to Ontology, usually used in the context of IT solutions that employ an ontology an execution time.

A semantic model in which relationships (associations between items) are explicity named and differentiated is call ontology. Because relatiobships are specified, there is no longer a need for strict strucuture that encompasses or defines the relationships. The model essentially becomes a network of connections with each connection having an association independent from any other connection.

Semantic Web:

An evolution of the Web to a web in which meaning can be exchanged and mediated to provide machine-to-machine and more effective human-to-machine interaction. Descrived as "a common framework that allows data to be shared and reused across application, enterprise, and community boundaries. It is a collaborative effort lead by W3C with participation from a large number of researchers and industrial partners. It is based on the Resources Description Framework (RDF), which integrates a variety of applications using XML for syntax and URIs for naming.

See W3C Semantic Web Website

Semantic Web Technology:

Semantic Web Technology is the technology that is enabling the Semantic Web and refers to technologies such as RDFRDFS, and Owl.

See W3C for RDF, RDFS, and OWL

Service-Oriented Architecture (SOA): See Multiple Definitions by Organizations Below.

A Service-Oriented Architecture (SOA) defines how two computing entities interact in such a way as to enable one entity to perform a unit of work on behalf of the another entity. The unit of work is refered to as a service, and the service interactions are defined using a description language. Each interaction is self-contained and loosley coupled, so that each interaction is independent of any other interaction.


A tree-like hierarchical structure of information. Taxonomies are often used by Internet portals (such as Yahoo!), online catalogs, and Web stores to categorize information and to offer consistent navigation. Taxonomical hierarchies provide an ordered connection between each item in the strucuture and the item or items below it.

Unified Modeling Language (UML):

Developed by the Object Management Group, UML is a visual language for specifying and documenting models of software systems, including their strucuture and design. UML is supported by many development tools.

See the OMG UML Website

Web Service:

A software application whose interfaces and binding are capable of being defined, described, and discovered through industry-standard XML protocols, such as SOAP, WSDL, and UDDI.

SOA Defined by OMG, Oasis, Open Group, W3C, and Wikipedia:

OMG: Service Oriented Architecture is an architectural style for a community of providers and consumers of services to achieve mutual value, that:

  • Allows participants in the communities to work together with minimal co-dependence or technology dependence
  • Specifies the contracts to which organizations, people and technologies must adhere in order to participate in the community
  • Provides for business value and business processes to be realized by the community
  • Allows for a variety of technologies to be used to facilitate interactions within the community

Oasis: Service Oriented Architecture (SOA) is a paradigm for organizing and utilizing distributed capabilities that may be under the control of different ownership domains.

  • In general, entities (people and organizations) create capabilities to solve or support a solution for the problems they face in the course of their business. It is natural to think of one person’s needs being met by capabilities offered by someone else; or, in the world of distributed computing, one computer agent’s requirements being met by a computer agent belonging to a different owner. There is not necessarily a one-to-one correlation between needs and capabilities; the granularity of needs and capabilities vary from fundamental to complex, and any given need may require the combining of numerous capabilities while any single capability may address more than one need. The perceived value of SOA is that it provides a powerful framework for matching needs and capabilities and for combining capabilities to address those needs.

Open Group: An architectural style that supports service orientation Service orientation.

  • A way of a way of thinking in terms of services and service based development and the outcomes that services bring Service
  • A logical representation of a repeatable business activity that has a specified outcome (e.g., check customer credit; provide weather data, consolidate drilling reports), is self-contained and maybe composed of other Services. It is a black box to consumers of the 
    Service Architectural Style
  • The combination of distinctive features in which Enterprise Architecture is done, or expressed The SOA Architectural style’s distinctive features: Based on the design of the services comprising an enterprise’s (or inter-enterprise) business processes. Services mirror real-world business activity
  • Service representation utilizes business descriptions. Service representation requires providing its context (including business process, goal, rule, policy, service interface and service component) and service orchestration to implement service Has unique requirements on infrastructure. Implementations are recommended to use open standards, realize interoperability and location transparency. Implementations are environment specific, they are constrained or enabled by context and must be described within their context. Requires strong governance of service representation and implementation Requires a “Litmus Test", which determined a “good services”

W3C: A Service Oriented Architecture (SOA) is a form of distributed systems architecture that is typically characterized by the following properties:

  • Logical view: The service is an abstracted, logical view of actual programs, databases, business processes, etc., defined in terms of what it does, typically carrying out a business-level operation.
  • Message orientation: The service is formally defined in terms of the messages exchanged between provider agents and requester agents, and not the properties of the agents themselves. The internal structure of an agent, including features such as its implementation language, process structure and even database structure, are deliberately abstracted away in the SOA: using the SOA discipline one does not and should not need to know how an agent implementing a service is constructed. A key benefit of this concerns so-called legacy systems. By avoiding any knowledge of the internal structure of an agent, one can incorporate any software component or application that can be "wrapped" in message handling code that allows it to adhere to the formal service definition.
  • Description orientation: A service is described by machine-processable meta data. The description supports the public nature of the SOA: only those details that are exposed to the public and important for the use of the service should be included in the description. The semantics of a service should be documented, either directly or indirectly, by its description.
  • Granularity: Services tend to use a small number of operations with relatively large and complex messages. Network orientation: Services tend to be oriented toward use over a network, though this is not an absolute requirement.
  • Platform neutral: Messages are sent in a platform-neutral, standardized format delivered through the interfaces. XML is the most obvious format that meets this constraint.



February 22 2006

  • Agenda:
    • Welcome and Introductions
    • Review Purpose, Chronology, Suggested Structure, Connections to the FEA SRM, and Responses
    • Open Discussion: Who is missing?, etc.
    • May 23-24, 2006, DRAFT Conference Agenda - Need to Start Filling This In
    • Other: E.g. Using the Wiki to Build a SOA for E-Government Knowledge Repository
    • Next Meeting: Date and Host?
    • Adjourn
  • Notes:
    • About 10 participants
    • Covered agenda items with discussion
    • May 23-24th Agenda Comment/Suggestion Period Open Until March 1st COB and Then Registration Opens and Formal Call for Presentations and Vendor Participation Begins
    • Susan Turnbull to provide Wiki training on March 3, 10:30 a.m. - 12 noon
    • Keynote Suggestion: Richard Solley (OMG)
    • Demo Suggestion (runtime SOA): GSA's Financial Management almost ready (MDA for SOA) (Cory), Sandia Labs Health Information Network (Susan), Multi-State Flu Pandemic, Disaster Response (Gerry), etc.
    • What do we mean by "SOA governance" {changing the fundmental way the government does IT systems individually and collectively, using a particular registry, starting in a certain way, etc.)
    • Submit CoP and Conference Purpose, Mission Statements, etc. ASAP
    • Thanks to all for your participation!

March 17 2006


  • Welcome and Introductions
  • Update Since First Meeting and AIC New Organizational StructureCBDI SOA Presentation and SOA CoP Handout, March 16th
  • March 13, 2006, Conference Call-Small Group with IAC SOA and EA SIGs (Meeting Notes)
  • Open Discussion: Questions, etc.
  • May 23-24, 2006, SOA for E-Government Conference, DRAFT Conference Agenda
  • SOA Demo Strawman, Rev 0.1 3/5/06 - Action: Start Core Team to define the plan and refine the specification (Cory Casanave to lead)
  • Other: E.g. Using the Wiki to Build a SOA for E-Government Knowledge Repository
    • How to subscribe to the SOA Community of Practice
      • The SOA Community of Practice is utilizing the soa-forum as our discussion forum. Here's how to join the soa-forum You can read the archive at:
      • The SOA Community of Practice is utilizing soa-demo as a discussion forum within SOA CoP to organize the SOA demonstration at the May 23-24 meeting. Here's how to join the soa-demo You can read the archive at:
      • Anyone can create an account on this Wiki and add content. To do so, simply hit the "Create account" link at the top right of this page and follow the directions.
    • You're invited to join the Wiki orientation telconferences.
  • Next Meeting: At the call of the Co-Chairs or CoP
  • Adjourn

June 8 2006

  • Agenda:
    • 1. Lessons learned from the First Conference
      • Thank you again for putting together an excellent first conference. I look forward to working with you again.
      • I was "wow"ed by the SOA presentations (went through them all) from the recent event. Thank you for sharing the links.
      • I really enjoyed the session as well. Hope to meet you all again soon!
      • Great conference. We had a great two days!
      • I just wanted to let you know the conference was very interesting and provided some interesting perspectives and useful information on SOA. Your efforts are greatly appreciated. Thank you for the opportunity to present at the conference.
      • Thanks for a great conference. If the registration is free, people have no compunction in signing up (and using up a slot) even if there is very little chance that they will actually make it. You might want to think about either charging some nominal fee, or overbooking as much as 2-3 times the available seats.
      • Thank you to everyone for organizing and staging a great conference.
      • Once again - amazingly catalyst moment in time and space. I think many good things are coming from the meeting of the minds for two days that we will point back to as a spark that triggered them.
      • It was a pleasure meeting you this week in DC. Thanks for the invitation and the smart audience.
      • Is there access to the video that was taken?
      • What does SOA stand for here?? (from someone from the KM WG who did not attend)
      • Thank you for providing us with the opportunity. We were honored to participate in this conference. This event received great reviews during the rest of the conference and the audience was particularly impressed with your responses to the Q&A.
      • Are you aware of federal agencies who have written their own Standards, SOPs, or Best-Practices for Web Services security?
      • I enjoyed the panel, too, and I'm glad the conference participants got some value from our observations.
      • Also, I never had the opportunity after the first SOA Forum to offer you my congratulations on a successful event. Please accept them belatedly. I look forward to collaborating with you again in the world of SOA in the future.
    • 2. Ideas for the Second Conference, October 30-31st. See minutes below.
    • 3. Priority Tasks: See minutes below.
      • a. IAC SOA Survey - Results So Far, Encourage More Participation, and When and Where To Report
      • b. Demo - More Vendors, Support Needs, Etc.
      • c. Web Site Content - White Papers, etc.
    • 4. Other - Welcome Your Suggestions
  • Minutes:
    • Main Action: Continue Discussion on SOA Forum leading to Next Conference Call Before End of June to Meet Early July Deadline to Formally Announce October 30-31st Second Conference
    • Greg Lomow: Lead on Themes Like "SOA for the Federal Transition Framework (FTF)," and Taxonomy of Sessions (with Lois Fairclough below)
    • John Weiland: No comments.
    • Greg Hauser: About ten have completed the Beta Survey (eventually at a new Web site for large participation) and report at the Second Conference.
    • Sukumar Dwarkanath: Case Studies, Core Benefits, Lessons Learned, Etc.
    • Cory Casanave: Demo running (October a good target) in say Plenary 2nd Day (Issues: GSA Server, More Vendors, Demo Focus - UI, etc.)
    • Andrew Townley: Focus of Demo Suggestions
    • Lois Fairclough: Agency Priorities Override Attendance - Organize Sessions Better for Reuse - White Paper on Proceedings and Global Grid with Tim Johnson's help - Work on next month and present at Second Conference - Taxonomy to Use in Call for Second Conference
    • Brand Niemann: Keynotes from Microsoft, Oracle, Sun, BEA, etc.

July 25 2006

  • Agenda:
  • See Action Items Below
  • June 8, 2006, Third Meeting: Conference Call
  • Agreed end of June to meet the early July deadline for the formal announcement of the Second Conference.
  • Greg Lomow: Conference Theme, Tracks, and Session Topics
  • Do a better job of grouping presentations that are related to one another so that it makes it easier and more worthwhile for people to breakaway from their "day jobs" and attend at least 1 day of the conference. Of course the trick to making this work is to find the appropriate "taxonomy" for grouping presentations
  • Joe Chiusano: "SOA and X" would mean 2 things: (a) How the disciple has been affected by SOA, or (b) How the discipline can be applied to SOA. An example of (a) would be content management (as I mentioned below), while an example of (b) would be Semantic Technologies - i.e. how Semantic Technologies are applied to SOA. Some examples of technology areas would be: Business Process Management (BPM), Semantic Technologies, Data Architecture, Modeling, and Metadata (can include Data Management under Data Architecture), Content and Document Management, Business Intelligence, etc.
  • Farrukh Najmi: Conference Theme "Towards Dynamic Metadata Driven SOA" and Topics could include: Federated Information Management / Cross Enterprise Data Sharing, Vocabulary Management, Role of Ontologies to annotate Information, and Managing and Governance of Service Artifacts (WSDL, Schema, BPEL)
  • Roy Roebuck: See COLAB
  • Rex Brooks: See COLAB
  • Suggestions Received (not in order of receipt):
    • 1. IAC SOA Survey Status
    • 2. Build on ArchitecturePlus Seminar, July 13th: The Major Issues Facing SOA Moderator: George Thomas, Chief Enterprise Architect, Office of the CIO, GSA, and Panelists: Dr. Chris Harding, Forum Director for SOA and Semantic Interoperability, The Open Group; Ken Laskey, MITRE, OASIS; Jeff Pendleton, Executive Director, SOA Alliance, Integration Consortium; and Ed Seidewitz, OMG, Enterprise Component
    • 3. Joe Chiusano: IBM Developer Works is running a nice synopsis of how to "Achieve semantic interoperability in a SOA" with a reference recognizing the work of Semantic Interoperability Community of Practice (SICoP) which members of Booz Allen have and continue to contribute to. Invite IBM Authors.
    • 4. John Weiland: Debunking the Myths of SOA by Daniel Magid
    • 5. SOA and Mainframes COLAB
    • 6. SOA for Higher Education
    • 7. DoD CoI Forum (July 18, 2006) - SOA Pilots Based on Community Vocabularies
    • 8. Webinar (June 27, 2006): Developing an Effective Enterprise Solution Powered by Service Oriented Architecture - HP, Intel and GCN
    • 9. EA 2006 Conference (September 11-13, 2006): Lots of SOA Abstracts that could not be used
      • Session: 3-4 Best Practices for Driving SOA Adoption With EA Programs 10:15AM - 11:30PM, Tuesday, September 12, 2006
    • 10. Navy SOA Task Force: Tim Johnson and Lois Fairclough
    • 11. Should All Services Be Reusable, Jason Bloomberg, May 31, 2006, ZapThink
    • 12. Open Group (July , 2006): A panel discussion led by SOA luminaries from The Integration Consortium, OASIS, OMG, The Open Group and moderated by Ed Harrington, Executive VP and COO, Data Access Technologies, challenged the audience's perspective on what standards mean for SOA. Prior to this panel discussion, Dr. Christopher Harding, Head of the SOA Working Group, The Open Group outlined the Open Group's perspective that for SOA, standards mean a framework for SOA, that it is based on ontology, and enables model driven interface definition and implementations.
    • 13. October 17-19, 2006, Service Oriented Architecture and Web Services Conference Proposed Collaboration to Bring the Best Content from this Conference to Ours
    • 14. MORE TO BE ADDED
  • Action Items:
    • Planning Committee: Ali Arsanjani, IBM; Cory Casanave, Data Access Technologies; Joe Chiusano, Booz Allen Hamilton; Mark Creighton, Contractor for the Navy DoN CIO; Greg Lomow, Bearing Point and Co-chair; Chuck Mosher, MetaMatrix; Brand Niemann, US EPA and Co-Chair; Ron Schmelzer, ZapThink; and Rick Tucker-MITRE. Did I miss Anyone Who Would like to Do This (Mainly August 18-25th to review proposals and make decisions)
    • Brand - Get Actual Attendance from Rick Tucker
    • Rick Tucker - Ask Mitre Security to Leave Registration Web Site Open (First Come First Serve Until the Limit is Reached)
    • All - Reduce No-shows - Suggestions - PC Promote
    • Greg Lomow Keep Same Basic Format
    • Morning Session Being Organized by Ron Schmelzer and others
    • Brand - Invite Dick Burk - did
    • Mark and Brand - Contact Lois & Tim
    • Track 1: Real World SOA Experiences/Lessons Learned Being Organized by Ali Arsanjani
    • Track 2: SOA for Information Sharing Being Organized by Greg Lomow
    • Track 3: SOA and BPM, MDA, etc. Being Organized by Cory Casanave
    • Track 4: SOA and Metadata Being Organized by Chuck Mosher (with help from Joe Chiusano)
    • Closing Keynote - David Lithicum (to be invited by Joe Chiusano)
Page statistics
1626 view(s) and 5 edit(s)
Social share
Share this page?


This page has no custom tags.
This page has no classifications.