W3C home > Mailing lists > Public > public-ws-policy@w3.org > December 2006

New Issue 4069: Updating References for Use of xml:id

From: Monica J. Martin <Monica.Martin@Sun.COM>
Date: Mon, 11 Dec 2006 09:07:36 -0800
To: "public-ws-policy@w3.org" <public-ws-policy@w3.org>
Message-id: <457D9058.5040905@sun.com>

see: http://www.w3.org/Bugs/Public/show_bug.cgi?id=4069

=============
Title: Updating References for Use of xml:id
Target: Primer, Framework
Description and Justification:
Issue #3752 and #3560 [1] introduced and clarified the use of xml:id. 
However, a few more areas exist where xml:id is available for use. This 
should be clarified in the Framework and Primer documents. Currently, no 
example using xml:id exists in the Framework and its use is missing in 
the Primer. With the addition of xml:id, its use should be described and 
exemplified.

Proposal:
1. Framework, Section 4.2 Policy Identification
[amend to end of this section]

The following example illustrates how to associate a policy expression 
with the IRI-reference |"#P1"| using xml:id:

  (01) <wsp:Policy
         xml:id="P1"
         xmlns:wsp="http://www.w3.org/@@@@/@@/ws-policy"
         xmlns:xml="|http://www.w3.org/XML/1998/namespace|" >
  (02)   <!-- Details omitted for readability -->
  (03) </wsp:Policy>

2. Primer
Section 2.8 Referencing Policy Expressions
a. Change from:
  A policy expression may be identified by an IRI and referenced for
  re-use as a standalone policy or within another policy expression.
  There are two mechanisms to identify a policy expression: the wsu:Id
  and Name attributes. A PolicyReference element can be used to
  reference a policy expression identified using either of these
  mechanisms.

Change to:
  A policy expression may be identified by an IRI and referenced for
  re-use as a standalone policy or within another policy expression.
  There are three mechanisms to identify a policy expression: the
  wsu:Id, xml:id and Name attributes. A PolicyReference element can be
  used to reference a policy expression identified using either of
  these mechanisms.

b. Change from: Example 2-14

Change to:
[new paragraph under Example 2-14]
In the examples 2-12, 2-13, and 2-14 Contoso could have used either the 
xml:id or wsu:Id.

Note: There are no changes to Example 2-14 or the existing paragraph 
that follows: The |Name| attribute is an alternate mechanism to identify 
a policy expression....

Section 3.2 Normal Form for Policy Expressions (now Section 3.6)
[Note: As Issue 3965 was accepted, this text would be updated in new 
Section 3.6, Primer.]

Change from:
  If the referenced policy expression is in the same XML document as
  the reference, then the policy expression should be identified using
  the |wsu:Id| (XML ID) attribute and referenced using an IRI
  reference to this XML ID value.

Change to:
  If the referenced policy expression is in the same XML document as
  the reference, then the policy expression should be identified using
  the |wsu:Id|xml:id (XML ID) attribute and referenced using an IRI
  reference to this XML ID value.

  Reason: This is really clean up from Issue 3752,
  http://www.w3.org/Bugs/Public/show_bug.cgi?id=3752. This is also
  consistent with text in Section 4.3.4 Policy References in the
  Framework ("This attribute references a policy expression by an IRI.
  For a policy expression within the same XML Document, the reference
  SHOULD be an IRI-reference to a policy expression identified by an
  |ID|.").

Note: No changes are proposed for Guidelines, Section 5.1 although they 
may be considered in the future.

References:
[1] Issues list: http://www.w3.org/Bugs/Public/show_bug.cgi?id=3752, 
http://www.w3.org/Bugs/Public/show_bug.cgi?id=3560
[2] Primer, Framework (5 December 2006)
http://dev.w3.org/cvsweb/~checkout~/2006/ws/policy/ws-policy-framework.html?content-type=text/html;%20charset=utf-8 

http://dev.w3.org/cvsweb/~checkout~/2006/ws/policy/ws-policy-primer.html?content-type=text/html;%20charset=utf-8 
Received on Monday, 11 December 2006 17:08:07 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:20:43 GMT