Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Purpose of this document

Provide the Farmstack goals and vision of what it eventually would turn out. This is not a one time document but a living doc which will change over time as we gain more understanding.

 

What is FarmStack?

FarmStack is a digital infrastructure reference implementation of open protocol in agriculture sector that enables data collaboration between different entities. It does this by providing a means to:

  1. Share data directly to the relevant organization without the need of third party through p2p connector (trusted peer to peer (p2p) connector)

  2. Empower the data provider to specify how data can or cannot be used restrict usage of data by the receiver through data owner defined usage policiesEnable organizations usage policies

  3. Publish and discover connectors and usage policies defined according to open standards

  4. Install trusted containerised applications within connector to use in-memory data

  5. Enable organisations to create plugins to make their data discoverable by publishing metadata (description of data) and data transformation services in data catalog

 

Why is FarmStack required?

FarmStack is required because:

  • Complete farmer profile ( including farmer activity ) not available including govt

  • Lack of trust on misuse or under utilization utilisation of data for centralized data repositorywith a centralised data warehouse

  • Need to comply with evolving data policy and privacy safeguarding measures

 

Value generated by FarmStack

  • By combining specific datasets, better services or products can be created

  • Organizations Organisations can discover what data resides with whom to foster collaboration

  • Potential to unlock value of data that was previously considered not shareable

  • More the feedback from farmers is combined, lead to more enriching the solution can be - giving rise to virtuous cycle

...

How will someone use FarmStack?

  • There are two ways to use p2p connectors: a) data providers can set up the entire p2p connector or b) service based model where FS team can deploy the connector

  • No difference between the two in terms of functionality of data exchange except that for first they need to get certificates issued and manage the deployment

  • Available resources:

    • Central place to download a p2p connector (github repo)

    • Help guide to set up a p2p connector

      • Documents

      • Tutorials

      • Videos

  • UI to manage data sharing

    • UI to configure p2p connector

      • Container network

      • Services (endpoints, auth mechanism etc)

      • Routes

    • UI to configure usage policy for consumers

    • UI to manage activity log

    • UI to manage certificates

    • UI to manage which catalog service to be used

...