Web Services Resource Access Working Group Teleconference

08 Dec 2009


See also: IRC log






<trackbot> Date: 08 December 2009

<dug> LOL

<Bob> new music while waiting feature

<dug> Love these picts: http://www.dailymail.co.uk/news/worldnews/article-1234047/Surfs-biggest-waves-years-come-Hawaii-North-Pacific-storm.html

<Bob> scribenick: Li

TOPIC agenda

bob: clarify last call issues can be resolved earlier

agenda agreed

TOPIC minutes of last meeting

minutes approved

TOPIC review of snapshots

scribe: 11/17/2009 revision

snapshots approved and issues therein are closed

<dug> very hard to hear you martin

TOPIC xml security x-path discussion thread

<MartinC> i was on headset mute thats why

bob: two options

asir: we need to look at the technical issues before making decisions

bob: need to make decision before LC

<dug> sorry - was distracted - what are the two options?

yves: changing behavior vs. changing syntax for LC
... cannot change behavior for LC

ram: other group should give us issues to address

bob: to contact fred for issues?


ram: will investigate it for the next meeting

AI: ram to investigate 8176 for the next meeting


<dug> word doc: http://lists.w3.org/Archives/Public/public-ws-resource-access/2009Dec/att-0012/wsmex_sections_7_and_8_for_6463.doc


katy: describe the issue and proposal

<tomrutt> about:blank

<dug> mind:blank

asir: haven't review it yet, but question is...
... does the proposal cover both examples

katy: wouldn't object to putting another example

asir: discuss it next week


<dug> http://www.w3.org/Bugs/Public/show_bug.cgi?id=8200

dug: describe the issue and proposal

<dug> http://www.w3.org/2009/09/ws-mex/Dialects/ws-mex-all

dug: it's a editorial typo

<Zakim> asir, you wanted to point out http://lists.w3.org/Archives/Public/public-ws-resource-access/2009Nov/0056.html

<asir> http://lists.w3.org/Archives/Public/public-ws-resource-access/2009Nov/0056.html

asir: agree it's a typo but also has non-editorial consequence
... the constraint at the table needs to be captured somehow

dug: needs proposed text to proceed

AI: dug to refine proposal for 8200


asir and dug to clarify this issue from ashok

asir: looks ok

bob: any objection to resolving it?
... the issue is resolved

<asir> is there a 3B?


bob: anybody speaking for gil?

ram: should say MUST generate and MAY transmit

dug: should make this global for all specs

AI: ram to define "generate fault" for 8283


bob: any objection to the proposal?
... issue resolved as proposed


<dug> Filtering occurs prior to any formatting of notification messages.

<dug> Context Node: the root of the event XML.

dug: section 2.3 clarifies the issue already

ram: cwna sounds good

bob: issue cwna but needs response to author

AI: dug to respond to issue 8323

<dug> and cc comments list

<Bob> email to reviewer and cc public comments list


bob: any objection?

dug: yes
... confused about the first child element
... need to discuss with gil


dug: describe the issue

bob: any objection?

ram: why need this for enumeration?

dug: same reason for ws-e, as enum items can be empty as well

ram: it's different and will talk with dug in detail


dug: describe the issue
... and propose option 1

ram: what is the reason for option 1?

dug: explain the reason for resource limited devices

ram: looks fine

bob: resolve issue with proposal 1


dug: describe the issue

ram: looks good

bob: issue resolved as proposed


dug: should be consistent with ws-e

bob: issue resolved as proposed


dug: describe the issue

ram: have question
... will do more research


dug: describe the issue

ram: fine with it

bob: issue resolved as proposed


dug: describe the issue
... proposed to remove the sentence

bob: issue resolved as proposed


dug: resolved already


dug/ram: agree in general but needs concrete text

AI: gil to propose concrete text for 8292


dug: what are the differences between two versions of wsdl?

ram: one is a profile of wsdl 1.1 with restrictions
... it's not clear how the profile is applicable to other use cases

asir: bp 1.1 limits wsdl to soap 1.1 and http, not other soap or transports
... not good to take a blank restriction on wsdl 1.1

wu: agree with asir, we should support both bp 1.1 and wsdl 1.1
... suggest cwna

dug: does bp 1.1 limit binding to http only?

ram: is checking bp 1.1

tom: wsdl 1.1 schema is fixed by bp 1.1 schemas
... need to consider the diff on schemas before closing it

asir: can implementations be ws-ra and bp compliant as well?
... there is no blocking for people to implement ws-ra and bp 1.1

bob: is there any wsdl in ws-ra that violates bp 1.1?

dug: profiling wsdl may be too restrictive while fixing it is ok
... ok with cwna after talking with gil

<Wu> wu: ok with cwna

<asir> Asir: ok with CWNA

AI: dug to take comments for cwna to the list




<dug> thanks yves!

<dug> works

<Bob> yves, cat you make a cron job to clear dug?

<dug> LOL

<dug> its pretty consistent about it too

ram: discuss it offline

wu: polling many events is ok while polling for one may be overkill
... could suggest using getstatus instead of mc polling

dug: subscription end provides more info than getstatus

wu: subscription end polling creates a lot overhead

dug: subscription end poll is the same poll for other events

wu: endto is different from notifyto by spec, as the default of endto is "not to send"

dug: sharing EPR is an implementation choice
... spec needs to give choices to implementations

wu: we need to coordinate endto and notifyto
... or treat no-addressable endto as not usable

AI: dug to modify proposal to address concern for 8164

<Ram> Wordsmithing: "Likewise, the wse:EndTo element MAY choose to supportmechanisms, such as the [WS-MakeConnection] specification, to enable delivery of the SubscriptionEnd message from the Subscription Manager."

bob: adjourn 40 sec early


Summary of Action Items

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.135 (CVS log)
$Date: 2009/12/08 21:59:05 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.135  of Date: 2009/03/02 03:52:20  
Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/

Guessing input format: RRSAgent_Text_Format (score 1.00)

Succeeded: s/somhow/somehow/
Succeeded: s/restricting/fixing/
Found ScribeNick: Li
Inferring Scribes: Li

WARNING: No "Present: ... " found!
Possibly Present: AI Asir MartinC Microsoft Sreed Tom_Rutt Wordsmithing Wu_Chou Yves aabb aadd about bob dug fmaciel jeffm joined katy mind ram scribenick tom tomrutt trackbot ws-ra wu
You can indicate people for the Present list like this:
        <dbooth> Present: dbooth jonathan mary
        <dbooth> Present+ amy

Agenda: http://lists.w3.org/Archives/Public/public-ws-resource-access/2009Dec/0019.html

WARNING: No meeting chair found!
You should specify the meeting chair like this:
<dbooth> Chair: dbooth

Found Date: 08 Dec 2009
Guessing minutes URL: http://www.w3.org/2009/12/08-ws-ra-minutes.html
People with action items: 

[End of scribe.perl diagnostic output]