Time: 2:30 PM EST
Zoom Link:
http://tinyurl.com/48n4yrzsMeeting ID: 850 9753 8468
Minutes for 5 December 2024 TC Meeting
I. Roll Call & Minutes
Voting members
Hal Lockhart (Co-Chair)
Bill Parducci (Co-Chair)
Steven Legg
Cyril Dangerville
Voting Members: 4 of 4 (100% - quorum)
Approve Minutes for 7 November, 2024 TC meeting
https://groups.oasis-open.org/discussion/minutes-xacml-7-november-2024-tc-meeting Vote: Approved unanimously.
II. Administrivia
GitHub “cc” to List update status
Bill:
We had a bit of a hiccup with the "cc" app from github and the agent has been disabled
pending resolution.
Calendar
Hall:
The calendar has been updated with meeting times Through March. In April will move back
to 4:30 EDT (unless TC decides upon another time)/
III. Issues
Follow-up from last meeting
Steven:
I am still working on the the ToDo list from last meeting: changing markdown to handle
indented paragraphs in the visually appealing way we discussed; continue making changes
to draft to simplify/reduce stuff: Combining Parameters (with the view that nothing is
taken out that cannot be achieved in another way); merge Obligation with Advice;
Decompose documents (XML/JSON, XPath JSONpath), will rename later. Implement markdown
change Bill and I came up with.
Cyril:
Please make sure to use the latest version I've committed. I also fixed some PDF issues.
Steven:
Yes, I have the latest version. I will use that as the basis for any changes.
Document Generation
Cyril:
I am testing a UML tool to generate all elements of XACML programmatically.
[ shared screen of current work, discussed ]
Noted that there are a number "tricks" that need to be used to manage attributes, etc.
The goal is to have automatic schema generation in XML, JSON, etc. This abstract
agnostic model should help develop the specification across schema languages.
There was a general discussion of how to express choices, expressions, etc.
Naming Convention
Cyril:
Would it be possible to change case so that XML types are capitalized. It would make
things cleaner/easier in the automated generation work.
Steven:
I think it would make sense to keep it for the XML version for familiarity. For JSON,
etc. we should have an field to follow what is normal there.
Bill:
To capture for clarity our guiding principles are:
XML = consistency with previous versions to ease transition
JSON = use the case/naming that is typical for JSON
General consensus is that is the approach we should use.
General discussion on formatting as Cyril walked through latest HTML/PDF generation.
Next meeting in 5 weeks (1 extra week to accomodate holiday schedules)
meeting adjourned.