Attributes Task Force Progress Report WSD Attributes Task Force November 4 th, 2003 WSDL F2F

Directions From Last F2F Requirements From the WG: –No Additions To Component Model –Use style attribute to mark operations for attribute access, ie getter/setters. –Only Individual Access operations be defined by WSDL wg Present it today

Results No New Components in the Component Model Attribute Concept => Data Query Methods for GEDs We introduce two different style URIs Even proved syntactic sugar is possible for ease of development

A GED example

Style: Get (1) Two wrapper elements for a GED (attribute)

Style: Get (2) Operation that uses these two wrapper elements <ws:interface name="MyInterface" xmlns:wrappers="Wrappers"> <ws:operation name="get_XXX"

Style: Set (1) Two wrapper elements for a GED in schema <!– Single child via reference

Style: Set (2) Operation uses the defined wrapper elements <ws:operation name=set_XXX"

Rules Let ф represent the name of a GED, e.g. XXX. Use the name convention for the operations on GED –get_ ф for readable –set_ ф to represent writeable. –Must refer to the same attribute by wrappers (via ref) The style attribute has the corresponding value –Get –Set Pattern URI for the operation must be in/out Wrapper definitions must not contain schema attributes The operations may contain {in|out} faults.

Syntactic Sugar Shortcut extension to generate operations that define get/set style Not Required as part of the style, but nice to have. <wsdlx:attribute elementReference=attributes:XXX" access="read-write"/>

Attribute Defn is in Syntactic Sugar not in Component Model <xs:attribute name="elementReference" type="xs:QName" use="required"/> <xs:attribute name="access" type="attributes:accessValues" use="required"/>

Result Simple Consistent with RPC style, can be used with language bindings (but not limited to) No new components! Also a well defined syntactic sugar exists to make use of attribute definition shortcut: Allows more complicated styles to be built