Time: 4:30 PM EDT
Zoom:
Zoom Link:
http://tinyurl.com/48n4yrzs Meeting ID: 850 9753 8468
Minutes for 18 July 2024 TC Meeting
I. Roll Call & Minutes
Voting members
Hal Lockhart (Co-Chair)
Bill Parducci (Co-Chair)
Steven Legg
Voting Members: 3 of 4 (75% - quorum)
Approve Minutes 20 June, 2024 TC Meeting
https://groups.oasis-open.org/discussion/minutes-20-june-2024-tc-meeting Vote: Approved unanimously.
II. Administrivia
GitHub “cc” to List update status
Bill:
TC Admin had troubles with getting this working. I think I can setup a forward from my
account. It may not be pretty but should get github messaging to the list for those not
actively participating.
General consensus that we should try this.
III. Issues
Steven:
Now that we have the template for v4.0 we can begin carving off work sections to begin
authoring content. Markdown allows for easy cooperative editing because of its text
based nature.
#34 Composite functions
Steven:
Cyril posted an issue that is similar to a parameterized or shared/global variables use
case that I have. #34 removes attribute selectors/designator and so commonality breaks
if we go down that path. It would be good if we can work through this so that we
can potentially merge these use cases. I'll follow up on the github list.
XPath (JSONPath) to separate Profile(s)
Steven:
I see the value in keeping the core spec as simple as possible.
Hal:
I agree, I think we should take it out of the core but keep it in the standard.
Is the plan to make XACML language agnostic? Is it possible.
Steven:
We haven't thrashed that out yet. It is already addressed to some extent in XACML v3.
Hal:
I'll be very interested to see if there is something that simply cannot be agnostically
described
There was a brief discussion on how the v4 standard might be named should the spec become
language agnostic. Some early ideas: XACMLJ, XACML/JACML. TC members are encouraged to
discuss this further on the list as v4 progresses.
meeting adjourned.
Next meeting: 15 August, 2024