You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »


White Paper Definition


An educational document to bring awareness, support, and promote adoption of philosophies, ideals, and deliverables supported and developed by the Trust over IP community.


White Paper Publication Process



  1. Gate 1 - Authors register white paper and status on the White Papers in Development Wiki - providing a link to document for comments and edits where applicable, contact information of author(s) and one or two sentences description.
  2. Approval Step 1 - Authors obtain draft approval for the white paper as a deliverable by Working Group (Sponsor) who can provide peer review oversight
  3. Gate 2 - Authors submit final version of white paper to Ecosystem Foundry Working Group for short presentation and recommendations from the White Paper Task Force
  4. Approval Step 2 - Sponsor Working Group approves deliverable and submits to Steering Committee
  5. Gate 3 - Steering Committee ensures alignment with Communication Strategy (may request recommendations) and gives final approval


White Paper Standards and Best Practices


Key Requirements


RequirementDescriptionOther
1IdentifierUnique WP IdentifierRegistered in GitHub White Paper Portal




2Classification

Proof of Concept

Proof of Vision

Use Case

Consultative






2Author(s)Names and Contacts




3Dates Created




Draft Approval


WG Final Approval


Steering Committee Approval


Published




4Working GroupWorking group responsible for deliverable




5Keywords

Primary

Working Group

Secondary

Community of interest

Ecosystem of interest





6Executive SummarySelf sufficient overview - one page




7Short DescriptionTwo to three sentences




8IntroductionBackground Information - Identify target community or ecosystem




9ObjectivePurpose of white paper - describe objective/opportunity




10Main ThesisDefine ecosystem/roles/actors


ToIP approach - role in solution


Requirements - functional and non-functional where applicable


Expected outcomes




11Conclusion





12ToIP ContactsInformation on who to contact - recruitment opportunity for WG




13References





14LinksEnsure active links to relevant ToIP materials and resources
15Media RecommendationsProvide relevant contacts, media (e.g., magazines, social media, links on websites, forums) to facilitate communication of ToIP white papers out to focus community/ecosystem
  • No labels