My point is that EPAL currently re-uses the partial syntax and the syntax
is uses is that of the condition part of XACML as the condition
specification language, it does not depend on a XACML runtime, just wanted
to make sure folks did not assume that, this I would not say EPAL uses
XACML.
Anthony Nadalin | work 512.436.9568 | cell 512.289.4122
|---------+---------------------------->
| | Robin Cover |
| | <|
| | > |
| | |
| | 07/15/2003 10:24 |
| | AM |
|---------+---------------------------->
>----------------------------------------------------------------------------------------------------------------------------------------------|
| |
| To: Anne Anderson <> |
| cc: Anthony Nadalin/Austin/IBM@IBMUS, XACML TC <> |
| Subject: Re: [xacml] IBM Develops New Language for Writing Privacy Policies |
>----------------------------------------------------------------------------------------------------------------------------------------------|
On XACML in EPAL
2003-07-15:
http://www.zurich.ibm.com/security/enterprise-privacy/epal/XML-Schema/cs-xacml-schema-policy-01.xsd
http://www.zurich.ibm.com/security/enterprise-privacy/epal/XML-Schema/
http://www.zurich.ibm.com/security/enterprise-privacy/epal/XML-Schema/epal-policy.xml
Some other references in:
http://xml.coverpages.org/ni2003-07-09-a.html
"IBM Releases Updated Enterprise Privacy
Authorization Language (EPAL) Specification"
clip:
---------------------------------------------------
<?xml version="1.0" encoding="UTF-8" ?>
- <xs:schema targetNamespace="urn:oasis:names:tc:xacml:1.0:policy"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:xacml="urn:oasis:names:tc:xacml:1.0:policy"
elementFormDefault="qualified" attributeFormDefault="unqualified">
- <!-- -->
<xs:element name="PolicySet" type="xacml:PolicySetType" />
- <xs:complexType name="PolicySetType">
- <xs:sequence>
<xs:element ref="xacml:Description" minOccurs="0" />
<xs:element ref="xacml:PolicySetDefaults" minOccurs="0" />
<xs:element ref="xacml:Target" />
- <xs:choice minOccurs="0" maxOccurs="unbounded">
<xs:element ref="xacml:PolicySet" />
<xs:element ref="xacml:Policy" />
<xs:element ref="xacml:PolicySetIdReference" />
<xs:element ref="xacml:PolicyIdReference" />
</xs:choice>
<xs:element ref="xacml:Obligations" minOccurs="0" />
</xs:sequence>
<xs:attribute name="PolicySetId" type="xs:anyURI" use="required" />
<xs:attribute name="PolicyCombiningAlgId" type="xs:anyURI"
use="required" />
</xs:complexType>
- <!-- -->
<xs:element name="PolicySetIdReference" type="xs:anyURI" />
<xs:element name="PolicyIdReference" type="xs:anyURI" />
- <!-- -->
<xs:element name="PolicySetDefaults" type="xacml:DefaultsType" />
<xs:element name="PolicyDefaults" type="xacml:DefaultsType" />
- <xs:complexType name="DefaultsType">
- <xs:sequence>
- <xs:choice>
<xs:element ref="xacml:XPathVersion" />
</xs:choice>
</xs:sequence>
</xs:complexType>
-----------------------------------------------------
Robin Cover
XML Cover Pages
WWW: http://xml.coverpages.org
Newsletter: http://xml.coverpages.org/newsletter.html
On Tue, 15 Jul 2003, Anne Anderson wrote:
> Perhaps EPAL has changed in a recent release, but the 9 May 2003
> version imports xacml-context:Request and xacml:Policy and uses
> xacml:Condition as the condition syntax. Examples make use of
> urn:...xacml:1.0:data-type:x500Name,
> urn:...xacml:1.0:data-type:rfc822Name, a bunch of our
> FunctionIds, xacml:AttributeDesignator, etc.
>
> Anne
> --
> Anne H. Anderson Email:
> Sun Microsystems Laboratories
> 1 Network Drive,UBUR02-311 Tel: 781/442-0928
> Burlington, MA 01803-0902 USA Fax: 781/442-1692
>
>
> You may leave a Technical Committee at any time by visiting
http://www.oasis-open.org/apps/org/workgroup/xacml/members/leave_workgroup.php
>
>
