...
- Human Colossus Foundation (HCF): is a not-for-profit and releases most of their work product under the GPL, with appropriate product under Apache (due to adoption and derivation concerns).
- Paul Knowles presented OCA-
- There is a schema-base (which is the base schemaa machine- machine readable definition of the semantics of a data structure) which also adds structure in its purest form) which includes a blinding block (which allows the issuer to flag any attributes that could potentially unblind the identity of a governing entity in reference to BIT (Blinding Identity Taxonomy or a set of ). In other words, sensitive fields that are blinded through encryption, hiding during presentation etc.),
overlays on top to - Overlays can then be layered on top of the schema-base to provide extra contextual and/or conditional information to that base object. They can can be used by an issuer to transform how information is displayed to a viewer or to guide a verifier or holder in how to apply a custom process to schema data. In other words, they enhance or guide the different aspects of the mapping of the schema-base to mapping for automatic processing and to present user interfaces these . These include (but not limited to) mapping, source, subset, label, entry, format etc. This transforms the schema-base into a multi-dimensional array. These schemas objects are linked to the schema-base using a hash and a pointer to a through a hash of the base object. All objects are stored in (but are not limited to) an OCA repository.
- Meta-data is a part of the data that is managed. The schema and the overlays can add items like source etc.
- JSON-LD as linked data co-exists with OCA
- There is a schema-base (which is the base schemaa machine- machine readable definition of the semantics of a data structure) which also adds structure in its purest form) which includes a blinding block (which allows the issuer to flag any attributes that could potentially unblind the identity of a governing entity in reference to BIT (Blinding Identity Taxonomy or a set of ). In other words, sensitive fields that are blinded through encryption, hiding during presentation etc.),
- Robert Mitwicki demonstrated the way this works at through a public sandbox argo.colossi.network. The sandbox has links to available schemas. There were some glitches mainly due to poor internet connectivity; the bane of WFH. However RM did make the whole thing work.
- Paul demonstrated a sample schema-base and various overlays in JSON. This brought clarity to the concepts and showed the succinct nature of the solution.
- Paul also said that most of this the pre-standards work was happening in TOIP Schema Semantics WG.
- He also showed how existing multi-dimensional constructs could be modified to bootstrap new use-cases in new contexts for different enterprises. The presence of a GICs GICS code also showed how meta-data standards could be used to make further enhance interoperability work.
- There was a Q&A
- How does it work with NIEM schemas? Although NIEM is specific to the US, there would be no problem converting the schemas into this architecture.
- Any production versions of this? Work was proceeding on getting this into production
- How do they work with GDPR, especially the data retention for legal purposes? Even if there were disconnects, the relying party could retain data if there overriding constructs.
- What about other fields (other than healthcare) can this also be applied to data other than Identity data? Yes, work is ongoing for Financial sector under Philippe Page who is the CEO? chairman of HCF.