See also: IRC log
<trackbot> Date: 09 February 2010
<Bob> scribe: Alessio Soldano
<Bob> scribenick: asoldano
RESOLUTION: agenda approved
RESOLUTION: minutes approved
currently outstanding action item to be handled at last call
next week we confirm the date for the last calls
katy: don't know if IBM can join F2F in France
<asir> where is that?
<asir> okay
<asir> How about east or west coast?
<Dug> http://www.w3.org/Bugs/Public/show_bug.cgi?id=8160
RESOLUTION: 8160 resolved with combination of comments 1 and 2
<Dug> zip: http://lists.w3.org/Archives/Public/public-ws-resource-access/2010Jan/att-0194/wseventing-8271.zip
RESOLUTION: 8271 resolved with the proposal on comment #1
<Dug> zip: http://lists.w3.org/Archives/Public/public-ws-resource-access/2010Feb/att-0006/wst_8298.zip
RESOLUTION: 8298 resolved with the proposal on comment #1
<Dug> zip: http://lists.w3.org/Archives/Public/public-ws-resource-access/2010Feb/att-0005/wsenum-8304.zip
katy: propose to use something
different from "ought not to" in introduction
... perhaps with a re-wording
... of the sentence
<Dug> In general, the ordering or completeness of the enumeration is not significant;
<gpilz> In general, the ordering or completeness of the enumeration is not guaranteed;
<gpilz> In general, the ordering or completeness of the enumeration is undefined;
<Dug> In general, the ordering or completeness of the enumeration is undefined; the returned data items represent a selection by the data source of items it wishes to present to that consumer at that time in that order, with no guarantee that every available item is returned or that the order in which items is returned has any semantic meaning whatsoever (of course, any specific data source can provide strong guarantees, if so desired).
<Dug> The ordering or completeness of the enumeration is undefined; the returned data items represent a selection by the data source of items it wishes to present to that consumer at that time in that order, with no guarantee that every available item is returned or that the order in which items is returned has any semantic meaning whatsoever (of course, any specific data source can provide strong guarantees, if so desired).
bob: last line acceptable?
... accepted change
ram: propose to leave SHOULD NOT instead of MUST NOT on section 3.2
katy: want to think about this some more
<Dug> +1 to Tom!
<Dug> The consumer MUST NOT issue additional Pull request messages after a Pull response containing a wsen:EndOfSequence element has been received.
Tom: change returned to received
accepted modified text
<Dug> Upon successful processing of a Pull request message, a data source MUST return a Pull response message of the following form:
<Dug> Upon successful processing of a Release request message, a data source MUST return a Release response message, of the following form:
<Dug> Upon successful processing of a Release request message, a data source MUST return a Release response message of the following form:
bob: above changes to be added to the proposal (1st and 3rd)
<Dug> Upon successful processing of an Enumerate request message, a data source MUST create an enumeration context and return that context in an Enumerate response message of the following form:
bob: change above in section 3 approved too
RESOLUTION: 8304 resolved with comments from 1 to 5
<Dug> zip: http://www.w3.org/2002/ws/ra/10/02/moap.zip
<asir> Bootstrap case is spelled out at http://www.w3.org/2002/ws/ra/edcopies/wsmex.html#Bootstrapping-Metadata-Retrieval
<Tom_Rutt> q
bob: more time for the proposal to be
analysed has been requested
... issues without proposal might be proposed for closing with no
action next week
bye