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
What is the relationship between a party running a node and a party authorised to view the contents of a Document?
This goes to the question of what content of a given document is available on-chain. Some options are:
FIXME
elaborate on each of the options below
all document content is on-chain and encrypted
document content is published by the issuing authority (who manages access) and only a reference to the document and it's hash is on-chain
all document content is on chain and not encrypted (being a node is the same as having authority to view document details)
Should an Inter Customs Ledger manage the state lifecyle of a Document?
What is a Document in the context of the Inter Customs Ledger?
FIXME
discuss these two conceptual approaches:
a thing added to the chain by an authorised body which has state and allows some party to take some action dependant on that state?
a digital asset granted to a party that allows that party to trade the asset for some service?
What is the appropriate 'chain of custody' of a document in the context of the Inter Customs Ledger?
FIXME
e.g.
export customs -> import customs
authorised body -> exporter -> importer -> import customs
How should the ICL function in the context of an existing legislated paper based process?
FIXME
other projects have maintained paper certificates and implemented print management solution and QR code for validation
review chapter 12 and artice 4.6 of ChAFTA for reference
Design Goals
Avoid proliferation of ledgers
FIXME
i.e. reduce burdon on parties wishing to join network
Maintain privacy of document content
FIXME
i.e. a node on the network may not be authorised to view the content of a document
Collect meaningful data about the use of a Document
FIXME
i.e. some state management to prevent double spend and track documents etc
Future Directions
FIXME
increase breadth and depth covered with interledger protocols. e.g. trade finance related processes may be managed on some other ledger which might need to reference the ICL for validation of the existance of a CoO. or before a certificate of origin is issued, some other ledger may track the provenance of a product and it's purchase by the exporter, opening the possibility of execution of smart contract for issuance of CoO
This service depends on - TBA.
The text was updated successfully, but these errors were encountered:
* add initial version of background survey
* add draft content to specification
* formatting fixes
* formatting fixes
* formatting changes
* formatting changes
* align structure of top level readme with other repos
* change version in header
* change editor
* formatting changes
* formatting changes
* some text tweaks, more formatting
* add WEF single window document
* add link to WEF single window doc
* move WEF doc into resources folder
* url encode link to WEF doc
* notes
* fix header content
* remove WEF IP
per comment in PR #2
* Update copyright text
* Update copyright text
* move non-normative TODO
per #12
* remove FIXME financial impact of goals
re: #13
* remove the purpose FIXME (to ticket)
re: #14
* remove users FIXME
per #7, #8, #9, #10
* remove questions section
per: #15
Open Questions
What is the relationship between a party running a node and a party authorised to view the contents of a Document?
This goes to the question of what content of a given document is available on-chain. Some options are:
Should an Inter Customs Ledger manage the state lifecyle of a Document?
What is a Document in the context of the Inter Customs Ledger?
What is the appropriate 'chain of custody' of a document in the context of the Inter Customs Ledger?
How should the ICL function in the context of an existing legislated paper based process?
Design Goals
Avoid proliferation of ledgers
Maintain privacy of document content
Collect meaningful data about the use of a Document
Future Directions
This service depends on - TBA.
The text was updated successfully, but these errors were encountered: