Re: [wsrf] Draft Proposal for Issue Priorities

[Ian Robinson <ian_robinson@uk.ibm.com>]

Since we resolved some of these and created a few more, here's an updated list of issues prioritized in a similar fashion, focussing on those required to make progress on WS-ResourceProperties.



Regards,
Ian Robinson

David Snelling <d.snelling@fle.fujitsu.com> 01/06/2004 17:03

To:        <wsrf@lists.oasis-open.org>         cc:                 Subject:        [wsrf] Draft Proposal for Issue Priorities

Folks,

As promised for the June 7th telecon here is a proposal for how we address
some of the issues on our list.

As we agreed in new Orleans, we will attack RP first, however there are some
issues that address wider concerns that we might want to look at in this
first pass too.

I propose that we knock off the First Group on the June 14th call and be
ready to start on the Second Group. This will mean assigning people to make
proposals to each issue and having them ready to present on the call. We can
address the Nits in the Fourth Group with spare time at the end of calls.

Any issue that appears to need a lot of work (e.g. a lot of preparation
needed or has an element of controversy) we should start to schedule for the
F2F. I believe the (34, 41, & 40) and (46 &47) clusters fall into this
category, but we can see.

Anyway, this should at least get us started on Monday.

First Group - Low Hanging Fruit to get us used to the process

WSRF6:  Describe properties consistently throughout the WS-RF specs

WSRF15: Consider how maxOccurs > 1 can be represented in an example

WSRF16: Add QueryExpressionDialects property

WSRF48: Specify behavior of nillable properties

Second Group - Interesting RP Issues

WSRF21: Consider splitting SetResourceProperties in separate Insert,
        Update and Delete operations
WSRF23: Combine the three operations to retrieve properties into a
        single operation with multiple dialects

WSRF9:  Need an API to list all properties including those allowed
        in an xsd:any
WSRF4:  GetResourceProperty on property document with xsd:any
WSRF27: Add operation to return entire property document

WSRF10: Need mechanism to express metadata on properties such as
        Œread-only¹

WSRF25: Fault messages should indicate which subset of properties
        were modified successfully

WSRF26: No fault defined to indicate invalid values

Third Group - Model Level Issues

WSRF1:  Interface association is lost with the required aggregation model

WSRF34: Need definition of a ŒStateful Resource¹
WSRF41: Is there a way to separate addressing a WS-Resource from the
        rest of the WSRF specification?
WSRF40: Is an EPR the right construct to use to reference a WS-Resource?

WSRF46: Finding WSDL given an EPR
WSRF47: Finding an EPR, given the WSDL

Fourth Group - Nits

WSRF20: Notification message format not clear

WSRF24: Should the XPath evaluations in WSRF specs be made in the
        context of some namespaces defined or not


--

Take care:

    Dr. David Snelling <d.snelling@fle.fujitsu.com>
    Fujitsu Laboratories of Europe
    Hayes Park Central
    Hayes End Road
    Hayes, Middlesex  UB4 8FE

    +44-208-606-4649 (Office)
    +44-208-606-4539 (Fax)
    +44-7768-807526  (Mobile)




#### InterScan_Disclaimer.txt has been removed from this note on July 13, 2004 by Ian Robinson

WSRF-IssuePriorities.doc