RE: [xacml] schema-16a

[Daniel Engovatov <dengovatov@crosslogix.com>]

Maybe a partial solution to that would be to revisit my suggestion on defining "policy declaration" schema, instead of the table and add an attribute to the FunctionDeclaration element, meaning "can be used for matching"?  That can not be used for XML based restriction though..

-----Original Message-----
From: Simon Godik [mailto:simon@godik.com]
Sent: Thursday, July 25, 2002 4:13 PM
To: xacml@lists.oasis-open.org
Subject: [xacml] schema-16a

in core schema 16a types MatchIdType, ConditionIdType, and FunctionIdType are defined either as enumeration

or restriction on enumeration. It is difficult to extend these type definitions.

 

The other way to do it (not perfect either but something that can be extended)

is to replace MatchIdType, ConditionIdType, FunctionIdType with xs:QName and document

QName values, such as function:interger-equal, etc.

 

Schema change: replace MatchIdType, ConditionIdType, and FunctionIdType with xs:QName.

Document all possible values that are currently defined in schema.

 

Simon Godik