Date
Sep 07, 2016
...
- Before making substantive changes I will send proposed updates to the group to see.
...
I will be using Word for editing. This has nothing to do with my time at Microsoft, it's simply a better tool for this job than Google docs or GitHub. I can create copies of the document in other formats for anyone who doesn't like using Word for reviewing.
I will have questions, especially early on. I can make a separate post for each question or I can send groups of questions in a single email. Does this group have a preference?
I need to get up to speed on how issue tracking is done in GitHub.
Content changes
As we gather and review examples of consent receipts based on the v0.8 spec, my initial editing focus will be on:
- Document hygiene.
- Expanding the Introduction (just a little) to give more context. A spec like this is usually created as one element of a larger system. The challenge here is that there is no definition of that system yet for us to reference, so it is necessary to provide some of the explanation in this document. However, to be clear, I'm talking about expanding the explanation, NOT the justification.
...
This is the proposed schedule
Current: call for comments on draft spec commences
Sep 19
COB: deadline Close of business (Pacific) deadline for feedback on spec draft including examples and feedback from implementers.
Oct 20 and Oct 27
WG Meetings: Discussion of comments received,
Finalize draft document20
Candidate draft to WG. WG to determine whether appropriate to take to IIW for comments and review
Oct. 27
Final working session for WG (with/without IIW comments) on candidate draft
Nov 3
Final draft for WG review
...
Spec approval
Action Items
- Former user (Deleted) to post roadmap/schedule