Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

What is a Document in the context of the Inter Customs Ledger? #4

Open
arpentnoir opened this issue Feb 26, 2019 · 7 comments
Open

Comments

@arpentnoir
Copy link
Contributor

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?

@monkeypants
Copy link

monkeypants commented Feb 27, 2019

An ICL exists as a working arrangement between Nations. Parties are identities that only exist within a national jurisdiction.

I suspect from an ICL perspective:

  • assertions by Parties are regulated in the jurisdiction where the party exists.
  • extra-jurisdictional assertions about parties should probably be considered non-authoritative

For this reason, I think the digital assets must be controlled by nations, either directly (by the regulator) or indirectly (by the regulated community, under the control of the regulator). Unregulated digital assets belong some place else.

@monkeypants
Copy link

could we provide lists of examples (is-a doc) and counterexamples (is-not-a doc)?

Think we should establish categories. If a doc:

  • is created in the export jurisdiction
  • is exported exactly zero or one time (from the country of origin, not including transshipments etc)
  • is imported exactly zero or one time (to the country of destination, not including transshipments)

Then it is a clear candidate, because it fits the generic payload protocol (chain does not need to capture any semantics of the asset itself).

We should frame that in the semantic model, and explore:

  • are there examples that are similar except the document originates in the country of destination?
  • are there other generic patterns that might be useful without modelling the specific document lifecycle in the asset?

@monkeypants
Copy link

Note: my comment above presupposes assumption about generic lifecycles rather than document-specific digital assets (per comments in #3). I should call them out more with explanation so that idea is exposed to debate.

@arpentnoir
Copy link
Contributor Author

arpentnoir commented Feb 27, 2019

  • are there examples that are similar except the document originates in the country of destination?

CITES export permit for an Appendix I specimen requires prior grant of an Import permit from the destination country

@arpentnoir
Copy link
Contributor Author

could we provide lists of examples (is-a doc) and counterexamples (is-not-a doc)?

Think we should establish categories. If a doc:

  • is created in the export jurisdiction
  • is exported exactly zero or one time (from the country of origin, not including transshipments etc)
  • is imported exactly zero or one time (to the country of destination, not including transshipments)

I think an ATA Carnet probably qualifies as a counter example. It is issued in one jurisdiction and is valid for multiple imports and re-exports e.g. travelling exhibition or trade show, etc...

@arpentnoir
Copy link
Contributor Author

arpentnoir commented Feb 27, 2019

Introduction from the Sea (CITES) is a slightly more obscure counterexample. i.e. a certificate issued by the importing country and only for the import (from international waters).

@monkeypants
Copy link

Right - ATA Carnet is a kind of bearer token, not some G2G business between a two customs authorities.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants