SIG Collaboration Task Force
A group looking holistically across activities in all of Hyperledger's SIGs and WGs to identify potential projects that would include stakeholders from multiple groups. Discussions about this are happening in ...
| Generic | Capital Markets | Climate Action & Accounting | Healthcare | Media & Entertainment | Public Sector | Social Impact | Supply Chain | Telecom | Trade Finance |
|---|---|---|---|---|---|---|---|---|---|---|
Tokenisation |
|
|
|
|
|
|
|
| ||
Interoperability |
|
|
|
|
|
|
|
|
| |
Algorithmic Market Making |
| AMM |
|
|
|
|
|
| Spectrum/Infrastructure Marketplace |
|
Use Case |
|
|
|
|
|
| Catalog in production ones |
|
| |
RF/RFP Questions |
|
|
|
|
|
|
| Create a template for SMEs to use |
|
|
Provenance |
|
| CFP t |
|
|
|
|
|
|
|
Link to functional & non-functional foundations.
Comments
@Alfonso Govela – I'm glad to hear that this looks like a valuable resource. And adding the WGs to the grid is a great idea. Everyone involved in the collaboration discussion is welcome to edit this page as you see fit, so feel free to add the WGs and add anything else that would be helpful.
Hi all,
Couple of quick points:
Was not able to edit this page!
Before we get sunk into projects, a quick survey of the ecosystem might be in order
The foundational ideas that have to be tackled by any project (in any SIG) :
functional: Identity, Smart Contracts, The concept of Tokens.
Non-functional: Performance & Scale, Security, Interoperability
We had hoped to address these in working groups, there was a white paper working group & a smart contract working group - Architecture, Performance, Identity working groups still exist, of this the architecture working group is the most generic to embody the cross silo approach. There was a Use case task force which had amassed a set of use cases. We have to revive that work and examine the Use Cases and their relevance today, it would be interesting to see how prescient or how off-base some of those use cases were. The requirements working group (now defunct) chaired by @Oleg Abrashitov was responsible. The original github has been removed by @Ry Jones as part of a cleanup- references in 2016 05 19 TSC Minutes (interestingly welcoming @Brian Behlendorf (Deactivated) as ED)- Requirements G has been archived as Ry noted below- (https://github.com/hyperledger-archives/wiki-archive.hyperledger.org/tree/master/data/pages/requirements)- There are hundreds of use cases there...https://github.com/hyperledger-archives/wiki-archive.hyperledger.org/tree/master/data/pages/requirements/use-cases many of them are empty. Some of them are quite detailed. We need to separate the wheat from the chaff.
The SIGs focused on business areas, of this Trade Finance, Supply Chain and Capital markets have special affinity as they are finance related. Climate Action and any other SIG interested in driving behavior or value through the markets (like the Media and Entertainment SIG) are also in this group.
Some of the other foundational ideas that we have to address include provenance of which ESG and Climate Accounting are special cases as well as crypto-economic considerations (Climate Action, tokenization of NFTs and other related topics)- these also affect any attempts at remaking markets uniting digital assets and payment systems.
I have created a page with comment.. Functional & non-Functional Foundations. I have also added three projects from CMSIG that are relevant....
Here is a copy of the wiki archive for this section, @Vipin Bharathan :
@Ry Jones thanks for quick turnaround
I also feel that the performance & scale group should work with architecture group and other SIGs to identify real-world scale problems and then possibly propose solutions. This task force could provide the platform for that collaboration.
@Javaid, Haris you are also right, each SIG and WG has components, both foundational and functional, that could interact with each other to consolidate, from different mindsets, our platform for collaboration.
Maybe Architecture WG v2 could build upon the structure of business models and use cases to connect in new ways available components, and to detect new opportunities for innovation.
Yes, agreed. I am trying to relaunch/revamp the performance and scale WG. I have often come across isolated efforts on performance improvements and scaling possibilities, but the biggest challenge is how those efforts can be channeled into the appropriate groups (architecture WG or SIGs) to actually make use of them or collaborate towards a more practical solution.
One possible way to begin @Javaid, Haris could be to categorize efforts and resources as foundational-functional, as Vipin said, then standardize an index page of such components at the top of each wiki of SIGs, WGs, Regional Chapters, etc, and cross-reference there links to other index pages. This homogeneous first page could be an entry point for the work of each community, and provide quick connection paths to traverse our complex wiki-space. (I confess that I don’t understand it)
Great idea and valuable resource! Thank you David for creating it. Could we also add the Working Groups to this Collaboration Task Force?