Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Current »

Problem statement

The current state of usage policy implemented in FarmStack restricts the usage by a specific containerised application. This needs the containerised application hash value to be generated at the point of time when it is verified.

There could be cases where the datasets are defined by a data model or ontology. Can the data models be used to verify what a containerised application can or cannot do with the dataset?

Example case

Most of the data sharing for extension work involves PII like location, name, identifier etc. Many of the applications need to join two different data sets based on some identifier, remove/ filter the identifier and aggregate/ transform the data.

In this example, there are two different data tables:

  1. Farmer produce details

    1. Information about farmers (PII)

    2. Information about produce (quality, quantity)

    3. Date and other meta information

  2. Farmer extension details

    1. Information about farmers (PII)

    2. Information about the activity on farm

    3. Date and other meta information

There is an application that wants to join the two datasets based on the common identifier and remove and aggregate the number of farmers by data, region, crop type etc for creating analytics dashboard.

For both the datasets we have:

  1. Ontologies

  2. A json or json - ld response about data

  3. Sample data (dummy)

Questions

  1. Can we create a policy that can check a node js or a python app to an extent that it does only the joining?

  2. Do we need json or json-ld response?

  3. Can it be used to help create a no code application?

  • No labels