Protocol conversion to GS1-compatible supply chain data

[pospi]

High-level epic for collecting information on this protocol conversion; which would enable interoperability with global supply chains and many existing commercial ERP systems.

Industry case studies already in progress should see support for this module landing some time early 2020.

[fosterlynn]

As input, here's the data elements that GoodRelations vocabulary has. I think GR was brought over to schema.org too, which is dominant in SEO I think, so the vocabulary naming may be somewhat standard in the semantic web, although I haven't really researched it. But we'd want to take requirements from whichever user group(s) want to use those identifiers, of course.

[pospi]

Also just came across some of these goodies in what OriginTrail are doing: https://github.com/OriginTrail/ot-node/tree/d8ba15bcc76ef7be2c627a9c962047b815f65408/modules/transpiler/epcis

They're targeting GS1 EPCIS, GS1 CBV, and W3C WoT.

[pospi]

So I've been talking with @TheLaughableCoder and it turns out that GS1 have a number of commercial aspects to their system which basically make them impractical to a lot of industries and to any small enterprise.

• they charge you a fee to join with licensing fee based on your turnover.
• And then there is a fee per number of barcodes. Each producer buys barcodes. https://www.gs1au.org/api/sharepointlibrary/download?g=MS82LzIwMjAgMTowMzowNiBQTXxHUzFhdS1mZWVzLWFkZGl0,aW9uYWwtbnVtYmVycy5wZGZ8,ZmlsZQ.,.

It's particularly problematic in industries like building where there are intermediary supply chain participants who perform processing on less refined materials. E.g. you buy some steel, it comes in 12m lengths with a GS1 barcode provided by the producer. Now you cut it up into 1m lengths and want to sell it on- so you end up having to pay for 12 more barcodes just to do that. Then it might get galvanised or coated and thus needs another barcode.

So, lots of problems stemming from this extractive mentality. Thus, I'm putting this waay down the bottom of the "wants" list until such time as a commercial client feels it is necessary. It would be much better to devise our own barcoding system that uses an open standard for encoding Holochain identifiers, and perhaps provide some registration functionality to associate our IDs with GS1 IDs for systems which need to use them.

[fosterlynn]

it turns out that GS1 have a number of commercial aspects to their system which basically make them impractical to a lot of industries and to any small enterprise.

yeah, that's why it is not part of VF atm

Thus, I'm putting this waay down the bottom of the "wants" list until such time as a commercial client feels it is necessary.

👍 In my opinion, that should be true of everything that is not the very basic core spec. Let's do these kinds of things in partnership with user / dev teams that actively want to start using HoloREA.

[pospi]

Yes of course! That's why these tasks are here, only as placeholders. They'll be filled in with actuals when partnerships emerge that want them. Maybe it's worth making a milestone for "proposed future work" to file these things in, so it's clear that they have not yet been planned or scoped.

…

On Mon, 6 Jan 2020 at 23:23, Lynn Foster ***@***.***> wrote: it turns out that GS1 have a number of commercial aspects to their system which basically make them impractical to a lot of industries and to any small enterprise. yeah, that's why it is not part of VF atm Thus, I'm putting this waay down the bottom of the "wants" list until such time as a commercial client feels it is necessary. 👍 In my opinion, that should be true of everything that is not the very basic core spec. Let's do these kinds of things in partnership with user / dev teams that actively want to start using HoloREA. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#105>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AADK2JGCQRNQJNP7CEFZIHLQ4MWEVANCNFSM4J4FAADA> .

-- writings <http://pospi.spadgos.com/> | twitter <https://twitter.com/pospigos> | github <https://github.com/pospi> ← where to find me ValueFlows <https://www.valueflo.ws/> | HoloREA <https://github.com/holo-rea/> ← things I'm working on

[fosterlynn]

Yes of course! That's why these tasks are here, only as placeholders.

Sorry, got it.

Maybe it's worth making a milestone for "proposed future work

Good idea, done.