OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

soa-rm-editors message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: RE: [soa-rm-editors] consolidated v11 issues andproposeddispositions


Thank you.


*******************************
Adobe Systems, Inc. - http://www.adobe.com
Vice Chair - UN/CEFACT  http://www.uncefact.org/
Chair - OASIS SOA Reference Model Technical Committee
Personal Blog - http://technoracle.blogspot.com/
******************************* 


-----Original Message-----
From: Don Flinn [mailto:flinn@alum.mit.edu] 
Sent: Tuesday, January 31, 2006 10:58 AM
To: peter@justbrown.net
Cc: 'soa-rm-editors'
Subject: RE: [soa-rm-editors] consolidated v11 issues
andproposeddispositions

Sorry

I guess sending documents from under my desk is not a good idea -:)
Here are the figures in jpeg. 

Don

On Tue, 2006-01-31 at 16:44 +0000, Peter F Brown wrote:
> Don:
> with what program(s) can you open these files: it won't open with Mind
> Manager or Visio....
> 
> Peter 
> 
> -----Original Message-----
> From: Don Flinn [mailto:flinn@alum.mit.edu] 
> Sent: 31 January 2006 15:22
> To: Ken Laskey
> Cc: soa-rm-editors
> Subject: Re: [soa-rm-editors] consolidated v11 issues and
> proposeddispositions
> 
> Hi 
> 
> Attached is my first cut at Cmaps with labels.  I'm not yet happy with
the
> verbs I used, but I wanted to get something to the group for comment.
The
> busiest is the Service Interaction Concepts.  To me, at least, the
labels
> give more meaning and understanding to the figures.
> If these appear to be of some use I can send the Cmap files, that is
if
> people are using Cmap. 
> 
> (Scurry, succry - sounds of d flinn hiding under his desk in
anticipation of
> an onslaught of flames :-)
> 
> Don
> 
> On Mon, 2006-01-30 at 20:56 -0500, Ken Laskey wrote:
> > 
> > 
> >
______________________________________________________________________
> > 
> > The attached spreadsheet combines my proposed dispositions, a new 
> > column for Frank's comments on those PDs, and an additional column 
> > with my further comments.  I also included Peter's glossary comments

> > (without issues numbers) at the end.  With the new columns and text 
> > added, I color-coded the rows as follows:
> > 
> > green - Frank accepted my PD or I am accepting his comment.  There
may 
> > be an additional comment for consideration when actually modifying
the 
> > master copy (103).
> > 
> > blue - The PDs and additional comment still need a little discussion

> > to come to closure (12).
> > 
> > red - This probably requires some nontrivial discussion (5).
> > 
> > The numbers in parenthesis above represent the number of issues (out

> > of the 120 total) falling into each category.  Of the five red ones,

> > four have to do with if/how to label the arcs in the figures.  The 
> > other one was issue 446 which asked for some words for Figure 1.
While 
> > I wasn't greatly inspired, I submit the following as a beginning for

> > the text to augment lines 115-116.
> > 
> > Figure 1 shows how a reference model for SOA relates to other 
> > distributed systems architectural inputs.  The concepts and 
> > relationships defined by the reference model are intended to be the 
> > basis for describing references architectures and patterns that will

> > define more specific categories of SOA designs.  Concrete 
> > architectures will be derived from reference architectures and other

> > related models, such as [can't think of example right now], will 
> > fulfill the needs for architectural work.  Architecture is not done
in 
> > isolation but must account for goals, motivation, and requirements 
> > that define the actual problems being addressed.  While reference 
> > architectures can form the basis of classes of solutions, concrete 
> > architectures will define specific solution approaches.
Architecture 
> > also builds on other infrastructure work, such as protocols,
profiles, 
> > specifications, and standards.  SOA implementations combine all of 
> > these, from the more generic architectural principles and 
> > infrastructure to the specifics that define the current needs, and 
> > represent specific implementations that will be built and used in an

> > operational environment.
> > 
> > Note, adding this text relieves the aesthetic problem for issue 445.
> > 
> > One final note:  I didn't comment on or color-code Peter's glossary 
> > issues and these are in addition to the 120, which already include 
> > several glossary items.  I haven't had the fortitude to tackle the 
> > glossary :-)
> > 
> > Ken
> > 
> > P.S.  I assume Frank still has control of the master document and
will 
> > incorporate the changes.
> > 
> > 
> > 
> >
______________________________________________________________________
> > 
> > 
> >
----------------------------------------------------------------------
> > --------------------
> > Ken Laskey
> > MITRE Corporation, M/S H305     phone:  703-983-7934
> > 7515 Colshire Drive                        fax:        703-983-1379
> > McLean VA 22102-7508
> --
> Don Flinn
> President, Flint Security LLC
> Tel: 781-856-7230
> Fax: 781-631-7693
> e-mail: flinn@alum.mit.edu
> http://flintsecurity.com
> 
> 
> 
-- 
Don Flinn
President, Flint Security LLC
Tel: 781-856-7230
Fax: 781-631-7693
e-mail: flinn@alum.mit.edu
http://flintsecurity.com


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]