Funded [TRIALL-002] Alfresco DIDs

Status
Not open for further replies.
Secured
#1
Dear Factom community,

Please find enclosed our grant proposal for the second Factom grant round of 2019.

The primary purpose of this project is to expand Triall’s electronic Trial Master File (eTMF) solution with a functionality that enables users to assign DIDs to trial-related essential documents registered on the Factom® blockchain. As the eTMF is built on top of the Alfresco ECM system, a leading Enterprise Content Management System, this would become a standard plug-in for Alfresco users. As such, we will make this integration available as an Open Source (LGPL) for use by the community, further broadening the appeal of the Factom® Protocol.

We will be happy to answer any questions you might have regarding this proposal in the public grant discussion.

Best,
Hadil

As required by document 107 that governs the Factom grant process, this is the thread for grant proposal FACTOM-GRANT-TRIALL-002.
The review process starts on 03-05-19, so please refrain from starting public review or submitting questions before that time. If you notice clear errors in the proposal you can contact the author of the grant proposal directly.
 

Attachments

Secured
#2
Thank you for your grant submission. I'm asking everyone these initial questions:

1. What specific date will you begin work on your grant?
2. What specific date will you be done with work on your grant?
3. Do you commit to providing regular updates on your grant in the grant tracking forum?
4. Please link to past grants your group has taken part in, if any.
 
Secured
#3
Thank you for your grant submission. I'm asking everyone these initial questions:

1. What specific date will you begin work on your grant?
2. What specific date will you be done with work on your grant?
3. Do you commit to providing regular updates on your grant in the grant tracking forum?
4. Please link to past grants your group has taken part in, if any.
1. This grant is estimated to require 3 months of work for 2 developers for about 240 hours a month. If this grant is rewarded, the work will start as soon as possible, but no later than June 3th.
2. We expect to be finished with the development and deliver it in three months’ time at the end of August.
3. We will provide updates after each milestone: 1) Factom DID method specification in Triall’s eTMF, 2) Integrating DIDs into eTMF and Alfresco, 3) Publishing source code and documentation
4. Triall has not received any previous grants. We requested a previous grant, but this was not rewarded (community contributions funded part of the development of the eTMF).
 
Secured
#8
I am happy to see uptake on digital identities from projects in the ecosystem. I think we all agree that Factom is ideally suited for this.

One question: is this work dependent on your identity/DID FIP proposal? And could you elaborate which standard will be used for the integration?
We will be using what hopefully becomes the signing standard in the identity/DID FIP, but since Sphereon has been doing signing solutions since 3 years that is not the hard part. We need to integrate the resolution and usage / linking of DIDs into Alfresco first.
 
Secured
#9
Do you have any usage estimates that will result from this implementation?
Usage is very much related to uptake and dependent on the business needs of those utilizing the integration. I will try to give you some insights in our line of reasoning, both from the perspective of Triall as well as from the perspective of other parties that might utilize this integration.

This DID functionality will become a standard available function within Trial applications and will provide Triall’s eTMF with an (even) more attractive value proposition that fits perfectly within the ‘ecosystem’ we envision. As our goal is to connect the different stakeholder involved in clinical trials, DIDs are another means to facilitate trust between parties and will therefore foster adoption and subsequent usage both in the short and long-term. The clinical research industry is worth around 100 Billion USD, and we are convinced that blockchain will play an integral part in the industry. Our business model is built around recurring customers who conduct one or more clinical trials over the course of several years. Usage will therefore dependent mostly on the number of customers and on the specific trial phase. A phase 3 clinical trial, for instance, includes over a million data points that all need to be registered.

By making this integration freely available on the Alfresco platform, we immediately reach a large audience of potential users who are now free to utilize it in their applications. As such, usage can increase significantly depending on the needs of the user and the size of the user’s operations.
 
Secured
#10
Hi Hadil,

Thank you for your application.

It is not clear to me what DID standard you will be using. The already existing one produced by Factomatic/BIF? Or the potentiel V2 DID if it appears at some point?

Moreover, you mention "Provide an open DID based document specification for Triall". Why do you need to define such specs? Are the exisiting DID specs not enough? How different will this spec be from the DID standard you will work with?

Thank you for your time.
 
Secured
#11
Hi Hadil,

Thank you for your application.

It is not clear to me what DID standard you will be using. The already existing one produced by Factomatic/BIF? Or the potentiel V2 DID if it appears at some point?

Moreover, you mention "Provide an open DID based document specification for Triall". Why do you need to define such specs? Are the exisiting DID specs not enough? How different will this spec be from the DID standard you will work with?

Thank you for your time.
Hi Matthias, thank you for your questions. As Niels explained in another thread the DID documents and URLs will not really change. The creation, update, deactivation, resolution inside of the resolver(s) and registrars itself will change. As the DID spec is basically a URI to a standard (DID) document, the impact on Triall is minimal.

We need to define a spec, because we are integrating DIDs on the document level in Triall. This means that you will assign identities to documents and control these documents using identities (organization, individuals). Then we want to be able to do service discovery (storage) for the documents that have DIDs attached. The focus of Triall is to create open and inclusive specification for the whole ecosystem to use. This means that not only our eTMF solution will be able to use the technology in the future, but anybody wanting to integrate it in their products.
 
Status
Not open for further replies.