18:08:16	 From Neil Thomson : @Robert -> Pointers, links to the Google "Enhanced Data" concept you were talking about?
18:08:41	 From Neil Thomson : Micro Ledgers came up in the DIF Interop call today...
18:12:58	 From Paul Knowles : https://github.com/the-human-colossus-foundation/microledger-spec/blob/main/microledger.md
18:13:06	 From Neil Thomson : https://github.com/the-human-colossus-foundation/microledger-spec/blob/main/microledger.md
18:14:08	 From Neil Thomson : DID portability came up in the DIF interop meeting...
18:15:47	 From Neil Thomson : So Microledger(s) is a reinvention of the log file...
18:16:45	 From Paul Knowles : “A Microledger is an event transaction log that is cryptographically bound to a self-certifying identifier, enabling auditable account details of the origin, changes to, and details supporting the confidence or validity of data. “
18:17:02	 From Carly Huitema : chained, cryptographically secured logs of transactions (like a private blockchain?)
18:18:18	 From Paul Knowles : Correct, Carly.
18:18:20	 From Paul Knowles : Network-agnostic. Microledgers are cryptographically bound to self-certifying identifiers and, therefore, are not locked to any given Blockchain network. They are network-agnostic and fully portable between any decentralised or centralised data management system.
18:18:52	 From Carly Huitema : fully portable as long as they follow the same structure/schema?
18:19:23	 From Carly Huitema : logs with benefits
18:26:03	 From Vitor Pamplona : digests with benefits :)
18:26:29	 From Steven Milstein : Can Controlling Identifiers contain business logic aside from who can write the next block? Behave like a Smart Contract?
18:26:55	 From Karen Hand : Not sure if this applicable, but would this allow parsing of a VC - for example pulling age from your mobile driver's licence?
18:27:45	 From Carly Huitema : Is the seals functioning like putting the has of the data as a transaction on the blockchain? (what do they call that...?)
18:27:51	 From Karen Hand : The Ontario initiative mentioned "micro VC's". They didn't have an answer for that
18:28:06	 From Carly Huitema : *the hash of the data
18:28:27	 From Carly Huitema : anchoring onto the chain (I think that's what they call it)
18:33:25	 From Neil Thomson : This will NOT scale
18:35:21	 From Steven Milstein : Would a Seals contain/point to an ACDC?
18:38:39	 From Carly Huitema : The whole microledger could be forged and replaced. Users of the microledger will want to connect to an external source of trust to confirm that the signatories were the correct ones (right?)
18:39:10	 From Neil Thomson : Microledger as the recorder (and data repository) for a transaction or a chain of transactions. ACDC is redundant - why move the data, vs. reference the micro-ledger? In this scenariothe controlling identifiers for each block is part of the supply chain management
18:40:16	 From Neil Thomson : To scale, a block is about a Transaction - e.g., within a supply chain.
18:41:19	 From Vitor Pamplona : The car transfer log is how you should explain these Microledger concepts. Start with an example and then abstract from it :)
18:42:11	 From Carly Huitema : It sounds like it is splitting the function of the ACDC into two parts - the authentication, and the data
18:45:14	 From Neil Thomson : So why are you moving the data?
18:45:57	 From Neil Thomson : Sharing data from a Transaction, is a different use case from the supply chain.
18:49:28	 From Vitor Pamplona : It looks like a Sign and Forward framework. Similar to the Store and Forward concept.
18:52:14	 From Vitor Pamplona : So, is the data transferred with the ownership of the digest or in order to see past data one needs to go back directly to previous owners and individually request it?
19:05:02	 From Neil Thomson : Comments on the spec in GitHub directly?