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 8124 - All: policy URIs - what do they reference?
Summary: All: policy URIs - what do they reference?
Status: CLOSED REMIND
Alias: None
Product: WS-Resource Access
Classification: Unclassified
Component: All (show other bugs)
Version: FPWD
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: notifications mailing list for WS Resource Access
QA Contact: notifications mailing list for WS Resource Access
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-10-29 15:32 UTC by Doug Davis
Modified: 2015-06-20 16:34 UTC (History)
0 users

See Also:

Attachments

Description Doug Davis 2009-10-29 15:32:39 UTC 
For each spec (except MEX) we've defined policy URIs -for example,
in WS-Transfer we now have the XML prefix "wstrp" mapping to:
   http://www.w3.org/2009/09/ws-trp

The WG needs to decide a couple of things:
1 - do we want to have a separate NS for the policy assertions or should
    we just reuse the normal NS for each spec
2 - if we do have separate namespaces then what do those URIs point to?
    For example, does http://.../2009/09/ws-trp reference the Transfer spec?
    What do we put in the Namespace table? Right now for "wstrp" it says
    "This specification".  Which, if remains, why do we have a separate NS?

If we see the policy assertions having a separate lifecycle from the specs
then a separate NS makes sense.  But if they will pretty much always be
tied to the spec then a separate NS seems pointless.

No proposal at this time - but we should discuss.
Comment 1 Robert Freund 2009-11-06 18:48:25 UTC 
Resolved, eliminate the policy namespaces and use the policy of the specification
Comment 2 Jackie 2015-06-20 16:34:07 UTC 
Please make my changes
Comment 3 Jackie 2015-06-20 16:34:57 UTC 
Please make my changes