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 3706 - editors to clarify the use of the term "domain"
Summary: editors to clarify the use of the term "domain"
Alias: None
Product: WS-Policy
Classification: Unclassified
Component: Framework (show other bugs)
Version: PR
Hardware: PC Windows XP
: P2 normal
Target Milestone: ---
Assignee: maryann
QA Contact: Web Services Policy WG QA List
Depends on:
Reported: 2006-09-12 18:32 UTC by maryann
Modified: 2006-10-04 02:53 UTC (History)
0 users

See Also:


Description maryann 2006-09-12 18:32:49 UTC
There is an action item for the editors to investigate the use of the term domain in section 3.1 and throughout the document which is underway.

The ambiguity of the term begins with the use of "domain-specific" in 
3.1 Policy Assertion...

"A policy assertion identifies a behavior that is a requirement (or capability) of a policy subject. Assertions indicate domain-specific (e.g., security, transactions) semantics and are expected to be defined in separate, domain-specific specifications."

This discussion was restarted in the F2F ( )and this issue was created to capture that this question still exists for the working group.
Comment 1 maryann 2006-10-04 02:53:23 UTC
closed by editors....

removed unqualified use of the term "domain" in the framework document, there are now uses of "domain-specific" which is necessary to distinguish between domain-independent and domain-specific processing of the framework, but "domain authors" was replaced by "authors" and "domain assertions" by "assertions.