• Access Control

  To expand upon Simple Signed Records which only losely outlines verification of signed requests, there should also be some form of configurable access control. The following example is tailored for the immediate use case of a dispatch and delivery system, but in theory could be refashioned for other uses cases like a collaborative blogging, etc. whereby multiple types of users can interact with records. Types Of Keys In order to better handle responses to various submissions, check that keys are black/whitelisted. ... Read More

  ---

• Developing

  Developing An assortment of notes on developing various aspects of EOTL. Continous Integration Due our use of Codeberg (and thus gitea platform), we are using Drone for continous integration testing instead of more widely used solutions. The admin web interface for Drone can be veiwed at the following URL. drone.sandbox.eotl.supply/ Your codeberg account needs to be granted access to view Drone admin. To manually trigger the Drone CI build of a given repo, do the following while logged into the CI server as root ... Read More

  ---

• Friendly ID

  Friendly ID The Friendly ID or fid is a namespace that aims to make it easy to lookup a various sets of entities (suppliers, items, categories, zones) that each have uniquely different properties or relationships. Some examples of this are: @grains - category which points to lists of various grains @rice - category with parent @grains which lists various types of rice @rice-white-organic - item which lists inventory of Organic White Rice @ber-ou-1 - supplier which has data about Orginal Unverpackt in Berlin ... Read More

  ---

• Identity & Account Keys

  Simple Signed Records (SSRs) is a scheme implemented around the concept of sending cryptographically signed data from a web browser or native app to a server. A basic example of this is sending data via HTTP requests to an HTTP server. This scheme is meant to work whereby the server MAY or MAY NOT have an existing relationship or knowledge of the user sending the records. SSRs offers cryptographic integrity of data and allows for authentication and verification of data, but do not deal with encryption or confidentiality of data. ... Read More

  ---

• Open Items

  Open Items The data model we created for Open Inventory has the following tables categories - simple logical ways of grouping items together, for instance grains or cereal items - basic information about what something is in abstract general sense oat-flakes and how to measure it inventory - a specific existence of an item at a phsical place or supplier which includes price details - a type of detail that is shared between multiple items such organic or allergen ... Read More

  ---

• Open Orders

  Open Orders The purpose of this specification is to outline a data structure for an order that is to be fulfilled from one or more suppliers and delivered by some method of transport. This specification exists to facilitate interoperability between different software platforms handling different parts of logistics in small to medium sized supply chains. Orders MUST contain at minimum an order_id a destination address and at least one entry in the items list. ... Read More

  ---

• Private Dispatch

  Private Dispatch Given the trend of surveillance capitalism’s exploitation of data, systems which aim to resist this exploitation, must take new precautions to safe guard user data. This of course puts constraints on how digital systems are usually built, especially hard to get right is systems which optimize for efficiency. Considering that location details are essential to effectively matchmake amongst couriers: “who is best geographically located person for a given job” the difficulty of private dispatching emerges as a worthwhile challenge. ... Read More

  ---

• Simple UID

  Simple UID Most applications implement a UUID follow the Universally Unique Identifier specification which results in UUIDs like: 123e4567-e89b-12d3-a456-426655440000 LTngDQ4LCWnzyYwDycmTnK1IpIYp1FR0QDWm6FNvLY= The later UUID is currently what is generated in Open Dispatch. Given EOTL’s use case of agile local logistics, it would be better to have a UUID which can be easily spoken or hand written on boxes or packages and thus simpler- thus a SUID. Ideally this SUID should be something significantly shorter like 8 chars: ... Read More

  ---