WSD WG Attributes Task Force
9 Jun 2003
Attendees
Present:
Steve Graham GGFWilliam Vambenepe Hewlett-Packard
Umit Yalcinalp Oracle David Snelling GGF
Regrets:
Philippe Le Hégaret W3C
Missing:
Jonathan Marsh WSD Chair (Microsoft)
Chair: Steve Graham
Scribe: Umit
Contents
Previous Minutes:
<umit> previous meeting minutes accepted.
... action items: umit to
find a CORBA IDL expert by Wednesday from Oracle.
Review of Action Items:
<umit> David Snelling
to propose writeup from OGSI perspective.
Review of Requirements:
<WilliamV>
http://lists.w3.org/Archives/Public/public-ws-desc-state/
<umit> Today's discussion around
requirements:
... http://lists.w3.org/Archives/Public/public-ws-desc-state/2003Jun/0013.html
... William discusses the
requirements posted above.
1.
User should be able to know what their
permissions are on attributes before trying
o
General agreement
2.
Query across attributes (in one
service): what query language?
o
Discussion on what the language should
be. Point made was that this is a
requirement, how we fulfill this (eg Xpath, Xquery) is possible, but not a
requirements discussion.
3.
Ability to know (partial?) list of
attributes at design time
o
Notion of partial is to allow that
dynamic serviceData scenarios can be supported.
4.
Ability to know type of attributes
ahead of time
o
Not all the listed ones may be requirements for this group but can
be used to shape the scope.
o
Typing: design time specification should not restrict use of xsi:type.
5.
Input/output messages that manipulate
attributes can be validated against WSDL
o
Group discusses how the response in the discussion list and the
objections/concerns with respect to creating specific operations for
accessing/manipulating attributes.
o
David points out that using the three different access operations
does not prohibit access in a different way.
o
William: The requirement is to know the messages that need to be
sent to be able to access attributes.
o
DS: A way to express what the attributes are and how to get them
are required. XPath/Query should be allowed. Access should be flexible.
o
DS happy with service data.
6.
Support for static attributes
o
William means nonchangeable attributes (eg constants), not static attributes in Java sense.
7.
Ability to restrict access on a per
attribute basis.
o
William discusses that there is a distinction between how the
service provides access vs what the client/user can
have access on the attributes
8.
Ability to restrict read vs. write
access
o
William says that there are two distinct requirements
9.
Attributes can be inherited through
WSDL 1.2 inheritance
o
agreed
10. Support metadata on attributes (creation date, type, description...)
o
meta-data should be supported, but providing the
exact profile (set of meta-data) may not be in our scope. Name & Type may
be the only ones that are universally applicable
11. Allow bulk retrieval of several attributes in one operation
o
Whether this is multiple by names or a
single “get everything” is to be decided, the requirement would be
addressed by either
12. Attributes can be of any schema type (simple or complex)
o
agreed
... attributes tf meeting is adjurned.
Summary of Action Items
ACTION: items to umit
to find a CORBA IDL expert by Wednesday from Oracle.
$Date: 2002/02/19