Working Group Title: Education Architecture
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 disadvantaged of students by giving them ownership of these achievements and the ability to display these as they pursue their goals in a changing education and workforce ecosystem.
Distributed ledger technologies (DLT), including Hyperledger and other blockchains, is an enabling technology tool that can form a part of the foundation of this educational transformation. As an anchor of a student-centered record, they can to integrate, extend, and enhance, existing institutional applications, processes, and workflows. As an anchor for self-sovereign identities, they enable individuals to curate the artifacts of their learning and exchange them for value in a marketplace of skills.
The Education Architecture Group will explore and advise on issues related to implementation of DLT in an educational context. This includes integration with legacy application infrastructure, such as 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), and Cloud Computing models (SaaS, PaaS, IaaS, Hybrid). In addition, this group will explore issues related to data security and privacy in the context of self-sovereign digital identity, including 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 curated as 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.
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:
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.
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
The following individual has volunteered to serve as the initial interim Chair for the working group:
Feng Hou - Maryville University
The following proposed items will be created:
● Wiki
● Mailing List
● Rocket Chat
● Optional Github Repository
● Meeting Recordings will be stored in the Hyperledger Community Google Drive
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.
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.
The chair is responsible for the following items:
● Sending agendas for meetings to make meetings more productive
● Ensuring that minutes are taken, including capturing list of participants. This does not mean that they will be responsible for taking the minutes, but rather that someone is taking the minutes
● Leading the meeting
● Sending out cancellation notices prior to the meeting
● Ensuring that working group updates to the TSC are done on a quarterly basis
● Facilitating the group and helping ensure that the goals and objectives are set
● Enforcing the Working Group’s adherence to the Hyperledger Code of Conduct
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.
Working group plans to initiate cadence calls on a monthly basis.
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.
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.
When a new working group gets approved, Hyperledger staff will ensure the following checklist is completed:
❏ A Working Group Charter is created on the Hyperledger wiki based on the application, adding two lines ”Approved by the TSC on <date>” and “Implementing the standard working group process defined <here>”, linking to the right page on the wiki.
❏ Set up real-time chat channel for the working group. Channel should be named #{working-group-name}-wg.
❏ Set up the mailing lists for the working group. Use mailing list request form to create hyperledger-{working-group-name}-wg mailing list for this project.
❏ Set up a wiki page for the working group. Create a page at https://wiki.hyperledger.org/groups/{working-group-name}. The initial sections on the Wiki should include: Charter, Antitrust Policy Notification, Meeting Details, Communication Channels, Community Folder.
❏ Set up a community folder within the Hyperledger Community folder to store meeting recordings and other documents. Give permissions to the working group chair to edit.
❏ Set up a Zoom meeting id for hosting the working group meetings. This meeting should ensure that all meetings will be recorded to the cloud.
❏ Set up the quarterly working group reports for this working group. Add the working group to the quarterly working group schedule and working group updates page.
❏ Send Welcome Email Template
❏ Work with the working group lead to ensure that the community calendar is updated (Hyperledger Community calendar) to include the date/time of the meeting. IMPORTANT: Since a single Zoom account allows multiple IDs, but only one meeting can occur at the same time, ensure that the meeting day/time does not conflict with an existing community meeting.
❏ Send out calendar invite to the mailing list.