<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "https://www.w3.org/Bugs/Public/page.cgi?id=bugzilla.dtd">

<bugzilla version="5.0.4"
          urlbase="https://www.w3.org/Bugs/Public/"
          
          maintainer="sysbot+bugzilla@w3.org"
>

    <bug>
          <bug_id>4198</bug_id>
          
          <creation_ts>2007-01-12 10:04:58 +0000</creation_ts>
          <short_desc>Policy assertion semantics independent of attachment mechanism</short_desc>
          <delta_ts>2007-01-17 20:03:23 +0000</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>1</classification_id>
          <classification>Unclassified</classification>
          <product>WS-Policy</product>
          <component>Guidelines</component>
          <version>LC</version>
          <rep_platform>Macintosh</rep_platform>
          <op_sys>All</op_sys>
          <bug_status>RESOLVED</bug_status>
          <resolution>FIXED</resolution>
          
          
          <bug_file_loc></bug_file_loc>
          <status_whiteboard></status_whiteboard>
          <keywords></keywords>
          <priority>P2</priority>
          <bug_severity>normal</bug_severity>
          <target_milestone>---</target_milestone>
          
          
          <everconfirmed>1</everconfirmed>
          <reporter name="Fabian Ritzmann">fabian.ritzmann</reporter>
          <assigned_to name="Fabian Ritzmann">fabian.ritzmann</assigned_to>
          <cc>monica.martin</cc>
          
          <qa_contact name="Web Services Policy WG QA List">public-ws-policy-qa</qa_contact>

      

      

      

          <comment_sort_order>oldest_to_newest</comment_sort_order>  
          <long_desc isprivate="0" >
    <commentid>13465</commentid>
    <comment_count>0</comment_count>
    <who name="Fabian Ritzmann">fabian.ritzmann</who>
    <bug_when>2007-01-12 10:04:58 +0000</bug_when>
    <thetext>Title

Policy assertion semantics independent of attachment mechanism

Description

A policy can be attached to a policy subject as external attachment, directly included, or referenced by the policy subject. The assertions contained in the attached policy maintain their semantics independent of the chosen attachment mechanism. The guidelines should make that explicit.

Justification

Assertion authors are constrained from designing assertions that change their semantics based on the attachment mechanism. Policy tools must have the liberty to choose the most appropriate or feasible attachment mechanism at any time without having to analyze the contents of the attached policy.

Target

Guidelines for Policy Assertion Authors

Proposal

Include in the Guidelines section 4.1:

WS-PolicyAttachment provides various mechanisms to attach a policy to a policy subject. Independent of the employed attachment mechanism, constraints may be defined to which policy subject an assertion may be attached [Web Services Policy Framework, section 3.4]. The semantics of a policy assertion may not depend on the mechanism by which a policy is attached to a policy subject. This allows policy tools to choose the most appropriate mechanism to attach a policy without having to analyze the contents of the policy.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>13599</commentid>
    <comment_count>1</comment_count>
    <who name="Fabian Ritzmann">fabian.ritzmann</who>
    <bug_when>2007-01-16 17:59:18 +0000</bug_when>
    <thetext>We modified the proposal and rephrased the sentence on constraining attachment to policy subjects. We hope this makes the text easier to understand.


Title

Policy assertion semantics independent of attachment mechanism

Description

A policy can be attached to a policy subject as external attachment, directly
included, or referenced by the policy subject. The assertions contained in the
attached policy maintain their semantics independent of the chosen attachment
mechanism. The guidelines should make that explicit.

Justification

Assertion authors are constrained from designing assertions that change their
semantics based on the attachment mechanism. Policy tools must have the liberty
to choose the most appropriate or feasible attachment mechanism at any time
without having to analyze the contents of the attached policy.

Target

Guidelines for Policy Assertion Authors

Proposal

Include in the Guidelines section 4.1:

WS-PolicyAttachment provides various mechanisms to attach a policy to a policy subject. Although a policy assertion may be tailored for a specific set of policy subjects by design, its semantics do not depend on the mechanism by which a policy is attached to a policy subject. 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.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>13674</commentid>
    <comment_count>2</comment_count>
    <who name="Christopher Ferris">chrisfer</who>
    <bug_when>2007-01-17 20:03:23 +0000</bug_when>
    <thetext>RESOLUTION: http://www.w3.org/Bugs/Public/show_bug.cgi?id=4198 closed with proposal in http://www.w3.org/Bugs/Public/show_bug.cgi?id=4198#c1 as amanded by Chris here: &quot;Although a policy assertion may be tailored for or constrained to a specific set of policy subjects by design, its semantics are not dependent upon the mechanism by which a policy expression is attached to a given policy...
&lt;fsasaki&gt; ...subject. For instance, an assertion &quot;Foo&quot; has the same semantic when attached to a WSDL1.1 operation regardless of whether it was attached using XML element policy attachment or the external URI attachment mechanism.&quot;
http://www.w3.org/2007/01/17-ws-policy-irc#T20-02-11

Note, the amendment merely changes one sentence and adds another to the original proposal.</thetext>
  </long_desc>
      
      

    </bug>

</bugzilla>