I was reading up everything I found related to the API work. I think we can use this thread to discuss the evolution of the API.
I have compiled a list of threads that mention and REQUIRE the evolution of the OFN API:
- the API will support DATA interoperability: Data Food Consortium: making food platforms interoperable
- the API will help supporting and building standalone user facing applications: Standalone websites plugged on public instances: how would that work?
- the API will support the technological diversity in terms of frontend dev: New frontend framework such as Angular/React/Vue/etc?
- the API will help supporting and building embeddable shopfronts: Embeddable Shopfronts - Whitelabelling
- the API CAN implement linked data: The future of OFN in a distributed web environment
- the API will help OFN integrate with other systems and help improve the overall architecture: Imagining the perfect platform / ecosystem session - Friday 8 Dec
- the API WILL support the implementation of networked ecommerce and other systems integrations: 'Networked e-commerce' overhaul [META]
- the API would help with implementing de-centralization of OFN, for example, managing distributed product catalogs (one of the main topics on this micro-services thread): Towards a microservice architecture?
And the API can evolve in parallel with the breaking down of OFN into domains. Actually, I think the OFN API must be organised in Business Domains.