Wednesday, 31 January 2007
- [Bug 4072] [Guidance] Statements not relevant to assertion design
- [Bug 4292] Intersection mode is neither defaulted nor specified
- [Bug 3953] [Guidelines] Remove language that use of security policy assertions forces nested assertions for other domains
- [Bug 4270] Primer versioning example
- [Bug 4292] Intersection mode is neither defaulted nor specified
Tuesday, 30 January 2007
Monday, 29 January 2007
Monday, 22 January 2007
- [Bug 4270] Primer versioning example
- [Bug 4251] [WSDL11Ids] Change syntax for some WSDL 1.1 identifiers
- [Bug 4263] [Primer] Add text to ignorable discussion on passing ignorable property of assertion to domain specific processing
- [Bug 4213] [Primer] Use of empty policy for nesting should be exemplified
- [Bug 4040] [Guidelines] Update guidelines to include discussion of ignorable
- [Bug 4212] [Guidelines] Use of empty policy for nesting should be exemplified
- [Bug 4103] [Primer] Questionable use of fictitious corp. name "Contoso Ltd."
- [Bug 4251] [WSDL11Ids] Change syntax for some WSDL 1.1 identifiers
- [Bug 3953] [Guidelines] Remove language that use of security policy assertions forces nested assertions for other domains
Friday, 19 January 2007
Thursday, 18 January 2007
- [Bug 4041] Update primer to mention ignorable as needed
- [Bug 3986] [Guidelines] Parameter vs. Nested Policy Decision at Domain Level?
- [Bug 3985] [Guidelines] Section 5.3.1 should use the definition of policy assertion parameters from the Framework spec
- [Bug 4263] Add text to ignorable discussion on passing ignorable property of assertion to domain specific processing
- [Bug 4041] Update primer to mention ignorable as needed
- [Bug 4262] [Guidelines] Use of @wsp:optional and @wsp:Ignorable on the same assertion
- [Bug 4262] Use of @wsp:optional and @wsp:Ignorable on the same assertion
- [Bug 4251] Change syntax for some WSDL 1.1 identifiers
- [Bug 4238] framework spec does not formally define syntax (outline, etc) for compact form policy expression
- [Bug 4196] Clarify namespace restrictions (Framework and Primer)
- [Bug 4254] Change of WSP namespace to be compliant with w3c namespace policy
- [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
- [Bug 4240] Title: The distribution example does not follow the axioms in Section 4.3.3
Wednesday, 17 January 2007
- [Bug 4255] [Primer] Section 2.9 should also explain basic attaching
- [Bug 4138] Normalization Algorithm is broken (single conjunctive expressions)
- [Bug 4253] [Primer] Basic Concepts section on Policy does not explain usage reasonably
- [Bug 4254] Ownership of WSP namespace
- [Bug 4253] Basic Concepts section on Policy does not explain usage reasonably
- [Bug 4127] Proposed WSDL 1.1 element identifiers can not deal with operation name overloading
- [Bug 4045] scoping of wsdl1.1 identifiers spec
- [Bug 4045] scoping of wsdl1.1 identifiers spec
- [Bug 4198] Policy assertion semantics independent of attachment mechanism
- [Bug 4206] Clarify treatment of policy assertion parameters in compatibility determination
- [Bug 4045] scoping of wsdl1.1 identifiers spec
- [Bug 4206] Clarify treatment of policy assertion parameters in compatibility determination
- [Bug 4179] Preferences for policy expressions
- [Bug 4178] Declaration of policy domains in policy expressions
- [Bug 3639] Which policy alternative was selected?
- [Bug 3639] Which policy alternative was selected?
- [Bug 4045] scoping of wsdl1.1 identifiers spec
- [Bug 4251] Change syntax for some WSDL 1.1 identifiers
- [Bug 4208] identifiers should use WSDL 1.1 element names not WSDL 2.0 component names
- [Bug 4127] Proposed WSDL 1.1 element identifiers can not deal with operation name overloading
- [Bug 4240] Title: The distribution example does not follow the axioms in Section 4.3.3
- [Bug 4238] framework spec does not formally define syntax (outline, etc) for compact form policy expression
- [Bug 4230] normative text masquerading as non-normative guidance
- [Bug 4226] Attachment editorial issues
- [Bug 4225] Framework editorial issues
- [Bug 4224] Section 4, last paragraph content is too restrictive - policy element information items are processed in multiple contexts
- [Bug 4209] Example 3.1 does not follow the algorithm in merging policies
- [Bug 4205] editorial nits
- [Bug 4207] misleading text in section 2.2
- [Bug 4204] misleading text in sect 2.3
- [Bug 4203] introduction unclear and misleading
Tuesday, 16 January 2007
- [Bug 4197] Inconsistency on treatment of unknown extensibility elements (Framework, Primer, Guidelines)
- [Bug 4195] How to ignore some of the assertions marked ?Ignorable? only?
- [Bug 4188] LC Comments from SAWSDL WG
- [Bug 4177] Disambiguate notational convention for choice syntax
- [Bug 4150] Duplicate text exists in Section 3 and 3.2, PolicyAttachments
- [Bug 4236] personal comment not a comment from the WS-RX TC
- [Bug 4236] personal comment not a comment from the WS-RX TC
- [Bug 4211] WSDL WG Editorial comments on Attachment
- [Bug 4210] WSDL WG Editorial comments on Framework
- [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
- [Bug 4212] Use of empty policy for nesting should be exemplified
- [Bug 4142] Contradictory recommendation for nesting and intersection
- [Bug 4213] Use of empty policy for nesting should be exemplified
- [Bug 4141] Policy parameter definition is not accurate
- [Bug 3985] [Guidelines] Section 5.3.1 should use the definition of policy assertion parameters from the Framework spec
- [Bug 4198] Policy assertion semantics independent of attachment mechanism
- [Bug 4230] normative text masquerading as non-normative guidance
Monday, 15 January 2007
- [Bug 4226] Attachment editorial issues
- [Bug 4225] Framework editorial issues
- [Bug 4224] Section 4, last paragraph content is too restrictive - policy element information items are processed in multiple contexts
Saturday, 13 January 2007
- [Bug 4142] Contradictory recommendation for nesting and intersection
- [Bug 4213] Use of empty policy for nesting should be exemplified
Friday, 12 January 2007
- [Bug 4142] Contradictory recommendation for nesting and intersection
- [Bug 4212] 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
- [Bug 4209] Example 3.1 does not follow the algorithm in merging policies
- [Bug 4196] Clarify namespace restrictions (Framework and Primer)
- [Bug 4196] Clarify namespace restrictions (Framework and Primer)
- [Bug 4208] identifiers should use WSDL 1.1 element names not WSDL 2.0 component names
- [Bug 4127] Proposed WSDL 1.1 element identifiers can not deal with operation name overloading
- [Bug 4207] misleading text in section 2.2
- [Bug 4206] Clarify treatment of policy assertion parameters in compatibility determination
- [Bug 4127] Proposed WSDL 1.1 element identifiers can not deal with operation name overloading
- [Bug 4138] Normalization Algorithm is broken (single conjunctive expressions)
- [Bug 4141] Policy parameter definition is not accurate
- [Bug 4142] Contradictory recommendation for nesting and intersection
- [Bug 4150] Duplicate text exists in Section 3 and 3.2, PolicyAttachments
- [Bug 4177] Disambiguate notational convention for choice syntax
- [Bug 4178] Declaration of policy domains in policy expressions
- [Bug 4179] Preferences for policy expressions
- [Bug 4196] Clarify namespace restrictions (Framework and Primer)
- [Bug 4197] Inconsistency on treatment of unknown extensibility elements (Framework, Primer, Guidelines)
- [Bug 4198] Policy assertion semantics independent of attachment mechanism
- [Bug 4205] editorial nits
- [Bug 4204] misleading text in sect 2.3
- [Bug 4203] introduction unclear and misleading
- [Bug 4198] Policy assertion semantics independent of attachment mechanism
- [Bug 4197] Inconsistency on treatment of unknown extensibility elements (Framework, Primer, Guidelines)
- [Bug 4197] Inconsistency on treatment of unknown extensibility elements (Framework, Primer, Guidelines)
- [Bug 4196] Clarify namespace restrictions (Framework and Primer)
- [Bug 4196] Clarify namespace restrictions (Framework and Primer)
Thursday, 11 January 2007
Wednesday, 10 January 2007
- [Bug 4130] Ignorable assertions must be ignored
- [Bug 4128] Need references to WSDL 1.1 and WSDL 2.0 component syntax
- [Bug 4129] Attaching Policies to EPRs
- [Bug 4188] LC Comments from SAWSDL WG
- [Bug 4179] Preferences for policy expressions
- [Bug 4178] Declaration of policy domains in policy expressions
- [Bug 4177] Disambiguate notational convention for choice syntax
Friday, 5 January 2007
Wednesday, 3 January 2007
- [Bug 4128] Need references to WSDL 1.1 and WSDL 2.0 component syntax
- [Bug 4069] Updating References for Use of xml:id
- [Bug 4142] Contradictory recommendation for nesting and intersection
- [Bug 3985] [Guidelines] Section 5.3.1 should use the definition of policy assertion parameters from the Framework spec
- [Bug 4141] Policy parameter definition is not accurate
- [Bug 4141] Policy parameter definition is not accurate
Tuesday, 2 January 2007
- [Bug 4138] Normalization Algorithm is broken (single conjunctive expressions)
- [Bug 4130] Ignorable assertions must be ignored
- [Bug 4129] Attaching Policies to EPRs
- [Bug 4128] Need references to WSDL 1.1 and WSDL 2.0 component syntax
- [Bug 4127] Proposed WSDL 1.1 element identifiers can not deal with operation name overloading