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 3984 - [Guidelines] Assertion Parameters vs. Name Value Pairs
Summary: [Guidelines] Assertion Parameters vs. Name Value Pairs
Status: RESOLVED FIXED
Alias: None
Product: WS-Policy
Classification: Unclassified
Component: Guidelines (show other bugs)
Version: FPWD
Hardware: PC Windows XP
: P2 normal
Target Milestone: ---
Assignee: Felix Sasaki
QA Contact: Web Services Policy WG QA List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-11-18 01:23 UTC by Asir V Selvasingh
Modified: 2006-12-20 18:34 UTC (History)
0 users

See Also:


Attachments

Description Asir V Selvasingh 2006-11-18 01:23:32 UTC
Title: Assertion Parameters vs. Name Value Pairs.

Description: The Guidelines document says, 'The framework allows WS-Policy domain authors to define name value pairs, for example, to qualify an assertion ' [1]. The framework allows assertion authors to define assertion parameters [2]. The framework does not use the phrase 'name value pairs'.

Justification: To avoid confusion, the Guidelines document should use the terms defined in the Web Services Policy language.

Target: Guidelines for Assertion Authors.

Proposal: s/name value pairs/assertion parameters/g

[1] http://dev.w3.org/cvsweb/~checkout~/2006/ws/policy/ws-policy-guidelines.html?rev=1.8&content-type=text/html;%20charset=utf-8#parameterized-assertions
 
[2] http://www.w3.org/TR/2006/WD-ws-policy-20061117/#policy_assertion_parameter
Comment 1 Christopher Ferris 2006-12-20 18:34:38 UTC
See http://www.w3.org/2006/12/20-ws-policy-irc#T18-33-10
RESOLUTION Issue 3984 is closed to:
a)  Section 4.4.1: The framework allows policy assertion authors to define policy assertion parameters to qualify an assertion.
b) Change name value pair with policy assertion parameters.