IRC log of ws-policy-eds on 2007-05-24

Timestamps are in UTC.

16:13:03 [RRSAgent]
RRSAgent has joined #ws-policy-eds
16:13:03 [RRSAgent]
logging to http://www.w3.org/2007/05/24-ws-policy-eds-irc
16:14:10 [maryann]
maryann has joined #ws-policy-eds
16:15:17 [maryann]
http://lists.w3.org/Archives/Public/public-ws-policy-eds/2007May/0122.html
16:15:38 [maryann]
agenda pointer is above
16:15:47 [maryann]
chair: Maryann
16:16:25 [maryann]
Present: David O, Prasad, Asir, Maryann
16:16:36 [maryann]
Regrets: Toufic, Frederick
16:17:03 [maryann]
Present: David O, Prasad, Asir, Felix, Maryann
16:18:42 [fsasaki]
meeting: WS Policy WG (editor's f2f May 2007)
16:18:50 [fsasaki]
agenda: http://lists.w3.org/Archives/Public/public-ws-policy-eds/2007May/0122.html
16:18:54 [fsasaki]
rrsagent, make log public
16:19:04 [fsasaki]
scribe: asir
16:21:25 [asir]
Topic: Administrivia
16:22:06 [dorchard]
dorchard has joined #ws-policy-eds
16:23:12 [asir]
Last week minutes are okay
16:24:14 [asir]
Next meeting arrangements:
16:24:20 [asir]
Chair –Asir
16:24:20 [asir]
Scribe - Maryann
16:24:41 [asir]
Future Chair Rotation: Toufic, Frederick, Maryann, Asir, DaveO, Prasad
16:24:41 [asir]
Scribe Rotation: DaveO, Toufic, Frederick, Maryann, Asir, Prasad
16:25:09 [asir]
Action-249 Open
16:25:39 [asir]
Action-265 closed
16:26:01 [asir]
Action-268 is closed
16:27:40 [asir]
Action-269 to 273 is Asir
16:28:09 [asir]
Action-274 is Asir
16:29:42 [asir]
Action-275 is Maryann
16:30:15 [asir]
Action-267 is Maryann
16:30:44 [asir]
Action-277 is dup
16:32:11 [asir]
Action-278 is Prasad
16:32:45 [asir]
Action-279 is Prasad
16:33:03 [asir]
Action-280 is Prasad
16:35:47 [asir]
Action-283 is Felix
16:37:55 [asir]
Action-284 is DaveO
16:38:00 [asir]
Action-285 is DaveO
16:38:38 [asir]
Action-286 is Asir
16:39:01 [fsasaki]
fsasaki has joined #ws-policy-eds
16:39:02 [asir]
Action-287 is closed
16:39:52 [asir]
Action-288 is Prasad
16:39:56 [asir]
Action-289 is Asir
16:41:16 [asir]
Action-290, 291 is Prasad
16:41:35 [asir]
Action-292 is Maryann
16:41:45 [asir]
Action-293 is Maryann
16:43:06 [asir]
Action-294 is Prasad
16:44:13 [asir]
Action-295 is Asir
16:44:26 [asir]
Action-296 is Prasad
16:46:32 [asir]
We'll have a conference call next week
16:46:42 [asir]
Tentative
16:51:34 [asir]
Need to figure out when the Framework and Attachement drafts would be delivered (that includes current actions + 4544
16:56:52 [asir]
Paul: plan to meet with Tim July 2nd
16:57:03 [asir]
s/July/in July/
16:57:34 [asir]
Need updated drafts of the Framework and Attachment 2 weeks prior to July 2nd
17:01:22 [asir]
Action: David to implement the resolution for issue 4544
17:01:23 [trackbot]
Created ACTION-297 - Implement the resolution for issue 4544 [on David Orchard - due 2007-05-31].
17:01:29 [asir]
When the WG approves
17:03:48 [asir]
Topic: Schedule
17:04:32 [asir]
Deliver Framework and Attachment drafts to the WG by Wed May 30th
17:05:54 [asir]
Deadline for Framework and Attachment related check ins is Tuesday May 29th
17:06:17 [asir]
s/Tuesday/COB Tuesday/
17:06:45 [asir]
Action: Asir to generate diff docs for Framework and Attachment drafts by Tuesday May 29th
17:06:46 [trackbot]
Created ACTION-298 - Generate diff docs for Framework and Attachment drafts by Tuesday May 29th [on Asir Vedamuthu - due 2007-05-31].
17:07:19 [asir]
Action: Maryann to deliver the updated Framework and Attachment drafts to the WG on Wednesday May 30th
17:07:19 [trackbot]
Created ACTION-299 - Deliver the updated Framework and Attachment drafts to the WG on Wednesday May 30th [on Maryann Hondo - due 2007-05-31].
17:13:26 [RRSAgent]
I have made the request to generate http://www.w3.org/2007/05/24-ws-policy-eds-minutes.html fsasaki
17:27:41 [asir]
Everyone to [Guidelines] update the best practice "Assertion Description Should Specify a Policy Subject" with Assertion authors should specify the set of relevant policy subjects with which the assertion may be associated. For instance, if a policy assertion is to be used with WSDL, the assertion description should specify a WSDL policy subject – such as service, endpoint, operation and message.
17:27:49 [asir]
Action: Everyone to [Guidelines] update the best practice "Assertion Description Should Specify a Policy Subject" with Assertion authors should specify the set of relevant policy subjects with which the assertion may be associated. For instance, if a policy assertion is to be used with WSDL, the assertion description should specify a WSDL policy subject – such as service, endpoint, operation and message.
17:28:00 [RRSAgent]
I have made the request to generate http://www.w3.org/2007/05/24-ws-policy-eds-minutes.html fsasaki
17:28:44 [trackbot]
trackbot has joined #ws-policy-eds
17:28:50 [trackbot]
Tracking ISSUEs and ACTIONs from http://www.w3.org/2005/06/tracker/wspolicyeds/
17:29:09 [asir]
Action: Everyone to [Guidelines] update the best practice "Assertion Description Should Specify a Policy Subject" with Assertion authors should specify the set of relevant policy subjects with which the assertion may be associated. For instance, if a policy assertion is to be used with WSDL, the assertion description should specify a WSDL policy subject – such as service, endpoint, operation and message.
17:30:44 [trackbot]
trackbot has joined #ws-policy-eds
17:30:50 [trackbot]
Tracking ISSUEs and ACTIONs from http://www.w3.org/2005/06/tracker/wspolicyeds/
17:31:20 [asir]
Action: Everyone to [Guidelines] update the best practice "Assertion Description Should Specify a Policy Subject" with Assertion authors should specify the set of relevant policy subjects with which the assertion may be associated. For instance, if a policy assertion is to be used with WSDL, the assertion description should specify a WSDL policy subject – such as service, endpoint, operation and message.
17:32:44 [trackbot]
trackbot has joined #ws-policy-eds
17:32:50 [trackbot]
Tracking ISSUEs and ACTIONs from http://www.w3.org/2005/06/tracker/wspolicyeds/
17:36:49 [asir]
Action: Everyone to [Guidelines] update the best practice "Assertion Description Should Specify a Policy Subject" with Assertion authors should specify the set of relevant policy subjects with which the assertion may be associated. For instance, if a policy assertion is to be used with WSDL, the assertion description should specify a WSDL policy subject - such as service, endpoint, operation and message.
17:36:49 [trackbot]
Created ACTION-303 - [Guidelines] update the best practice \"Assertion Description Should Specify a Policy Subject\" with Assertion authors should specify the set of relevant policy subjects with which the assertion may be associated. For instance, if a policy assertion is to be used with WSDL, the assertion description should specify a WSDL policy subject - such as service, endpoint, operation and message. [on Everyone Everyone - due 2007-05-31].
17:36:49 [asir]
Action: Everyone to [Guidelines] Update the bumper sticker "Choose a Granular Policy Subject" with "Choose the Most Granular Policy Subject".
17:36:49 [asir]
Action: Everyone to [Guidelines] Update the best practice "Choose the Most Granular Policy Subject" with s/that the behavior represented by a policy assertion applies to/to which the behavior represented by a policy assertion applies/
17:36:49 [trackbot]
Created ACTION-304 - [Guidelines] Update the bumper sticker \"Choose a Granular Policy Subject\" with \"Choose the Most Granular Policy Subject\". [on Everyone Everyone - due 2007-05-31].
17:36:54 [trackbot]
Created ACTION-305 - [Guidelines] Update the best practice \"Choose the Most Granular Policy Subject\" with s/that the behavior represented by a policy assertion applies to/to which the behavior represented by a policy assertion applies/ [on Everyone Everyone - due 2007-05-31].
17:45:23 [asir]
Action: Everyone to [Guidelines] Update the best practice "Specify Preferred Attachment Point for an Assertion" with s/multiple points/multiple attachment points/
17:45:23 [trackbot]
Created ACTION-306 - [Guidelines] Update the best practice \"Specify Preferred Attachment Point for an Assertion\" with s/multiple points/multiple attachment points/ [on Everyone Everyone - due 2007-05-31].
17:47:17 [asir]
Action: Everyone to [Guidelines] Update the best practice bump sticker with "Describe Semantics of Multiple Assertions of Same Type"
17:47:17 [trackbot]
Created ACTION-307 - [Guidelines] Update the best practice bump sticker with \"Describe Semantics of Multiple Assertions of Same Type\" [on Everyone Everyone - due 2007-05-31].
17:48:13 [asir]
Action: Everyone to [Guidelines] Update the best practice "Describe Semantics of Multiple Assertions of Same Type" with s/A policy alternative can contain multiple instances of the same policy assertion./A policy alternative can contain multiple instances of the same policy assertion type/
17:48:13 [trackbot]
Created ACTION-308 - [Guidelines] Update the best practice \"Describe Semantics of Multiple Assertions of Same Type\" with s/A policy alternative can contain multiple instances of the same policy assertion./A policy alternative can contain multiple instances of the same policy assertion type/ [on Everyone Everyone - due 2007-05-31].
17:56:58 [asir]
Action: Everyone to [Guidelines] Update Section 5.8 to use the Arch of the WWW format plus add an example
17:56:58 [trackbot]
Created ACTION-309 - [Guidelines] Update Section 5.8 to use the Arch of the WWW format plus add an example [on Everyone Everyone - due 2007-05-31].
18:00:15 [asir]
Action: Everyone to [Guidelines] update the best practice bumper sticker "Use Independent Assertions for Multiple Versions of a Behavior" to "Use Independent Assertions for Different Versions of a Behavior"
18:00:15 [trackbot]
Created ACTION-310 - [Guidelines] update the best practice bumper sticker \"Use Independent Assertions for Multiple Versions of a Behavior\" to \"Use Independent Assertions for Different Versions of a Behavior\" [on Everyone Everyone - due 2007-05-31].
18:01:20 [asir]
Action: Everyone to [Guidelines] update the best practice "Use Independent Assertions for Different Versions of a Behavior" to "An assertion author should use different assertions for modeling different versions of a behavior"
18:01:20 [trackbot]
Created ACTION-311 - [Guidelines] update the best practice \"Use Independent Assertions for Different Versions of a Behavior\" to \"An assertion author should use different assertions for modeling different versions of a behavior\" [on Everyone Everyone - due 2007-05-31].
18:40:20 [asir]
Action: Asir to [Framework] implement the resolution for issue 4579
18:40:20 [trackbot]
Created ACTION-312 - [Framework] implement the resolution for issue 4579 [on Asir Vedamuthu - due 2007-05-31].
18:56:20 [maryann]
maryann has left #ws-policy-eds
20:49:55 [fsasaki]
rrsagent, bye
20:49:55 [RRSAgent]
I see 16 open action items saved in http://www.w3.org/2007/05/24-ws-policy-eds-actions.rdf :
20:49:55 [RRSAgent]
ACTION: David to implement the resolution for issue 4544 [1]
20:49:55 [RRSAgent]
recorded in http://www.w3.org/2007/05/24-ws-policy-eds-irc#T17-01-22
20:49:55 [RRSAgent]
ACTION: Asir to generate diff docs for Framework and Attachment drafts by Tuesday May 29th [2]
20:49:55 [RRSAgent]
recorded in http://www.w3.org/2007/05/24-ws-policy-eds-irc#T17-06-45
20:49:55 [RRSAgent]
ACTION: Maryann to deliver the updated Framework and Attachment drafts to the WG on Wednesday May 30th [3]
20:49:55 [RRSAgent]
recorded in http://www.w3.org/2007/05/24-ws-policy-eds-irc#T17-07-19
20:49:55 [RRSAgent]
ACTION: Everyone to [Guidelines] update the best practice "Assertion Description Should Specify a Policy Subject" with Assertion authors should specify the set of relevant policy subjects with which the assertion may be associated. For instance, if a policy assertion is to be used with WSDL, the assertion description should specify a WSDL policy subject – such as service, endpoint, operation and message. [4]
20:49:55 [RRSAgent]
recorded in http://www.w3.org/2007/05/24-ws-policy-eds-irc#T17-27-49
20:49:55 [RRSAgent]
ACTION: Everyone to [Guidelines] update the best practice "Assertion Description Should Specify a Policy Subject" with Assertion authors should specify the set of relevant policy subjects with which the assertion may be associated. For instance, if a policy assertion is to be used with WSDL, the assertion description should specify a WSDL policy subject – such as service, endpoint, operation and message. [5]
20:49:55 [RRSAgent]
recorded in http://www.w3.org/2007/05/24-ws-policy-eds-irc#T17-29-09
20:49:55 [RRSAgent]
ACTION: Everyone to [Guidelines] update the best practice "Assertion Description Should Specify a Policy Subject" with Assertion authors should specify the set of relevant policy subjects with which the assertion may be associated. For instance, if a policy assertion is to be used with WSDL, the assertion description should specify a WSDL policy subject – such as service, endpoint, operation and message. [6]
20:49:55 [RRSAgent]
recorded in http://www.w3.org/2007/05/24-ws-policy-eds-irc#T17-31-20
20:49:55 [RRSAgent]
ACTION: Everyone to [Guidelines] update the best practice "Assertion Description Should Specify a Policy Subject" with Assertion authors should specify the set of relevant policy subjects with which the assertion may be associated. For instance, if a policy assertion is to be used with WSDL, the assertion description should specify a WSDL policy subject - such as service, endpoint, operation and message. [7]
20:49:55 [RRSAgent]
recorded in http://www.w3.org/2007/05/24-ws-policy-eds-irc#T17-36-49
20:49:55 [RRSAgent]
ACTION: Everyone to [Guidelines] Update the bumper sticker "Choose a Granular Policy Subject" with "Choose the Most Granular Policy Subject". [8]
20:49:55 [RRSAgent]
recorded in http://www.w3.org/2007/05/24-ws-policy-eds-irc#T17-36-49-2
20:49:55 [RRSAgent]
ACTION: Everyone to [Guidelines] Update the best practice "Choose the Most Granular Policy Subject" with s/that the behavior represented by a policy assertion applies to/to which the behavior represented by a policy assertion applies/ [9]
20:49:55 [RRSAgent]
recorded in http://www.w3.org/2007/05/24-ws-policy-eds-irc#T17-36-49-3
20:49:55 [RRSAgent]
ACTION: Everyone to [Guidelines] Update the best practice "Specify Preferred Attachment Point for an Assertion" with s/multiple points/multiple attachment points/ [10]
20:49:55 [RRSAgent]
recorded in http://www.w3.org/2007/05/24-ws-policy-eds-irc#T17-45-23
20:49:55 [RRSAgent]
ACTION: Everyone to [Guidelines] Update the best practice bump sticker with "Describe Semantics of Multiple Assertions of Same Type" [11]
20:49:55 [RRSAgent]
recorded in http://www.w3.org/2007/05/24-ws-policy-eds-irc#T17-47-17
20:49:55 [RRSAgent]
ACTION: Everyone to [Guidelines] Update the best practice "Describe Semantics of Multiple Assertions of Same Type" with s/A policy alternative can contain multiple instances of the same policy assertion./A policy alternative can contain multiple instances of the same policy assertion type/ [12]
20:49:55 [RRSAgent]
recorded in http://www.w3.org/2007/05/24-ws-policy-eds-irc#T17-48-13
20:49:55 [RRSAgent]
ACTION: Everyone to [Guidelines] Update Section 5.8 to use the Arch of the WWW format plus add an example [13]
20:49:55 [RRSAgent]
recorded in http://www.w3.org/2007/05/24-ws-policy-eds-irc#T17-56-58
20:49:55 [RRSAgent]
ACTION: Everyone to [Guidelines] update the best practice bumper sticker "Use Independent Assertions for Multiple Versions of a Behavior" to "Use Independent Assertions for Different Versions of a Behavior" [14]
20:49:55 [RRSAgent]
recorded in http://www.w3.org/2007/05/24-ws-policy-eds-irc#T18-00-15
20:49:55 [RRSAgent]
ACTION: Everyone to [Guidelines] update the best practice "Use Independent Assertions for Different Versions of a Behavior" to "An assertion author should use different assertions for modeling different versions of a behavior" [15]
20:49:55 [RRSAgent]
recorded in http://www.w3.org/2007/05/24-ws-policy-eds-irc#T18-01-20
20:49:55 [RRSAgent]
ACTION: Asir to [Framework] implement the resolution for issue 4579 [16]
20:49:55 [RRSAgent]
recorded in http://www.w3.org/2007/05/24-ws-policy-eds-irc#T18-40-20
20:49:57 [fsasaki]
zakim, bye
20:50:06 [fsasaki]
fsasaki has left #ws-policy-eds