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 and proposed dispositions


responses inline.  When we make final decisions, this should be reflected in updated issues spreadsheet that is uploaded to SOA-RM documents.  I don't think the intermediate spreadsheets need be kept.

Ken

On Jan 31, 2006, at 3:23 PM, Duane Nickull wrote:

Ken:

 

My take:

 

All green are accepted – let’s change ASAP.

 

Open:

 

Issue 390 – I do not find the concept of Service interface confusing and recommend no change.  The words are used in accordance with generally accept industry practice (GAIP).

 

I think part of the confusion was the wrong figure.  This should be resolved per issue 503 unless someone can suggest other clarification.  Your opinion is none other is necessary.

Issue 436 – we cannot add names as that constitutes a technical change.  Leave no names for now.  If we want to add them, we can do that for a subsequent revision to the doc which will have to be voted on as CD again.

 

I would think we could add names if these only reflected words in the approved text.  I know Frank has reasons for no names and that is topic for discussion.  If that was resolved in favor of names being added, could we just state we feel this does not represent substantive change and get simple concurrence of TC?

Issue 443 – agree with Frank (reject).  Can be done on subsequent rev.


OK, I had no preference.

 

How about 392?

Issue 446 – not hard to add.  I can word if anyone wants.

 

Frank revised my wording in separate email and that is converging quickly.

Issue 496 – not sure what we need to do here.  Is it solved?

 

I think something like my suggested wording needs to be added to the body of the document.  As I said, a major guidance should not just be an orphan in the abstract.

Issue 465 – recommend accepting proposed text on right.

 

OK, if no other comments on this.

Issues 460, 468 and 401 – all these are minor and editorial.  Recommend we do not change them given we should change as few things as possible.


Issue 468 was not meant to be minor, but I can concur with doing nothing.

 

Issue 472 – should not remove paragraphs given this constitutes a major change.  Unless there is a really strong reason, this should be addressed in a subsequent rev 1.1

 

OK

Issue 498 – Again – should not change anything that is major.  If we need to revise, this can be done in subsequent rev 1.1

 

OK

In general, we cannot change things around too much other than typos and corrections of headings.  A lot fo other changes such as labels constitute a technical change and mean we would have to approve again.  We can do that but it requires a second revisions and CD vote.

 

Duane

 

 

*******************************
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/
*******************************

 


From: Ken Laskey [mailto:klaskey@mitre.org]
Sent: Monday, January 30, 2006 5:57 PM
To: soa-rm-editors
Subject: [soa-rm-editors] consolidated v11 issues and proposed dispositions

 

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





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