- From: George Blanck <gsblanck@nyc.rr.com>
- Date: Thu, 6 Feb 2003 10:45:52 -0500
- To: "Mark Baker" <distobj@acm.org>, "Hugo Haas" <hugo@w3.org>
- Cc: <www-ws-arch@w3.org>
Mark, Hugo: I usually stay out of definition discussions since "everyone has an opinion" but in the case of element what is needed is simple clarification whether the term is used as "base element" (as in "elementary particle") or in the generic sense (as in "an element of the solution"). Suggestion: > Architectural Element > > A generic term referring to a part of an architecture such as a component, connector, or data. > Relationships between elements are constrained in order to > achieve a desired set of architectural properties. George Blanck -----Original Message----- From: www-ws-arch-request@w3.org [mailto:www-ws-arch-request@w3.org]On Behalf Of Mark Baker Sent: Thursday, February 06, 2003 10:13 AM To: Hugo Haas Cc: www-ws-arch@w3.org Subject: Re: Glossary - Working UEB Stuff On Wed, Feb 05, 2003 at 06:58:19PM +0100, Hugo Haas wrote: > > Element - RF definition is not really a definition, it is sort of a > > statement that seems to contain an implied definition. UEB definition > > is cryptic. I don't really like either, but I guess I'd go with RF as > > at least being comprehensible. > > I think that Fielding's dissertation excerpt could be reworded as: > > Element > > A part of an architecture (component, connector, or data). > Relationships between elements are constrained in order to > achieve a desired set of architectural properties. I'd suggest calling this an "Architectural Element". Then instead of "part" you could just use "element". MB -- Mark Baker. Ottawa, Ontario, CANADA. http://www.markbaker.ca Web architecture consulting, technical reports, evaluation & analysis
Received on Thursday, 6 February 2003 11:00:24 UTC