This document is also available in these non-normative formats: .
Copyright © @@@@ W3C® (MIT, ERCIM, Keio), All Rights Reserved. W3C liability, trademark, document use and software licensing rules apply.
This document describes Web Services Description Language (WSDL) Version 1.2 Properties and Features
This document is an editors' copy that has no official standing.
1. Introduction
2. Feature components
3. Dummy reference section to let the document validate
4. References
A. Acknowledgements (Non-Normative)
B. Change Log (Non-Normative)
1. Introduction
1.1 Notational Conventions
2. Feature components
2.1 Feature
2.1.1 The Feature Component
2.1.2 XML Representation of Feature Component
2.1.2.1 uriattribute information item with feature [owner]
2.1.2.2 requiredattribute information item with feature [owner]
2.1.3 Mapping Feature's XML Representation to Component Properties
2.2 Property
2.2.1 The Property Component
2.2.2 XML Representation of Property Component
2.2.2.1 uriattribute information item with property [owner]
2.2.2.2 valueelement information item with property [parent]
2.2.2.3 constraintelement information item with property [parent]
2.2.3 Mapping Property's XML Representation to Component Properties
3. Dummy reference section to let the document validate
3.1 Language Extensibility (Part1)
3.2 Documentation (Part1)
4. References
4.1 Normative References
4.2 Informative References
A. Acknowledgements (Non-Normative)
B. Change Log (Non-Normative)
B.1 Changes
The SOAP 1.2 specification defines extensibility in terms of "features" [SOAP 1.2 Part 1: Messaging Framework]. Features are abstractly defined pieces of functionality which generally extend the basic SOAP processing model with semantics such as "security", "correlation", or "routing" among others.
Features are typically described by an abstract "distributed state machine" which operates on XML-like "properties" which act as virtual inputs and outputs to whatever processing occurs (see [SOAP 1.2 Part 1: Messaging Framework]). These properties and descriptions are bound to specific "on the wire" syntax and semantics in the specifications for SOAP modules and bindings, the pieces of SOAP processors which concretely implement features.
This documents allows services to indicate:
That a given feature is available for use. For instance, "I understand Joe-Bob's correlation module, so using it will likely get you good results".
That a given feature is required for a particular service or operation. For instance, "you had better be using WS-Routing when you talk to me".
The values for properties associated with particular features. For instance, "the MEP should be set to request-response".
The keywords "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [IETF RFC 2119].
A feature component describes a particular feature that a Web service accepts or requires in particular interactions. Features can be engaged in inbound, outbound messages, or both. Features in the feature component are identified by their URI. Unless otherwise specified, recognizing a feature's URI is assumed to be semantically equivalent to understanding the feature's specification.
The properties of the Feature Component are as follows:
{name} A URI as defined by [IETF RFC 2396].
{required} A boolean value.
The XML representation for a feature definition component is an element information item with the following Infoset properties:
A [local name] of feature
A [namespace name] of "http://www.w3.org/@@@@/@@/wsdl"
One or more attribute information items amongst its [attributes] as follows:
A uri attribute information item as described below in 2.1.2.1 uriattribute information item with feature [owner].
An optional required attribute information item as described below in 2.1.2.2 requiredattribute information item with feature [owner].
Zero or more namespace qualified attribute information items. The [namespace name] of such attribute information items MUST NOT be "http://www.w3.org/@@@@/@@/wsdl".
Zero or more element information items amongst its [children], in order as follows:
An optional documentation element information item (see 3.2 Documentation (Part1)).
Zero or more namespace qualified element information items amongst its [children]. Such element information items MUST be a member of one of the element substitution groups related to features described in 3.1 Language Extensibility (Part1).
uri attribute information item with feature [owner]
The uri attribute information item specifies the URI of the feature.
The uri attribute information item has the following
Infoset properties:
A [local name] of uri
A [namespace name] which has no value
The type of the uri attribute information item is xs:anyURI .
required attribute information item with feature [owner]
The required attribute information item specifies whether the use of the feature
is mandatory or optional.
The required attribute information item has the following
Infoset properties:
A [local name] of required
A [namespace name] which has no value
The type of the required attribute information item is xs:boolean .
The mapping between the properties of the Feature Component (see
2.1.1 The Feature Component) and the XML Representation of
the feature element information item (see 2.1.2 XML Representation of Feature Component) is
as described in Table 1.
| Property | Mapping |
|---|---|
| {name} | The actual value of the uri attribute information item |
| {required} |
If the value of the required attribute information item is
"true" or "1",
then "true", otherwise "false".
|
A property component describes the set of possible values for a particular property. The permissible values are specified by references to a Schema description. A property is typically used to control a feature's behaviour. Properties, and hence property values, can be shared amongst features.
The properties of the Property Component are as follows:
{name} A URI as defined by [IETF RFC 2396].
{value constraint} A type definition constraining the value of the property.
The XML representation for a property definition component is an element information item with the following Infoset properties:
A [local name] of property
A [namespace name] of "http://www.w3.org/@@@@/@@/wsdl"
One or more attribute information items amongst its [attributes] as follows:
A uri attribute information item as described below in 2.2.2.1 uriattribute information item with property [owner].
Zero or more namespace qualified attribute information items. The [namespace name] of such attribute information items MUST NOT be "http://www.w3.org/@@@@/@@/wsdl".
One or more element information items amongst its [children], in order as follows:
One element information item from among the following:
A value element information item as described in 2.2.2.2 valueelement information item with property [parent]
A constraint element information item as described in
2.2.2.3 constraintelement information item with property [parent]
An optional documentation element information item (see 3.2 Documentation (Part1)).
Zero or more namespace qualified element information items amongst its [children]. Such element information items MUST be a member of one of the element substitution groups related to properties described in 3.1 Language Extensibility (Part1).
uri attribute information item with property [owner]
The uri attribute information item specifies the URI of the property. It has the following
Infoset properties:
A [local name] of uri
A [namespace name] which has no value
The type of the uri attribute information item is xs:anyURI .
value element information item with property [parent]
The value element information item specifies the value of the property.
It has the following
Infoset properties:
A [local name] of value
A [namespace name] of "http://www.w3.org/@@@@/@@/wsdl"
The type of the value element information item is xs:anySimpleType .
constraint element information item with property [parent]
The constraint element information item specifies a constraint on the value
of the property. It has the following
Infoset properties:
A [local name] of constraint
A [namespace name] of "http://www.w3.org/@@@@/@@/wsdl"
The type of the constraint attribute information item is xs:QName .
The mapping between the properties of the Property Component (see
2.2.1 The Property Component) and the XML Representation of
the property element information item (see 2.2.2 XML Representation of Property Component) is
as described in Table 2.
| Property | Mapping |
|---|---|
| {name} | The actual value of the uri attribute information item |
| {value constraint} | If the constraint element information item is present, the type referred to by the value of this element information item.
Otherwise, if the value element information item is present, an anonymous simple type, whose
base type is "xs:anySimpleType", with a single "enumeration"
facet whose value is that of the element information item. Otherwise, "xs:anySimpleType".
|
This document is the work of the W3C Web Service Description Working Group.
Members of the Working Group are (at the time of writing, and by alphabetical order): Adi Sakala (IONA Technologies), Allen Brookes (Rogue Wave Softwave), Amelia Lewis (TIBCO/Extensibility), Arthur Ryman (IBM), Ingo Melzer (DaimlerChrysler Research and Technology), Dale Moberg (Cyclone Commerce), Dan Kulp (IONA Technologies), Daniel Schutzer (Citigroup), Dave Solo (Citigroup), David Booth (W3C), Dietmar Gaertner (Software AG), Don Mullen (TIBCO Software), Erik Ackerman (Lexmark), Glen Daniels (Macromedia), Igor Sedukhin (Computer Associates), Jacek Kopecky (Systinet), Jean-Jacques Moreau (Canon), Jeff Mischkinsky (Oracle Corporation), Jeffrey Schlimmer (Microsoft Corporation), Jerry Thrasher (Lexmark), Johan Pauhlsson (L'Échangeur), Jonathan Marsh (Chair, Microsoft Corporation), Kevin Canyang Liu (SAP), Laurent De Teneuille (L'Échangeur), Lily Liu (webMethods, Inc.), Martin Gudgin (Microsoft Corporation), Michael Champion (Software AG), Michael Mahan (Nokia), Michael Mealling (Verisign), Mike Ballantyne (Electronic Data Systems), Mike Davoren (W. W. Grainger), Mike McHugh (W. W. Grainger), Philippe Le Hégaret (W3C), Prasad Yendluri (webMethods, Inc.), Roberto Chinnici (Sun Microsystems), Sandeep Kumar (Cisco Systems), Sandra Swearingen (U.S. Department of Defense, U.S. Air Force), Sanjiva Weerawarana (IBM), Stefano Pogliani (Sun Microsystems), Stephen White (SeeBeyond), Steve Graham (Global Grid Forum), Steve Lind (AT&T), Steve Tuecke (Global Grid Forum), Tim Finin (University of Maryland), Tom Jordahl (Macromedia), Umit Yalcinalp (Oracle Corporation), Waqar Sadiq (Electronic Data Systems), William Vambenepe (Hewlett-Packard Company), Youenn Fablet (Canon)
Previous members were: Aaron Skonnard (DevelopMentor), Don Wright (Lexmark), Barbara Zengler (DaimlerChrysler Research and Technology), Jochen Ruetschlin (DaimlerChrysler Research and Technology), Joyce Yang (Oracle Corporation), Keith Ballinger (Microsoft), Krishna Sankar (Cisco Systems), Mario Jeckle (DaimlerChrysler Research and Technology), Pallavi Malu (Intel Corporation) William Stumbo (Xerox),
The people who have contributed to discussions on www-ws-desc@w3.org are also gratefully acknowledged.
| Date | Author | Description |
|---|---|---|
| 20030407 | JJM | Refined and corrected the definitions for features and properties. |
| 20030314 | JJM | Fixed markup so document validates. |
| 20030304 | JJM | Filled in blank description of feature and property component. |
| 20030304 | JJM | Filled in introduction, from earlier text from Glen. |
| 20030303 | MJG | Skeleton document |