[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [xacml] IBM Develops New Language for Writing Privacy Policie s
Tim, My point exactly, you reuse the elements that have value, in this case it was the condition part of XACML as the condition specification language but this is hardly EPAL using XACML. I'm not knocking XACML in any way, just clarifying. Anthony Nadalin | work 512.436.9568 | cell 512.289.4122 |---------+----------------------------> | | Tim Moses | | | <tim.moses@entrus| | | t.com> | | | | | | 07/16/2003 07:16 | | | AM | |---------+----------------------------> >----------------------------------------------------------------------------------------------------------------------------------------------| | | | To: Anthony Nadalin/Austin/IBM@IBMUS, XACML TC <xacml@lists.oasis-open.org> | | cc: | | Subject: RE: [xacml] IBM Develops New Language for Writing Privacy Policie s | >----------------------------------------------------------------------------------------------------------------------------------------------| Anthony - Sounds to me like the Zurich researchers recognized the value of re-using some well-thought-out work that has been thoroughly reviewed, rather than starting from scratch. All the best. Tim. -----Original Message----- From: Anthony Nadalin [mailto:drsecure@us.ibm.com] Sent: Tuesday, July 15, 2003 5:04 PM To: XACML TC Subject: Re: [xacml] IBM Develops New Language for Writing Privacy Policies 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 | | | <robin@isogen.com| | | > | | | | | | 07/15/2003 10:24 | | | AM | |---------+----------------------------> >--------------------------------------------------------------------------- -------------------------------------------------------------------| | | | To: Anne Anderson <Anne.Anderson@Sun.com> | | cc: Anthony Nadalin/Austin/IBM@IBMUS, XACML TC <xacml@lists.oasis-open.org> | | 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-xac ml-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-p olicy.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: Anne.Anderson@Sun.COM > 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.p hp > > You may leave a Technical Committee at any time by visiting http://www.oasis-open.org/apps/org/workgroup/xacml/members/leave_workgroup.p hp You may leave a Technical Committee at any time by visiting http://www.oasis-open.org/apps/org/workgroup/xacml/members/leave_workgroup.php
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]