OASIS eXtensible Access Control Markup Language (XACML) TC

 View Only

Minutes for September 12, 2024 TC Meeting

  • 1.  Minutes for September 12, 2024 TC Meeting

    Posted 10-10-2024 15:45
    I. Roll Call & Minutes
    Voting members
    Hal Lockhart (Co-Chair)
    Steven Legg
    Cyril Dangerville

    (Because of a technical problem Hal was not able to hear the call. Steven provided the following summary.)

    Voting Members: 3 of 4 (75% - quorum)

    Approve Minutes for 15 August, 2024 TC meeting

    Vote: Approved unanimously.

    II. Administrivia
    GitHub "cc" to List update status
    Report from Bill via Hal:
    Oasis consultant is still working on this issue.

    III. Issues
    Steven:
    Markup v4.0 docs have begun. I have pasted the simple bitmap files for now. Cyril has
    begun exploring various technologies to develop these diagrams semantically.

    Next up will be to dive into replacing the Target framework with conditional mechanics...
    which opens up the conversation of possibly redefining the relationship between Targets,
    Conditions and Rules. My current thinking is that we keep both Target and Condition, both
    have same structure but, Condition can only exist in a Rule and Target only exists in
    a Policy.

    Combining Algorithms have been coalesced into a single structure. The Only One Applicable
    Combining Algorithm has some issues that make it unique (e.g. doesn't apply to Rules)
    and unwieldy. I suggest we remove this from v4.0.

    Sections 5 & 7 assumes XML is the only XACML syntax used for XACML. This creates issues
    if we are going to pursue JSON and/or YAML syntax in version 4.0. Perhaps we can address
    this with generic elements of each syntactic structure. A non-normative examples could
    help demonstrate this. Also, it may make sense to merge these two sections. I will
    explore using an example to create a description using the merged approach.

    ====

    IV. The next meeting will be on Thursday, October 10.