[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
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). 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. Issue 443 – agree with Frank
(reject). Can be done on subsequent rev. Issue 446 – not hard to add. I
can word if anyone wants. Issue 496 – not sure what we need to
do here. Is it solved? Issue 465 – recommend accepting
proposed text on right. 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 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 Issue 498 – Again – should not
change anything that is major. If we need to revise, this can be done in
subsequent rev 1.1 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 ******************************* From: Ken Laskey
[mailto:klaskey@mitre.org] 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. |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]