Thursday, 31 May 2007
- RE: New issue on duplicate assertions of a single type in an alternative: 4583
- RE: New issue on duplicate assertions of a single type in an alternative: 4583
- RE: New issue on duplicate assertions of a single type in an alternative: 4583
- RE: BEA Reporting Interop Round 3 Test Results
Wednesday, 30 May 2007
Tuesday, 29 May 2007
Saturday, 26 May 2007
- RE: Bug 4584 : Clarify how lax mode and ignorable assertions affect the intersection algorithm
- Re: BEA Reporting Interop Round 1, 2 and 4 Test Results
- Re: Oracle Round 3 Results
Friday, 25 May 2007
- RE: Bug 4584 : Clarify how lax mode and ignorable assertions affect the intersection algorithm
- RE: Bug 4584 : Clarify how lax mode and ignorable assertions affect the intersection algorithm
- Oracle Round 3 Results
- BEA Reporting Interop Round 1, 2 and 4 Test Results
- Re: Bug 4584 : Clarify how lax mode and ignorable assertions affect the intersection algorithm
- Bug 4584 : Clarify how lax mode and ignorable assertions affect the intersection algorithm
Thursday, 24 May 2007
- WS-Policy Interop Report
- RE: New issue on duplicate assertions of a single type in an alternative: 4583
- New issue on duplicate assertions of a single type in an alternative: 4583
- Re: Additional lax intersection testing
- Fw: Revised positions for closed/open world assumptions
- Additional lax intersection testing
- RE: Revised positions for closed/open world assumptions
- BEA Reporting Interop Round 3 Test Results
- BEA Reporting Interop Round 3 Test Results
- One more editorial suggestion
- Re: from the whiteboard f2f dicussion
- Re: WS-Addressing 1.0 Metadata second last call
- [Fwd: [New Issue] Issue 4579: Context for Parent Policy Assertions and Nested Policy Expressions]
- [New Issue] Issue 4579: Context for Parent Policy Assertions and Nested Policy Expressions
- RE: from the whiteboard f2f dicussion
- AI: Suggestions for explanation of normalization
Wednesday, 23 May 2007
- RE: from the whiteboard f2f dicussion
- Re: [Bug 4555] Should policy intersection be called policy intersection?
- from the whiteboard f2f dicussion
- Re: [Bug 4554] Configurability and comformance of intersection algorithm
- Summary: Test Suite Issues
- FW: [Bug 4568] Incorrect namespaces in testcases
- FW: [Bug 4572] Typo in wsp:URI in wsdl2.0 for round4
- Revised Open World/Closed World positions
- RE: FW: [Bug 4567] Typo in wsdl2.0 attachment URIs
- FW: [Bug 4567] Typo in wsdl2.0 attachment URIs
- RE: [Bug 4554] Configurability and comformance of intersection algorithm
- Re: Reporting Interop / Unit Test Results 4 CR Dashboard
- RE: Revised positions for closed/open world assumptions
- FW: [Bug 4575] Minor Bugs in Round 2 WSDL 20 Test Cases from WSO2/Manjula
- Reporting Interop / Unit Test Results 4 CR Dashboard
Tuesday, 22 May 2007
- Re: FW: [Bug 4553] Exact meaning of "all of the assertions in both alternatives"
- [VER 2] Agenda: WS-Policy WG face-to-face meeting 42 - 2007-05-23 and 24
- Re: FW: [Bug 4553] Exact meaning of "all of the assertions in both alternatives"
- RE: [NEW ISSUE] 4561 clarification of domain-specific processing
Monday, 21 May 2007
- [NEW ISSUE] 4573 [Guidelines] Uses Guidelines, Best Practices and Good Practices interchangeably
- Re: Revised positions for closed/open world assumptions
- One from column A and one from column B
- Updated Editor's Draft of WS-Policy 1.5 Guidelines Document
- Re: Revised positions for closed/open world assumptions
- Re: Revised positions for closed/open world assumptions
- Re: Revised positions for closed/open world assumptions
- Re: FW: [Bug 4552] Should the word "collection" be changed to something more specific?
- Re: FW: [Bug 4552] Should the word "collection" be changed to something more specific?
- Re: Comments on "normal form" of policy expressions
- Agenda: WS-Policy WG face-to-face meeting 42 - 2007-05-23 and 24
- RE: Client policy processing
- RE: RE: WS-Addressing 1.0 Metadata second last call
- RE: FW: [Bug 4552] Should the word "collection" be changed to something more specific?
- RE: FW: [Bug 4552] Should the word "collection" be changed to something more specific?
Sunday, 20 May 2007
- RE: FW: [Bug 4552] Should the word "collection" be changed to something more specific?
- RE: Comments on "normal form" of policy expressions
- RE: FW: [Bug 4552] Should the word "collection" be changed to something more specific?
- RE: Client policy processing
- FW: [Bug 4571] round2 wsdl2 needs QNames not NCNames
- Re: FW: [Bug 4552] Should the word "collection" be changed to something more specific?
- RE: Client policy processing
- RE: Client policy processing
- Re: Client policy processing
Friday, 18 May 2007
- RE: Revised positions for closed/open world assumptions
- RE: Revised positions for closed/open world assumptions
- RE: WSDL 2.0 external attachment
- WSDL 2.0 external attachment
- RE: Revised positions for closed/open world assumptions
- RE: Revised positions for closed/open world assumptions
- RE: Revised positions for closed/open world assumptions
- Re: Revised positions for closed/open world assumptions
- Re: Revised positions for closed/open world assumptions
- Fw: Revised positions for closed/open world assumptions
- Re: Revised positions for closed/open world assumptions
- RE: Revised positions for closed/open world assumptions
- RE: Revised positions for closed/open world assumptions
- RE: FW: [Bug 4552] Should the word "collection" be changed to something more specific?
- [NEW ISSUE] 4566 Guideline G2 to be reconsidered
- RE: Bug 4558: Scalability and performance problems with expressing allowable nested policy assertions
- RE: Bug 4558: Scalability and performance problems with expressing allowable nested policy assertions
- RE: Bug 4558: Scalability and performance problems with expressing allowable nested policy assertions
- RE: Action-297 - Example Policies that Don't Interesect
- RE: FW: [Bug 4552] Should the word "collection" be changed to something more specific?
- RE: FW: [Bug 4552] Should the word "collection" be changed to something more specific?
Thursday, 17 May 2007
- RE: Revised positions for closed/open world assumptions
- RE: [Bug 4555] Should policy intersection be called policy intersection?
- Re: [Bug 4554] Configurability and comformance of intersection algorithm
- Re: [Bug 4555] Should policy intersection be called policy intersection?
- RE: [Bug 4555] Should policy intersection be called policy intersection?
- RE: WS-Addressing 1.0 Metadata second last call
- RE: Bug 4558: Scalability and performance problems with expressing allowable nested policy assertions
- RE: [Bug 4554] Configurability and comformance of intersection algorithm
- WS-Addressing 1.0 Metadata second last call
Wednesday, 16 May 2007
- Re: Utility of Ignorable?
- Re: Utility of Ignorable?
- WS-Addressing 1.0 Metadata second last call
- [NEW ISSUE] 4561 clarification of domain-specific processing
- Re: Bug 4558: Scalability and performance problems with expressing allowable nested policy assertions
- Re: Revised positions for closed/open world assumptions
- RE: Revised positions for closed/open world assumptions
- RE: Bug 4558: Scalability and performance problems with expressing allowable nested policy assertions
- Re: Bug 4558: Scalability and performance problems with expressing allowable nested policy assertions
- Re: FW: [Bug 4552] Should the word "collection" be changed to something more specific?
- RE: Bug 4558: Scalability and performance problems with expressing allowable nested policy assertions
- RE: FW: [Bug 4552] Should the word "collection" be changed to something more specific?
- RE: Bug 4558: Scalability and performance problems with expressing allowable nested policy assertions
- RE: FW: [Bug 4552] Should the word "collection" be changed to something more specific?
- Re: Bug 4558: Scalability and performance problems with expressing allowable nested policy assertions
- RE: Bug 4558: Scalability and performance problems with expressing allowable nested policy assertions
- RE: Revised positions for closed/open world assumptions
- RE: Revised positions for closed/open world assumptions
- Re: FW: [Bug 4552] Should the word "collection" be changed to something more specific?
- Re: FW: [Bug 4553] Exact meaning of "all of the assertions in both alternatives"
- RE: Revised positions for closed/open world assumptions
Tuesday, 15 May 2007
- RE: Revised positions for closed/open world assumptions
- RE: Revised positions for closed/open world assumptions
Wednesday, 16 May 2007
- FW: [Bug 4552] Should the word "collection" be changed to something more specific?
- FW: [Bug 4553] Exact meaning of "all of the assertions in both alternatives"
- Action-297 - Example Policies that Don't Interesect
- Re: Agenda: WS-Policy WG distributed meeting 41 - 2007-05-16
- Action 292: Minor Editorial Update on Versioning Text in Primer (New Issue 4559)
- Bug 4558: Scalability and performance problems with expressing allowable nested policy assertions
Tuesday, 15 May 2007
- Re: Agenda: WS-Policy WG distributed meeting 41 - 2007-05-16
- RE: Revised positions for closed/open world assumptions
- RE: Revised positions for closed/open world assumptions
- RE: Revised positions for closed/open world assumptions
- RE: Revised positions for closed/open world assumptions
- Re: Revised positions for closed/open world assumptions
- RE: Agenda: WS-Policy interop F2F meeting 2 - 2007-05-23 to 2007-05-25
- Re: Revised positions for closed/open world assumptions
- RE: Revised positions for closed/open world assumptions
Monday, 14 May 2007
- Performance problems with policy intersection
- RE: Revised positions for closed/open world assumptions
- RE: Revised positions for closed/open world assumptions
- RE: Revised positions for closed/open world assumptions
Sunday, 13 May 2007
- Action-295 (was NEW ISSUE - 4556 Editorial Issue from David Hull
- [Bug 4553] Exact meaning of "all of the assertions in both alternatives"
- [Bug 4555] Should policy intersection be called policy intersection?
- Agenda: WS-Policy WG distributed meeting 41 - 2007-05-16
- [Bug 4554] Configurability and comformance of intersection algorithm
- RE: Revised positions for closed/open world assumptions
Friday, 11 May 2007
- RE: Revised positions for closed/open world assumptions
- RE: Revised positions for closed/open world assumptions
- Extensions and policy intersection
- Re: Response to the Last Call comments by WS-Policy to the WS-Addressing Metadata document 1.0
- RE: Revised positions for closed/open world assumptions
- Re: Revised positions for closed/open world assumptions
Thursday, 10 May 2007
- Revised positions for closed/open world assumptions
- RE: AIN, NOBI and composition
- Re: AIN, NOBI and composition
- RE: AIN, NOBI and composition
- RE: AIN, NOBI and composition
- RE: AIN, NOBI and composition
- RE: AIN, NOBI and composition
- RE: AIN, NOBI and composition
- Re: AIN, NOBI and composition
- Re: AIN, NOBI and composition
- RE: AIN, NOBI and composition
- RE: AIN, NOBI and composition
- Re: AIN, NOBI and composition
- RE: AIN, NOBI and composition
- RE: AIN, NOBI and composition
- RE: AIN, NOBI and composition
- RE: AIN, NOBI and composition
- RE: AIN, NOBI and composition
- Re: AIN, NOBI and composition
- Re: WS-Policy and interopearbility (Was: policy vocabulary, will not be applied, oh my!)
Wednesday, 9 May 2007
- Re: WS-Policy and interopearbility (Was: policy vocabulary, will not be applied, oh my!)
- RE: WS-Policy and interopearbility (Was: policy vocabulary, will not be applied, oh my!)
- RE: WS-Policy and interopearbility (Was: policy vocabulary, will not be applied, oh my!)
- RE: AIN, NOBI and composition
- Alternative with neutral language for Issue 4544 (was RE: policy vocabulary, will not be applied, oh my!)
- RE: WS-Policy and interopearbility (Was: policy vocabulary, will not be applied, oh my!)
- Re: AIN, NOBI and composition
- Re: Utility of Ignorable?
- RE: AIN, NOBI and composition
- Re: Are nested assertions part of the policy vocabulary?
- Re: Client policy processing
- Re: Client policy processing
- RE: Utility of Ignorable?
- RE: policy vocabulary, will not be applied, oh my!
- RE: AIN, NOBI and composition
- RE: Utility of Ignorable?
- RE: [SPAM] Round 4 UDDI
- RE: AIN, NOBI and composition
- RE: Utility of Ignorable?
- RE: WS-Policy and interopearbility (Was: policy vocabulary, will not be applied, oh my!)
- Re: Utility of Ignorable?
- Re: Are nested assertions part of the policy vocabulary?
- RE: Are nested assertions part of the policy vocabulary?
- Re: Are nested assertions part of the policy vocabulary?
- RE: Are nested assertions part of the policy vocabulary?
- RE: Are nested assertions part of the policy vocabulary?
- (VER 2) Agenda: WS-Policy WG distributed meeting 40 - 2007-05-09
- RE: policy vocabulary, will not be applied, oh my!
- RE: Utility of Ignorable?
- WS-Policy and interopearbility (Was: policy vocabulary, will not be applied, oh my!)
- RE: Are nested assertions part of the policy vocabulary?
- Re: Are nested assertions part of the policy vocabulary?
- Re: Utility of Ignorable?
- Re: Agenda: WS-Policy WG distributed meeting 40 - 2007-05-09
- Re: policy vocabulary, will not be applied, oh my!
- Re: AIN, NOBI and composition
- RE: policy vocabulary, will not be applied, oh my!
Tuesday, 8 May 2007
- Re: policy vocabulary, will not be applied, oh my!
- RE: AIN, NOBI and composition
- RE: AIN, NOBI and composition
- RE: AIN, NOBI and composition
- RE: AIN, NOBI and composition
- RE: policy vocabulary, will not be applied, oh my!
- Re: AIN, NOBI and composition
- RE: AIN, NOBI and composition
- WS-Policy 1.5 Primer Editors draft and Diff
- AIN, NOBI and composition
- RE: policy vocabulary, will not be applied, oh my!
- Client policy processing
- Policy expression meaning different if in alternative?
- RE: policy vocabulary, will not be applied, oh my!
- RE: policy vocabulary, will not be applied, oh my!
- Round 4 UDDI
- RE: Are nested assertions part of the policy vocabulary?
- RE: policy vocabulary, will not be applied, oh my!
- RE: policy vocabulary, will not be applied, oh my!
- RE: policy vocabulary, will not be applied, oh my!
- RE: Are nested assertions part of the policy vocabulary?
- RE: Utility of Ignorable?
- Re: ACTION-294 Ashok to open a CR issue with text to define "collection"
- RE: policy vocabulary, will not be applied, oh my!
- RE: Utility of Ignorable?
- RE: ACTION-294 Ashok to open a CR issue with text to define "collection"
- RE: policy vocabulary, will not be applied, oh my!
- RE: Response to the Last Call comments by WS-Policy to the WS-Addressing Metadata document 1.0
- RE: policy vocabulary, will not be applied, oh my!
- RE: policy vocabulary, will not be applied, oh my!
- Re: policy vocabulary, will not be applied, oh my!
- RE: policy vocabulary, will not be applied, oh my!
- Re: policy vocabulary, will not be applied, oh my!
- Re: Are nested assertions part of the policy vocabulary?
Monday, 7 May 2007
- RE: Are nested assertions part of the policy vocabulary?
- Re: policy vocabulary, will not be applied, oh my!
- RE: [Bug 4522] Namespace problems in the WSDL 1.1 and WSDL 2.0 External Attachment Test Cases.
Friday, 4 May 2007
- No need for concept of assertion negation
- Re: policy vocabulary, will not be applied, oh my!
- Re: ACTION-294 Ashok to open a CR issue with text to define "collection"
- RE: ACTION-294 Ashok to open a CR issue with text to define "collection"
- Re: policy vocabulary, will not be applied, oh my!
- Re: ACTION-294 Ashok to open a CR issue with text to define "collection"
- Re: policy vocabulary, will not be applied, oh my!
- RE: policy vocabulary, will not be applied, oh my!
- ACTION-294 Ashok to open a CR issue with text to define "collection"
- Re: policy vocabulary, will not be applied, oh my!
- RE: [Bug 4522] Namespace problems in the WSDL 1.1 and WSDL 2.0 External Attachment Test Cases.
- RE: Utility of Ignorable?
- RE: [Bug 4522] Namespace problems in the WSDL 1.1 and WSDL 2.0 External Attachment Test Cases.
Thursday, 3 May 2007
- RE: policy vocabulary, will not be applied, oh my!
- Utility of Ignorable?
- 4414 finished
- Re: policy vocabulary, will not be applied, oh my!
- RE: policy vocabulary, will not be applied, oh my!
- Re: policy vocabulary, will not be applied, oh my!
- RE: policy vocabulary, will not be applied, oh my!
- RE: [Bug 4522] Namespace problems in the WSDL 1.1 and WSDL 2.0 External Attachment Test Cases.
- RE: policy vocabulary, will not be applied, oh my!
Wednesday, 2 May 2007
- Agenda: WS-Policy WG distributed meeting 40 - 2007-05-09
- RE: Collections: Sets, bags or something else?
- May F2F update hosted by Nortel
- RE: Collections: Sets, bags or something else?
- Re: Collections: Sets, bags or something else?
- Re: policy vocabulary, will not be applied, oh my!
- Re: Ferris wsp 5/1/2007: 'Will Not be Applied'
- RE: policy vocabulary, will not be applied, oh my!
- Re: Collections: Sets, bags or something else?
- Re: Editorial issues
- WSDL 1.1 External Attachment Tests
- Re: Ferris wsp 5/1/2007: 'Will Not be Applied'
- Re: policy vocabulary, will not be applied, oh my!
- Re: policy vocabulary, will not be applied, oh my!
- [VER 2] Agenda: WS-Policy WG distributed meeting 39 - 2007-05-02
- RE: Action-288 (was RE: [Bug 4479] Editorial, note is obscure or unclear
Tuesday, 1 May 2007
- Ferris wsp 5/1/2007: 'Will Not be Applied'
- Re: Bug 4414 proposed - Relationship to Issues 4393 and 4292
- Updated Interop Scenarios - Release 2
- RE: Are nested assertions part of the policy vocabulary?
- RE: Collections: Sets, bags or something else?
- RE: Collections: Sets, bags or something else?
- RE: Editorial issues
- Action-288 (was RE: [Bug 4479] Editorial, note is obscure or unclear
- Bug 4414 proposed
- policy vocabulary, will not be applied, oh my!
- Editorial issues
- Collections: Sets, bags or something else?
- Comments on "normal form" of policy expressions