[Bug 4196] Clarify namespace restrictions (Framework and Primer)

• From: <bugzilla@wiggum.w3.org>
• Date: Fri, 12 Jan 2007 23:08:56 +0000
• To: public-ws-policy-qa@w3.org
• CC:
• Message-Id: <E1H5VW4-0002OB-Vt@wiggum.w3.org>

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





------- Comment #1 from monica.martin@sun.com  2007-01-12 23:08 -------
UPDATES

1. DESCRIPTION
Schema snippet used for reference only:

[start]...
- <xs:element name="Policy">
- <xs:complexType>
- <xs:complexContent>
- <xs:extension base="tns:OperatorContentType">
  <xs:attribute name="Name" type="xs:anyURI" /> 
  <xs:anyAttribute namespace="##any" processContents="lax" /> 
  </xs:extension>
  </xs:complexContent>
  </xs:complexType>
  </xs:element>
  <xs:element name="All" type="tns:OperatorContentType" /> 
  <xs:element name="ExactlyOne" type="tns:OperatorContentType" /> 
- <xs:complexType name="OperatorContentType">
- <xs:sequence>
- <xs:choice minOccurs="0" maxOccurs="unbounded">
  <xs:element ref="tns:Policy" /> 
  <xs:element ref="tns:All" /> 
  <xs:element ref="tns:ExactlyOne" /> 
  <xs:element ref="tns:PolicyReference" /> 
  <xs:any namespace="##other" processContents="lax" /> 
  </xs:choice>
  </xs:sequence>
  </xs:complexType>
...[end]

Link reference: http://www.w3.org/2006/11/ws-policy.xsd

2. UPDATE to proposed change for Framework, Section 2.2:
Extensions that are Child Element Information Items added to Policy operators
wsp:Policy, wsp:All and wsp:ExactlyOne MUST NOT use the policy language XML
namespace name.

Received on Friday, 12 January 2007 23:09:21 UTC