Yeah, reconciling the OGF processes with any ISO requirements is a next step, as is updating various pages to call out the ISO/PAS relationship and correspondence of GFD.240 with ISO/IEC 23415:2024.
re: "given the ISO restrictions" you are referring to the limited access restrictions on the proof copy of the spec? Or something else?
If you think any OGF working docs pre-drafts we create can be public, but ISO-flavor-thereof should not be (for brand protection or just control reasons), then yes we need a private repo for that.
There's more issues like this. On the DFDL call today on our agenda is always the statement that everything must follow the OGF Intellectual Property rules, but that raises the concern of how does that need to evolve for us to smoothly interoperate with ISO also? Does the reminder statement need to change? As part of setting up OGF as a PAS submitter I am sure you guys worked through a bunch of this stuff. We need the short course on your conclusions from that analysis. (If this is written up anywhere I can RTFM)
We need something like this.