1 of 19

# DATAFOOD CONSORTIUM�07/10/2020 OFN GLOBAL GATHERING

2 of 19

PRODUCTS

Sells on

​

Currently :�I have to maintain a product catalog on each platform�

​

​

​

​

On

Open Food network

On

Socleo

3 of 19

LOGISTICS

Platform

B

Platform

A

Platform

C

4 of 19

SOLUTION: BUILDING A STANDARD

Source : AFUL

Compatibility

The winner takes it all

Interoperability

5 of 19

PARTNERS

DATAFOOD

CONSORTIUM

6 of 19

MILESTONES

Consortium was created

Bi-weekly meetings started

2016

First version of the ontology was published

On https://github.com/datafoodconsortium/ontology

2017

To be continued

20XX

Developing a prototype

With 3 sales platforms

2019

7 of 19

THE PROTOTYPE

Source : AFUL

8 of 19

THE PROTOTYPE

Logistics

How to optimize logistic on a territory regardless of which app the order was made?

Product catalog & stock info

Stage 1: how to read from different databases and match product together?��Stage 2: CRUD products!��

Orders

Who ordered what and when to deliver it?

9 of 19

WHY SO MUCH TIME ON CATALOG?

10 of 19

WHY SO MUCH TIME ON CATALOG?

11 of 19

WHY SO MUCH TIME ON CATALOG?

12 of 19

THE PROTOTYPE

Logistics

How to optimize logistic on a territory regardless of which app the order was made?

Product catalog & stock info

Stage 1: how to read from different databases and match product together?��Stage 2: CRUD products!

​

WIP: repo on shared taxonomies :-)

��

Orders / Offers

Who ordered what and when to deliver it?

13 of 19

PRODUCT OPPORTUNITIES FOR OFN

More authentication options���Shared discovery map on openfoodnetwork.org

��More whitelabel instances / easily moving data from one to the other

​

​

Dedicated Apps

​

Source : Guillaume Rouyer & Romain Weeger

​

14 of 19

PRODUCT OPPORTUNITIES FOR OFN

Sells on

​

��Tomorrow:�Open standard to create apps => data become fully managed by their owners => Sovereignty

​

​

​

​

On

Open Food Network

On

Open Food Network

15 of 19

CHALLENGES FOR THE OFN ORGANISATION

How to make these contributions to the OFN codebase without stealing from the pipe bandwidth?

​

If François has no more time to contribute, can DFC-compliance be handled by current core devs?��Should the DFC engine be maintained by OFN global?

��

​

​

16 of 19

MORE ON TECHNICAL SIDE

DFC Standard is composed of:

​

  • Semantic specifications defined by the model (for human) and the ontology (for machines)

https://github.com/datafoodconsortium/ontology

​

  • Technical specifications defined by the choices made by the consortium in order to use the semantic layer (JSON-LD format, Authentication through OAuth2, …)

https://datafoodconsortium.gitbook.io

​

17 of 19

THE PROTOYPE: TECHNICAL REVIEW

  • The prototype is an example of an application of the specifications.

https://github.com/datafoodconsortium/dfc-prototype-V3

​

  • Developed in NodeJS with 3 separate Docker containers to deal with the core logic, the SemApps layer and the UI part

​

  • SemApps: Project from Virtual Assembly, LDP server based on Apache Jena Fusuki (SPARQL server) https://semapps.org/docs/guides/ldp-server

​

  • Authentication managed through external OAuth2 server hosted by lescommuns.org

18 of 19

DFC ROADMAP

Short term:

  • Work on internationalization
  • Improve and update the documentation
  • Implement CRUD actions on product catalog
  • Define a common taxonomy to classify products

​

Middle term:

  • Tune up performance
  • Extend the logic with offers, stocks, …

​

Long term:

  • Integrate the system with other semantic platforms

19 of 19

THE DFC-OFN CONNECTOR

Presentation:

  • Propose an API to exchange with the DFC POC and using the OAuth2 authentication provided by Lescommuns.org

​

  • Logic isolated to a Rails engine for clean integration (dfc_provider)

​

Features:

  • Model mapping through serializers
  • API to propose data with 1.3 DFC Format

​

  • Better OAuth2 integration (using OmniAuth gem)
  • API to allow CRUD actions