[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (XDI-38) Rework intro to policy expression pattern
[ https://issues.oasis-open.org/browse/XDI-38?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=50083#comment-50083 ] Peter Davis commented on XDI-38: -------------------------------- TC: Drummond to initiate a thorough scrub of glossary and update the wiki page accordingly, pulling from OASIS-XACML as appropriate. > Rework intro to policy expression pattern > ----------------------------------------- > > Key: XDI-38 > URL: https://issues.oasis-open.org/browse/XDI-38 > Project: OASIS XRI Data Interchange (XDI) TC > Issue Type: Bug > Components: XDI Policy > Affects Versions: 1.0 > Reporter: Hubert Le Van Gong > Labels: editorial > > Policy Expression Requirements - Policy Expression Pattern > We really need to make an effort to better explain this section. I suggest that before laying out the exact pattern, we describe the approach in layman's terms. How about something like this: > [Place at the top of Policy Expression Pattern] > A policy is the combination of individual policy statements. An XDI policy statement can take two forms: > - A condition that must be met or, > - An authorized operation that may only be performed over a particular XDI statement (or subgraph?). > A condition is described using a <context> / <value> / <condition> patten where: > - <context> describes the relationship of this statement to other statements > in the policy (i.e. how to compose those statements) > - <value> is the boolean value the condition must match > - <condition> describes the condition to be evaluated by the policy > An authorized operation is described using a <context> / <operator> / <XDI subgraph> pattern where: > - <context> describes the relationship of this statement to other statements > in the policy (i.e. how to compose those statements) > - <operator> describes the graph operation that is requested > - <XDI subgraph> describes the targeted XDI statement (or subgraph) > In details, /.../ <== At this point, we can add the formal pattern description that’s already in the spec. However, I would recommend keeping the separation between the 2 types (condition & authorized operation) and align the terminology with the above. -- This message was sent by Atlassian JIRA (v6.2.2#6258)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]