Please describe your proposed solution.
Below we first explain the overall background, vision and progress of LearnerShape SkillsGraph, and then describe what we will deliver through this proposal.
LearnerShape SkillsGraph – Background and Vision
LearnerShape SkillsGraph will be a fully-functional open-source, standards-based Web 3 skills management solution. It is built on three core technical pillars:
- blockchain authentication with credential privacy
- open source code with standard APIs
- standards compliance.
The proof-of-concept version of SkillsGraph was developed with Catalyst F6 funding and is available to the public at <https://skillsgraph.learnershape.com/>. Full documentation is available at <https://learnershape.gitbook.io/learnershape-skillsgraph/>. The open source code is available at <https://github.com/LearnerShape/ls-auth-api> and <https://github.com/LearnerShape/ls-auth-ui>.
SkillsGraph is currently being piloted in two Catalyst-funded projects:
- F7 - PACE: Skills credentials (<https://cardano.ideascale.com/c/idea/381645>) – This project is piloting SkillsGraph technology with a community-selected skill. This is currently being discussed on the Gimbalabs Discord server at <https://discord.com/channels/767416282198835220/905784720565080084> (Gimbalabs is LearnerShape partner and Randall Harmon of Gimbalabs is leading this effort).
- F8 - PeopleCert DevOps Pilot on Cardano (https://cardano.ideascale.com/c/idea/397146) – This project is using SkillsGraph and the technology of our partner ProofSpace (<https://www.proofspace.id/>) to pilot a blockchain solution for the DevOps qualification of leading global certification company PeopleCert (<https://www.peoplecert.org/>). The pilot will conclude by Q4 2023, and we aim to extend the service to other PeopleCert qualifications if the pilot is successful.
LearnerShape's vision is that SkillsGraph will provide an open-source alternative to existing skills management solutions. For example, the leading current solution is LinkedIn, which is highly functional, but a proprietary walled garden that controls user data. By contrast, SkillsGraph is open source so that any entity that wishes to do so can operate a SkillsGraph instance, and all instances can access standards-based user data (to the extent users wish to make it available) and blockchain proofs of skills authentication.
Separately from SkillsGraph, LearnerShape has developed an open-source AI-based library for recommendation of learning content and jobs using skills (with any skills taxonomy). This library is available at <https://github.com/LearnerShape/lsgraph>, and descriptions of its capabilities are available on our blog at <https://www.learnershape.com/blog>. As a key element of the vision set out above, we intend to combine this AI-based recommendation technology with the authentication technology of SkillsGraph.
LearnerShape SkillsGraph v2
LearnerShape will develop and improve various functions of the current proof-of-concept version of SkillsGraph as part of the F7 and F8 pilots described above (which are focused on proving the uses of SkillsGraph and learning how the service should be evolved). However, significant further development work is needed to make larger enhancements to SkillsGraph, and move it towards being a robust solution that is ready for widespread market application. That is the purpose of this proposal.
This proposal will deliver the following enhancements to LearnerShape SkillsGraph:
- support for integration with other skills / credential authentication protocols based on World Wide Web Consortium (W3C) and other relevant standards, including:
- enhanced decentralized ID (DID) and credential management
- export of DIDs and credentials generated by SkillsGraph
- import of user DIDs and credentials generated by other services (or self-generated)
- integration with credential wallets
- RootsWallet (<https://www.rootswallet.com/>) — the leading (and currently only) open-source credential wallet in the Catalyst ecosystem
- RootsID (the developer of the RootsWallet) is our partner in this project
- RootsWallet will be able to send/receive/verify/manage/search/display LearnerShape SkillsGraph verifiable credentials that are stored on a user's mobile device – we will collaborate with RootsID to make these functions as familiar and consistent as possible across the two environments
- ProofSpace (<https://www.proofspace.id/>) — commercial authentication provider which is active in Catalyst and partnered with LearnerShape's in the F8 project described above; integration is being implemented in F8 project, and the same approach will be adapted for the current project
- additional detail in credentials — support additional and flexible details in credential schemas beyond the basic details available in the proof-of-concept (i.e. name, choice of 3 credential types, description, issuance date); specific details will be determined during the planning phase of project
- enhanced authentication — currently limited to email address; extend to additional communications networks (e.g. Discord, Telegram and WhatsApp) and physical tokens
- enhanced UI / UX
- graphical interface — currently a simple interface using hyperlinks links and text
- simple, powerful user experience integrating above new features
- other enhancements identified in F7 and F8 pilots.
During the project period, we will also actively promote use of SkillsGraph to projects both inside and (especially) outside the Cardano community. Current opportunities include:
- significant interest in the Cardano community for skills credentials beyond the initial one in the F7 pilot described above
- expansion of PeopleCert qualifications beyond the DevOps qualification in the F8 pilot described above
- an opportunity to create a skills management platform for London, with sponsorship by the Lord Mayor of the City of London and possibly the Greater London Authority.
Please describe how your proposed solution will address the Challenge that you have submitted it in.
The Dapps, Products and Integrations challenge aims to generate "Dapps, products and integrations for the community to use that increasingly become the better alternatives over current centralized providers". This is precisely the goal of LearnerShape SkillsGraph. We aim for a product (with associated integrations) that offers a better alternative to centralized skills management platforms.
The current leader for centralized skills management is LinkedIn, which provides an excellent service but has serious limitations of being proprietary, limiting access to user data, and having high cost for enhanced services. There are also (i) many other companies that assist companies, other organizations and their employees to manage individual skills (e.g. Degreed, Cornerstone/EdCast), and (ii) providers of skills data for use by third parties (e.g. Burning Glass). But there is no widely-adopted public protocol for management of skills – which is a glaring hole in a global economy that depends heavily on future skills development.
The following main advantages of SkillsGraph can allow it to become over time a leading open alternative for skills management:
- robust and seamless integration with blockchain functions to provide public proof of skills authentication
- open source software to allow instances of the solution to be implemented by anyone
- individual control of skills privacy, and no restrictions on use of data that is publicly available
- standards-based approach to promote interoperability with credentials issued using other solutions – focused on W3C standards, and also taking account of other standards efforts including the Decentralized Identity Foundation.
What are the main risks that could prevent you from delivering the project successfully and please explain how you will mitigate each risk?
We believe that our project is relatively low-risk from a technical perspective, because the tasks we are undertaking are well-understood (although somewhat complex), and our team has deep technical experience and a strong track record of delivery. The largest risk relates to demand for our services, which is inevitably uncertain.
Risk 1: There is insufficient demand for the services that we are developing.
Explanation and mitigations: This risk is not a direct risk to delivery of the project, but it is an important consideration because we are building in order to provide a widely-used service. As explained in response to the previous question, there are major reasons to believe that we will succeed in doing so.
In addition to the reasons for long-term success noted above, we are mitigating risk by taking an incremental approach that tests features and demand over time. With F6 funding, we delivered a proof-of-concept that is already attracting strong attention through a community pilot funded in F7. With F8 funding, we are running a larger pilot with PeopleCert, a global certification company that has the potential to send high volumes to our service. This F9 proposal, if funded, will further expand our capabilities to satisfy increasingly demanding applications.
In the medium term, we intend for SkillsGraph to generate sufficient demand to be self-funding. Although our code is open-source, we will use it to deliver paying services. For example, we are in initial discussions to use SkillsGraph as part of a skills management platform for the City of London.
Risk 2: Development is more complex than expected, especially the elements requiring integration with third parties.
Explanation and mitigations: We have a very strong development team, with decades of experience, as explained under Feasibility below, and we are confident that we have the technical ability to deliver the proposed project. However, it is possible that we will encounter technical challenges that this team cannot solve, and if so our approaches will include (i) working with existing collaborators in the Cardano community (including the Atala PRISM team, RootsID, Gimbalabs and ProofSpace), (ii) recruiting other experts via our networks and (iii) modifying the project to reduce technical challenges with minimum feasible impact on functionality.
Risk 3: Sufficient qualified development personnel are not available.
Explanation and mitigations: Our core technical team have busy schedules, and we will likely hire one or two additional people to deliver this project. While there is a great variation in talent of developers and strong ones can be hard to find, we are confident that the Catalyst community and our existing networks provide sufficient resources to address this risk.
Risk 4: The project is not delivered on time, due to complexity, availability of personnel and/or other factors.
Explanation and mitigations: There is a significant chance that complexity will delay delivery of this project. For example, our F6 project was forecast to be delivered in 6 months and ultimately took 7.5 months. Although we believe the project plan detailed under Feasibility below is realistic, it is intentionally designed so that a moderate delay will not impair ultimate delivery – in particular, there are no significant external dependencies that will be affected by delay. We have sufficient financial resources to handle the impact of delay within the proposed budget.
Risk 5: ADA volatility impairs our ability to pay personnel.
Explanation and mitigations: Like other Catalyst proposers, we are affected by ADA volatility. Because we believe in the long-term strength of ADA, we are reluctant to immediately trade all project funds into fiat. Accordingly, we have adopted a strategy of trading some funds into fiat upon receipt and otherwise trading opportunistically / as needed. To date, this strategy has been effective and has allowed us to deliver past projects.