Wednesday, 31 January 2007
- RE: Bug 4270: Primer versioning example
- RE: NEW ISSUE (4072): [Guidance] Statements not relevant to assertion design
- RE: NEW ISSUE (4072): [Guidance] Statements not relevant to assertion design
Tuesday, 30 January 2007
- RE: Issue 3953 [Guidelines] Update to issue on domain interactions and assertion nesting
- RE: NEW ISSUE (4263) [Primer] Inform domain specific processing of ignorability of assertions
- [Primer] Proposal to close action 196
- [NEW ISSUE] Primer: Absence of Policy Assertions (editorial) [Issue 4288]
- ...[GUIDELINES] Use of @wsp:optional and @wsp:Ignorable on an assertion (Issue
Monday, 29 January 2007
- RE: NEW ISSUE: [GUIDELINES] Use of @wsp:optional and @wsp:Ignorab le o n the same assertion
- Re: NEW ISSUE: [GUIDELINES] Use of @wsp:optional and @wsp:Ignorab le o n the same assertion
- Agenda: WS-Policy WG telcon 25 - 2007-01-31
Thursday, 25 January 2007
Wednesday, 24 January 2007
- Re: NEW ISSUE 4130: Ignorable assertions must be ignored
- Re: [NEW ISSUE] 4103 Questionable use of Contoso Ltd in Primer
Tuesday, 23 January 2007
- Re: LC Comments from SAWSDL WG (WS Policy issue 4188)
- Bug 4270: Primer versioning example
- RE: policy scenarios and test cases
Monday, 22 January 2007
- RE: WS-Addressing comments relating to WS-Policy LC
- RE: NEW ISSUE 4130: Ignorable assertions must be ignored
- RE: policy scenarios and test cases
- policy scenarios and test cases
- Re: NEW ISSUE 4130: Ignorable assertions must be ignored
Friday, 19 January 2007
- Re: I volunteer for the UDDI scenario / test case definition work
- I volunteer for the UDDI scenario / test case definition work
- Re: [WS Policy Working Group Jan 2007 f2f day 2 2007-01-17] minutes (DRAFT)
- Re: NEW ISSUE 4130: Ignorable assertions must be ignored
Thursday, 18 January 2007
Friday, 19 January 2007
Thursday, 18 January 2007
- RE: NEW ISSUE: 3986 [Guidelines] Parameter vs. Nested Policy Decision at Domain Level?
- RE: NEW ISSUE: [GUIDELINES] Use of @wsp:optional and @wsp:Ignorab le o n the same assertion
- Re: NEW ISSUE: [GUIDELINES] Use of @wsp:optional and @wsp:Ignorable o n the same assertion
- NEW ISSUE: [GUIDELINES] Use of @wsp:optional and @wsp:Ignorable o n the same assertion
- RE: Initial proposal for Issue 4041
- resolution to 4238 and 4196
- RE: Editorial issues in the Attachment spec
- Proposed Resolutions to 4238 and 4196
- Re: New ISSUE 4254: Ownership of WSP namespace
- Re: [NEW ISSUE] 4103 Questionable use of Contoso Ltd in Primer
- RE: NEW ISSUE 4251 - Change syntax of some WSDL 1.1 identifiers
- RE: NEW ISSUE 4251 - Change syntax of some WSDL 1.1 identifiers
- [NEW ISSUE] 4255 [Primer] Section 2.9 should also explain basic attaching
Wednesday, 17 January 2007
- [NEW ISSUE] 4253 [Primer] Basic Concepts section on Policy does not explain usage reasonably
- New ISSUE 4254: Ownership of WSP namespace
- ROUGH outkine of steps with suggested dates
- Candidate Recommendation schedule and exit criteria
- RE: [Bug 4235] clarification needed to sect 4.3 to indicate that the normalization algorithm can be applied to wsp:Policy element used as XML element policy attachment
- FW: [Bug 4240] Title: The distribution example does not follow the axioms in Section 4.3.3
- [UPDATE] Issue 4206 - Updated Framework Proposal Only
- [UPDATE] Issue 4206 - Updated Framework Proposal Only
- RE: [Bug 4235] clarification needed to sect 4.3 to indicate that the normalization algorithm can be applied to wsp:Policy element used as XML element policy attachment
- NEW ISSUE 4251 - Change syntax of some WSDL 1.1 identifiers
- RE: Solution space for Issue 4127: Proposed WSDL 1.1 element identifiers can not deal with operation name overloading
- RE: [Bug 4235] clarification needed to sect 4.3 to indicate that the normalization algorithm can be applied to wsp:Policy element used as XML element policy attachment
- RE: NEW ISSUE 4138: Normalization Algorithm is broken
- RE: NEW ISSUE 4206: Clarify treatment of policy assertion parameters in compatibility determination
- RE: ACTION-152 Review 4.4.8 with respect to the addition of the ignorable attribute
- Re: [NEW ISSUE] 4103 Questionable use of Contoso Ltd in Primer
- action 173 issue 4045 scoping of wsdl1.1 identifiers
- Agenda: WS-Policy WG F2F 24 - 2007-01-16 to 2007-01-18
- Re: Issues omitted from f2f agenda
- Re: [NEW ISSUE] 4235 clarification needed to sect 4.3 to indicate that the normalization algorithm can be applied to wsp:Policy element used as XML element policy attachment
- [NEW ISSUE] 4238 framework spec does not formally define syntax (outline, etc) for compact form policy expression
- resolutions to 4204 and 4207
Tuesday, 16 January 2007
- Issues omitted from f2f agenda
- Re: WS-Addressing comments relating to WS-Policy LC
- Re: LC Comments from SAWSDL WG (WS Policy issue 4188)
- Re: [Bug 4211] WSDL WG Editorial comments on Attachment
- Re: [Bug 4210] WSDL WG Editorial comments on Framework
- [NEW ISSUE] 4235 clarification needed to sect 4.3 to indicate that the normalization algorithm can be applied to wsp:Policy element used as XML element policy attachment
- RE: NEW ISSUE 4138: Normalization Algorithm is broken
- Re: [Guidelines] NEW ISSUE 4198: Policy assertion semantics independent of attachment mechanism
- RE: NEW ISSUE 4138: Normalization Algorithm is broken
- FW: Last Call for C14N 1.1
- Re: NEW ISSUE 4206: Clarify treatment of policy assertion parameters in compatibility determination
- Re: Agenda: WS-Policy WG F2F 24 - 2007-01-16 to 2007-01-18
- Re: [NEW ISSUE]: 4207 misleading text in sect 2.2 (Attachments)
- WS-Policy Features and Interop Scenarios
- RE: NEW ISSUE 4138: Normalization Algorithm is broken
- RE: NEW Issue 4195: How to ignore some "ignorable" assertions only?
- Re: Initial proposal for Issue 4041
- RE: [NEW ISSUE]: LC Comments from SAWSDL WG
- RE: proposal for ACTION 181
- proposal for ACTION 181
- RE: NEW ISSUE 4206: Clarify treatment of policy assertion parameters in compatibility determination
- RE: [NEW ISSUE] 4230 normative text masquerading as non-normative guidance (Attachment)
- Re: [NEW ISSUE]: LC Comments from SAWSDL WG
- [NEW ISSUE] 4230 normative text masquerading as non-normative guidance (Attachment)
Monday, 15 January 2007
- Re: [NEW ISSUE]: LC Comments from SAWSDL WG
- Re: Suggested Feedback to WS-Policy
- Re: Initial proposal for Issue 4041
- Re: NEW ISSUE 4206: Clarify treatment of policy assertion parameters in compatibility determination
- RE: NEW ISSUE 4206: Clarify treatment of policy assertion parameters in compatibility determination
- RE: NEW ISSUE 4206: Clarify treatment of policy assertion parameters in compatibility determination
- Agenda: WS-Policy WG F2F 24 - 2007-01-16 to 2007-01-18
- Issue 4225 (was RE: Editorial issues in the Framework spec
- Issue 4226 (was RE: Editorial issues in the Attachment spec
- Re: Solution space for Issue 4127: Proposed WSDL 1.1 element identifiers can not deal with operation name overloading
- RE: NEW ISSUE 4224: [Framework] Section 4, last paragraph content is too restrictive - policy element information items are processed in multiple contexts
- NEW ISSUE 4224: [Framewokrk] Section 4, last paragraph content is too restrictive - policy element information items are processed in multiple contexts
- RE: NEW ISSUE 4138: Normalization Algorithm is broken
- RE: NEW ISSUE 4209: Example 3.1 does not follow the algorithm/definition in merging policies
- Re: NEW ISSUE: 4142 Contradictory recommendation for nesting and intersection
- RE: NEW ISSUE 4138: Normalization Algorithm is broken
- RE: NEW ISSUE 4209: Example 3.1 does not follow the algorithm/definition in merging policies
- RE: NEW ISSUE: 4142 Contradictory recommendation for nesting and intersection
Sunday, 14 January 2007
- RE: [NEW ISSUE]: 4204 misleading text in sect 2.3 (Framework)
- RE: [Bug 4211] WSDL WG Editorial comments on Attachment
- RE: [Bug 4210] WSDL WG Editorial comments on Framework
- RE: [NEW ISSUE]: LC Comments from SAWSDL WG
- Editorial issues in the Attachment spec
- Editorial issues in the Framework spec
- RE: NEW Issue: How to ignore some "ignorable" assertions only?
- RE: [UPDATE] 4196 Minor Updates to Issue and Proposal
Saturday, 13 January 2007
- RE: NEW ISSUE 4209: Example 3.1 does not follow the algorithm/definition in merging policies
- RE: NEW ISSUE: 4142 Contradictory recommendation for nesting and intersection
- RE: [NEW ISSUE]: 4203 Introduction misleading (Framework)
- RE: [NEW ISSUE]: 4207 misleading text in sect 2.2 (Attachments)
- RE: [NEW ISSUE]: 4205 editorial nits WS-Policy 1.5 - Framework
- FW: WSDL WG interest in WS-Policy issues
- Use of empty policy for nesting should be exemplified
- [Bug 4211] WSDL WG Editorial comments on Attachment
- [Bug 4210] WSDL WG Editorial comments on Framework
Friday, 12 January 2007
- NEW ISSUE: Example 3.1 does not follow the algorithm/definition in merging policies
- [UPDATE] 4196 Minor Updates to Issue and Proposal
- ACTION-174: See what XPointer are in line with WSDL and syntax
- Bug 4208: identifiers should use WSDL 1.1 element names not WSDL 2.0 component names
- RE: [NEW ISSUE] 4177 Disambiguate notational convention for choice syntax
- Solution space for Issue 4127: Proposed WSDL 1.1 element identifiers can not deal with operation name overloading
- RE: NEW ISSUE 4206: Clarify treatment of policy assertion parameters in compatibility determination
- [NEW ISSUE]: 4207 misleading text in sect 2.2 (Attachments)
- NEW ISSUE 4206: Clarify treatment of policy assertion parameters in compatibility determination
- [NEW ISSUE]: 4205 editorial nits WS-Policy 1.5 - Framework
- [NEW ISSUE]: 4204 misleading text in sect 2.3 (Framework)
- RE: [NEW ISSUE] How to ignore some "ignorable" assertions only?
- [NEW ISSUE]: 4203 Introduction misleading (Framework)
- Re: [NEW ISSUE]: 4196 Clarify namespace restrictions (Framework and Primer)
- [Guidelines] NEW ISSUE 4198: Policy assertion semantics independent of attachment mechanism
- RE: [NEW ISSUE] 4177 Disambiguate notational convention for choice syntax
- RE: [NEW ISSUE] 4197 LC Inconsistency on treatment of unknown extensibility elements (Framework, Primer, Guidelines)
- Re: [NEW ISSUE] 4103 Questionable use of Contoso Ltd in Primer
- [NEW ISSUE] 4197 LC Inconsistency on treatment of unknown extensibility elements (Framework, Primer, Guidelines)
- [NEW ISSUE]: 4196 Clarify namespace restrictions (Framework and Primer)
Thursday, 11 January 2007
- Suggested Feedback to WS-Policy
- RE: Initial proposal for Issue 4041
- Re: Initial proposal for Issue 4041
- RE: Initial proposal for Issue 4041
Wednesday, 10 January 2007
- RE: NEW ISSUE 4130: Ignorable assertions must be ignored
- NEW Issue: How to ignore some "ignorable" assertions only?
Thursday, 11 January 2007
Wednesday, 10 January 2007
- Initial proposal for Issue 4041
- RE: NEW ISSUE: Contradictory recommendation for nesting and intersection
- Re: NEW ISSUE 4130: Ignorable assertions must be ignored
- Re: [V.Next] 4178 Declaration of policy domains in policy expressions
- Re: NEW ISSUE 4130: Ignorable assertions must be ignored
- RE: NEW ISSUE 4127: Proposed WSDL 1.1 element identifiers can not deal with operation name overloading
- [NEW ISSUE]: LC Comments from SAWSDL WG
- RE: Last Call for C14N 1.1 (and updated WG notes)
- Re: [V.Next] 4179 Preferences for policy expressions
- RE: Agenda: WS-Policy WG Teleconference 23 - 2007-01-10
- Re: [V.Next] 4178 Declaration of policy domains in policy expressions
- Re: NEW ISSUE: Contradictory recommendation for nesting and intersection
- [V.Next] 4179 Preferences for policy expressions
- [V.Next] 4178 Declaration of policy domains in policy expressions
- [NEW ISSUE] 4177 Disambiguate notational convention for choice syntax
- RE: [NEW ISSUE] 4150 Duplicate text exists in Section 3 and 3.2, PolicyAttachment
- RE: Proposed solution for Issue 4141
- Re: Updated Policy Drafts
Tuesday, 9 January 2007
- Updated Policy Drafts
- RE: Proposed solution for Issue 4141
- Re: NEW ISSUE 4130: Ignorable assertions must be ignored
- RE: NEW ISSUE 4130: Ignorable assertions must be ignored
- RE: Proposed solution for Issue 4141
- Re: NEW ISSUE: Contradictory recommendation for nesting and intersection
- Re: NEW ISSUE 4130: Ignorable assertions must be ignored
- RE: NEW ISSUE 4130: Ignorable assertions must be ignored
- RE: Proposed solution for Issue 4141
- Re: NEW ISSUE 4130: Ignorable assertions must be ignored
- Re: NEW ISSUE 4130: Ignorable assertions must be ignored
- RE: NEW ISSUE 4130: Ignorable assertions must be ignored
- Re: NEW ISSUE 4130: Ignorable assertions must be ignored
- Re: NEW ISSUE 4130: Ignorable assertions must be ignored
- Re: [NEW ISSUE] 4103 Questionable use of Contoso Ltd in Primer
- WS-Addressing comments relating to WS-Policy LC
Monday, 8 January 2007
- RE: Agenda: WS-Policy WG Teleconference 23 - 2007-01-10
- Re: Concrete Proposal Around 3619
- Re: NEW ISSUE 4130: Ignorable assertions must be ignored
- Re: NEW ISSUE 4130: Ignorable assertions must be ignored
- Re: NEW ISSUE 4130: Ignorable assertions must be ignored
- Re: NEW ISSUE 4130: Ignorable assertions must be ignored
Sunday, 7 January 2007
Saturday, 6 January 2007
- Agenda: WS-Policy WG Teleconference 23 - 2007-01-10
- [DRAFT] Agenda: WS-Policy WG F2F 24 - 2007-01-16 to 2007-01-18
Friday, 5 January 2007
- [NEW ISSUE] 4150 Duplicate text exists in Section 3 and 3.2, PolicyAttachment
- RE: Proposed solution for Issue 4141
- Proposed solution for Issue 4141
- Re: [NEW ISSUE] 4103 Questionable use of Contoso Ltd in Primer
Thursday, 4 January 2007
- RE: Issue 4128 -- Action Item Dan Roth, Ashok Malhotra
- RE: Issue 4128 -- Action Item Dan Roth, Ashok Malhotra
Wednesday, 3 January 2007
- Re: Comment on Fragment Identifiers
- Re: NEW ISSUE: Contradictory recommendation for nesting and intersection
- Re: IRC Channel is down.
- IRC Channel is down.
- Re: [VER2] Agenda: WS-Policy WG Teleconference 22 - 2007-01-03
- [VER3] Agenda: WS-Policy WG Teleconference 22 - 2007-01-03
- RE: [VER2] Agenda: WS-Policy WG Teleconference 22 - 2007-01-03
- NEW ISSUE: Contradictory recommendation for nesting and intersection
- NEW ISSUE: Policy parameter definition is not accurate
Tuesday, 2 January 2007
- RE: ws-policy 12/20/2006: Updated Issue and Proposal - Issue 4069
- NEW ISSUE: Normalization Algorithm is broken
- RE: NEW ISSUE 4130: Ignorable assertions must be ignored
- RE: NEW ISSUE 4130: Ignorable assertions must be ignored
- [VER2] Agenda: WS-Policy WG Teleconference 22 - 2007-01-03
- Re: NEW ISSUE 4130: Ignorable assertions must be ignored
- Re: [NEW ISSUE] 4103 Questionable use of Contoso Ltd in Primer
- NEW ISSUE 4130: Ignorable assertions must be ignored
- NEW ISSUE 4129: Attaching Policies to EPRs
- NEW ISSUE 4128: Add References to WSDL 1.1 and WSDL 2.0 Component Syntax
- AI 175 done
- NEW ISSUE 4127: Proposed WSDL 1.1 element identifiers can not deal with operation name overloading
- Re: [NEW ISSUE] 4103 Questionable use of Contoso Ltd in Primer