All:
The first formal working draft of the TGF Primer has been finalised and loaded to the TC work area. You will have received an automated notification from OASIS.
This Working Draft 01 was created after three ‘passes’ from the informal editors’ draft of 13 February:
- 1st pass moved the entire original content into the OASIS official template;
- 2nd pass:
o integrated comments and edits from Andy regarding the Critical Success Factors (and aligned the Guiding Principles in consequence);
o I transposed Components 3 and 2, so that the running order is now Guiding Principles, CSF’s, Delivery Processes and Benefits Realisation;
o A Disclaimer is added at the beginning to clarify that much potential standards material appears in this draft, including draft conformance clauses (which will be moved to the ‘full’ standard deliverable as soon as we start work on that – this can obviously be dropped when the document is finalised;
o Complete editorial check for language, house style, formatting and consistent use of key terms.
- 3rd pass added my further content as promised:
o First cut of Technology Management Framework summary and diagram, including introduction to basic SOA concepts;
o Section on terminology and reference model;
o First draft list of key terminology for use in the Primer (not the complete terminology that would appear with the standard);
The draft is now officially open for comment!
Procedure for comments
This may look a little bureaucratic, but I’ve seen TC’s where there are hundreds of issues opened against working drafts, so a little planning will keep us out of trouble…
Comments should only be made against the PDF version of a formal draft even when other formats are available: line numbers may change in any .doc or .odf version of a text (because of layout/formatting differences – hence, the use of the PDF version only) and will change from one draft to the next.
To make a comment, send a new e-mail message to the TGF list, with the subject line: “New Issue – ” followed by a short issue title.
In the body of the message indicate:
Either that your issue is a general comment; or
the first line number in the PDF text that the issue is concerned with,
then give a succinct paragraph explaining your issue, and indicate (optionally) what you suggest changing or doing differently.
The editors will be reviewing all comments regularly and keeping track in the Issues List available in the work area. For minor, uncontroversial changes, an editor may simply reply that the issue taken on board and is resolved; otherwise, the editor will reply (with subject line amended, to remove the ‘New Issue’ prefix), an Issue number will be posted and the TC invited to comment further on the list in reply.
Please try to resist the urge to reply immediately to a new issue, to allow the editors to do their initial work! ;-)
The editors will close the issues list before each TC meeting and present a summary of the main issues, resolutions and items that require further consideration by the TC. When the TC decides to ask the editors to create a new iteration of a draft, the process will be repeated.
All the best,
Peter
Peter F Brown
Independent Consultant
Transforming our Relationships with Information Technologies
Blog pensivepeter.wordpress.com
LinkedIn www.linkedin.com/in/pensivepeter
Twitter @pensivepeter
P.O. Box 49719, Los Angeles, CA 90049, USA
Tel: +1.310.694.2278