# WG Meeting: 2025-07-01
## Agenda
- Review issues since review period started
- Version numbering
- Review period ends Sunday, August 10, 2025
- Voting period begins: Monday, August 11, 2025
- Voting period ends: Monday, August 25, 2025

## Attendees
- Atul Tulshibagwale (SGNL)
- Mike Kiser (Sailpoint)
- Sean O'Dell (Disney)
- John Marchesini (Jamf)
- Vatsal Gupta
- Shayne Miel (Cisco)
- Jay Baskar (Radiant Logic)
- Yair Sarig (Omnissa)

## Notes
### Version numbering
- (Atul) We should publish each intermediate draft
- (Shayne) This feels like a branching issue
- (Shayne) I feel all these changes we are making are working toward a version 5
- (Atul) What if people want to refer to the intermediate working drafts?
- (Shayne) We should only refer to voted on versions
- (Atul) Can we add a "sub version" number?
- (Shayne) Can we add commit hashes?
- (Sean) Agrees to "sub version" number
- (Yair) We can identify the sub-version as an "iteration" or something. So that people don't confuse it with an official version.
- (Shayne) What is the need to distinguish between the different iterations
- (Atul) People could use the iteration numbers to determine what they have implemented
- (Shayne) Shouldn't they be not using the iterations?
- (Atul) They might use them within their development process
- (Mike) This also causes confusion between interops and
- (Jen) There's confusion because we publish iterations on GitHub, and the implementers drafts too.
- (Jen) we can add a header section to clarify
- (Shayne) Unless we have an automated way of adding version numbers (in whichever form), it will be a nightmare to merge.
- (Atul) Is everyone OK with not identifying the working versions? (Shayne and Jen agree)

## Action Items
- Jen to add an issue to note header section for working group drafts (to be worked on after current spec goes final)