OASIS eXtensible Access Control Markup Language (XACML) TC

 View Only
Back to discussions
Expand all | Collapse all

Minutes 21 August 2025 XACML TC meeting

  • 1.  Minutes 21 August 2025 XACML TC meeting

    Posted 08-22-2025 17:33
    Time: 4:30 PM EST
    Zoom Link: http://tinyurl.com/48n4yrzs
    Meeting ID: 850 9753 8468

    Minutes for 21 August 2025 TC Meeting

    I. Roll Call & Minutes
    Voting members
    Bill Parducci (Co-Chair)
    Steven Legg
    Cyril Dangerville
    Voting Members: 3 of 4 (75% - quorum)

    Approve Minutes for 24 July 2025 TC meeting
    https://groups.oasis-open.org/discussion/minutes-24-july-2025-tc-meeting
    Approved unanimously

    II. Administrivia

    Bill:
    ACAL starter documents have been received from TC Admin. Oasis is aware of the move to
    the "core spec/language specific" model of ACAL.

    Steven:
    I will take a shot at creating the original ACAL version.

    There was a general discussion on migration from current (XML centric) document to the
    ACAL version. Timing and priorities were considered, as well as the relationship between
    language specific terminology ramifications and schema alignment.

    There was a discussion about how the ACAL work should be handled in gitHub. The consensus
    was that extending the current repository would be best.

    Cyril:
    Have we thought about a Logo for ACAL?

    Bill:
    I believe that we have latitude to come up with something. I can come up with some ideas
    to explore.

    III. Issues
    Mappings
    There was a discussion on how UML descriptions syntactically map to local language terms,
    definitions, etc. There was general consensus that there will be a glossary and mapping
    component.

    Regex
    There was a discussion on how regex should be used for validation and what level of
    detail the specification should attempt to specify for various string types.

    There was general agreement that the ShortID pattern in regex is OK.

    There was ongoing discussion in that the Identifier type would be an AnyURI that has a
    reference to the ABNF structure, with or without regex.

    ID References
    There was a general discussion re: how IDs should be referenced for different applications
    (PolicyId, CategoryId, AttributeId, etc.)

    Steven will list the references that will be effected by various naming options.

    Various issues were reviewed from gitHub has well.

    The next meeting will be held in 4 weeks.

    meeting adjourned.


Related Content