W3C home > Mailing lists > Public > www-wsa-comments@w3.org > February 2003

[ISSUES] Issue #8 - proposed resolution

From: <Daniel_Austin@grainger.com>
Date: Mon, 3 Feb 2003 15:29:26 -0600
To: dmh@contivo.com, hugo@w3.org, Mike.Champion@SoftwareAG-USA.com, Tom_Carroll@grainger.com, www-ws-arch@w3.org, www-wsa-comments@w3.org
Message-ID: <OF4A4C25E1.B59807ED-ON86256CC2.007607BA@grainger.com>


      Per my action item from the previous f2f meeting, I have an action
item to propose a resolution for issue #8 [1]. This proposal is intended to
comply with the WSA Issues Process [2].

      Issues #7-12 are all from a single email from Joseph Reagle
(reagle@w3c.org). An individual email response will be crafted for each
individual issue in accordance with the Issues Process [2]. This is the
proposed response to #8.

<original comment>
 AC008 is                                                                                             |                 |
 consistent and                                                                                       |                 |
 coherent. This                                                                                       |                 |
 applies to both                                                                                      |                 |
 the reference                                                                                        |                 |
 architecture                                                                                         |                 |
 itself and the                                                                                       |                 |
 document that                                                                                        |                 |
 contains its                                                                                         |                 |
 definition.                                                                                          |                 |
                                                                                                      |                 |
                                                                                                      |                 |
 What is a                                                                                            |                 |
 "reference                                                                                           |                 |
 architecture"?                                                                                       |                 |

</original comment>

<proposed response>
Dear Mr. Reagle,

      Thank you very much for your comment to the WSA Working Group. We
very much appreciate your time and effort in sending us this comment. Your
comment has been added to the WSA Issues List [1] and will be resolved
according to the WSA Issues process [2]. In your email, there were several
comments, which have been assigned issue IDs #7-12. Each of these comments
has been scheduled to be addressed individually.

      Regarding your question "What is a reference architecture?": the term
"reference architecture" is defined in the Web Services Glossary document
[3]. I quote:

reference architecture
      A reference architecture is the generalized architecture of several
      end systems that share one or more common domains. The reference
      architecture defines the infrastructure common to the end systems and
      the interfaces of components that will be included in the end
      systems. The reference architecture is then instantiated to create a
      software architecture of a specific system. The definition of the
      reference architecture facilitates deriving and extending new
      software architectures for classes of systems. A reference
      architecture, therefore, plays a dual role with regard to specific
      target software architectures. First, it generalizes and extracts
      common functions and configurations. Second, it provides a base for
      instantiating target systems that use that common base more reliably
      and cost effectively.

      Using the Architecture Tradeoff Analysis Method(SM) to Evaluate a
      Reference Architecture: A Case Study, B. Gallagher, June 2000 (See

            Again, thank you for your comment.


</proposed response>

[1] http://www.w3.org/2002/ws/arch/2/issues/wsa-issues.html#x6

[2] http://www.w3.org/2002/ws/arch/2/04/wd-wsa-issues-process-20020426

[3] http://www.w3.org/TR/2002/WD-ws-gloss-20021114/

Dr. Daniel Austin
Sr. Technical Architect / Architecture Team Lead
daniel_austin@notes.grainger.com <----- Note change!
847 793 5044
Visit http://www.grainger.com
Received on Monday, 3 February 2003 16:29:21 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 19:40:41 UTC