19:27:50 RRSAgent has joined #ws-ra 19:27:50 logging to http://www.w3.org/2010/05/04-ws-ra-irc 19:27:52 RRSAgent, make logs public 19:27:52 Zakim has joined #ws-ra 19:27:54 Zakim, this will be WSRA 19:27:54 ok, trackbot; I see WS_WSRA()3:30PM scheduled to start in 3 minutes 19:27:55 Meeting: Web Services Resource Access Working Group Teleconference 19:27:55 Date: 04 May 2010 19:28:05 asoldano has joined #ws-ra 19:28:18 WS_WSRA()3:30PM has now started 19:28:24 +Bob_Freund 19:29:36 +??P11 19:30:16 DaveS has joined #ws-ra 19:30:30 Hello, Dave the scribe 19:30:33 Vikas has joined #ws-ra 19:30:34 +Gilbert_Pilz 19:30:44 +Doug_Davis 19:30:53
  • li has joined #ws-ra 19:31:15 Tom_Rutt has joined #ws-ra 19:31:18 +Wu_Chou 19:31:43 +Tom_Rutt 19:33:17 +asoldano 19:33:37 + +1.646.361.aaaa 19:33:51 scribenick: DaveS 19:34:17 someone is pounding hard on their keyboard 19:34:22 agenda: http://lists.w3.org/Archives/Public/public-ws-resource-access/2010May/0003.html 19:35:17 +MartinC 19:35:23 Ashok has joined #ws-ra 19:35:27 +Yves 19:35:33 MartinC has joined #ws-ra 19:35:58 Scribe: Daves 19:36:01 +Ashok_Malhotra 19:36:10 Agenda Approved. 19:36:19 Minutes approved. 19:36:55 Topic New Issues 19:36:57 and: http://www.w3.org/Bugs/Public/show_bug.cgi?id=9655 19:37:32 9607 - 9613 Accepted as New issues 19:37:47 9655 accepted as a new issue 19:37:59 9588 accepted as a new issue 19:38:03 +1 to proposal for 9588 19:38:07 +[Microsoft] 19:38:37 Resolved 9588 Resolved as proposed. 19:38:53 + +1.408.970.aabb 19:39:00 Topic F2F Meeting 19:39:10 Fred Joined. 19:39:32 breakfast? 19:39:41 Start each day at 9:00 (Ram will let people in from 8:00) 19:40:03 phew! :-) 19:40:09 Fred_Maciel has joined #ws-ra 19:40:11 Breakfast will be provided. 19:40:12 woo hoo! 19:40:35 Topic Next F2F 19:40:40 ram will FedEX it :-) 19:40:47 ;) 19:40:50 Proposal from Bob to leave it open. 19:42:00 To be discussed at the F2F. Expected to be inline with the normal 6 to 8 weeks cadence. 19:43:23 I'd prefer if the next f2f were an interop 19:43:58 F2F meeting discussion time will be announced in time for EU people to make sure they can dial in 19:44:19 Topic 9567 19:45:02 Gil is working on a new approach to this issue. 19:45:15 Should be no problem for the F2F. 19:45:38 Topic 9568 19:45:58 There seems to be little discussion on this one. 19:46:20 May be due to discussion on other issues. 19:46:31 Topic 9087 19:46:50 Proposal from Doug to limit the scope of a resource 19:47:04 Latest note on this: http://lists.w3.org/Archives/Public/public-ws-resource-access/2010May/0005.html 19:47:07 Bob (the proposer) is mostly OK with it. 19:47:42 q+ 19:48:19 A friendly ammendnent that UTF both modes 8 and 16 also be supported. 19:48:27 ack tom 19:48:31 q+ 19:48:48 The XML 1.0 spec states that 8 and 16 are required. 19:48:56 ack dug 19:49:28 Doug's proposal states that the 8 and 16 issues is applied to all specs. 19:49:34 it's already there by reference to XML 1.0, duplicating XML 1.0 spec using a MUST is not good 19:50:03 There is a difference between sender and receiver in the UFT encoding question. 19:51:00 - +1.646.361.aaaa 19:51:05 XML 1.0 specifies that it must be supported, but there are other parts of the system that also need to comply. 19:51:28 Ram has joined #ws-ra 19:51:50 Tom: Receiver MUST accept both. 19:53:39 Sender may typically send either and the receiver must understand both. 19:54:35 Gil: This it really only a problem with fragment, since the normal transfer puts the whole thing. 19:54:43 you may require a specific encoding using ws-policy, but the policy is not defined for that, yet. 19:55:08 q+ 19:55:10 Bob: But what if the 16 version come in a GET to a clinet that would rather have 8 only. 19:55:13 I'm lost as to the current proposal 19:55:41 it sounds a bit like everyone is agreeing and yet the conversation still goes on .... 19:55:45 daveS: Agrees with Dug. 19:56:03 Implementations are expected to support both UTF-8 and UTF-16 as described in XML 1.0. 19:56:21 in compliance section for all specs 19:56:23 a client implementation may take the get response, in utf-16, parse it into a dom tree, and when they send it back the dom tree will be encoded in utf-8. The sending is an implementation specific matter 19:56:27 proposal: add a note the the specs that implementations must support 8 and 16 as described in XML 1.0. 19:57:15 Tom: it is only the receiver that matters. 19:58:28 Tom: Both schemes will handle both. 19:59:02 Please satisfy the 3 Japanese guys in a bar in Kawasaki. 19:59:06 Agreed. 19:59:21 Resolved as proposed. 19:59:29 Guess we don't care about gals in those bars 20:00:22 Topic 9558 20:01:05 The issue includes a sketch of a proposal. 20:01:43 This may be specific to frag only. 20:02:31 The content of the Frag spec would define the subset in question. 20:02:56 XPath Level 1 is a lightweight subset 20:03:27 q 20:03:37 q+ 20:04:12 ack tom 20:04:19 This provides at least two levels of support in support of small servers. 20:04:57 The important issue here is that the server is the small light weight device in this case. 20:05:07 E.g. a lightbulb. 20:05:30 eeekkk a lightbulb supporting soap! scary! 20:05:34 We lost Gill. 20:05:39 -Gilbert_Pilz 20:05:43 +Gilbert_Pilz 20:05:59 Gil is back. 20:07:43 q+ 20:08:09
  • li has joined #ws-ra 20:08:19 ack dave 20:08:53 Gil: WS Man is concerned that Level 2 needs supported. 20:09:03 q+ 20:09:15 Maybe they shouldn't be lumped together. 20:09:27 But the use cases are distinct. 20:09:34 ack tom 20:09:44 Tom: WS Man can do this them selves in their spec. 20:10:12 Level 1 is liked by a number of other uses. 20:10:34 The security request has a few comparisons. 20:10:55 The differences are minimual. 20:11:00 q+ 20:11:09 ack ram 20:12:10 q+ 20:12:17 Ram: There seems to be some interest in having these subsets (unchanged) moved into a separate spec. 20:13:05 This would consolidate the number of document that subset XML. 20:13:16 ack ram 20:13:39 q+ 20:13:52 Ash: Multiple dialects are a bad idea. 20:15:01 It may be handy to put the Level 1 spec in a separate document. 20:15:03 q+ 20:15:14 ack tom 20:15:15 + +1.919.349.aacc 20:15:21 -Doug_Davis 20:15:33 http://www.w3.org/2008/xmlsec/Drafts/proposals/xpath-profile-levels.html 20:15:41 Tom: Level 1 in a separate spec is OK. Or is there another cahnge being proposed. 20:16:41 We need to at least answer the group. 20:17:27 From Section 3 of the proposal: 20:17:28 Create a separate XPath profile with WS-Fragment Level 1 profile (unchanged), XML Signature 2.0 XPath profile, renamed as Level 2 and material in section 7 ("XPath 1.0 Expression Language") of WS-Fragment. 20:18:25 Bob: These look definitly different. 20:18:56 Bob: Is it a good idea to have fewer dialects? 20:19:33 There is general support for having only one dialect and therefore maybe we should try theirs. 20:19:55 q+ 20:20:07 It would probably need to be in a separate spec. 20:20:29 Tom: The functions they include look pretty useful. 20:21:08 Asjh: We mostly have full implementations. It is sometimes more dificult to take stuf out. 20:21:38 Tom: these extensions are easy to implement and help the user a lot. 20:21:54 + +1.703.860.aadd 20:22:25 Ram: Who in this group would test this set of features? 20:23:00 Bob: Is Level 1 at risk anyway? 20:23:30 Doug: But if full support exists, we get the subset for free. The concern is with oour schedule. 20:23:48 Tom: Who are the customers? 20:24:44 Bob: We could close with no action, as this is mostly about spec efficiency. 20:24:52 q- 20:24:58 q 20:25:00 = 20:25:02 q 20:25:34 Tom: The functions actually look handy. Maybe we should look at these. 20:25:40 q+ 20:26:22 ack dav 20:26:48 Bob: One possility is close with no action. 20:26:50 q+ 20:27:03 Bob: How do we test this? 20:27:23 Tom: We build a test that tests only Level 1. 20:27:26 test cases could only exercise level one constructs 20:27:42 Then we also test full XPath as well. 20:27:54 -Gilbert_Pilz 20:28:10 +Gilbert_Pilz 20:28:15 ack tom 20:28:42 Tom: The aim is to allow receivers to implement simple subsets. and it is easy to test. 20:29:41 What is the impact on schedule? 20:29:49 Gill: is breaking up. 20:29:58 -Gilbert_Pilz 20:30:24 +Gilbert_Pilz 20:30:30 Gill said it could help schedule, but we still need to hear why. 20:31:12 Proposal: drop Level one from us and say look at the other spec for subsets. 20:31:49 q 20:32:04 This implies keeping the QName only and Full XPath. 20:32:06 q+ 20:33:07 q+ 20:33:27 ack ram 20:33:29 Ram: Take the path of least resistance. 20:35:11 There are some concerns with how to addres this testing of these. 20:35:20 -asoldano 20:35:29 Option 1) Close no action 20:35:46 what would our conformance test use for xpath elements, 20:35:47 just the xpath 1 subset? 20:36:00 Option 2) We like your subset, please put it some where we can teverence it 20:36:28 Option 3) Make out level match theirs. 20:36:35 +asoldano 20:36:50 q+ 20:36:54 Option 4) Give them our level 1 20:37:38 ack tom 20:38:00 Option 5) Our spec says nothing and other specs can define what ever they want. 20:38:38 Number 5 leaves QName. 20:39:56 additional: if use option 5 we have to decide how complicated our test cases will exercise xpaty 20:40:26 In 5 we don't need to reference other specs. 20:40:53 In 4 we would reference another doc. 20:40:58 q+ 20:41:19 ack dav 20:42:00 ack tom 20:42:19 Dave and Tom like 5, but Tom's worried about testing. 20:42:57 Bob: Test Qname and an example of XPath. 20:43:58 The test only verifies that XPath is there. It is up to XPath compliance to cover the full XPath support. 20:45:05 We can stll say that the security guys could have Level one. And then possibly include a non-normative reference to their work if they finished first. 20:45:41 People should think about this over the next week. 20:46:44 Topic 9655 20:47:14 Paus whail people think. 20:47:34 s/paus whail/pause while/ 20:48:09 This means that no delivery mechanism is required. 20:48:26 Sounds like more time is needed. 20:48:44 Thank you all have a good time next week. 20:48:48 Bye 20:48:49 -[Microsoft] 20:48:50 - +1.703.860.aadd 20:48:52 -Ashok_Malhotra 20:48:53 -Wu_Chou 20:48:53 - +1.919.349.aacc 20:48:55 -Bob_Freund 20:48:55 -Gilbert_Pilz 20:48:56 -asoldano 20:48:56 -Yves 20:48:58 - +1.408.970.aabb 20:49:00 -Tom_Rutt 20:49:02 -??P11 20:49:03 I have made the request to generate http://www.w3.org/2010/05/04-ws-ra-minutes.html Yves 20:49:10 -MartinC 20:49:11 WS_WSRA()3:30PM has ended 20:49:13 Attendees were Bob_Freund, Gilbert_Pilz, Doug_Davis, Wu_Chou, Tom_Rutt, asoldano, +1.646.361.aaaa, MartinC, Yves, Ashok_Malhotra, [Microsoft], +1.408.970.aabb, +1.919.349.aacc, 20:49:15 MartinC has left #ws-ra 20:49:16 ... +1.703.860.aadd 23:15:55 Zakim has left #ws-ra