OASIS ACAL [XACML] TC

Bill Parducci (Chair)

Steven Legg

Cyril Dangerville

Key Outcomes

Decisions Made

• Schema alignment: Maintain identical type hierarchies across YAML, JSON, and XML schemas to match the ACAL core model, including abstract base types like named attribute designator type
• Non-negative integral type: Keep in specification with custom regex definition (YAML integer without minus sign) rather than relying on deprecated YAML 1.1 native type
• Apply element property: Replace expression property with argument across all specifications and examples
• Reserved prefixes: The prefixes urn:oasis:names:tc:xacml and urn:oasis:names:tc:acal are reserved for TC identifiers; external parties cannot create short identifier sets using these prefixes
• Core short identifier immutability: Explicitly documented that the predefined core short identifier set shall not be modified by implementers
• Example ordering: Keep XACML first, YAML second, JSON third in examples so JSON (most commonly used) appears closest to the description text
• Meeting cadence: Return to three-week meeting schedule

Pending Confirmation

• Literal double type schema fragment: William to review Cyril's question about accompanying schema example for this type
• XACML alignment: Steven assigned to check XACML conformance alignment with ACAL core model (similar to JACAL work completed)
• Metanorma framework evaluation: Cyril suggested exploring Metanorma (AsciiDoc-based standards framework used by ISO/OGC) for automated document generation; William to potentially discuss with OASIS staff

Technical Issues Resolved

• YAML schema differences: Identified that William's YAML schema flattened some type hierarchies (e.g., removed base attribute selector type) for simplicity; decision to restore full hierarchy for consistency
• Short ID value type: Replaced with URI type in YAML schema due to common naming conventions
• Obsolete conformance text: Removed incorrect statement that decision type, description type, and parameter type don't correspond to standalone ACAL root keys (they now do)
• Section numbering pain point: Cyril investigating Pandoc extensions for automatic section numbering to eliminate manual renumbering when inserting sections; will test on smaller JSON Path profile first

Specification Updates Completed

• Conformance tables: Cyril created three-column alignment table (ACAL type | JACAL schema | YAML schema) for issue #89, identifying discrepancies.
• Issue #88 (JACAL conformance): Cyril addressed all recommendations via sub-issue tracking
• YAML examples: Steven added YAML representation to all existing XACML/JSON example pairs in ACAL core, making YAML examples the shortest of the three formats
• README and FAQ: Cyril created comprehensive README with FAQ covering validation methods for XACML 1.0/1.1, JACAL, and conversion guidance

Action Items

• Cyril: Fix YAML schema to restore type hierarchies matching JSON schema and ACAL core model (issue #89)
• Cyril: Update three-column alignment table after schema fixes
• William: Incorporate updated alignment table into Reviewer's Guide (rename?) once Cyril completes schema work
• Steven: Check XACML conformance alignment with ACAL core model (issue #86)
• William: Review literal double type schema fragment question from Cyril (issue #88)
• Cyril: Complete UML diagram work (deferred to next week)
• Cyril: Test Pandoc automatic section numbering on JSON Path profile
• Team: Update multiple decision profile as priority over SAML profile

Website and Documentation

• OASIS site cleanup needed: Current site contains excessive pre-XACML 3 content; team discussing deprecation policy and removing outdated material
• GitHub Wiki consideration: William exploring GitHub Wiki as alternative to difficult-to-edit OASIS site (small dialog box, poor context visibility)
• Deprecated resources: LinkedIn group no longer exists, Jira no longer needed with GitHub, OASIS wiki outdated with old branding
• Mailing list naming: Future discussion needed on whether to rename lists from XACML to ACAL and ramifications for mail server