DIF Interop WG - Nov 30th ...Human Colossus Foundation

gistfile1.txt

WEBVTT

Lamari Lavarrette (DIF):
Hi Paul, how are you? This is Lamari. I'm the community manager here at DIF.

Paul Knowles:
Hi Lamari, nice to meet you.

Lamari Lavarrette (DIF):
Nice to meet you as well. Uhm...So, Kaliya should be getting on, uhm, in a minute here. .so.and we're just waiting here for other people to get on.
So it looks like, uhm, people are going to be a bit late. So they should arrive shortly.

Paul Knowles:
Let me just try to get some a more professional looking background.

Lamari Lavarrette (DIF):
Good. No worries.

Paul Knowles:
(Inaudible) Is that looking strange on your side? I presume it is.

Lamari Lavarrette (DIF):
Uh, yeah that would be a very interesting meeting

Paul Knowles:
(laugh)

Brent Shambaugh:
I see the blue thing, like the Bitcoin blue eyes

Lamari Lavarrette (DIF):
(laugh)

Paul Knowles:
Okay, we'll just have to stick with this one, not as professional but at least you can see me. (laugh)

Lamari Lavarrette (DIF):
(laugh)

Lamari Lavarrette (DIF):
It looks fine.

Lamari Lavarrette (DIF):
Hi, there for anyone who just hopped on the call. We're just,um, we're just wanted to update people as to where we are at

Brent Shambaugh
The sound seemed to cut out.

Paul Knowles:
Lamari, I don't know if you are, you are speaking, but you're on mute

Lamari Lavarrette (DIF):
Uh, can you guys hear me okay?

Paul Knowles:
We can now, yup.

Lamari Lavarrette (DIF):
Oh, okay. I was just saying that,uh, Kaliya should be on any minute. We are. We're just waiting for her. And then we'll be able to uh, to shart the call.
So, I just wanted to let people know where things were at.

Paul Knowles:
Perfect.

Kaliya Identity Woman:
Hi!

Lamari Lavarrette (DIF):
Hi Kaliya.

Kaliya Identity Woman:
Hello. Hey, Kaliya here. Paul is here. Welcome Paul.

Paul Knowles:
Thank you very much.

Kaliya Identity Woman:
Um, Brent is here. Uhm. I'm on the airplane about to disembark. We got in late, but anyway, so, I'll be here as long as I can.

Kaliya Identity Woman:
Paul's going to present the over, over, the Overlay Capture , archi, Architecture. Yeah?

Paul Knowles:
Yep.

Kaliya Identity Woman:
Cool. Uhm, is there anything else before we leap into that that we should cover?

Kaliya Identity Woman:
Uh, I don't think so. Okay, great, go ahead Paul.

Paul Knowles:
Okay/ Perfect, alright. So let me, uh, let me share my screen and I will share the whole desktop, actually, cause, uh, I'm gonna try my best to basically get into, to get into, to get into a demo as well, so so we are cooking to cover quite a lot.

Paul Knowles:
Okay. So I'm gonna say it. I'm gonna put this presentation into kind of 3 parts the first one is, uh, decentralized semantics, the second one is overlays capture architecture which is basically an implementation of, of, decentralized semantics.

Paul Knowles:
And then if we have time, I'll go through a Swiss passport, uh, demo as well. Um, We've got a lot to get through but I will certainly try.

Paul Knowles:
Keith, Keith, you've got your hand up?

Keith:
Could you just go a quick overview on who is human colossus foundation? I've always been curious about what your organization [inaudible].

Paul Knowles:
Yeah. Sure. Um, Sure. So yeah. Human Colossus Foundation is a Non-Profit Foundation in Geneva, um, It was set up by by three founders coming from three different exp, exp, sorry expertise in three different domains.
So it was myself coming from the Semantics Space, um, Philipe Paje coming from the governanace space,  and uh, an uh, and Robert Mitwicki coming from the Authentication space.
And we kind of got together, because we realized, uh, very early on, that um, that in order to build distributed data ecosystems that we were going to have to do a lot of conceptual mapping and and to start, uh, contributing 
by bui building open source, uh um, open source code and, uh, and tooling for people to just pick up and start, uh, being able to, kinda to, plug things into that kind of space. Um, So this was really started, uh,,
even before the Europe started really going hammer and tongs at the, at the data spaces, uh, so we  were really early, on it, on it.
Um, And I guess, I guess in in hindsight we really built it because of overlays capture architecture. That was kind of what triggered it. We realized that OCA was too big to have as a, as a, uh, corporate piece of code, and it really needed to be open sourced, um,
so that's kind of a background of the, the foundation, I'm  the,  I'm the head of the head of the Advisory Council at the, at the,foundation. We also have a proprietary company in Basel, Switzerland. Um, So the, um, Meddea solutions.
That's where we do consultancy and stuff for you know anybody that wants to build any proprietary products with, some of those, some of those open technologies we can do that through that through, through, Meddea. 

So that's a a quick background. I will launch quickly into, uh, I don't know how much people know about semantics.
Some of this will be like teaching people to suck eggs. I'm sure [laughter], but I, I always try and, uh, define the space before we go heavily,[inaudible] ,more into the weeds.
So what is the data Semantics? Data semantics is the study of the meaning and use of data in any digital environment.  

In data semantics, the focus is on how a data object represents a concept or object in the real world.
So, uh, you can kind of think of, um, Actually, I can do it here.

So these are, uh, This is where the semantic domain sits. There's basically 4 domains. Uh, There's the, um, the, inputs domain which is really all about authentication.
So that's about factual, um, factual authenticity. 
So it's really about, uh, the events. Um, Semantic space is totally about objects. So that's a, a objectual integrity we call that, and and those are the 2, those are the 2 machine domains, and then the human domains or the governance domain and the economic domain.

|| ====== stop ======= ||
So in the governance, domain we talk about connect consensual veracity. So in that space. You know if if everyone within an ecosystem believes that data is true, then by consensus, it's considered true.
So that's the governance domain. And then the last one is the economics, domain the economic domain is about transactional reputability.
So, you know, within within a transaction whether that one of those actors have a have a good reputation or not.
Obviously a reputation, and and and rules are are more humans and are more around humans authentication and objectual integrity.
We can do that in the machines. So this is a this is another.
Just just the machine layers. This is a really early diagram that we put together to try and really separate the imports domain in the Semantic domain.
And I, with all my modeling, I I always work off a kind of yin yang modeling, so I put in here some of the the essential items that we needed in the authentication space and then I kind of merrored what those objects are in the semantic space so
I think it's a really nice a nice diagram, so that you know what pieces fit. Where?
Obviously in the inputs domain. It's all about all authentication.
So the authentic is their main characteristic in the semantic space.
We just care in a distributed space. We just care that every single object is deterministic, so that wherever those objects end up in any network or any database whatever you always know exactly what that object is because it's deterministic yeah everything in the in the inputs domain is
about factual authenticity. So the idea of the fact is, you you guys will all know in this space.
So what a claim is! You have a set of claims is is a credential and and the credential is the transient object, and in the inputs domain.
So basically one once a claim is is signed, then it becomes a fact.
So that's what that factual is there on the other side of the on the other side?
You can think of when you, when somebody gives you a credential, you would tend to fill in a form. So you go to the post office.
You fill in a form, and they give you something. That's the sort of thing there.
The the the low the lowest level item in the in the semantic space is an attribute as opposed to a claim.
Everything and inputs is about data entry. So as soon as you enter something into the system, it's it's it's it's marked in a pandemic and then and and that's what turns it into effect, on in the semester space it's
All about data capture. So a lot of people kind of treat semantics as a secondary process, and what we what we try and say, human colossus is.
Actually, it's a really important process to get up. Get right up front.

00:17:27.000 --> 00:17:42.000
So you know, as soon as you're entering data into the system, you've got all this beautiful metadata as well categorized and everything so that when the data objects are propagated through the life cycle they've got full integrity and and they're fully

00:17:42.000 --> 00:18:00.000
Interpretable and and understandable by by you machines or humans so semantic is is literally Ios say to people, as soon as you hit a keyboard a key on a keyboard you immediately want to be thinking about about the metadata what is it what it is that's being

00:18:00.000 --> 00:18:07.000
Captured objectual integrity. This is the the core security aspect of the semantic space.

00:18:07.000 --> 00:18:13.000
So the foundational characteristic of the semantic data domain is objects to integrity.

00:18:13.000 --> 00:18:15.000
The overall accuracy and completeness and consistency of objects and their relationships, so object that's why we use the word object.

00:18:15.000 --> 00:18:24.000
Sure, so it's not object integrity. It's objectual integrity.

00:18:24.000 --> 00:18:29.000
So it basically takes care of objects and relationships. What is decentralized semantics.

00:18:29.000 --> 00:18:38.000
Okay. So decentralized semantics is a domain that that human colossus basically invented because it didn't exist before but it said it.

00:18:38.000 --> 00:18:45.000
It involves separating all of the semantic tasks within a schema into separate objects.

00:18:45.000 --> 00:19:07.000
So which are cryptographically bound to what we call a capture base, and what what that enables in in a distributed data ecosystem is that different entities can act as customs of different granular objects within this within the schema so that's a really powerful

00:19:07.000 --> 00:19:13.000
concept. If you think about something like a passport, you know when you have an Indian visa, say, in a Swiss passport.

00:19:13.000 --> 00:19:24.000
The Indian visa could be controlled by the Indian government, whereas the passport is controlled by the the the citizen of Switzerland.

00:19:24.000 --> 00:19:29.000
In that case, and you know maybe the the the branding objects in the digital space for a Swiss passport could be controlled by the Swiss passport office.

00:19:29.000 --> 00:19:41.000
So it becomes really interesting. The the the kind of the the custodianship of these different objects.

00:19:41.000 --> 00:19:53.000
Okay. So that was a kind of a brief on decentralized semantics, overlays, capture architecture is basically an implementation of of that of that domain.

00:19:53.000 --> 00:19:54.000
It's a global solution for data and semantic harmonization.

00:19:54.000 --> 00:20:04.000
At the moment. It deals very well with forms and credentials in the future.

00:20:04.000 --> 00:20:07.000
We will, we will ramp that up so that it can deal with notices and and contracts and things like that as well.

00:20:07.000 --> 00:20:25.000
Through the same, the same layered architecture. Yeah, that's probably all I need to say on that overlays capture architecture represents transient and persistent objects.

00:20:25.000 --> 00:20:26.000
So just to explain a little. Bit what transient and persistent is in this case.

00:20:26.000 --> 00:20:48.000
Some like a credential, would be a transient object, because it's something that tends to be propagated through the system to allow you to do something whereas a persistent record could be a persistent record held on a personal data store something like that where you know it doesn't

00:20:48.000 --> 00:21:04.000
Necessarily move as much, as a persistent object. So, anyway, Oca treats these as multi-dimensional objects, consisting of a stable capture, base and interoperable overlay by introducing overlays as task specific objects within an oca bundle the

00:21:04.000 --> 00:21:11.000
Architecture, offers an optimal level of both efficiency and interoperability and alignment with the fair principles, fair principles.

00:21:11.000 --> 00:21:21.000
Let's see if I can remember this are basically findable, findable, accessible, interoperable, and reusable.

00:21:21.000 --> 00:21:24.000
I think that's what that apprentice means. So primarily devised for semantic object.

00:21:24.000 --> 00:21:44.000
Interoperability and privacy, compliant data sharing Oca as a proposed global standard for data capture that promises to significantly enhance the ability to define manage and use data in terms of simplicity accuracy and allocation, of resources so this is kind of what

00:21:44.000 --> 00:21:50.000
What what we how we represent it in in a schematic diagram.

00:21:50.000 --> 00:21:55.000
So the the core object. Here is the capture, base, and and with, and and I'll explain what that is in a minute.

00:21:55.000 --> 00:22:11.000
So that's your basically your base object and you you cryptographically link any of these task specific overlays to that capture base to so that's a kind of a richer metadata structure.

00:22:11.000 --> 00:22:15.000
And this is this is split into into 4.

00:22:15.000 --> 00:22:21.000
So we have the the semantic overlays so you can think of things like labels.

00:22:21.000 --> 00:22:26.000
You know the the labels, for instance, could be an English French German doesn't matter.

00:22:26.000 --> 00:22:40.000
You can have multiple label overlays, but pushed into the stack information overlay is things like, you know, the the data entry hints on a form that would be held in an information overlay etc.

00:22:40.000 --> 00:22:43.000
Inputs, the input server lays are things that come more from the the data entry side.

00:22:43.000 --> 00:22:54.000
So you can think of like predefined entries that you would get in a form where they're trying to.

00:22:54.000 --> 00:23:09.000
They only give you a specific number of options, those those entries are would be in the inputs domain I'll just point out 2 in there one's the entry code overlay and one's the entry overlay they're very slightly different the entry code overlayers

00:23:09.000 --> 00:23:13.000
for coded entries. So you can think things like if you wanted to pull in.

00:23:13.000 --> 00:23:30.000
Some iso, an an Iso code table, for instance, the the coded part, you know, ch: for Switzerland is is held in an entry code overlay, and then the entry overlay is separated that's where you you Spell out Switzerland, in

00:23:30.000 --> 00:23:46.000
That case, and the reason we separate, that is because an entry code overlay will just be one within the stack, whereas an entry code an entry overlay could be multiple languages that you could pull in there so there's some separation there transformation overlays i'll go

00:23:46.000 --> 00:24:05.000
into that in a little bit more. But basically the idea here is that we can't control how purpose purpose- driven services are capturing data so they can basically be have custodianship of their own mapping overlays there's actually more than just these 2 I think this is

00:24:05.000 --> 00:24:26.000
An old diagram, but, for instance, if they want to change from their attribute names to to the attribute names held, and the capture, base then they could use an attribute mapping it related to on their side and then that could be cryptographically linked back into the capture base and then

00:24:26.000 --> 00:24:27.000
The presentation over laser and and that's what I'm going to demonstrate later on today.

00:24:27.000 --> 00:24:38.000
So traditionally when you have a schema, you know it's it tends to be for one specific presentation.

00:24:38.000 --> 00:24:46.000
If you like. What's nice about Oca is that you could have 2 different presentations cryptographically linked to the same capture base.

00:24:46.000 --> 00:24:51.000
So if you wanted to render a form, for instance, that could be the form layout overlay.

00:24:51.000 --> 00:24:58.000
If you wanted to render a credential, it would be a credential layout overlay, and I'll show you that with a with one of our tools.

00:24:58.000 --> 00:25:01.000
How you can kind of see that the difference in in that.

00:25:01.000 --> 00:25:04.000
So it's just a pretty, cool, cool concept. And then this is a another schematic of of Ocas.

00:25:04.000 --> 00:25:20.000
So here you've got a a a digital password form rendered, and it's this is just saying that you know these different objects within the stack are basically have different.

00:25:20.000 --> 00:25:21.000
Tasks within that rendering. So you know the the Meta overlay.

00:25:21.000 --> 00:25:38.000
There is basically where they have the in the English form title and and the description things like a label overlay.

00:25:38.000 --> 00:25:54.000
In this case label overlays. Actually do the the the label of the attribute but also, the they can do category labels as well, so that just get yeah, just shows you that you can render using a multi multiple multiple objects okay.

00:25:54.000 --> 00:26:04.000
So what is a capture, base so capture! Base is a stable base object that defines a single data set in its purest form, providing a standard base to harmonize.

00:26:04.000 --> 00:26:26.000
Data. So if you think in within a distributed data ecosystem, where per purpose driven services are capturing data in different ways, you could have a data governance administration for for a specific data ecosystem that is defining the the oca structures that

00:26:26.000 --> 00:26:35.000
That that will be used within their ecosystem and and the capture base is really the the standard base for that harmonization process.

00:26:35.000 --> 00:26:50.000
So in that object you define, attribute names and some core types so I think there's 7 quarters that we use boolean binary text date, time, yeah, we'll be kinda usual so you'd expect to see but the other interesting thing in the capture.

00:26:50.000 --> 00:27:12.000
Basis has a flagging block which basically means that the issue of the schema has has the opportunity to flag any any attributes right at the start that could be dangerous you know we we don't dictate what what are done with those attributes that's a that's a

00:27:12.000 --> 00:27:30.000
Governance. That's a governance decision for the ecosystem, but at least with them flagged it just means that when when date, when the data objects are properated through the system, you know somebody can quickly encrypt all of that debt all of that dangerous information you know at the

00:27:30.000 --> 00:27:32.000
At the at the click of a button. So yeah, so that's pretty much all I need to say on that.

00:27:32.000 --> 00:27:47.000
I think so. I should go to here, you guys. Obviously in this group are, are. There's a lot of coders here, so I just wanted to show you what what a capture base in looks like very simple object.

00:27:47.000 --> 00:27:52.000
It just has the type which is says that that object is a capture.

00:27:52.000 --> 00:27:54.000
Base classification is really used for for schemes and coding systems.

00:27:54.000 --> 00:28:05.000
So the the gigs code. Here is a global industry classification, sector code.

00:28:05.000 --> 00:28:14.000
So you know, in this instance, it passport, be coming from some governed government agency that has that gigs code in there.

00:28:14.000 --> 00:28:22.000
So when you're searching for this, these schemas for to reuse them again, it gives you a little bit of a classification to be able to find the things.

00:28:22.000 --> 00:28:30.000
Then there's the attribute blocks, so the attribute block is just obviously the attribute, names and and and the and the attribute.

00:28:30.000 --> 00:28:35.000
Types I should say at this stage that Oca is just an architecture.

00:28:35.000 --> 00:28:38.000
It's not a data model, and it's not sorry.

00:28:38.000 --> 00:28:39.000
It's not an ontological data model, so we don't.

00:28:39.000 --> 00:28:45.000
We don't tell people how to name their attributes anything like that.

00:28:45.000 --> 00:28:53.000
They name them, how they like. Obviously the core data types are are set in stone, but we've captured everything in those 7 types.

00:28:53.000 --> 00:28:58.000
And then the the the flag attributes block at the bottom.

00:28:58.000 --> 00:29:03.000
There are just flagging any any of the censorships

00:29:03.000 --> 00:29:10.000
And then what is an overlay? So an overlays are cryptographically linked objects that provides layers of task oriented tech contextual information to the capture.

00:29:10.000 --> 00:29:30.000
Base. And this basically allows any actor in the system interacting with a published capture base can use the overlays to transform how information is displayed or guide an agent in applying a custom process to capture data etc.

00:29:30.000 --> 00:29:36.000
So in the future. With those Ca: One thing that we are looking at is is is ethical.

00:29:36.000 --> 00:29:53.000
AI, for instance, so there might be a chance of having processing overlays into the stack, so you can kind of think, of maybe, like smart contracts and that kind of stuff. I say it doesn't do that at the moment but in the future it it definitely. Could do

00:29:53.000 --> 00:29:59.000
Okay. So before I mentioned the difference between the entry code overlay and the entry overlay.

00:29:59.000 --> 00:30:03.000
So I just wanted to just pull that up and go show you what that looks like.

00:30:03.000 --> 00:30:15.000
So yeah. On the left there the entry code overlay not particularly human readable documents, types a bunch of alphabetical alphabetical alphabetic letters.

00:30:15.000 --> 00:30:21.000
And then you know, yeah. So there's obviously not particularly human readable.

00:30:21.000 --> 00:30:25.000
And then the entry overlay. You'll see that the the difference there you've got a language option.

00:30:25.000 --> 00:30:29.000
There, so that's where you define your your language to Iso.

00:30:29.000 --> 00:30:30.000
Standards would be my suggestion, and then and then you can put this, you know.

00:30:30.000 --> 00:30:42.000
Put all of your your English and predefined entries in there.

00:30:42.000 --> 00:30:45.000
So yeah, that's that

00:30:45.000 --> 00:30:46.000
And then this is just another another picture of what we'll be looking at in a minute.

00:30:46.000 --> 00:31:06.000
So as I said before, Meta, overlay kind of does your your your title, and your description of the form there, in this case you've got an entry overlay which you can see all the predefined entries there in one of the attribute in one of the

00:31:06.000 --> 00:31:27.000
Fields, label overlay for category labels and and and attribute labels, and then the information overlay, as I said, does some some entry hints for the user can be done in an information over there okay, so I've been talking a little bit about distributed

00:31:27.000 --> 00:31:31.000
data ecosystems, but I just wanted to kind of show you a picture of what what that looks like.

00:31:31.000 --> 00:31:48.000
So within these data ecosystems you'll have a data, Governance administration which is a multi-stakeholder place which you know they defend all the rules and regulations for the ecosystem but also they also they also define the the oca

00:31:48.000 --> 00:31:59.000
Objects that that are acceptable for to be used within that ecosystem and and around the in the middle of the sorry the next ring of the donut.

00:31:59.000 --> 00:32:02.000
If you like. There is in this case, is a purpose driven.

00:32:02.000 --> 00:32:09.000
Services so you know you could have hospitals, taxi services, whatever you want, providing a service to citizens, they are the the the initial entry point for new data into the system.

00:32:09.000 --> 00:32:34.000
So I I put purpose. Driven services here as opposed to insights, driven services which are our services that are looking for data so that they can do you know statistical analysis, machine learning AI algorithmic processing all that sort of stuff so i'm separating the 2 the 2

00:32:34.000 --> 00:32:37.000
there purpose driven and insights driven. So this is just purpose driven.

00:32:37.000 --> 00:32:40.000
Servers shown here, and then round the outside is the citizens.

00:32:40.000 --> 00:32:51.000
So the citizens they have full autonomy to be able to join any a number of ecosystems as members as they wish.

00:32:51.000 --> 00:32:53.000
In this kind of system, and why? Why I've drawn it like this is because it really gives a nice representation of what Oca can do.

00:32:53.000 --> 00:33:15.000
So you can imagine here that the data governance administration in the middle has defined a capture base and potentially some some core overlays to go on top of that but then all of the purposes driven services that are part of that ecosystem can just have custodianship.

00:33:15.000 --> 00:33:31.000
Of a couple of mapping overlays that they can map from their existing data capture to through those mapping overlays onto the capture base, so they can automatically harmonize the data so they don't even have to change how they're capturing data it's it's kind of part of the

00:33:31.000 --> 00:33:39.000
Flow if you like, they capture data as they always have done, and then it kind of pipes through the mapping overlays onto the capture base and so romatically harmonized.

00:33:39.000 --> 00:33:49.000
And that's really important. So when you're looking for searching for data within the ecosystem that harmonization process is essential.

00:33:49.000 --> 00:33:50.000
Yoca. It offers a solution to harmonization between data models and data representation formats.

00:33:50.000 --> 00:34:13.000
So, for instance, in the health care sector, which is a sector, I know very well that's where my whole career has been in working for big pharmaceutical companies in clinical clinical trials, and but even in in the farmer sector they use a bunch of different data

00:34:13.000 --> 00:34:15.000
Models, you know, within the authentication space or the identity space.

00:34:15.000 --> 00:34:24.000
They talk a lot about fire fire is used a lot for host hospitals and electronic health records.

00:34:24.000 --> 00:34:28.000
That sort of but now I'm only clinical in the clinical trial space.

00:34:28.000 --> 00:34:32.000
They use a totally different data model called Cdc.

00:34:32.000 --> 00:34:41.000
And those 2, those 2 data models have been trying to find harmonization solutions for over a decade, and they're still struggling with it.

00:34:41.000 --> 00:34:56.000
So oca kind of can do that for them now, because of the all the separation of the objects, you can actually go from fire to sea disk being piped through and Oca's structure or seed is to fire or whatever you want so that's kind of where our Ca

00:34:56.000 --> 00:35:01.000
Sits the key benefit of Oca is that different actors from different institutions.

00:35:01.000 --> 00:35:06.000
Departments can control specific task orientated objects within the same oca bundle.

00:35:06.000 --> 00:35:14.000
In other words, different actors may have dynamic control over assigned overlays rather than the entire semantics structure.

00:35:14.000 --> 00:35:19.000
As which is the case in today's digital landscape.

00:35:19.000 --> 00:35:38.000
Object, interoperability is essential in an data agile economy, where multiple actors from various institutions participate in complex use cases, supply chains, and data flows, supported by multi-stakeholder data governance administrations, and frameworks so here's another another example where where it could

00:35:38.000 --> 00:35:44.000
Be useful, you know we're obviously going into a world where we're getting more and more IoT devices.

00:35:44.000 --> 00:35:56.000
So if you think about something like unit conversions where there will capturing different units, you could have a the data governance administration for an ecosystem, saying: you know we we want to harmonize to this unit for for this this type of measurement.

00:35:56.000 --> 00:36:20.000
And and and and also had, you know, supported underpinned, if you like, by a unit conversion table, and then all of those IoT devices could literally, just have a unit mapping over atlay that maps from their unit to the preferred unit in the capture base you know using

00:36:20.000 --> 00:36:25.000
The Unit conversion Tab to to do the conversion factor.

00:36:25.000 --> 00:36:36.000
So yeah, it's got that. So that's another interesting use case which which I'm sure will will come up more and more often as we progress into the into the digital space.

00:36:36.000 --> 00:36:42.000
And then this is a this is one I really like, and I'll demonstrate this in the demo as well as internationalization.

00:36:42.000 --> 00:37:02.000
So, if you think about Switzerland, which is obviously where we're based in Switzerland, it has 3 official languages, German, Italian, and French, and an an unofficial language called romance and romance is only speaking spoken in one of the

00:37:02.000 --> 00:37:21.000
Swiss cantons, obviously Switzerland is, is predominantly German, but to the in the in the southwest of the of the country is French speaking, and and in the dead South into Chino they speak Italian so you know what Oca could do in this, case

00:37:21.000 --> 00:37:40.000
Is, say you had a you know, a government governmental form that could be, you know the capture base and a few core overlays could be issued by the by the Federal government of Switzerland and actually the can the different cantons, the can be defining all of the the overlay

00:37:40.000 --> 00:37:41.000
The language-specific overlays in their language.

00:37:41.000 --> 00:37:49.000
So you know that the there's a better chance that the translations are going to be more accurate because it's being is.

00:37:49.000 --> 00:37:52.000
They're being defined by people that speak the language.

00:37:52.000 --> 00:38:08.000
So actually even today, in Switzerland, I live at I live very close to Tucino in the Italian section, but because the Federal government most of the forms are developed in German or German as the primary language in Switzerland some of those translations are definitely

00:38:08.000 --> 00:38:17.000
Inaccurate. So this this would stop some of that core characteristics of oca task, or intended, I should say, task specific objects.

00:38:17.000 --> 00:38:23.000
So I'll change that count content bound objects.

00:38:23.000 --> 00:38:31.000
So content, bound, just means that the identifier of the object is is determined by the content of the object, so that's that's what we, call you know.

00:38:31.000 --> 00:38:39.000
Being a deterministic identifier. So all of the objects, all of the overlays or the capture base.

00:38:39.000 --> 00:38:47.000
They're all deterministic and actually the oca bundle itself is also is is also deterministic.

00:38:47.000 --> 00:38:52.000
Stable capture bases. So that's kind of more about the harmonization process, because because different actors can change different overlays.

00:38:52.000 --> 00:38:58.000
It just means that the capture bases don't.

00:38:58.000 --> 00:39:04.000
You don't have to keep reproducing capture bases because they can stay kind of stable.

00:39:04.000 --> 00:39:21.000
You can flag attribute, obviously sensitive at attributes in the capture base good for internationalization.

00:39:21.000 --> 00:39:22.000
Yes.

00:39:22.000 --> 00:39:28.000
As I just showed in the previous slide object presentation, which is a form or a quadruple, rendering those cryptographically linking those to the capture, base composability, because you obviously have lots of overlays, so you know makes it very composable ontology agnostic we don't care

00:39:28.000 --> 00:39:48.000
about you know, ontologies, or at the moment you know whatever ontologies need to be read in, we can produce tagging overlays at the schema level, the the attribute, level the predefined entry, level and the unit, level so different tagging overlays which are not

00:39:48.000 --> 00:40:06.000
In the stack at the moment, but they will be. They could be ontologists could use those to basically tag ontology, codes onto whatever they need within the capture base multiple users as a yeah, this is the idea of distributed custodianship of the different

00:40:06.000 --> 00:40:21.000
Objects, and it's it's cross-platform. It's it's not.

00:40:21.000 --> 00:40:22.000
At least in 21 min.

00:40:22.000 --> 00:40:30.000
There's no there's no blockchains or anything like that involved with with oca, you know, so you could be controlling certain objects in one network and other objects in another network and you can still cryptographically oh, have I gone past my time already

00:40:30.000 --> 00:40:40.000
Kalia. Am I out of time

00:40:40.000 --> 00:40:41.000
Oh, sorry. Okay.

00:40:41.000 --> 00:40:45.000
Oh, sorry I'm talking to my sorry. No, no, sorry I'm in transit and talking to myself.

00:40:45.000 --> 00:40:51.000
Bless you, okay, no problem. I thought I was getting a heckled off.

00:40:51.000 --> 00:40:57.000
It's all good. Okay. Yeah, so this: this this last part I don't know if there was any questions at all.

00:40:57.000 --> 00:41:04.000
I can take a few questions now if you want, or if you just want to see the the next demo, I can go straight in if you like.

00:41:04.000 --> 00:41:05.000
So yeah up to you that

00:41:05.000 --> 00:41:09.000
I've always been curious about what your is or what they do.

00:41:09.000 --> 00:41:10.000
I will. I'll take silence. Okay, okay, yeah.

00:41:10.000 --> 00:41:21.000
Hold for demo. I like the you said the demo is going to include the how you could determine cryptographic integrity across different yeah, across a data element through various presentations.

00:41:21.000 --> 00:41:26.000
I like. Yeah, if that's part of the demo that would be cool

00:41:26.000 --> 00:41:28.000
Yep. Yeah. Yeah. Absolutely. Yeah. And I'll I'll show you that.

00:41:28.000 --> 00:41:48.000
So so in this demo. How quickly th this is pretty much what we'll be seeing where we have that where we have the the picture of Switzerland with the different cantons having different language capabilities that is also kind of included, in the demo as well, but really what

00:41:48.000 --> 00:41:52.000
We're really concentrating is this idea of a Swiss passport seeing the the data capture form and the presentation.

00:41:52.000 --> 00:42:03.000
The the credential presentation, both cryptographically linked to the same capture base.

00:42:03.000 --> 00:42:05.000
So we've got some nice tooling where you can.

00:42:05.000 --> 00:42:18.000
We can show that all the industry you can do. You can do this demo yourself as well, so I've kind of constructed the slides so that you can follow the example just go through it step by step and you can actually do it yourself.

00:42:18.000 --> 00:42:30.000
There'll be 3 past this demo. One is so rendering a a form template, and rendering a credential template off the same capture base so in this case.

00:42:30.000 --> 00:42:45.000
You see here there's this zip file here that zip file basically contains a form layout over the end credential layout overlay in the oca bundle, so I basically pull that into our passer oh, sorry into our viewer and then you you can see the objects the

00:42:45.000 --> 00:42:46.000
Second part is integrating a record into the credential template.

00:42:46.000 --> 00:43:00.000
So in in the credential template. The passport there it's just it'll have like, you know, just just just the metadata, if you like, so what we're doing in this part is actually bringing in a data proper data object.

00:43:00.000 --> 00:43:10.000
Into, into into the metadata object so I can show you that part.

00:43:10.000 --> 00:43:12.000
So in here you've got this preview record set.

00:43:12.000 --> 00:43:20.000
That's basically a a self addressing identifier of of the data of the data object.

00:43:20.000 --> 00:43:28.000
And then finally, the last piece is gonna pull in an authentication mechanism from outside of Oca.

00:43:28.000 --> 00:43:31.000
So Oca. Does not do any authentication by itself.

00:43:31.000 --> 00:43:32.000
It's purely in the semantic domain, so it's it just cares about.

00:43:32.000 --> 00:43:50.000
Objects, or integrity, but if you wanted to bring some authentication into it in this case we're gonna bring in a an authentic chain chain data container and in the there's a in in in the authentic chain data container where there's the

00:43:50.000 --> 00:43:54.000
schema attributes basically a long self-addressing identifier.

00:43:54.000 --> 00:43:56.000
I would change one character in there, and the passport will go from verified to to not verified.

00:43:56.000 --> 00:44:03.000
So I'll share that part. Okay. So let me get on with that.

00:44:03.000 --> 00:44:21.000
So well, first of all, what I'll show you, I think, is this: so this is an Oca passing spreadsheet and obviously the readme file is just you know tells you exactly what's what's what's what's in the sheet but this is a

00:44:21.000 --> 00:44:26.000
Possible spreadsheet. So you can basically pull this into our pastor and it will build.

00:44:26.000 --> 00:44:30.000
It'll build the oca Bndle for you in Json.

00:44:30.000 --> 00:44:31.000
The main tab. Here are all of the all of the well.

00:44:31.000 --> 00:44:40.000
Basically these first, 4. Here, these first 4 columns are the capture base.

00:44:40.000 --> 00:44:41.000
So that's where you have your classification. Attribute names.

00:44:41.000 --> 00:44:49.000
Your attribute types, and and you can flag anything in the capture days.

00:44:49.000 --> 00:44:53.000
There, everything else is an overlay, so a character encoding overlay.

00:44:53.000 --> 00:45:04.000
So, for instance, with a photo image here you could change that to base 64, rather than utf 8 standard overlay, which I didn't show you in the other slides.

00:45:04.000 --> 00:45:10.000
But this this is a a new overlay. This is where you can, basically put in the official standard for that.

00:45:10.000 --> 00:45:22.000
You're using a format overlay. That the formatting you're using in the entry code here, here, where you see this self addressing identifier.

00:45:22.000 --> 00:45:23.000
This long ring. What that means is that that's that's referencing an external object.

00:45:23.000 --> 00:45:32.000
So just just so, you know that's what that's doing.

00:45:32.000 --> 00:45:48.000
These ones that are not addressing an external object are basically an internal coding system so this is a good example here, whereas Fmx, this is female, male and I think it's unspecified or something like that conditional overlay I won't go

00:45:48.000 --> 00:46:05.000
Into that too much. But you you can do a little bit of conditional programming here, so like you know, if you know, you can maybe make a couple of couple of attributes invisible, and and having it dependent on on on on an entry, of a of a of another attribute, if you

00:46:05.000 --> 00:46:06.000
Like. So that's the in in this case. You see, there's a conditional dependency.

00:46:06.000 --> 00:46:23.000
It just means, you know, if unless the document type in this case is filled in then and then the other, these these 2 things height and height, unit will stay hidden that's what that's doing cardinality cardinality.

00:46:23.000 --> 00:46:31.000
Basically that just means. If you have say you can only enter, say a maximum of 2 values for that particular attribute.

00:46:31.000 --> 00:46:41.000
Conformance is, if something's mandatory or or or will be mandatory and optional.

00:46:41.000 --> 00:46:50.000
Thank you, and then a unit overlay. So in this case, heights unit is done in sets and centimeters.

00:46:50.000 --> 00:46:54.000
So these are all different different overlays here, and they're all language agnostic.

00:46:54.000 --> 00:46:59.000
These ones in the main tab, and then, if you're doing different languages, these are all all separate tabs.

00:46:59.000 --> 00:47:00.000
So this is all done in in English, so you'll met her lay in English.

00:47:00.000 --> 00:47:04.000
This is a your attribute. Names are obviously the same.

00:47:04.000 --> 00:47:13.000
English labels in English, predefined entries.

00:47:13.000 --> 00:47:24.000
Here female mail specified English information. You could do that in French as well so this is all in French, and except same same concept.

00:47:24.000 --> 00:47:34.000
So this is a possible spreadsheet, as I said, but I just wanted to show you that just so you can kind of have have an idea how how the hell do I build building an oca bundle this is a this is a good starting place.

00:47:34.000 --> 00:47:35.000
Okay, so where are we? So there's so this is the Oca official website.

00:47:35.000 --> 00:47:42.000
I can. I can basically cut and paste that in.

00:47:42.000 --> 00:47:48.000
I think. Let me just see if I can get this to work.

00:47:48.000 --> 00:47:58.000
You know what I what I'll do is I will send Kalia this deck, and and any any instructions that you guys need and stuff.

00:47:58.000 --> 00:48:16.000
I'll I'll make sure that you have all the information I would do it now, but unfortunately I'm having trouble finding the chat, so it's me being a muppet rather than zoom being a muppet and then here so in in the oca on the website you

00:48:16.000 --> 00:48:26.000
have this application section here, and the applications are basically some of the some of the the use cases that I showed in the in the presentation.

00:48:26.000 --> 00:48:48.000
But for the third use case here on internationalization. This this one here at the bottom of this part, there's actually a Swiss don't know here, Swiss passport, example, so and that goes into that basically goes into here and you can go through this whole thing step by step and it has all

00:48:48.000 --> 00:48:49.000
linked, and everything. So in the demo I show you that like this will be the data.

00:48:49.000 --> 00:48:58.000
That the data object that I pull into the into the credential template.

00:48:58.000 --> 00:49:03.000
Okay, so let's get started. I won't show you an Rca bundle yet, because they're actually pretty boring.

00:49:03.000 --> 00:49:11.000
They're just usually a whole bunch of self-addressing identifiers and individual objects.

00:49:11.000 --> 00:49:19.000
But what I will do is when I, when I send this over to you guys I'll send you the the zip file that I'm using for all of the rendering that you're about to.

00:49:19.000 --> 00:49:23.000
See and then I'll also send over a human readable zip file, so you can click into that and with human readable names.

00:49:23.000 --> 00:49:31.000
So that you know what those different objects are, is kind of easier to find them that way.

00:49:31.000 --> 00:49:36.000
Okay. So we start here with your sa browser. Let's I'm gonna go.

00:49:36.000 --> 00:49:39.000
So where you would pull in that possible spreadsheet?

00:49:39.000 --> 00:49:45.000
Is that here this select select oca file. But but I won't.

00:49:45.000 --> 00:50:01.000
I won't do that for this for this particular demo. Just so I've already got a zip file that's ready to go. So I'm I'm gonna go straight to preview here and I'm gonna pick pick up the oca bundle

00:50:01.000 --> 00:50:07.000
So in oca Swiss passport there should be a zip file.

00:50:07.000 --> 00:50:15.000
There you go! Pick up the zip file and upload it and then this will automatically pass, and in here you've got the form.

00:50:15.000 --> 00:50:20.000
So you know, it's so basically that spreadsheet that I showed you this.

00:50:20.000 --> 00:50:23.000
That's that's the form that's being passed.

00:50:23.000 --> 00:50:27.000
Everything, all of your predefined entries here, or all in English.

00:50:27.000 --> 00:50:32.000
You know, when I said that you have a self-addressing identifier that can point to an external code table.

00:50:32.000 --> 00:50:36.000
That's what's what's happening here with this issuing state and organization.

00:50:36.000 --> 00:50:40.000
So that's a 3 digit Iso code for any country in the world.

00:50:40.000 --> 00:50:46.000
You have things like this here, which is an information overlay.

00:50:46.000 --> 00:50:55.000
You have a find some proper entries here again. This is a this is being pulled from a an external code. Table.

00:50:55.000 --> 00:51:02.000
Your your sex, etc. So that's where you have this little yellow oh, sorry!

00:51:02.000 --> 00:51:10.000
This little blue tick box on the side here. These are these are basically the the the the attributes that have been flagged in the capture.

00:51:10.000 --> 00:51:13.000
There's the ones with the little blue boxes.

00:51:13.000 --> 00:51:17.000
Obviously, if I just change this all to French, then the entire form changes to French.

00:51:17.000 --> 00:51:23.000
It's now a very French form, all of your predefined entries again.

00:51:23.000 --> 00:51:41.000
All of your information as all now in French, and I can prove that in the in the code table as well, even nationality, that's now in those are all in French as well and and obviously female male okay, so that's the form rendered and and that's done with a form form

00:51:41.000 --> 00:51:42.000
Layout. So overlay is basically dictating how that form looks.

00:51:42.000 --> 00:51:51.000
But then we've also got a credential layout in this in in this stack.

00:51:51.000 --> 00:51:55.000
So this is this is where you have all your branded objects and your credential template.

00:51:55.000 --> 00:51:57.000
So all I'll show you on here, is it? It has.

00:51:57.000 --> 00:52:08.000
It has full of objects, your integrity, you know everything that you've seen so far is just metadata, and everything is self addressing identifiers.

00:52:08.000 --> 00:52:18.000
So here. If I change here this possible from English rendering into French, you'll see that you know all of the all of them, all of the attribute labels.

00:52:18.000 --> 00:52:22.000
There are now changing interface, etc. So that's so.

00:52:22.000 --> 00:52:24.000
What I've shown you here is just like the part one of the demo.

00:52:24.000 --> 00:52:41.000
So this is just metadata: that I've showed you so far, so it's already pretty cool, but it gets even cooler once we kind of move through the different the different parts so moving into the second part of the demo for this one i'm basically oh, I'm gonna I just

00:52:41.000 --> 00:52:49.000
Have to pick up. So this is this: is this part is where we're going to pick up that the the data object and basically integrate it into the into the credential template. So that's what this part.

00:52:49.000 --> 00:52:56.000
Is going to do so. To do this I have to actually pick up this.

00:52:56.000 --> 00:53:02.000
This said of the preview: record so I just go to find that I think it's yeah.

00:53:02.000 --> 00:53:09.000
He's right here, so I'm gonna pick up this said no control C.

00:53:09.000 --> 00:53:19.000
And then I gotta go back to here. Okay so the first thing I'm gonna do is I'm gonna pick up the same zip file that I just did for the initial rendering.

00:53:19.000 --> 00:53:36.000
So that stuff here there we go zip, file, and then I'm gonna upload that and then that the preview set I will just paste in what I just copied and then the the data store here is is is is let me explain.

00:53:36.000 --> 00:53:39.000
That a little bit. So we have 2 storage components here one is called an Oc.

00:53:39.000 --> 00:53:52.000
Repository, so the Oca repository stores, all of the the capture base, all of the overlays the bundle stuff is all held in that, and then we have this other this other storage.

00:53:52.000 --> 00:54:03.000
Here? Could be anything, right. It's but for in our case we have this thing called a database, and in the data boat we have all the Swiss branched to credential images code tables as well, we tend to bung them.

00:54:03.000 --> 00:54:11.000
Into the dead data vault as well. So for the essay that was pointing to those country codes.

00:54:11.000 --> 00:54:28.000
They were pulling that out of this data vault. So if I now load this you now go a the Swiss passport rendered, and you've got that data.

00:54:28.000 --> 00:54:31.000
Object is now included, so you've got here.

00:54:31.000 --> 00:54:34.000
John's citizen, Who's Swiss, etc.

00:54:34.000 --> 00:54:40.000
And again. So now this has this still has obviously full full objectual integrity.

00:54:40.000 --> 00:54:58.000
I can change the entire credential into French and now it's it's obviously rendering all these pieces all these labeling bits in French, and what's kinda nice about this actually is if you think what what you could do is something like this in the future is say, I've got a so I'm

00:54:58.000 --> 00:55:14.000
Actually not Swiss. I'm I'm British, so I don't say about my British passport, and I'm traveling to to could be anywhere else. Let's pick one maybe I'm gonna go visit the the the Enduit community and in Northern Canada and and somebody wants

00:55:14.000 --> 00:55:24.000
to understand what's in my passport. I could basically render my English passport into Anuca, Took which is the language that they speak in a really minority language, and then they can understand you know exactly what they're seeing in their side on their language.

00:55:24.000 --> 00:55:40.000
And it would still have full crypto objection, integrity, because you know all of their language overlays will all have the self addressing identifiers.

00:55:40.000 --> 00:55:45.000
It will be. Track. All of those objects will be built by the Inuit people.

00:55:45.000 --> 00:55:47.000
In this case. So yeah, you could you could have a lot of fun with this in the future.

00:55:47.000 --> 00:55:55.000
The internationalization pop. Okay? And then the last part I wanted to show you is, is Yeah, go ahead, Keith.

00:55:55.000 --> 00:56:02.000
So I mean in the context of a verifiable credentials and wallets.

00:56:02.000 --> 00:56:03.000
Hmm.

00:56:03.000 --> 00:56:20.000
So can you just talk me through the process, so I am issued a digital passport from a Swiss government, or from account on does the Oca bundle come with that credential or when Mike while it goes to render that credential it reaches out to your data storage layer and

00:56:20.000 --> 00:56:23.000
It, it grabs the oca bundle that to then render the credential in mobile, which is it is it come with the credential?

00:56:23.000 --> 00:56:32.000
Or does the wall, and always have to reach out and grab the bundle at time at presentation

00:56:32.000 --> 00:56:39.000
Yeah, the wallet would grab at the time of presentation exactly, and yeah, those are, you know.

00:56:39.000 --> 00:56:57.000
That's obviously how you do. That is actually more of a kind of a governance, more of a governance question so you know how how, how you, how an app, how an app, how how an app at a at a at a national border how they want to in ingest that, information is up to them and even

00:56:57.000 --> 00:57:00.000
the storage, you know the storage of the objects.

00:57:00.000 --> 00:57:18.000
We use an oca repository for that, but you know, if they were to do that on a blockchain or something they could do that as well, depending on on on what the what the use cases and depending on what the governance should decide they want to do for for that so all our Ca does

00:57:18.000 --> 00:57:20.000
is really is literally just, the the the the metadata objects, making sure that they have full integrity.

00:57:20.000 --> 00:57:32.000
Everything else is, is, is done on the application side to answer your question.

00:57:32.000 --> 00:57:34.000
Yeah? Yeah? And then I think the other question I had was in your example.

00:57:34.000 --> 00:57:35.000
Hmm.

00:57:35.000 --> 00:57:42.000
So it seems like a lot of this would require like a governing organization to define a lot of the base.

00:57:42.000 --> 00:57:54.000
Oca, and I think in your example you said, Okay, well, maybe the switch National Government does some of the oca work, and then individual cantons can do maybe more individual language elements.

00:57:54.000 --> 00:58:03.000
But then that would all have to then eventually be brought back into some big bundle that would be hosted by something like a National Swiss government or something. And am I kind of thinking about this right

00:58:03.000 --> 00:58:09.000
Yeah, so basically the the oca bundle itself has a self addressing identifier.

00:58:09.000 --> 00:58:27.000
So you you could imagine. You know that if if the if the object is is is fairly stable, then within the data governance, administration, they could just say, You know, at the moment the oca, bundle that we're using which is a verifiable object is is this this

00:58:27.000 --> 00:58:36.000
Sa Id, you know. Obviously, if they they have new versions and stuff, then, you know, there'll be new overlay types going into a new bundle.

00:58:36.000 --> 00:58:37.000
That will be the reason rehashed or whatever goes on.

00:58:37.000 --> 00:58:58.000
There and then you have a new essay id for a new bundle, and then the the official website, wherever that's coming, from we'll just say, this is the this is the the bundle to use so yeah, yeah, so Yeah, I I I didn't want to get too. Involved.

00:58:58.000 --> 00:58:59.000
With governance. There's a totally different domain, governance.

00:58:59.000 --> 00:59:13.000
I'm not a governance expert. I'm only a semantics guy, but yeah, a lot of the certainly the the way that I look at it is, you know the the very first thing that you'll get in place within one of these data ecosystems.

00:59:13.000 --> 00:59:17.000
Is going to be that. Go get the governance administration.

00:59:17.000 --> 00:59:22.000
You know what is? What is the the problem? Space that we're trying to solve?

00:59:22.000 --> 00:59:33.000
And you know within a multi stakeholder administration they get together, and they decide what's objects they need to put into that ecosystem for the benefit of the of the members so it starts with the the governance but then it.

00:59:33.000 --> 00:59:51.000
Quickly moves into the semantics, because then they have to decide how they want to define the objects, and then, once the objects are defined, then that then that's really when the authentication kicks in and i'll show you the authentication.

00:59:51.000 --> 00:59:54.000
Part right now. How that works yeah, is that is that anything else you wanted to know?

00:59:54.000 --> 01:00:00.000
Keith.

01:00:00.000 --> 01:00:06.000
Okay. Okay. Perfect. Okay, so the next demo is gonna be this one.

01:00:06.000 --> 01:00:19.000
So all this is done is this is basically automatically pulled in this this authentic chain data container I don't know if you guys know what that is, but I put here also this is the th.

01:00:19.000 --> 01:00:24.000
This is the the the the standard, or whatever you call it, for A/C.

01:00:24.000 --> 01:00:25.000
DC. And then in here the the only thing I wanted to show you is this: basically this line here?

01:00:25.000 --> 01:00:37.000
So S. Stands for schema. Right? So this is basically the scheme of bundle, the the the sa id.

01:00:37.000 --> 01:00:45.000
Of the scheme bundle. So here I'm just gonna issue this credential here and then it's pulled it into the rendering part.

01:00:45.000 --> 01:00:46.000
I'm gonna have to scroll down a little bit 1 s, so I can see.

01:00:46.000 --> 01:00:55.000
Hey? Go down, hey! Where are you?

01:00:55.000 --> 01:01:11.000
Hang on count. Oh, it's right there. Okay. So I hit this bottom down the bottom, render credential, and then if I scroll down now, you'll see that it's the same object, and it's now saying that it's verified so all of the all of the sa ids are

01:01:11.000 --> 01:01:17.000
As expected, and that there's been no no corrupted objects and it's verified again.

01:01:17.000 --> 01:01:18.000
I can change that whole thing into French. The whole, the whole possibility now is changing into French.

01:01:18.000 --> 01:01:27.000
It's still verified right? Because all of the objects are in the in that bundle.

01:01:27.000 --> 01:01:32.000
So that's all good, and then. So now I'm going to go into that same thing here.

01:01:32.000 --> 01:01:38.000
I should see an S. S for schema. So any here I'll just change change one of these characters.

01:01:38.000 --> 01:01:40.000
I'll just remove a full there, and just render the credential, and you'll see because because it's lost objectual integrity.

01:01:40.000 --> 01:01:51.000
It's now not verified. So that's the cryptographic element, and that's it.

01:01:51.000 --> 01:01:52.000
That's the end of that demo. I can go back to.

01:01:52.000 --> 01:02:00.000
I can go back to the deck here so that I can quickly just remind you what you saw.

01:02:00.000 --> 01:02:04.000
Sort of the first first part was rendering a form and a credential template.

01:02:04.000 --> 01:02:13.000
Second part was pulling in a data record into the credential template, and then the third part was attaching that Acdc.

01:02:13.000 --> 01:02:23.000
That authentication mechanism in that credential and and showing how it it was verified, and then changing something, and then it was not verified.

01:02:23.000 --> 01:02:25.000
So that's it. I can before I kind of explain these links here.

01:02:25.000 --> 01:02:26.000
I can. I can take some more questions if anybody wants

01:02:26.000 --> 01:02:41.000
I'm not less. We can look at the next demo and see what time we have

01:02:41.000 --> 01:02:44.000
Any questions.

01:02:44.000 --> 01:02:45.000
Cool. Hmm.

01:02:45.000 --> 01:02:46.000
So I think in our example, Switzerland, I mean, I think it.

01:02:46.000 --> 01:02:47.000
This makes a lot of sense for governments. When you have a governing organization to kind of put together these oca.

01:02:47.000 --> 01:02:48.000
But I mean you mentioned you worked a lot time in health care so like I did work on.

01:02:48.000 --> 01:02:49.000
Let's say Clinton, trials in which you have multiple pharmaceuticals that want to, you know, work together on a critical trial, but I think what always we saw lacking and this is particularly for the us, context is there's lax this kind of a gum over overriding organization that could do this kind

01:02:49.000 --> 01:03:19.000
Of semantic definition. You have more like individual pharmaceuticals, defining their own credentials and defining their own semantics and they're not really willing to get together in a room and have like discussion on like broad semantics across their industry I I wonder what you thought about this just

01:03:27.000 --> 01:03:28.000
Yeah. Yeah. Sure. So I think in the Us. It is a little bit different than in Europe.

01:03:28.000 --> 01:03:52.000
I think in the Us. The the health care sector is is, is more fragmented in a way, but I think that the way that the world is is going to go where obviously Europe is really hammering these data spaces now here's so much public funding available for some of these things

01:03:52.000 --> 01:04:02.000
Now you know they're actually building a European health data space, you know, and that will have to have some sort of multi stakeholder data governance administration for that space.

01:04:02.000 --> 01:04:04.000
So I think it's gonna it's gonna come.

01:04:04.000 --> 01:04:05.000
I don't have no idea how long it's gonna take.

01:04:05.000 --> 01:04:12.000
You know there's so much to think about. It's not gonna happen overnight.

01:04:12.000 --> 01:04:22.000
Even the European. You know even the things. They're funding, I think, are some of the things that are funding the wrong things, but you know they're they haven't really defined some of the plumbing they're they're already.

01:04:22.000 --> 01:04:30.000
They're talking about you know, wallets and stuff without really thinking about you know.

01:04:30.000 --> 01:04:33.000
How's this gonna work within a distributed data ecosystem?

01:04:33.000 --> 01:04:41.000
So yeah, didn't really answer your question all all I can say is that in Europe it's definitely going that way.

01:04:41.000 --> 01:04:46.000
I presume that at some stage us will follow the model.

01:04:46.000 --> 01:04:53.000
I'm guessing so that everything is so that they can interact with some of these European data spaces.

01:04:53.000 --> 01:04:57.000
But maybe you guys know better than me. I mean what's going on in the Us.

01:04:57.000 --> 01:04:58.000
There. Are you seeing any movement towards this

01:04:58.000 --> 01:05:16.000
Because, you know, you spoke what you had experience in that

01:05:16.000 --> 01:05:21.000
Yup!

01:05:21.000 --> 01:05:23.000
Yeah. Yeah. Yeah. Yeah. I mean we'll you know I mean the other thing I didn't say is that you know.

01:05:23.000 --> 01:05:32.000
Obviously I've I've I've been kind of saying that the data governance administration will issue these things.

01:05:32.000 --> 01:05:36.000
But actually anybody could issue these things is totally fine. You know.

01:05:36.000 --> 01:05:37.000
It's a it's still a it's still a very powerful, fully extensible architecture for building metadata.

01:05:37.000 --> 01:05:40.000
Go ahead. Keep going. You're good. We have

01:05:40.000 --> 01:05:53.000
So it just means that you know there's gonna be a gazillion overlay types that we haven't even seen yet and there'll be you know, as new used cases.

01:05:53.000 --> 01:05:56.000
Come in and work. So you know that that needs a new type.

01:05:56.000 --> 01:05:57.000
But I think the core structure is that, you know, because we've kept it kept everything very pure, and everything is task task.

01:05:57.000 --> 01:05:58.000
Hey, Paul, so we're at the top of the hour.

01:05:58.000 --> 01:06:16.000
Specific. It just means. If if if there's new tasks coming in, we can kind of deal with those at when when we see them yeah.

01:06:16.000 --> 01:06:21.000
Sure.

01:06:21.000 --> 01:06:24.000
Yeah. Sure. So so at the moment with those say, all the objects are in Json.

01:06:24.000 --> 01:06:34.000
But it's Json's just a serialization format as as is Json, Ld.

01:06:34.000 --> 01:06:37.000
So there's nothing stopping you from building in Json, Ld.

01:06:37.000 --> 01:06:46.000
Just keeping, you know, just keeping the same methodology. That's the important thing with Oca is really the methodology rather than the serialization format.

01:06:46.000 --> 01:06:54.000
But one thing I would say is that I know there's some conversations going on about the the context attribute with Json. Ld.

01:06:54.000 --> 01:07:00.000
The only thing to be aware of is that with those Ca: Everything is deterministic.

01:07:00.000 --> 01:07:05.000
So what that means is that whatever is behind the context, attribute in Json, Ld.

01:07:05.000 --> 01:07:11.000
You need to make sure that that is a deterministic object that's not going to change.

01:07:11.000 --> 01:07:15.000
Right so at the moment I think that with Json, Ld.

01:07:15.000 --> 01:07:20.000
Some of the implementations have been haven't probably thought that through.

01:07:20.000 --> 01:07:21.000
But definitely, I think even without Oca. I think that is a a potential weakness with Json, Ld.

01:07:21.000 --> 01:07:26.000
But we did start 5 min late. I have one question: how does this relate to like Jason, Ld.

01:07:26.000 --> 01:07:27.000
But yeah, I think if if people are in implementing it properly, then you could definitely use Json how these? Not a problem

01:07:27.000 --> 01:07:28.000
Great. Thank you, Paul, this is really great. I appreciate you coming and sharing with us, and I don't.

01:07:28.000 --> 01:07:29.000
I'm not sure if you're on the interrupt list.

01:07:29.000 --> 01:07:52.000
But if you're not, just send along the links and follow up that you want, and we'll be sort of posting to the list

01:07:52.000 --> 01:07:59.000
Okay. Perfect. What I'll do Kelly. I'll probably send you a a week transfer file, because I'm gonna send like some zip.

01:07:59.000 --> 01:08:00.000
Zip files and things in there as well. So I'll just I'll send that to you.

01:08:00.000 --> 01:08:01.000
Okay. Great.

01:08:01.000 --> 01:08:07.000
And then you can send that to the group and I think with those we transfers they they!

01:08:07.000 --> 01:08:08.000
They they automatically delete or are not possible to get into that thing.

01:08:08.000 --> 01:08:12.000
Yeah, I think it's a challenge right? I mean. I think I think like a country like Canada could probably get together and define semantics, for let's say, drivers licenses across. Canada I think that works already happening but as you get more decentralized I think this becomes harder

01:08:12.000 --> 01:08:19.000
After about 5, 5 5 days or something, but yeah, good. And then this is my email address.

01:08:19.000 --> 01:08:26.000
So yeah. If anybody wants to email me, then feel free and I'll comp put that in that shell as well

01:08:26.000 --> 01:08:43.000
Human process.org. Yeah, there's that. So if anybody wants to email me about this stuff, then feel free and apart from that, thank you very much for having me very kind of you and yeah, I I hope you enjoyed the demo and yeah, any questions feel free.

01:08:43.000 --> 01:08:44.000
To reach out anytime. I'm available 31, so

01:08:44.000 --> 01:08:50.000
Thank you.

01:08:50.000 --> 01:08:56.000
And I'll stop sharing.

01:08:56.000 --> 01:08:57.000
Okay. I think we're we're all good

01:08:57.000 --> 01:08:58.000
Morning.

01:08:58.000 --> 01:08:59.000
Hello!

01:08:59.000 --> 01:09:00.000
Lamari told me to just save the chat.

01:09:00.000 --> 01:09:01.000
Well be the host, and

01:09:01.000 --> 01:09:02.000
I guess we'll just save automatically save it. Once I close out

01:09:02.000 --> 01:09:32.000
It'll just stop recording