OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

wsrf message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Agenda for Monday August 9th Teleconference


Folks,

Ian has been on Holiday and I am now, but this agenda should be pretty  
close to what is needed. Sorry for the late notice.

  Roll Call

  Confirm minute taker.

  Approve minutes of F2F.

  Call for AOB.

  Action Review.

(Bryan) Re-categorize issue 48 as an application note
(AlanW) Create an issue to discuss the creation of a ‘Usage Notes’  
(Primer) document.
(SteveG) Propose text to resolve issue 4
(MartinC) Raise a new issue to address Schema discovery on a dynamic  
property, including the cardinality within the RP document.
(TomM) Write resolution for issue 10.
(MartinC) Raise an issue to elucidate the meaning of ‘default’ to  
(separate this from issue 10).
(Bryan) Move issues 56 through to 60 to ‘open’ state.
(Bryan) Move new issues from the meeting to ‘open’ state.
(Bryan) Raise new issue to describe requirement for aggregation  
operations.
(Bryan) In issue 1, record WSDM’s interest and add the requirement to  
normatively describe the portType aggregations process.
(Igor, Anish and SteveG.) Create new document to abstractly describe  
the implied resource pattern and what it means to satisfy it (etc).
(Sam) Raise a new issue to consider an identity mechanism.
(Chairs) Upload new issue priorities list to web site.

  Accept any new issues to the issue list.

  Discussion Topics identified at the end of our F2F:
	
	-      Requirements document

	-      App notes document

	-      Schedule for the interop

Issue review:

See:  
http://www.oasis-open.org/apps/org/workgroup/wsrf/download.php/8308/ 
WSRF-IssuePriorities.doc
And:  
http://www.oasis-open.org/apps/org/workgroup/wsrf/download.php/8355/ 
WSRF_IssuesList.doc

We should be able to attack:

	WSRF48: Specify behavior of nillable properties
	I believe this was thought to be ok, except that the App-Note needed a  
section on it.

	WSRF1: Interface association is lost with the required aggregation  
model
	This is next, but I haven't seen a proposal on it yet.

Others at the top of the list are:

	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

     WSRF27: Add operation to return entire property document

     WSRF25: Fault messages should indicate which subset of properties
            were modified successfully
    WSRF26: No fault defined to indicate invalid values

     ...

  AOB

  Straggler Roll Call

-- 

Take care:

     Dr. David Snelling < David . Snelling . UK . 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)



[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]