W3C home > Mailing lists > Public > www-ws-desc@w3.org > June 2004

Issue 197 action: proposed text

From: Amelia A Lewis <alewis@tibco.com>
Date: Wed, 30 Jun 2004 11:08:31 -0400
To: WS Description List <www-ws-desc@w3.org>
Message-id: <20040630110831.28405a0f.alewis@tibco.com>

In fulfillment of the action item given me, here is proposed text for Part
One, which establishes a mechanism whereby the 'requiredness' of a feature
or property may be 'fixed' at a particular scope, and subsequently may not
be overridden.  This solution is slightly broader than the requirement
(that it be possible to establish these in interface, so they couldn't be
overridden in binding) because doing so keeps the component model cleaner
(otherwise, in order to introduce the additional property, we would have
to have a different component model for interface versus binding/service).
 As a consequence, it is possible also for a binding to establish a fixed
requirement that a service/endpoint cannot override.

Explanatory text might be useful, it seems to me.  This really addresses
the problem of predictability, when multiple authors specialize WSDL. 
That is, by setting the feature 'fixed' (whether it is required or
optional), it sets a requirement upon implementors of services to extend
the WSDL in a predictable fashion, such that clients can rely upon
particular features/properties.  I'm not sure where this information
belongs, though; somewhere in the primer?  Is there an appropriate topic
for this sort of problem area in the primer at present?  Should an
explanation of why this is interesting/useful appear in part one?

Section 2.7.1: add bullet

{fixed} A boolean value.  If the {fixed} property is true, then the value
of the {required} property in this scope applies to all contained scopes;
it may not be overridden.

Section add final paragraph

If the value of the {fixed} property is 'true', then the value of the
{required} attribute MUST NOT be changed in any contained scope. 
Subsequent declarations in contained scopes MUST be ignored.

Add section fixed attribute information item with feature [owner]

The fixed attribute information item specifies whether the {required}
property may be overridden in contained scopes or not.

The fixed attribute information item has the following Infoset properties:

    * A [local name] of required
    * A [namespace name] which has no value

The type of the fixed attribute information item is xs:boolean.

Section 2.8.1: add the bullet as in section 2.7.1 addition above

Section add the paragraph as in section addition above

Add section (or insert as, to follow required, and
renumber current .3 and .4), identical to added section above
except that [owner] is 'property' rather than 'feature'

Amelia A. Lewis
Senior Architect
TIBCO/Extensibility, Inc.
Received on Wednesday, 30 June 2004 11:08:59 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 23:06:41 UTC