This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 3551 - Misc. (editorial) corrections throughout
Summary: Misc. (editorial) corrections throughout
Alias: None
Product: WS-Policy
Classification: Unclassified
Component: Framework (show other bugs)
Version: FPWD
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Prasad Yendluri
QA Contact: Web Services Policy WG QA List
Keywords: editorial
Depends on:
Reported: 2006-07-31 21:18 UTC by Prasad Yendluri
Modified: 2006-08-31 14:32 UTC (History)
2 users (show)

See Also:


Description Prasad Yendluri 2006-07-31 21:18:29 UTC
From: [] On Behalf Of Prasad Yendluri
Sent: Tuesday, July 25, 2006 4:02 PM
Subject: NEW ISSUE: Misc. (editorial) corrections throughout

Title: Misc. (editorial) corrections throughout
Description: I would like to suggest a few mostly editorial corrections:

1.	section 2.3 terminology
Change From:  [Definition: A policy vocabulary of a policy is the set of all policy assertion types used in a policy.]  
              To:       [Definition: A policy vocabulary is the set of all policy assertion types used in a policy.]
            The removed words are redundant and this now becomes consistent with the description in section 3.2 (Policy Alternative) that reads The vocabulary of a policy is the set of all assertion types used in all the policy alternatives in the policy.

2.	Section 3  starting text says, This abstract model is independent of how it is represented as an XML Infoset. However the description of the Policy Assertion in section 3.1 makes a generous use of XML Infoset.:

a.	The policy assertion type is identified only by the XML Infoset  (QName)
b.	Policy expression nesting is used by domain authors to further qualify one or more specific aspects of the original assertion.   (Policy Expression is defined to be XML Infoset representation of a policy).
c.	The XML Infoset of an assertion MAY contain a non-empty [attributes] property and/or a non-empty [children] property.

Suggest rephrase the main description of section 3 to state that, the XML Infoset terminology is used for convenience of description but, the abstract model itself is independent of any Infoset serialization. 

3.	Section 3.1 last sentence: 

.. domain authors are encouraged to consider when the identity of the root Element Information Item alone is enough to convey the requirement (capability).

This seems to imply capability is another name for requirement?  Suggest take capability out of parenthesis like requirement or capability

4.	Section 4.1 last paragraph below example: 

Change Lines (02-05) to (Lines (03-05)

5.	Section 3.4:

Note that a requester may be able to support a policy even if the requester does not understand the type of each assertion in the vocabulary of the policy; the requester only has to understand the type of each assertion in the vocabulary of a policy alternative.

It is not sufficient if the requester understands assertions in a policy alternative. It also needs to be able to support them.
Rephrase the latter part of the sentence (after ;) as below:

;the requester only has to understand the type of each assertion in the vocabulary of a policy alternative the requester supports.

Justification: Provided Interspersed in the description part.
Target: WS-Policy 1.5 - Framework
Proposal  Replacement text proposed with the description.

Prasad Yendluri
Comment 1 Asir V Selvasingh 2006-08-02 00:17:25 UTC
These are good editorial changes. Thank you for carefully reviewing the drafts.

I request the WG to assign these changes to the editors.


Asir S Vedamuthu
Microsoft Corporation
Comment 2 Prasad Yendluri 2006-08-03 21:55:19 UTC
This was accepted and resolved on 08/02/1006 WS-Policy WG Call, with the resolution proposed in the issue originally.
Comment 3 Prasad Yendluri 2006-08-09 18:14:37 UTC
To follow the convention recommended in the WG meetig today, adding reference the minutes of the Aug 02, 2006 when this issues was resolved: