Re: SIG Request for Support from Technical Community: Defining Standards
I have heard from Brian several times that Hyperledger is not a standards organization, which stands to reason.
There is a survey of Blockchain standards in GSMI. This illustrates the dictum that standards are so great because there are so many of them.
One of the points that GSMI brought up is the need for the SDOs (Standards Development Organizations) to co-ordinate, plus the fact that orgs like ISO are closed to regular folks and that they charge a lot for their standards.
I chair the Interoperability workstream in Digital Currency Global Initiative (DCGI) - a collaboration between ITU-T (an SDO) and Stanford. This is open for participation and one of their methods is to study use cases for extracting common elements and the state of the art of implementations which are far in advance of standards settings. I invite the HL cactus folks to present on this topic. The DCGI will publish a roadmap towards standards for Digital Currencies, the ur-use case for Blockchain. The working groups in DCGI include Policy & Governance, Architecture, & Security.
From: tsc@... <tsc@...> on behalf of Arnaud Le Hors via lists.hyperledger.org <lehors=us.ibm.com@...>
Sent: Monday, February 8, 2021 7:43 AM
To: tracy.a.kuhrt@... <tracy.a.kuhrt@...>
Cc: SIG-Chairs@... <SIG-Chairs@...>; tsc@... <tsc@...>
Subject: Re: [Hyperledger TSC] SIG Request for Support from Technical Community: Defining Standards
I think this actually raises a couple of issues.
The first one is the framework to develop standards within Hyperledger. Hyperledger wasn't set up to develop standards. The belief was that this would be done in other organizations and we would merely focus on implementation. That question was recently raised in the context of the Aries project which has been in fact developing a specification. I will let Brian speak up about what we can do here.
The second one is a question of socialization of the work happening in different parts of Hyperledger. This is a need we have across Hyperledger. The TSC has had several discussions about what we could do to help projects know more about each other so that opportunities for collaboration could be seized - projects often work on similar topics in isolation due to a lack of awareness. We clearly haven't figured this one out yet and ought to give this another look.
Arnaud Le Hors - Senior Technical Staff Member, Blockchain & Web Open Technologies - IBM
From: "Kuhrt, Tracy A. via lists.hyperledger.org" <tracy.a.kuhrt=accenture.com@...>
To: "tsc@..." <tsc@...>
Cc: "SIG-Chairs@..." <SIG-Chairs@...>
Date: 02/04/2021 11:01 PM
Subject: [EXTERNAL] [Hyperledger TSC] SIG Request for Support from Technical Community: Defining Standards
Sent by: tsc@...
On January 11th, I provided a report back on the SIG chair meetingthat I attended. On our TSC call on January 14th, we had some initial discussions about each of the items that I reported back on. It was suggested that I break out the individual items so that if there were any additional thoughts on the topic that we could discuss in a single thread instead of mixing topics.
This is the email to discuss item #1 Defining standards -- data standards, process standards. How to get standards to interoperate. How to break things out of silos since different SIGs are working on standards in separate groups. Can presenting these standards efforts to the TSC help break these out of standards? Can the technical community help with implementation of the standards?
Here is what has been mentioned on the previous thread so far regarding this topic:
Do we need to streamline the outcomes of these standardization activities? TSC can help here by reviewing current modes of collaboration. Another way TSC can be involved is to review the content as you suggested. TSC could guide SIGs on what is possible, already available, what alternatives are available, be able to bridge to other similar outcomes. This will help TSC in a way to respond to project needs and requests.
This message is for the designated recipient only and may contain privileged, proprietary, or otherwise confidential information. If you have received it in error, please notify the sender immediately and delete the original. Any other use of the e-mail by you is prohibited. Where allowed by local law, electronic communications with Accenture and its affiliates, including e-mail and instant messaging (including content), may be scanned by our systems for the purposes of information security and assessment of internal compliance with Accenture policy. Your privacy is important to us. Accenture uses your personal data only in compliance with data protection laws. For further information on how Accenture processes your personal data, please see our privacy statement at https://www.accenture.com/us-en/privacy-policy.