You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Up until now we have had 3 major practicality issues:
Walking the supply chain.
Authorization Model
Data sharing
Manifests are one solution to walking the supply chain.
We propose that the manifests structure looks like: [ParentSignature] -> [] = new manifest / first entry in a manifest, [a] = normal transaction, [a, ...] = aggregation event. EventID Timestamp GLN EventHash (Possibly) Signature -> (Composite of all the other fields in the event structure signed with the organisations public key)
We intend to provide an MVP solution of/for Manifests as an enabler of discovering solutions for the other problems and to see if this solution works in practice and so that we can demonstrate our proposed architecture.
The text was updated successfully, but these errors were encountered:
Up until now we have had 3 major practicality issues:
Manifests are one solution to walking the supply chain.
We propose that the manifests structure looks like:
[ParentSignature]
-> [] = new manifest / first entry in a manifest, [a] = normal transaction, [a, ...] = aggregation event.EventID
Timestamp
GLN
EventHash
(Possibly)Signature
-> (Composite of all the other fields in the event structure signed with the organisations public key)We intend to provide an MVP solution of/for Manifests as an enabler of discovering solutions for the other problems and to see if this solution works in practice and so that we can demonstrate our proposed architecture.
The text was updated successfully, but these errors were encountered: