W3C home > Mailing lists > Public > www-ws-desc@w3.org > January 2005

Re: Proposed Changes to the Interface Component, Features and Properties

From: Amelia A Lewis <alewis@tibco.com>
Date: Fri, 28 Jan 2005 18:13:32 -0500
To: Arthur Ryman <ryman@ca.ibm.com>
Cc: www-ws-desc@w3.org
Message-Id: <20050128181332.2ff6314a.alewis@tibco.com>

Arthur,

On Fri, 28 Jan 2005 16:44:37 -0500
Arthur Ryman <ryman@ca.ibm.com> wrote:
> The proposal makes the Component Model more self consistent and helps
> to  make the formal specification clearer.

[snip]
> We really have two concepts here. One is the children Feature and
> Property  components, and the other is the in-scope Feature and
> Property components.  This is very analogous to namespace attributes
> in the Infoset. In Infoset  there are two properties:
> 1. [namespace attributes]
> 2. [in-scope namespaces]
> 
> The [in-scope namespaces] are computed from the [namespace attributes]
> of  the element and the [in-scope namespaces] of the parent.

Thanks, this helps a lot.  All right, then corresponding {in-scope
features} and {in-scope properties} properties would include the
contents of {features} and {properties}, correct?

I think I can live with this formulation, especially as we can point at
the infoset spec as an example.  Objections withdrawn.

(I really should have noticed [namespace attributes] from the start,
shouldn't I?  Please accept my apologies)

Amy!
-- 
Amelia A. Lewis
Senior Architect
TIBCO/Extensibility, Inc.
alewis@tibco.com
Received on Friday, 28 January 2005 23:13:54 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 7 December 2009 10:58:34 GMT