The Work Product now would be XDI Core Specification Version 1.0. This work product would have to advance through the required stages: Committee Spec Draft, Public Review Draft, Committee Spec, Candidate OASIS Standard, and OASIS Standard. The key though is that now, going towards the OS vote - you would be managing and voting on *one* WP - the multi-part spec - and you would ultimately present the membership with a vote on one Candidate OASIS Standard.
This seems like an excellent solution for the XDI TC. The advantages to this approach include:
- Each initial WP can evolve & progress at its own pace without being dependent on the others
- Each can achieve Committee Specification on its own pace, triggering the coverage of the OASIS IPR commitments when each is ready
- The TC can gain experience working with the Work Products and the spec in a more nimble manner while going through the early steps of documenting them
- When you are ready to proceed towards OASIS Standard, you only present the membership with a single vote, instead of 7 or 8.
The only disadvantage we noted was that TC members or external reviewers might find issues in the combined WP because they see it all together for the first time. The TC can manage this in part by keeping everyone apprised of the other parts and making sure to encourage people to look across the collection even when they are reviewing an initial single part CS.
I think the best next step is for us to work together to start setting up the filenames, URLs and other metadata associated with the set of Work Products that you are ready to start on.
Even though you will be working in the Docbook template, you will need to have the metadata to include as part of the cover pages in your work.
We will give you templates in Word or Open Office (your choice). The templates will give your editors the model for what to put into the Docbook files - the urls to use, etc. - and you'll be able to look at your output and compare it to the template to make sure you're getting it right.
This will also let us all get in alignment on the work titles, filenames and urls in docs.oasis-open.org
from the beginning.
Let me know if you have any questions on any of this. Personally, I am looking forward to learning more about XDI as we go forward as I certainly see that it may have value for OASIS in the future.