September 27 

White paper Meeting Agenda

1. Read  anti trust policy:

       Antitrust Policy Antitrust Policy Notice

   Linux Foundation meetings involve participation by industry competitors, and it is the intention of the Linux Foundation to conduct all of its activities in accordance with applicable antitrust and competition laws. It is therefore extremely important that attendees adhere to meeting agendas, and be aware of, and not participate in, any activities that are prohibited under applicable US state, federal or foreign antitrust and competition laws. Examples of types of actions that are prohibited at Linux Foundation meetings and in connection with Linux Foundation activities are described in the Linux Foundation Antitrust Policy available at http://www.linuxfoundation.org/antitrust-policy. If you have questions about these matters, please contact your company counsel, or if you are a member of the Linux Foundation, feel free to contact Andrew Updegrove of the firm of Gesmer Updegrove LLP, which provides legal counsel to the Linux Foundation.

2. Submitting White paper for 9/27 deadline, ( Bobbi - Completed Bio's except Sean, ran out of spots  and will add his information as a note .
   1. **Do we invite Rose to mediate?

   2. The Wiki Page GLOBAL FORUM has the rest of the submission that needs to be completed  Our submission is due on 27th.  ACTION ITEM -COMPLETE SUBMISSION

3. Discuss Whitepaper Status:  ( White paper space on the wiki)

4. Discuss Sections
   1. Use Cases
      1. Bank Loans 
      2. Peer to Peer Energy Transaction
      3. Land Rights
      4. Grants Management

4. Promote  Works: 

September 20, 2019

White paper Meeting Agenda

1. Read  anti trust policy:

       Antitrust Policy Antitrust Policy Notice

   Linux Foundation meetings involve participation by industry competitors, and it is the intention of the Linux Foundation to conduct all of its activities in accordance with applicable antitrust and competition laws. It is therefore extremely important that attendees adhere to meeting agendas, and be aware of, and not participate in, any activities that are prohibited under applicable US state, federal or foreign antitrust and competition laws. Examples of types of actions that are prohibited at Linux Foundation meetings and in connection with Linux Foundation activities are described in the Linux Foundation Antitrust Policy available at http://www.linuxfoundation.org/antitrust-policy. If you have questions about these matters, please contact your company counsel, or if you are a member of the Linux Foundation, feel free to contact Andrew Updegrove of the firm of Gesmer Updegrove LLP, which provides legal counsel to the Linux Foundation.

2. Submitting White paper for 9/27 deadline, ( Bobbi - Completed Bio's except Sean, ran out of spots  and will add his information as a note .
   1. **Do we invite Rose to mediate?

   2. The Wiki Page GLOBAL FORUM has the rest of the submission that needs to be completed  Our submission is due on 27th.  ACTION ITEM -COMPLETE SUBMISSION

3. Discuss Whitepaper Status:  ( White paper space on the wiki)

4. Discuss Sections
   1. Use Cases
      1. Bank Loans 
      2. Peer to Peer Energy Transaction
      3. Land Rights
      4. Grants Management

4. Promote  Works: 

September 13th

White paper Meeting Agenda

1. Read  anti trust policy:

       Antitrust Policy Antitrust Policy Notice

   Linux Foundation meetings involve participation by industry competitors, and it is the intention of the Linux Foundation to conduct all of its activities in accordance with applicable antitrust and competition laws. It is therefore extremely important that attendees adhere to meeting agendas, and be aware of, and not participate in, any activities that are prohibited under applicable US state, federal or foreign antitrust and competition laws. Examples of types of actions that are prohibited at Linux Foundation meetings and in connection with Linux Foundation activities are described in the Linux Foundation Antitrust Policy available at http://www.linuxfoundation.org/antitrust-policy. If you have questions about these matters, please contact your company counsel, or if you are a member of the Linux Foundation, feel free to contact Andrew Updegrove of the firm of Gesmer Updegrove LLP, which provides legal counsel to the Linux Foundation.

2. Submitting White paper for 9/27 deadline, 

   Global Forum March:  Our submission is due on 27th.  Panel discussion of White Paper. Action Item: Bobbi to collect bio for submission and have completed for next week review.

3. Discuss Whitepaper Status:  ( White paper space on the wiki)
4. Discuss Sections
   1. Use Cases
      1. Bank Loans 
      2. Peer to Peer Energy Transaction
      3. Land Rights
      4. Grants Management
   2. For Submission each public sector segment will start with the Use case template and then recommendation . Recommendations will discuss via the 4 ring (or buckets or positioning or connections or segments or ecosystem. Groups is assigned with creating marketing term for "public sector journeys" (identity, interactions, regulations , governance )  a citizen takes .

September 6, 2019 

White paper Meeting Agenda

1. Read  anti trust policy:

       Antitrust Policy Antitrust Policy Notice

   Linux Foundation meetings involve participation by industry competitors, and it is the intention of the Linux Foundation to conduct all of its activities in accordance with applicable antitrust and competition laws. It is therefore extremely important that attendees adhere to meeting agendas, and be aware of, and not participate in, any activities that are prohibited under applicable US state, federal or foreign antitrust and competition laws. Examples of types of actions that are prohibited at Linux Foundation meetings and in connection with Linux Foundation activities are described in the Linux Foundation Antitrust Policy available at http://www.linuxfoundation.org/antitrust-policy. If you have questions about these matters, please contact your company counsel, or if you are a member of the Linux Foundation, feel free to contact Andrew Updegrove of the firm of Gesmer Updegrove LLP, which provides legal counsel to the Linux Foundation.

2. Submitting White paper for 9/27 deadline, 

   Global Forum March:

3. Discuss Whitepaper Status:  ( White paper space on the wiki)
4. Discuss Sections
   1. Use Cases
      1. Bank Loans 
      2. Peer to Peer Energy Transaction
      3. Land Rights
      4. Grants Management :Higher Ed

4. Promote Works:

Meetups

Online exhibitors Presentation

Building Relationships - Local govt agencies and civil society together. , spread info on our meeting makes onboarding simple. Find assoc. that are looking (second Muse) for blockchain solutions on govt enterprise level.  reach out to City of Chicago. Reach out to Metropolis. 

August 30, 2019 

White paper Meeting Agenda

1. Read  anti trust policy:

       Antitrust Policy Antitrust Policy Notice

   Linux Foundation meetings involve participation by industry competitors, and it is the intention of the Linux Foundation to conduct all of its activities in accordance with applicable antitrust and competition laws. It is therefore extremely important that attendees adhere to meeting agendas, and be aware of, and not participate in, any activities that are prohibited under applicable US state, federal or foreign antitrust and competition laws. Examples of types of actions that are prohibited at Linux Foundation meetings and in connection with Linux Foundation activities are described in the Linux Foundation Antitrust Policy available at http://www.linuxfoundation.org/antitrust-policy. If you have questions about these matters, please contact your company counsel, or if you are a member of the Linux Foundation, feel free to contact Andrew Updegrove of the firm of Gesmer Updegrove LLP, which provides legal counsel to the Linux Foundation.

2. Discuss Whitepaper Status:  (Bobbi - - I updated the White paper space on the wiki)
   
   
3. Discuss Use Cases
4. Bank Loans  -Govt watch dog for predatory leading, how does that work int the bank loan transactions and how Blockchain solution will benefit.

Sean:  Fina. service task force in IDWG , joined to align us with id group.  Pred. Lending  AML KYC 

1. Peer to Peer Energy Transaction
2. Land Rights
3. Grant Management : 

4. Promote Works:

Meetups

Online exhibitors Presentation

Global Forum March

Building Relationships - Local govt agencies and civil society together. , spread info on our meeting make on boarding simple. Find assoc. that are looking (second Muse) for blockchain solutions on govt enterprise level.  reach out to City of Chicago. Reach out to Metropolis. 

August 23, 2019 

White paper Meeting Agenda

1. Read  anti trust policy:

       Antitrust Policy Antitrust Policy Notice

   Linux Foundation meetings involve participation by industry competitors, and it is the intention of the Linux Foundation to conduct all of its activities in accordance with applicable antitrust and competition laws. It is therefore extremely important that attendees adhere to meeting agendas, and be aware of, and not participate in, any activities that are prohibited under applicable US state, federal or foreign antitrust and competition laws. Examples of types of actions that are prohibited at Linux Foundation meetings and in connection with Linux Foundation activities are described in the Linux Foundation Antitrust Policy available at http://www.linuxfoundation.org/antitrust-policy. If you have questions about these matters, please contact your company counsel, or if you are a member of the Linux Foundation, feel free to contact Andrew Updegrove of the firm of Gesmer Updegrove LLP, which provides legal counsel to the Linux Foundation.

2. Discuss Whitepaper Status:  (Bobbi - Not able to attend - I updated the White paper space on the wiki. My goals or this week are to clean up the introduction by updating graphics and adding relevant data.  
   
   
3. Discuss Use Cases
4. Bank Loans  -Govt watch dog for predatory leading, how does that work int the bank loan transactions and how Blockchain solution will benefit.
5. Peer to Peer Energy Transaction
6. Land Rights
7. Grant Management : (Bobbi - . I will discuss Grant section with Saptarshi during the LMDWG call, ( https://zoom.us/my/hyperledger.community,Monday,  1pm ET). 

August 9, 2019

White paper Meeting Agenda

White paper Meeting Agenda

1. Read  anti trust policy:

       Antitrust Policy Antitrust Policy Notice

   Linux Foundation meetings involve participation by industry competitors, and it is the intention of the Linux Foundation to conduct all of its activities in accordance with applicable antitrust and competition laws. It is therefore extremely important that attendees adhere to meeting agendas, and be aware of, and not participate in, any activities that are prohibited under applicable US state, federal or foreign antitrust and competition laws. Examples of types of actions that are prohibited at Linux Foundation meetings and in connection with Linux Foundation activities are described in the Linux Foundation Antitrust Policy available at http://www.linuxfoundation.org/antitrust-policy. If you have questions about these matters, please contact your company counsel, or if you are a member of the Linux Foundation, feel free to contact Andrew Updegrove of the firm of Gesmer Updegrove LLP, which provides legal counsel to the Linux Foundation.

2. Discuss Whitepaper Status:
3. Discuss Use Cases
   1. Bank Loans  -Govt watch dog for predatory leading, how does that work int the bank loan transactions and how Blockchain solution will benefit.
   2. Bill Payment for Public Service  Energy Sector
   3. Land Rights
   4. Grants Management

August  2, 2019

1. Read  anti trust policy:

       Antitrust Policy Antitrust Policy Notice

   Linux Foundation meetings involve participation by industry competitors, and it is the intention of the Linux Foundation to conduct all of its activities in accordance with applicable antitrust and competition laws. It is therefore extremely important that attendees adhere to meeting agendas, and be aware of, and not participate in, any activities that are prohibited under applicable US state, federal or foreign antitrust and competition laws. Examples of types of actions that are prohibited at Linux Foundation meetings and in connection with Linux Foundation activities are described in the Linux Foundation Antitrust Policy available at http://www.linuxfoundation.org/antitrust-policy. If you have questions about these matters, please contact your company counsel, or if you are a member of the Linux Foundation, feel free to contact Andrew Updegrove of the firm of Gesmer Updegrove LLP, which provides legal counsel to the Linux Foundation.

2. Discuss Whitepaper Status:
    Today's discussion was focused on what we learned in the Drummond Reed presentation on Self Sovereign identity can be applied to the Whitepaper. Each on of the four use cases must first discuss the identity issues associated with the functions in the use case.  With a new foundation for "Internet Attestations " a new model for verifying personal identities. professional / public verification with blockchain must be examined and discussed further. 
3. Discuss the Use Case for Grant Models,  Balwinder suggested reading https://www.mitre.org/sites/default/files/publications/PR-19-1654-MITRE%20Grants%20Mgt%20Blockchain%20Study%20Report.pdf
   Bobbi advised each use case has a section on wiki for work. Coming soon from the Learning Materials Development White Paper  Working Group. a Use Case Template for all Use Cases to use as a guide to developing Use cases 
   
   
   MOVING FORWARD:

Everyone will expand on the use case they discussed. A section of wiki page has been created for each of the use cases. Alphonso updated the map but wasn't on call to expand. will update the mapping.

NOTE: We have an updated version of the Mind Map already in the Wiki. I got confused as we talked with a previous version. Please look at the latest one, and let me know what you think about it. Thank you.

White paper Meeting Agenda

July 26, 2019

1. Read  anti trust policy:

       Antitrust Policy Antitrust Policy Notice

   Linux Foundation meetings involve participation by industry competitors, and it is the intention of the Linux Foundation to conduct all of its activities in accordance with applicable antitrust and competition laws. It is therefore extremely important that attendees adhere to meeting agendas, and be aware of, and not participate in, any activities that are prohibited under applicable US state, federal or foreign antitrust and competition laws. Examples of types of actions that are prohibited at Linux Foundation meetings and in connection with Linux Foundation activities are described in the Linux Foundation Antitrust Policy available at http://www.linuxfoundation.org/antitrust-policy. If you have questions about these matters, please contact your company counsel, or if you are a member of the Linux Foundation, feel free to contact Andrew Updegrove of the firm of Gesmer Updegrove LLP, which provides legal counsel to the Linux Foundation.

2. Discuss Whitepaper Status:
   We decided to discuss the Public Sector environment as see though commonalities 
   • Digital Identity
   • Regulated Transaction
   • Regulations
   • Governance
     
     
     As reflective by four areas of Public Sector involvement:
   • Public Administration
   • Public Service
   • Government
   • Community and Territory

By describing use case as they relate to the above criteria

1. • Bank Loans  -Govt watch dog for predatory leading, how does that work int the bank loan transactions and how Blockchain solution will benefit.
   • Bill Payment for Public Service  Energy Sector
   • Land Rights
   • Grant Management :

MOVING FORWARD:

Everyone will expand on the use case they discussed. A section of wiki page has been created for each of the use cases. Alphonso will update the mapping.

July 19, 2019

1. Read  anti trust policy
2. Discuss Whitepaper Status:
   1. Bobbi:First attempt at opening statement:

   2.  Purpose of Hyperledger Public Sector white paper is to discuss the incorporation of Blockchain technology in the Journeys/ situations a Citizen, Individual or Non-Public Entity many cover when dealing with areas of the Public Sector. We will discuss these events through four sectors of governmental functions:

      1. Public Administration
      2. Public Service
      3. Government
      4. Community and Territory

      We will discuss the effects Blockchain technology can have in transforming function and efficiencies in all areas of Public Sector initiatives.  With the governments, Business and citizens working together (3 pillars) we can transform the effectiveness of services / interactions. In order to leverage this new technology, analyze the implementations of public sector interactions to best utilize this technology.   Each sector of governments’’ journeys must pass through “RINGS” of blockchain implementation.  The “rings” are as follows:

      
      

      • Digital Identity
      • Regulated Transaction
      • Regulations
      • Governance

1. Discussed changing the terminology for the regulated transaction to COMPLIANCE transaction. "
2. Talked about Credit scores as a model where compliance governance a cooperation have been successful.
3. Must watch DATA issues , in light of a 5 year plan
4. Drummnd Reeds SSI presentation in two weeks will shed light on how SSI will interact with our use case models.
5. USE Cases:
   1. Bank Loans  -Govt watch dog for predatory leading, how does that work int the bank loan transactions and how Blockchain solution will benefit.
   2. Bill Payment for Public Service  Energy Sector
   3. Permits and Licencing 
6. Next Steps
   1. Work on describing each use case situation as a process through our concentric circles. 

June 28, 2019

1. Read  anti trust policy
2. Discussed Whitepaper Status
3. Discussed "getting Involved"  ( how to get LFID, How to edit wiki)
4. Presentation by Tarun Shukla on Decentralized Identity Management
   1. Evolution cycle of technology protocols
   2. Global Standards for identity management
   3. If you don't own id you cant manage it.  
   4. SSI everyone is a peer with a DID , Issuer , Verifier, individual routed on the blockchain
   5. Protocol established to enable different entries to share DID  ex: Did:sovern:Identifier, DID:eth;identifier
   6. DID ( decentralized ID )interacts with DID Document
   7. Elements of DID Document: 1. Did 2, Public Keys 3. Set of Auth 4. End points 5. timestamp 6. signature
   8. Adoption : top down or bottom up. Barriers include change business processes, change mind set, funding, understanding
5. Next Steps: Sean will attempt to get  Drummond Reed ,  authority in field, at next session(s)

June 21, 2019

II.  Paper Topics Pillars of data privacy wo/ Countries barriers

1. WHAT data are we collecting
2. HOW are we storing
3. Data transmission
4. Data Processing
5. Date Breech - mech to avoid . mitigate impact

Define functional nature of the blockchain . 

Governance model - can you access public data, govt regulation over info. 

Do Govt accept proposals? must be Yes to continue 

Who can access date - Agencies or Individual.  Permissioned / public 

Alphonso - Land Markets

Bahodir - Capital Markets / privacy / commodity exchange / regulations 

Next meeting : uses cases

Date:

June 14, 2019

II.  Paper Topics:

Discuss how to incorporate Public Sector Mapping diagram into whitepaper:

Alphonso:

Mind Map: 

Government (a regulatory environment) and Compliance , Highly regulated transactions .

Re-did to provide regulatory environment government provides 

Depicts a comprehensive framework for deciphering procedures of government

Regulatory environment for Data Privacy Laws

How do we parse personal from sensitive personal data. different level of data. 

Validate the mind map.

Introduction

1.1 Identity Management in Government

1.2 Compliance

1.3 Governance

III. Next Steps

NOTES:  6/7

Sean: 

 Standards - What does validation mean and at what 100% do you trust validation?

Sliding Scale

Rights and permission validators.

What are the Multiple layers of permissioned Identity

Alphonso

Regions::  Kinds of validation depends on how you see it thru the layers.

Highly Regulated information

Mind Map - add layer of complexity

permission of validators

Regulations  ( meta data)  What stays in Tradition DB or move to BC

Privacy Standards Multi Layered

Identity would be nodes

Govt. has power over ID,, Build an instrument  (dashboard) to slide along different decks, defend change to the way we Identify ourselves

Governments entities , do they handle the four sectors? 

No one should own your ID

How to Validate, 

Will government recognize  ID

Frameworks

NEXT STEPS:

How deep do we want to go?

*Technical Arch - not redo work

• Layers of IDentity
• Conceptual Schema
• How much information on one's Identity do we want to capture
• Use Cases

No POC but how BC can be used in human statistics .

Concept of Identity and how Governments interact with attestation.

, 

June 7, 2019

II.  Paper Topics:

Discuss how to incorporate Public Sector Mapping diagram into whitepaper

Introduction ( Bobbi, no new updates)

1.1 Identity Management in Government

1.2 Compliance

1.3 Governance

III. Next Steps

White paper Meeting Agenda

May 31, 2019

Layers of Identity, 

layer One : Public and Open 

Layer Two - {Public and Private

Layer Three - Private Permissioned

II.  Paper Topics:

Discuss how to incorporate Public Sector Mapping diagram into whitepaper

Introduction ( Bobbi, no new updates)

1.1 Identity Management in Government

1.2 Compliance

1.3 Governance

III. Next Steps

White paper Meeting Agenda

May 24, 2019

I. Introduction /  People on the call / Contact Information

II.  Paper Topics:

Introduction

1.1 Identity Management in Government

1.2 Compliance

1.3 Governance

III. Next Steps
https://www.oecd-ilibrary.org/governance/trust-and-public-policy_9789264268920-en).

White Paper Meeting Agenda

May 17, 2019

I. Introduction /  People on the call / Contact Information

II.  Paper Topics:

Introduction

1.1 Identity Management in Government

1.2 Compliance

1.3 Governance

III. Next Steps

May 10th

I. Introduction /  People on the call / Contact Information

II. Decide Where to edit Google or Wiki

III.

IV. 

Meeting Recordings

LikeBe the first to like this                                                                                                                                                                                                                                                                                No labels

• Edit Labels

Write a comment…

Hyperledger Public Sector White Paper

I. Introduction

1.1 What is Hyperledger 

1.2 Public Sector:

1.3 IMPACT STATEMENT

II. Identity management for Governments 

2.1 What is Identity Management 

2.2 Use Cases 

2.3 Recommendation Moving Forward 

III. Compliance 

3.1 What Is the Highly Regulated Transaction 

3..2 Use Cases

       * Land Entitlements

        *Agriculture   

3.3 Recommendations  Moving Forward 

IV. Governance 

4.1 Governments Blockchain governance 

4.2  Use cases 

4.3  Recommendations Moving Forward 

V. Conclusions 

Notes 8

Introduction

Purpose of This Paper

The purpose of this paper is to derive pathways for the Public Sector when discovering the benefits of Blockchain Technology When discussing Blockchain thru a Public Sector lense, (3) important segments need addressing: (1) Identity Management for Public Sector

(2) Compliance, as seen though government transaction ,and/or viewed thru the Highly regulated transaction, and (3) Governance . These areas we see the most benefits blockchain can effect.

We will describe Use cases to show how blockchains are being utilized to improve the public sector.  How tools can help across governments World wide efforts . This whitepaper will tackle the issues by looking at the problem facing the Public Sector and what is being done today and what will our recommendation  for government when adopting blockchain in the public sector.

Intended Audience

Across Governments [state the intended audience as precisely as possible. For most white papers, this will be a technical audience, not a business audience. Does their level of technical understanding matter? Are there some matters they should already understand before they can get anything from the current document? Can we point them to this kind of prerequisite information? Does it matter which framework(s) they are using: Fabric, Indy, Sawtooth, etc? Does it matter what issue they are trying to understand: security, interoperability, etc?]

What is Hyperledger 

Hyperledger is an open source collaborative effort created to advance cross-industry blockchain technologies. It is a global collaboration, hosted by The Linux Foundation, including leaders in finance, banking, Internet of Things, supply chains, manufacturing and technology. Hyperledger, as part of the Linux Foundation, provides technology leaders a uniquely open and collaborative international community from which to develop, validate, and field enterprise-grade blockchain technology solutions.

What is Hyperledger

Table 1: Summary of Hyperledger Frameworks:

Comment From Sofia Terzi The frameworks that must be listed here should include also Iroha and Indy. Iroha is an engine that can run public sector's smart contracts and Indy is for the identity part of our whitepaper.

FIGURE 1: THE HYPERLEDGER GREENHOUSE STRUCTURE

[Add a page break at the end of this section]his white paper explains... [start with a brief topic sentence that sums up what’s in the document. This section “tells them what you’re going to tell them.”]

[In this section, provide a high-level introduction to the topic being covered. If the main body of the white paper will cover four different topics, name them each here, and point to the section where they are considered in more detail.]

[This section doesn’t have to be written first, but it must be filled in before the publication is complete. This helps readers understand the scope of the white paper and whether it’s worth their time to read the entire publication.]  

Public Sector

Definitions

Public sector organisations are businesses set up with the aim of providing a public service rather than making a profit., existing in all three layers of government ( Federal. State Local)

Public Sector is usually comprised of organizations that are owned and operated by the government and exist to provide services for its citizens, instead of working toward the goal of collecting a profit, public sector entities seek to provide services, regulate activities and enforce laws.

1. Funding for public services are usually raised through a variety of methods, including taxes, fees, and through financial transfers from other levels of government

   1. Examples of organizations in the public sector include:

      • Education (Schools, Libraries)
      • Electricity
      • Emergency Services
      • Fire Service
      • Gas and Oil
      • Healthcare
      • Infrastructure
      • Law Enforcement
      • Police Services
      • Postal Service
      • Public Transit
      • Social Services
      • Waste Management
   2. .

IMPACT STATEMENT: 

Blockchain technology is relatively new technology and is in its very early stages of adoption. Questions need to be answered as to how the Public Sector and related industries  can  leverage blockchain technology in various verticals.  While there is a great hype and interest in the technology it is critical to ensure that initial deployments consider right use cases to demonstrate the effective use of technology.

The intent of this document is to help shape the role blockchain technology can have in optimizing what government can do for its citizens. By delving into three areas (Identity, Compliance issues and Governance ) we will draw conclusions as to how to structure blockchains, develop programs, and run these new system to best aid citizens the derive the optimal success. If  we understand how current use cases are leveraging this technology we can devise standards and guidelines for  governments on all levels to implement.

1 Identity Management in Government 

2. Compliance 

3. Governance 

2. Identity management for Governments:

 Topics discussed in working group:

CROSS BORDER ID credentials.

No personal information interoperability and privacy management  DID .

Information should not leave the boundaries (geo fencing) Cross countries boundaries.

Interoperability and privacy [If you need to list several points, consider using a set of bullets:

• People

• Places

• Things - IOT

2.1 What is Identity Management in dealing with the Public Sector

2.2 Use Cases

2.3 Recommendation Moving Forward

3. Compliance

3.1 What is the Highly regulated Transaction common with most dealing with the Public Sector

3.2 Use Cases

3.3 Recommendation Moving Forward

4. Governance

4.1 What is Blockchain Governance  in dealing with the Public Sector

4.2 Use Cases

4.3 Recommendation Moving Forward

5. Conclusions

This white paper explained... [sum up the white paper briefly. This section “tells them what you told them.” Although this may seem repetitive, some people flip to the back of a document to see “the bottom line” and what they might have missed.]

Further Resources

[In this section, list any further resources or interesting reading that might illuminate the topic more. Include enough detail so that a reader could easily locate that source, including URLs if appropriate.]

Notes

.01 VN.N published May,2019.

This work is licensed under a Creative Commons Attribution 4.0 International License

creativecommons.org/licenses/by/4.0

Acknowledgements

[list all the contributors to the white paper in alphabetical order by LAST name. Many working groups keep a list of members or contributors on their wiki pages or their minutes. Don’t include anyone’s name without their okay.]

[Although GDocs can’t do Endnotes, the designer will move all your footnotes here. In every footnote, provide the AUTHOR(s), the article or document TITLE, the PUBLISHER, the DATE, and if you have it, the PAGE NUMBER. For a website, include the URL and RETRIEVED ON DATE.]

Public Sector SIG Whitepaper

Standards Contributed by Learning Materials Development Working Group, Gordon Graham and Bobbi Muscara