 So, we'll come again to the second part of my talk that talks about what is an ontology. Again I am Mustafa Jarrar from BZ University in Palestine and I'm specialized in semantics and ontologies and that integration. So what is an ontology and why do we need it for governments? And how? What's an ontology? If you go to Google and you ask Google what is an ontology, you will find something related to philosophy, which is the subject of existence. But we are not dealing with these things. We are actually mean with an ontology as this specification of, or the description of the meanings of the words we use in a domain, like in the government domain. So it's like the characterization or specification of the meanings of terms, of concepts we have in the government domain. So this is simply what is an ontology, or to make it even simpler to say, it is a dictionary written in a certain way that organizations share, have in common, to understand each other when they exchange information. So why do we need it? Well, if you have, for example, a web service between institution A and institution B, and the meaning of the data, the semantics of the data, inside the data message, have to be defined. So otherwise the receiver will not understand the data, like as we said in the previous talk, what does it mean, if name, what does it mean, person, what does it mean, salary. So these concepts have to be, or terms have to be defined. So their definition now have to be, let's say, agreed among all organizations. But why do we need it? Why do we need this ontology? It's actually, can we replace, can I call organization A, the sender of the data message, and tell them, what does it mean, if name, what does it mean, person, yes, you can do. And then you don't need an ontology by the way. But if we have more organizations, then people typically sign MOU about the technical specifications of their web services. So if you have two organizations, there is an MOU. If you have three organizations, then you have three wings between A and B, B and C, and A and C. So you have three MOUs. If you have four, you have, if you have five, six, if you have, what, 1500 organizations sharing, or they want to exchange data messages, so it's not scalable at all to have MOUs between these organizations. So what is the solution? The framework to have semantic interoperability is to build an ontology. And you say this ontology is shared among all organizations. And then we don't, everyone respect this ontology, and then that's it. We don't need any more technical MOUs. And well, then maybe you say, what, how the ontology from inside look like? Well, it looks like, it's not a dictionary actually, but it looks like that every term we use, we have first its name, then we write its definition, typically written in OWL, something called standard web ontology language, but it's not necessarily to be written. Maybe you write it in UML, or I really advise you to write it even in something called ORM, object role modeling, which is a graphical language. Just draw it on paper. That's fine. And you can classify things. For example, take which I highly recommend every country in the world to, when they build semantic interoperability framework to build something called legal person ontology, which is a classification of the legal personalities in a country according to the law of that country. For example, so a legal person can be a natural person, like me, or an organization. So like bank, university, company, whatever, it also has a legal personality. So then a natural person can be a citizen, it can be a refugee, it can be a visitor to the country, et cetera. So we have classifications of even natural personalities, not persons in the physical sense, in the legal sense. And when we have organization, we can have association, we can have a company, we can have local authorities, like municipalities, et cetera. So we need a company can be shareholding, non-shareholding. So we can build a tree of legal personalities. This is actually, it is itself, is the definition of the meaning of the concept, for example, company. But this is data, by the way. This is data ontology. Later I will talk a little bit about what is that mean service ontology. Now, how can I use this ontology? If I build an ontology, even I build it on paper, I don't have to build it as something part of a program. How can I use it? Well, if you are a developer, I can tell you, when you develop a web service, avoid inventing names of variables. Don't do this. You have to follow the naming that provided in the ontology. And you respect the meaning of the concept as it provided in the ontology. So it became like the vocabulary space for your web service. It provides the, again, the naming conventions, and sometimes even multi-languages. It provides the meaning, the semantics of your variables, of your data, and also it can provide the structure of the information, the terminology, the structure of your, I use an example, for example, the address. How should I structure my information about address or any profile that I want to send and receive? So you can respect the structure provided in the ontology. So please remember that the ontology will help you for naming, for meanings, and for data structure. Now, another very interesting use of the ontology. So as I told you, imagine this tree of legal personalities and imagine you have government services, renewing passport, issuing birth certificate, ID, whatever. Try to link each, so each service, each government service, have provider, and also it has consumers, list of consumers. Try to list the list of consumers or to link them with notes in the legal person ontology tree. This is very important because in many countries, even they say, my government services will define, but it's actually not. You need to link this. And last thing I want to say about service ontology. So service ontology are also important to classify services because sometimes we need to compose services. So a government service consists of several web services. But a web service can be used in more than one government service. So if you classify your services, it helps you for composition. Again, if you want to have a look to an ontology being used in practice, and how it looks like, and how it's used, I propose you to have a look to our framework in Palestine. It's called ZINAR, Z-I-N-N-A-R, dot P-N-A dot P-S. There is an ontology there, and it's explained in details. Thank you very much.