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

[Bug 5185] Guidelines - BP 1 and 21 are Duplicates

From: <bugzilla@wiggum.w3.org>
Date: Sat, 13 Oct 2007 02:25:19 +0000
To: public-ws-policy-qa@w3.org
Message-Id: <E1IgWgp-0007ZX-2X@wiggum.w3.org>


           Summary: Guidelines - BP 1 and 21 are Duplicates
           Product: WS-Policy
           Version: LC
          Platform: PC
        OS/Version: Windows NT
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Guidelines
        AssignedTo: fsasaki@w3.org
        ReportedBy: asirveda@microsoft.com
         QAContact: public-ws-policy-qa@w3.org

Title: Guidelines - BP 1 and 21 are Duplicates


The following two best practices and their narratives are duplicates.

a) [1] "Although a policy assertion may be constrained to a specific set of
policy subjects by Assertion Authors, its semantics should not be dependent
upon the mechanism by which the policy expression is attached to a given policy
subject. For instance, an assertion "Foo" has the same semantics when attached
to an operation policy subject regardless of whether it was attached using XML
element policy attachment or the external URI attachment mechanism.
Independence from a specific attachment mechanism allows policy tools to choose
the most appropriate mechanism to attach a policy without having to analyze the
contents of the policy.

Best Practice 1: Semantics Independent of Attachment Mechanisms

The semantics of a policy assertion should not depend on the attachment
mechanism used."

b) [2] "The Policy attachment mechanism used to communicate the policy
assertions should not affect or imply additional semantics in the
interpretation of Policy alternatives. If it did, each policy assertion would
need to be written with different (and possibly unknown) attachment mechanisms
in mind.

Best Practice 21: Reusable Assertions

Assertion Authors are encouraged to create policy assertions that can be used
regardless of attachment mechanism."

Justification: minimize the number of best practices.

Target: Guidelines

Proposal: attached is a concrete proposal to resolve the issue.


Asir S Vedamuthu
Microsoft Corporation
Received on Saturday, 13 October 2007 02:25:33 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:02:10 UTC