Working Group Title: Education Architecture

Introduction.

Education today is an experience that spans multiple, traditional education segments and that is lifelong and lifewide. Digital tools have enabled students to curate personalized learning paths based on their individual interests and needs, earning credentials, badges, and certifications from an increasingly diverse set of learning providers. These tools also have the potential to empower the most traditionally disadvantaged of students by giving them ownership of these achievements and the ability to display these as they pursue their goals in a changing workforce.


Hyperledger’s extensibility is an enabling technology tool that can form one part of the foundation of educational transformation. As an anchor of a student-centered record, it can to integrate, extend, and enhance, existing institutional applications, processes, and workflows.
The Education Architecture Group will explore and advise on issues related to integration with legacy application infrastructure of learning management systems (LMS), Student Information Systems (SIS), Enterprise Resource Planning (ERP), Integrated Library Systems (ILS), Instructional Apps, Customer Relationship Management Systems (CRM), Human Capital Management (HCM), Cloud Computing models (SaaS, PaaS, IaaS, Hybrid), and self-sovereign digital identity. In addition, this group will investigate the integration of data across the multiple institutional, informal, and workplace learning experiences in the student’s lifetime of learning, and whether these can be integrated into a comprehensive record of an individual’s knowledge, skills, and ability.

Goals of the Hyperledger Working Group for Education Architecture:

Please provide an introduction that addresses why the working group is required and what are the main goals and objectives of the group.


Scope: Please provide the scope and audience of the working group. Also, include items that are not within scope of this working group.  It’s as important to define the boundaries, to ensure a well-focused working group.

The Education Architecture working group is open to interested participants of all skill levels. In particular, this group will be comprised of institutional or individual participants across the education sector, including K12 school, districts, state entities, and institutions of higher education. In addition, individual instructors, researchers, students, entrepreneurs, investors, technology vendors, practitioners, artists, librarians, and policymakers are valuable participants.

The community will take initiative to specifically address:

Scope Not within Charter:

Work Products-Output assets from the Working Group may include

Collaborators (other groups)

The Education Architecture Working Group will collaborate with other existing or future Hyperledger working groups focused on Education and Training (curriculum focused).

The Education Architecture Working Group will also collaborate and share community development and standards work in credentialing and interoperability with appropriate standards bodies and groups interested in (1) DIDs; (2) data security; and (3) privacy policy.

Other Industry Affiliations may include: We will reach out to other industry groups to determine their interest in participating.

Interested Parties

The following individuals have already expressed an interest in joining this working group, and we hope they will become contributors over the first year:
(List of interested parties listed with their consent, including name, association, and optionally email addresses)

TBD

Proposed Chair

The following individual has volunteered to serve as the initial interim Chair for the working group: 

Feng Hou - Maryville University

Process of the Group

Transparency

The following proposed items will be created:

Amendments

Changes to the charter may be proposed by active group members and, if it obtains rough consensus as determined by the Chair, can be brought forward to TSC.

Disbanding

Should the scope reach completion or conversely the traffic on the various conversation forums and the teleconference activity wither to very low levels, then the Chair of the WG may ask the TSC to disband the WG.

Running the Working Group


Responsibilities of a Chair


The chair is responsible for the following items:

Minutes

Minutes for each meeting should be kept and accessible from the working group's wiki page on wiki.hyperledger.org. Members of the working group will need to decide who will keep notes.

Meeting Cadence

Working group plans to initiate cadence calls on a monthly basis.

Agendas

In advance of every meeting, the Chair should send out an agenda to both the Rocket.Chat and Mailing List to ensure that attendees know what will be discussed.

Cancelling a Meeting

Meetings are placed on the Hyperledger Community calendar. To ensure that the meeting can be removed, please send an email in advance of the meeting to zoom@hyperledger.org. In addition, please notify the mailing list and Rocket.Chat.

After Approval of Working Group

When a new working group gets approved, Hyperledger staff will ensure the following checklist is completed: