W3C home > Mailing lists > Public > public-ws-policy@w3.org > May 2007

Bug 4414 proposed

From: David Orchard <dorchard@bea.com>
Date: Tue, 1 May 2007 15:13:48 -0700
Message-ID: <E16EB59B8AEDF445B644617E3C1B3C9C03A8B25B@repbex01.amer.bea.com>
To: "ws policy" <public-ws-policy@w3.org>

Here's the revised text roughly agreed upon by myself, Maryann, Asir and
reviewed but not agreed by Monica.  Note, it has been revised somewhat
since all of them reviewed it so the fragile consensus may have fallen
into a pile of sticks like so much dead wood ready to be kindling to
warm the fires of our hearts.  I have not looked at the relationship
between this text and the optional or ignorable sections.  I think
perhaps this could be "swizzled" into those.

If Company-X knows about the EndOfLife Policy assertion, it may or may
not include that assertion in an alternative in the first version.  If
it 
does include the assertion, marks the assertion with an "ignorable"
attribute, and provides no alternative without the
assertion, then:
- a client that does not know about the assertion and using lax
intersection will produce an intersection.  
- a client that does not know about the assertion and using strict
intersection will not produce an intersection.  
- a client that does know about the assertion and using strict or lax
intersection
will produce an intersection. 

If it does include the assertion, marks the assertion with an
"ignorable" attribute, and provides an alternative without the
assertion, then:
- a client that does or does not know about the assertion and using lax
or strict
intersection will produce an intersection.  

If Company-X adds theEndOfLife policy assertion type to a subsequent
Alternative and does not provide an alternative without the assertion
then after the policy expression has been deployed/used the same
algorithm holds true, notably that a client using
strict mode that does not understand the assertion will not intersect
with the alternative.   If CompanyX adds the EndOfLife policy assertion
with an ignorable attribute to only one alternative, and leaves another
alternative 
without the assertion alltogether, then clients
using strict mode who do not understand the EndOfLife assertion with the
ignorable information will still be compatible with the alternative that
does not contain the EndOfLife policy assertion as per the intersection
rules and the server can return an error if the request is received
after the expiry date.

If Company-X knows about the EndOfLife Policy assertion, it can
guarantee that clients that know or don't know about the EndOfLife
Policy Assertion can intersect under any mode by providing one
alternative with the assertion, and another alternative without the
assertion.   Clients that know about the EndOfLife Policy
assertion and performing strict intersection can guarantee interaction
with
services that know or don't know about the EndOfLife Policy assertion by
providing one alternative with the assertion and one alternative without

the assertion (wsp:Optional="true").  Clients that know about the
EndOfLife Policy
assertion and performing lax intersection can guarantee interaction with
services that know or don't know about the EndOfLife Policy assertion by
providing one alternative with the assertion and marked with
ignorable="true".

Cheers,
Dave
Received on Tuesday, 1 May 2007 22:13:57 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:20:50 GMT