Wednesday, 28 March 2007
Tuesday, 27 March 2007
- [Bug 4393] [Primer] Add text to strict and lax policy intersection discussion describing how a policy consumer can determine issues due to intersection mode conflicts
- [Bug 4300] Misuse of best practices in primer
Monday, 26 March 2007
Friday, 23 March 2007
Thursday, 15 March 2007
- [Bug 4394] Type of the WSDL 2.0 {policy} property?
- [Bug 4394] Type of the WSDL 2.0 {policy} property?
Wednesday, 14 March 2007
- [Bug 4212] [Guidelines] Use of empty policy for nesting should be exemplified
- [Bug 4319] [Guidelines] (Editorial) WS-RM(P) reference format should be consistent with other references
- [Bug 3990] [Guidelines] Content in Section 5.7 is unclear
- [Bug 3989] [Guidelines] Suggested Format
- [Bug 3981] [Guidelines] Section 4 Relevance to Assertion Design
- [Bug 3988] [Guidelines] Section 8 Doesn't Illustrate How to Design an Assertion
- [Bug 3989] [Guidelines] Suggested Format
- [Bug 4072] [Guidance] Statements not relevant to assertion design
- [Bug 3987] [Guidelines] Section 5.9 - Lifecycle of Assertions?
- [Bug 4389] WS-Policy 1.5 Attachment UDDI tModel keys and related references outdated
- [Bug 4304] Test case for application/policy+xml media type
- [Bug 4393] [Primer] Add text to strict and lax policy intersection discussion describing how a policy consumer can determine issues due to intersection mode conflicts
- [Bug 4262] [Guidelines] Use of @wsp:optional and @wsp:Ignorable on the same assertion
- [Bug 4301] Test case for xml:id
- [Bug 4292] Intersection mode is neither defaulted nor specified
- [Bug 4391] Update WS-Policy 1.5 Attachment to point to latest UDDI specs in the references section
Tuesday, 13 March 2007
- [Bug 4073] [Guidelines] Free standing statements
- [Bug 3979] [Guidelines] Clarify guidance in section 5.9.1 on referencing policy expressions
- [Bug 3987] [Guidelines] Section 5.9 - Lifecycle of Assertions?
- [Bug 3987] [Guidelines] Section 5.9 - Lifecycle of Assertions?
- [Bug 4040] [Guidelines] Update guidelines to include discussion of ignorable
- [Bug 4035] Guidelines Section 2 should account for impact of assertions that do not manifest on the wire, or only apply to one party but may still impact the ability to interoperate, depending on whether they may be ignored.
- [Bug 4040] [Guidelines] Update guidelines to include discussion of ignorable
- [Bug 4035] Guidelines Section 2 should account for impact of assertions that do not manifest on the wire, or only apply to one party but may still impact the ability to interoperate, depending on whether they may be ignored.
- [Bug 4288] [Primer] Absence of Policy Assertions (editorial)
- [Bug 4263] [Primer] Add text to ignorable discussion on passing ignorable property of assertion to domain specific processing
- [Bug 4339] Update references to interoperability in Ignorable Policy Expressions section
- [Bug 4103] [Primer] Questionable use of fictitious corp. name "Contoso Ltd."
- [Bug 4255] [Primer] Section 2.9 should also explain basic attaching
- [Bug 4255] [Primer] Section 2.9 should also explain basic attaching
- [Bug 4142] Contradictory recommendation for nesting and intersection
- [Bug 4253] [Primer] Basic Concepts section on Policy does not explain usage reasonably
- [Bug 4300] Misuse of best practices in primer
- [Bug 4213] [Primer] Use of empty policy for nesting should be exemplified
- [Bug 4370] Round 2 WSDL 1.1 input file contains invalid references
- [Bug 4391] Update WS-Policy 1.5 Attachment to point to latest UDDI specs in the references section
- [Bug 4288] [Primer] Absence of Policy Assertions (editorial)
- [Bug 4379] Note about c14n 1.1
- [Bug 4311] test suite framework?
Monday, 12 March 2007
- [Bug 4389] WS-Policy 1.5 Attachment UDDI tModel keys and related references outdated
- [Bug 4389] WS-Policy 1.5 Attachment UDDI tModel keys and related references outdated
Thursday, 8 March 2007
Wednesday, 7 March 2007
- [Bug 4045] scoping of wsdl1.1 identifiers spec
- [Bug 4332] WSDL WG comment 2
- [Bug 4331] WSDL WG comment 1
- [Bug 4213] [Primer] Use of empty policy for nesting should be exemplified
- [Bug 4311] test suite framework?
- [Bug 4040] [Guidelines] Update guidelines to include discussion of ignorable
- [Bug 4035] Guidelines Section 2 should account for impact of assertions that do not manifest on the wire, or only apply to one party but may still impact the ability to interoperate, depending on whether they may be ignored.
- [Bug 4376] [Primer] need to change qname for the ws-addr metadata elements in examples
- [Bug 4375] [Guidelines] need to change qname for the ws-addr metadata elements in examples
- [Bug 4374] [Attachment] need to change qname for the ws-addr metadata elements in examples
- [Bug 4376] need to change qname for the ws-addr metadata elements in examples
- [Bug 4375] need to change qname for the ws-addr metadata elements in examples
- [Bug 4374] need to change qname for the ws-addr metadata elements in examples