WSD WG Attributes Task Force
30 Jun 2003
Present:
Jeff Mischkinsky OracleWilliam Vambenepe Hewlett-PackardUmit Yalcinalp OracleDavid Snelling GGFPhilippe Le Higaret W3CSanjiva Weerawarana IBM
Regrets:
Steve Graham GGF
Missing:
Jonathan Marsh WSD Chair (Microsoft)
Chair: William
Scribe: William
Contents
Previous Minutes:
No comment/correction. Previous
meeting minutes accepted.
Review of
Action Items:
Philippe verifying with W3C
if Charlie Catlett's statement was sufficient: PENDING
Attribute support in Corba IDL
JeffM presentation of attributes in Corba IDL
Slides at http://www.w3.org/2003/06/27-idl-attr.html
Error in last slide. Updated slides at http://lists.w3.org/Archives/Public/public-ws-desc-state/2003Jun/0072.html
<Philippe> int myattr() does not guarantee
no side effects
<Philippe> Corba objects are stateful
<WilliamV> david: attributes are singular (no minocur/maxocur)
<WilliamV> jeff: corect
<WilliamV> this is achieved
through structs
<WilliamV> attributes are only
possible for simple types since you can't return a struct
as value in corba because of limitation of some programming
languages
Review of Requirements
David walks through the OGSI requirement
list he sent: http://lists.w3.org/Archives/Public/public-ws-desc-state/2003Jun/0061.html
<WilliamV>
Highly Desirable: Whatever the state access mechanisms are, it would be useful
if they can be reused in other contexts, e.g. notification. The OGSI Service
Data model is reused for the notification framework. We can think of "subscribe
to SDE foo" as a push form of "find SDE foo", i.e. a pull model.
<WilliamV>
umit: there can be other operations to access the
attributes
<WilliamV>
Required: We need predefined attributes
<WilliamV>
Required: We need to query across multiple attributes in one service
<WilliamV>
david: could be provided in
domain-specific way
<WilliamV>
william: yes, but would be good in the generic spec
and could meet 80/20 case
<WilliamV>
Required: Ability to restrict access on a per attribute basis
<WilliamV>
Required: Ability to restrict access on a per attribute basis
<WilliamV>
Required: We need the ability to restrict read vs. write access by the client
over the service interface
<WilliamV>
Required: We need the ability to restrict read vs. write access based on the structure
of the value
<WilliamV>
Required: We need the ability to know a (partial) list of attributes at design
time
<WilliamV>
Required: We ability to know type (some) of attributes ahead of time
<WilliamV>
Required: Input/output messages that manipulate attributes need to be validated
against WSDL
<WilliamV>
Highly desirable: The service data model makes a
distinction between a SDE that is absent from one that is present but has the
value nil
<WilliamV>
Highly desirable: If it turns out that W3C defines a
standard mechanism the access attributes, we would like to use these directly
<WilliamV>
Required: Some attributes may occur multiple times
<WilliamV>
discussion on whether this should happen through wrapper elements for
multiple-value attributes
<WilliamV>
Required: There is a need for handling opaque or abstract types
<WilliamV>
Required: Attributes can be inherited through WSDL 1.2 inheritance
<WilliamV>
Required: Support metadata on attributes
<WilliamV>
Required: Attributes need to be of any schema type (simple or complex)
attributes task force meeting is adjourned.
$Date: 2002/02/19