soa-forum
[Top] [All Lists]

Re: [soa-forum] Question/Issue for the SOA CoP

To: "Service-Oriented Architecture CoP" <soa-forum@xxxxxxxxxxxxxx>
From: "John, Anil" <Anil.John@xxxxxxxxxx>
Date: Fri, 13 Oct 2006 14:15:01 -0400
Message-id: <AA78D806E90D1946A604A61827E77048A6BDA2@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
Indeed! Thanks for reminding me, Ken :-)    (01)

Regards,    (02)

- Anil (The person who needs to make some of those updates)     (03)

:- 
:- Anil John 
:- Johns Hopkins University - APL 
:- http://www.jhuapl.edu 
:- (240) 228-0612 
:- 
:- E-Mail Response Time: 24 hrs 
:-    (04)

-----Original Message-----
From: soa-forum-bounces@xxxxxxxxxxxxxx
[mailto:soa-forum-bounces@xxxxxxxxxxxxxx] On Behalf Of Ken Laskey
Sent: Friday, October 13, 2006 9:56 AM
To: Service-Oriented Architecture CoP; Service-Oriented Architecture CoP
Subject: Re: [soa-forum] Question/Issue for the SOA CoP    (05)

Just to continue Rex's point, there is an active discussion in 
progress that relates to governance, among the many other aspects.  I 
expect the governance page to have significant changes in the near
future.    (06)

Ken    (07)

At 09:00 AM 10/13/2006, Rex Brooks wrote:
>Hi Brand, Everyone,
>
>This is a topic the OASIS SOA Reference Model Technical Committee's
>Reference Architecture Subcommittee is working on in concert with the
>other issues pertaining to the Reference Architecture we are building
>to flesh-out the Reference Model. Here is the wiki page for the topic:
>
>http://wiki.oasis-open.org/soa-rm/TheArchitecture/Governance
>
>We are an open, public effort and encourage more participation, which
>anyone can join through your company/employer organization if your
>company/employer organization is an OASIS member, or through an
>individual membership. You can discover more information at
>
>http://www.oasis-open.org/committees/join.php
>
>Cheers,
>Rex
>
>
> >I have been asked about the ownership/governance issue and whether
> >any best practices exist for SOA. We covered governance in the First
> >SOA Conference for E-Government, but I don't recall specifically
> >ownership being discussed. Any suggestions, references, etc. would
> >be appreciated.
> >
> >
> >
> >Thanks, Brand
> >
> >
> >  _________________________________________________________________
> >Subscribe/Unsubscribe/Config:
> >http://colab.cim3.net/mailman/listinfo/soa-forum/
> >Shared Files: http://colab.cim3.net/file/work/soa/
> >Community Portal: http://colab.cim3.net/
> >Community Wiki:
http://colab.cim3.net/cgi-bin/wiki.pl?AnnouncementofSOACoP
>
>
>--
>Rex Brooks
>President, CEO
>Starbourne Communications Design
>GeoAddress: 1361-A Addison
>Berkeley, CA 94702
>Tel: 510-849-2309
>  _________________________________________________________________
>Subscribe/Unsubscribe/Config: 
>http://colab.cim3.net/mailman/listinfo/soa-forum/
>Shared Files: http://colab.cim3.net/file/work/soa/
>Community Portal: http://colab.cim3.net/
>Community Wiki:
http://colab.cim3.net/cgi-bin/wiki.pl?AnnouncementofSOACoP    (08)

--    (09)

------------------------------------------------------------------------
---------
   /   Ken 
Laskey                                                                \
  |    MITRE Corporation, M/S H305    phone:  703-983-7934   |
  |    7515 Colshire Drive                    fax:      703-983-1379   |
   \   McLean VA 22102-7508
/    (010)

------------------------------------------------------------------------
----------     (011)


 _________________________________________________________________
Subscribe/Unsubscribe/Config:
http://colab.cim3.net/mailman/listinfo/soa-forum/
Shared Files: http://colab.cim3.net/file/work/soa/
Community Portal: http://colab.cim3.net/
Community Wiki:
http://colab.cim3.net/cgi-bin/wiki.pl?AnnouncementofSOACoP
 _________________________________________________________________
Subscribe/Unsubscribe/Config: http://colab.cim3.net/mailman/listinfo/soa-forum/
Shared Files: http://colab.cim3.net/file/work/soa/
Community Portal: http://colab.cim3.net/
Community Wiki: http://colab.cim3.net/cgi-bin/wiki.pl?AnnouncementofSOACoP    (012)
<Prev in Thread] Current Thread [Next in Thread>