[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [tgf] Starter document for Transformational Government Framework Emergency Alerting Profile Version 1.0
|
Thank Paul, thanks John We probably need to think about the range of formatting options for the work. Some profiles I have worked on are almost like a chart, where each part of the original is referenced, and described and alongside it are the parts that are changed/profile
specific. Other profiles I have worked on are just narrative, but following the same sequence as the original, so you need to have both docs open to work out where the differences are. Yet others offer little reference to the original and is simply a description of changes. In technical profiles (like SAML) a distinction is made between a conformance profile and a deployment profile. A conformance profile indicates which features of the original
to be used (‘we will choose option a of the 3 options in the original’). A deployment profile indicates how the selected features for the conformance profile are to be configured. Now all this might be too fine-grained for the TGF but....what general approach do we want to follow, and make clear to readers? Cheers Colin From: tgf@lists.oasis-open.org [mailto:tgf@lists.oasis-open.org]
On Behalf Of Paul Knight Per the TC's submission request [1], please find the attached starter document for: Transformational Government Framework Emergency Alerting Profile Version 1.0 WP-abbrev: TGF-EA-Profile We expect this Work Product to be published at: Please let me know if anything here fails to meet your expectations. Further revisions to this Work Product must be maintained in Working Drafts, following procedures detailed in the TC Handbook [2]. Working Drafts should be made available by uploading the document(s) to the TC's Kavi document repository, or (provisionally/temporarily) to the TC's Subversion (SVN) repository, if SVN has been activated for your TC [3]. TCs are encouraged
to use ZIP packaging when the WD releases contain multiple files (and directories). For each WD revision, you will need to: 1) increment the Working Draft revision (number) from 01 to 02, 03, 04 etc., as successive Working Drafts are produced; the revision number needs to be updated at the top of the document in the stage identifier (Working Draft ##) and in
the document identifier within the page footer. 2) supply the relevant publication/release/upload date for each successive Working Draft instance, using the prescribed date format: DD Month YYYY; the date needs to be updated at the top of the document (just below the stage identifier,
Working Draft ##) and in the page footer. 3) provide suitable text for a document Abstract, updating this summary with successive revisions to provide an accurate description of the subject matter, goals, scope, etc. 4) keep the Acknowledgments (Appendix A) and Revision History (Appendix C) up-to-date with each WD revision. 5) consult the OASIS Naming Directives document when creating new artifacts that may be part of the Work Product (e.g., image files, XML schemas), observing the rules for name characters in files and proposed directories, and for proposed
URIs/namespaces [4]. When the TC votes [5] to approve a Working Draft as a Committee Draft (CSD or CND), the Chair or other designated person must submit a "Committee Specification Draft Creation and Upload Request" accessible on the TC Administration Requests
Page [6]. Upon receipt of this form, the TC Administrator will QC and process the Work Product for official publication in the OASIS Library as a Committee Draft (http://docs.oasis-open.org/), including addition
of the requisite cover page metadata and other boilerplate information, as described in the TC Handbook. [7] =========== References: [2] Working Drafts [3] SVN Version control, via Tools [4] OASIS Naming Directives [5] Approval of a WD as a CD (CSD or CND) [6] TC Administration Requests Page, see Committee Specification Draft Creation / Upload Request [7] Committee Specification Drafts and Committee Note Drafts Best wishes, Paul -- CAUTION: This email message and any attachments contain information that may be confidential and may be LEGALLY PRIVILEGED. If you are not the intended recipient, any use, disclosure or copying of this message or attachments is strictly prohibited. If you have received this email message in error please notify us immediately and erase all copies of the message and attachments. Thank you. ==== |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]