4. What is e-Government (Simplified Demo)
e-Government is a (framework) to enable electronic services:
government-to-government (G2G), government-to-business (G2B),
and government-to-citizen (G2C).
اﳊﻜﻮﻣﺔ اﻹﻟﻜﺘﺮوﻧﻴﺔ ﻫﻲ )أﻃﺮ وﻣﻌﺎﻳﻴﺮ( ﲤﻜﻦ اﳊﻜﻮﻣﺔ ﻣﻦ ﺗﻘﺪﱘ ﺧﺪﻣﺎﺗﻬﺎ إﻟﻜﺘﺮوﻧﻴﺎً ﳉﻬﺎت
.ﺣﻜﻮﻣﻴﺔ أﺧﺮى وﻟﻠﻤﺆﺳﺴﺎت واﳌﻮاﻃﻨﲔ
########
########
########
########
Ministry B
à Authenticate User?
Ministry A
Transport
Ministry C
Interior
Health
Ministry D
Name:###########
PIN:###########
K?
Kü
12345
Portal
Metadata
Payment
Server
Authentication
Server
5. What is e-Government (Simplified Demo)
########
########
########
########
Ministry B
Ministry A
Transport
Ministry C
Interior
Health
Ministry D
List of allowed services
àChoose Renew Driving License
Renew License
Register Car
Renew Passport
Register New born Copy
of Birth Certificate
<Query>
<Query>
Portal
Metadata
Payment
Server
Authentication
Server
6. What is e-Government (Simplified Demo)
Ø Servers interoperate among each other to exchange data messages (to
implement an e-service), similar to exchanging papers between
ministries in the real world.
ﻹﳒﺎز أي ﺧﺪﻣﺔ ﺣﻜﻮﻣﻴﺔ، ﺗﺘﺒﺎدل أﻧﻈﻤﺔ اﻟﻮزارات ﻓﻴﻤﺎ ﺑﻴﻨﻬﺎ رﺳﺎﺋﻞ ﺑﻴﺎﻧﺎت إﻟﻜﺘﺮوﻧﻴﺎ، ﻛﻤﺎ ﻳﺘﺒﺎدل
.اﳌﻮﻇﻔﲔ وﺛﺎﺋﻖ رﺳﻤﻴﺔ
#########
#########
#########
#####
Ministry B
=====
=====
Ministry A
Transport
Ministry C
Interior
=====
=====
Health
Ministry D
List of allowed services
àChoose Renew Driving License
Xxxxxxxx
Xxxxxxxx
Renew License
Register Car aaaaa
Aaa aaa aaa a
Name:
Name: Bbbbb bbbb a bb aaa
Name: Vvvv ccc
Renew Passport
bbbbb
Aaa aaa aaa a aaaaa
Bbbbb bbbb a born
Register New bb aaa Copy
of Birth Certificate
<Query>
<Query>
<Query>
<Query>
<Query>
Portal
Metadata
Payment
Server
Authentication
Server
7. What is e-Government (Simplified Demo)
Ø Servers interoperate among each other to exchange data messages (to
implement an e-service), similar to exchanging papers between
ministries in the real world.
Ministry D
Ministry C
Ministry B
Health
Interior
ﻹﳒﺎز أي ﺧﺪﻣﺔ ﺣﻜﻮﻣﻴﺔ، ﺗﺘﺒﺎدل أﻧﻈﻤﺔ اﻟﻮزارات ﻓﻴﻤﺎ ﺑﻴﻨﻬﺎ رﺳﺎﺋﻞ ﺑﻴﺎﻧﺎت إﻟﻜﺘﺮوﻧﻴﺎ، ﻛﻤﺎ ﻳﺘﺒﺎدل
.اﳌﻮﻇﻔﲔ وﺛﺎﺋﻖ رﺳﻤﻴﺔ
Transport
List of allowed services
àChoose Renew Driving License
Ministry A
ü
Xxxxxxxx
Xxxxxxxx
Renew License
Register Car aaaaa
Aaa aaa aaa a
Name:
Name: Bbbbb bbbb a bb aaa
Name: Vvvv ccc
Renew Passport
bbbbb
Aaa aaa aaa a aaaaa
Register Newbb aaa Copy
Bbbbb bbbb a born
of Birth Certificate
Portal
Metadata
Payment
Server
Authentication
Server
8. What is e-Government (Simplified Demo)
Ø Servers interoperate among each other to exchange data messages (to implement
an e-service), similar to exchanging papers between ministries in the real world.
.ﻹﳒﺎز أي ﺧﺪﻣﺔ ﺣﻜﻮﻣﻴﺔ، ﺗﺘﺒﺎدل أﻧﻈﻤﺔ اﻟﻮزارات ﻓﻴﻤﺎ ﺑﻴﻨﻬﺎ رﺳﺎﺋﻞ ﺑﻴﺎﻧﺎت، ﻛﻤﺎ ﻳﺘﺒﺎدل اﳌﻮﻇﻔﲔ وﺛﺎﺋﻖ رﺳﻤﻴﺔ
A framework is needed to allow this Interoperability between servers, taking into
account the (Organizational, Technical, and Semantics) issues.
ﻟﺒﻨﺎء اﳊﻜﻮﻣﺔ اﻹﻟﻜﺘﺮوﻧﻴﺔ ﻧﺤﺘﺎج اﻟﻰ ﺑﻨﺎء أﻃﺮ وﻣﻌﺎﻳﻴﺮ ﻟﺘﺘﻤﻜﻦ أﻧﻈﻤﺔ اﻟﻮزارات ﻣﻦ ﺗﺒﺎدل رﺳﺎﺋﻞ إﻟﻜﺘﺮوﻧﻴﺔ
########
########
########
########
Ministry B
Ministry A
Transport
Ministry C
Interior
=====
=====
Health
Ministry D
ü
Xxxxxxxx
Xxxxxxxx
Renew License
Register Car aaaaa
Aaa aaa aaa a
Name:
Name: Bbbbb bbbb a bb aaa
Name: Vvvv ccc
Renew Passport
bbbbb
Aaa aaa aaa a aaaaa
Register Newbb aaa Copy
Bbbbb bbbb a born
of Birth Certificate
<Query>
<Query>
<Query>
Portal
Metadata
Payment
Server
Authentication
Server
9. What is e-Government (Simplified Demo)
Data Message
Ø <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/" implement
Servers interoperate among each other to exchange data messages (to
SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
an e-service), similar to exchanging papers between ministries in the real world.
Transport
########
########
########
########
Interior
=====
=====
Health
<SOAP-ENV:Header>
. . .
.ﻹﳒﺎز أي ﺧﺪﻣﺔ ﺣﻜﻮﻣﻴﺔ، ﺗﺘﺒﺎدل أﻧﻈﻤﺔ اﻟﻮزارات ﻓﻴﻤﺎ ﺑﻴﻨﻬﺎ رﺳﺎﺋﻞ ﺑﻴﺎﻧﺎت، ﻛﻤﺎ ﻳﺘﺒﺎدل اﳌﻮﻇﻔﲔ وﺛﺎﺋﻖ رﺳﻤﻴﺔ
<SOAP-ENV:Header>
<SOAP-ENV:Body>
A framework is needed to allow this Interoperability between servers, taking
...
<Person>
into account the (Organizational, Technical, and Semantics) issues.
<PersonID>123456789</PersonID>
<FName>Rula</FName>
ﻟﺒﻨﺎء اﳊﻜﻮﻣﺔ اﻹﻟﻜﺘﺮوﻧﻴﺔ ﻧﺤﺘﺎج اﻟﻰ ﺑﻨﺎء أﻃﺮ وﻣﻌﺎﻳﻴﺮ ﻟﺘﺘﻤﻜﻦ أﻧﻈﻤﺔ اﻟﻮزارات ﻣﻦ ﺗﺒﺎدل رﺳﺎﺋﻞ إﻟﻜﺘﺮوﻧﻴﺔ
...
<Nationality>PAL33</Nationality>
Ministry D
Ministry C
Ministry B
Ministry A
...
</SOAP-ENV:Body>
ü
Xxxxxxxx
Xxxxxxxx
Renew License
Register Car aaaaa
Aaa aaa aaa a
Name:
Name: Bbbbb bbbb a bb aaa
Name: Vvvv ccc
Renew Passport
bbbbb
Aaa aaa aaa a aaaaa
Register Newbb aaa Copy
Bbbbb bbbb a born
of Birth Certificate
<Query>
<Query>
<Query>
Portal
Metadata
Payment
Server
Authentication
Server
18. Palestinian Interoperability Framework (Zinnar)
Interoperability is divided into three types:
1- Semantic Interoperability ()ﻣﺪى اﻟﺘﻮاﻓﻖ ﻋﻠﻰ اﳌﻔﺎﻫﻴﻢ اﳌﺘﺒﺎدﻟﺔ ودﻻﻻﺗﻬﺎ
The ability of computer systems to exchange data and have that data
properly interpreted by the receiving system in the same sense as
intended by the transmitting system.
2- Organizational Interoperability
()اﻟﻘﺪرة اﻹدارﻳﺔ واﻹﺟﺮاﺋﻴﺔ ﺑﲔ اﳌﺆﺳﺴﺎت وﺗﻨﺎﻏﻤﻬﺎ ﻹﳒﺎز ﺧﺪﻣﺔ ﻣﺸﺘﺮﻛﺔ
The ability of the government organisations to collaborate to achieve
their mutually agreed goals. In practice, organisational interoperability
is established through the integration of business processes and the
related exchange of information. (read more)
3- Technical Interoperability
()ﻣﺪى اﻟﺘﻮاﻓﻖ اﻟﻔﻨﻲ واﻟﺘﻘﻨﻲ ﺑﲔ اﻷﻧﻈﻤﺔ
The ability of organisation’s systems to communicate and exchange
data messages
19. Zinnar – The Palestinian Interoperability Framework
20. Palestinian Interoperability Framework (Zinnar)
http//:zinnar.pna.ps
Technical Interoperability
e-Government Service Bus
(Service-Oriented Architecture )
Tech Standards
SOAP, WSDL, UTF-8…
Semantic & Organizational Interoperability are (realized in five servers)
ﺳﺠﻞ
اﻟﻌﻨﺎوﻳﻦ
اﻷﻧﻄﻮﻟﻮﺟﻴﺎ
ﺳﺠﻞ ﻗﻮاﻋﺪ اﻟﺒﻴﺎﻧﺎت
Government
Ontology
Database of
Databases
Entity
ﺳﺠﻞ
Server اﻟﻜﻴﻨﻮﻧﺎت
Classification codes
Entity mappings
Metadata about
all state DBs
CommitTo
Address GIS-enabled
Addresses
Server
ﺳﺠﻞ
اﳋﺪﻣﺎت
Service
Business Processes,
Repository AsIs-ToBe, WSDL, UDDI
21. How to use the Ontology?
The (naming, meaning, data structure)
in all exchanged messages commit to
the Ontology
Ministry D
Ministry C
Ministry B
Health
Interior
Transport
Ontology
Message1
Message2
Message3
Ministry A
Xxxxxxxx
Xxxxxxxx
Renew License
Register Car aaaaa
Aaa aaa aaa a
Name:
Name: Bbbbb
Message4
Portal
Metadata
Payment
Server
bbbb a bb aaa
Name: Vvvv ccc
Renew Passport
bbbbb
Aaa aaa aaa a aaaaa
Register Newbb aaa Copy
Bbbbb bbbb a born
of Birth Certificate
22. Government Ontology: Why do we need it?
•
Why do we really need a “Framework” to agree on the naming, meaning,
structure of the data, …?
Can’t we simply agree on all of this “ad-hoc”, without a framework or ontology?
•
B
A
C
D
F
E
Suppose
• A governmental agency A provides
a certain service to agency B.
• The developers from agency B
must understand/(agree with the
developers from agency A) on the
naming, meaning, structure of the
data, business rules, …
This must be done for all other
agencies that want to consume
certain services from A.
23. Government Ontology: Why do we need it?
•
Why do we really need a “Framework” to agree on the naming, meaning,
structure of the data, …?
Can’t we simply agree on all of this “ad-hoc”, without a framework or ontology?
•
B
A
C
D
F
E
Suppose
B is the provider of the services
…
24. Government Ontology: Why do we need it?
•
Why do we really need a “Framework” to agree on the naming, meaning,
structure of the data, …?
Can’t we simply agree on all of this “ad-hoc”, without a framework or ontology?
•
B
A
C
D
F
E
Suppose
C is the provider of the services
…
25. Government Ontology: Why do we need it?
•
Why do we really need a “Framework” to agree on the naming, meaning,
structure of the data, …?
Can’t we simply agree on all of this “ad-hoc”, without a framework or ontology?
•
B
A
C
D
F
E
§ Building the Palestinian e-Government
“ad-hoc” is not scalable.
26. Government Ontology: Why do we need it?
•
Why do we really need a “Framework” to agree on the naming, meaning,
structure of the data, …?
Can’t we simply agree on all of this “ad-hoc”, without a framework or ontology?
•
B
A
C
Ontology
D
F
E
§ Building the Palestinian e-Government
“ad-hoc” is not scalable.
§ We need a framework (Ontology), such
that:
• The WSDL of a service “commits” to
the Ontology.
• The consumer of the service refers to
the ontology to understand the
meaning, structure and business
rules pertaining to the data.
28. e-Government (Data Messages)
Transport
########
########
########
########
Interior
=====
=====
Health
Data Message
Ø Servers interoperate among each other to exchange data messages
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
implement an e-service), similar to exchanging papers between
<SOAP-ENV:Header>
...
ministries in the real world.
Such codes should be
<SOAP-ENV:Header>
<SOAP-ENV:Body> is needed allow this Interoperability between servers,
Ø A. framework
standardized between the
. .
<Person>
taking into account the (Organizational, Technical, and and the
service provider Semantics)
<PersonID>123456789</PersonID>
issues.
consumer
<FName>Rula</FName>
...
<Nationality>PAL33</Nationality>
Ministry D
Ministry C
Ministry B
Ministry A
...
</SOAP-ENV:Body>
ü
Xxxxxxxx
Xxxxxxxx
Renew License
Register Car aaaaa
Aaa aaa aaa a
Name:
Name: Bbbbb bbbb a bb aaa
Name: Vvvv ccc
Renew Passport
bbbbb
Aaa aaa aaa a aaaaa
Register Newbb aaa Copy
Bbbbb bbbb a born
of Birth Certificate
<Query>
<Query>
<Query>
Portal
Metadata
Payment
Server
Authentication
Server
(to
29. How to use the Entity Server?
Using the same entity codes when
transferring data between governmental
agencies.
Entity Server
Ministry D
Ministry C
Ministry B
Health
Interior
Transport
All entities (codes, names, and
mappings) appear in data messages
should defined in the Entity Server.
Message1
Message2
Message3
Ministry A
Xxxxxxxx
Xxxxxxxx
Renew License
Register Cara aaaaa
Aaa aaa aaa
Name:
Name: Bbbbb bbbb a bb aaa
Name: Vvvv ccc
Renew Passport
bbbbb
Aaa
aaa
aaaaa
Registeraaabbbb a bb aaa Copy
Bbbbb New born
a
of Birth Certificate
Message4
Portal
Metadata
Payment
Server
30. How to use the Entity Server?
• Governmental agencies cannot communicate without the Entity Server.
• Service providers and consumers don’t have to change their internal
databases, but when exchanging messages they have to use those
shared entities.
Entity Server
NationalityCode
NationalityName
PSE
ﻓﻠﺴﻄﻴﻨﻲ
...
Agency A
Code
Name
PAL
ﻓﻠﺴﻄﲔ
...
Agency B
...
<NationalityCode>PSE<NationalityCode/>
...
Nationality
ﻓﺎﻟﺴﻄﻴﻨﻲ
...
35. The Entity Server (Methodology)
• For each Entity, we:
– provide the classification in different formats: (Web service
(XML), xls, sql, html).
– provide Documentation that also serves as log/history document
of the Entity.
– make sure the developed standards cover tables used in
different governmental agencies.
37. The Entity Server (entity-identity mappings)
In case same entities (e.g. people) are identified differently across
organizations, exchanging data about such entities requires that their
identities are mapped to each other
For example:
(Passportnumber1, Passportnumber2) of the same person,
(IDNumber, Name-Bdate-BirthPlace) of the same person,
(A.Platnumber, B.platenumber) of the same car; or
(A.landnumber, B.landcode) of the same land.
A mapping table should be built to link different identities of the same
entity.
Such entity-identity mappings are stored in the Entity server.
39. The address server: Why do we need it?
Addressing info is not consistent across all governmental agencies
• E.g., different agencies register different names/numbers for the same
building/street/area/region.
• In addition, how to know that ‘Beit Sahour Str’ is part of ‘Beit Sahour ’, and
that ‘Beit Sahour ’ is part of ‘Bethlahem’.
Street
Street
Street
Beit Sahour St
Shepherds Field
Karkafe Street
agency A
agency B
agency C
Currently: citizens have different address cross ministries; ministries
cannot register full address; different spellings of towns and streets;
ministries cannot send official letters to citizens, etc.
Ø In order for different governmental agencies to interoperate, they must
use the same address system.
46. Service Repository
• Metadata about e-governmental services will be collected and kept in
a repository of services.
• Such metadata includes specifications of:
• Formal description of governmental services (including the ASIS and TO-BE business processes models),
• Web services (WSDL) ,
• Web service repository (UDDI).
47. Business Process modeling
• There is typically a set of services that a ministry provides to citizens,
to enterprises, and to other governmental institutions.
• Such services (called business processes) for all ministries should be
well defined (formal AS-IS and TO-BE models); or at least those
services that need to be provided.
49. .
.
.
Citizen
.
.
.
FirstName
.
.
.
CitizenProfile
Service
Commits to
Commits to
<?xml
version="1.0"
e ncoding="UTF-‐8"?>
<definitions
xmlns="http://xmlsoap.org/wsdl/">
.
.
.
<element
n ame=“Citizen“>
Maps
.
.
.
<service
name=“CitizenProfileService">.
.
.</service>
</definitions>
Implements
Business
Process
Models
Registry (1)
to
Registered
Data
FirstName, …
.
.
.
.
.
.
Provided
Services
Citizen
P rofile
Service, …
Database
of
State
Databases
Service
Specification
WSDL
Government
Ontology
Ontology-based Service Governance
50. .
.
.
Citizen
.
.
.
FirstName
.
.
.
Government ontology
describes not only the
data but also the services
(classification).
CitizenProfile
Service
Commits to
Commits to
<?xml
version="1.0"
e ncoding="UTF-‐8"?>
<definitions
xmlns="http://xmlsoap.org/wsdl/">
.
.
.
<element
n ame=“Citizen“>
Maps
.
.
.
<service
name=“CitizenProfileService">.
.
.</service>
</definitions>
Implements
Business
Process
Models
Registry (1)
to
Registered
Data
FirstName, …
.
.
.
.
.
.
Provided
Services
Citizen
P rofile
Service, …
Database
of
State
Databases
Service
Specification
WSDL
Government
Ontology
Ontology-based Service Governance
Thus, not only the data in
WSDL files are rooted and
linked with concepts in the
ontology but also the
services names (web
services) are also linked
and rooted in the ontology
In this way, as web services are sub
processes in the ASIS and TOBEs, it
implies a link between the business
process and ontology.
52. Ontology-based Service Governance
The Government Ontology can be viewed as a framework
(or a standard) that consists of the agreed-upon
vocabulary (naming), meaning, structure and business
rules pertaining to the data exchanged in e-Government
services.
54. Government Ontology – What is it?
The Government Ontology is a formal description of the
terminology (concepts and their interrelationships) that are
communicated in the Government domain.
è so that all the terminology in the web services is mapped to
(commits to) this ontology.
55. Government Ontology – How it was built?
• The Government Ontology in Palestine was built smoothly with low cost.
• Only two persons were involved, and it was delivered at a short time;
• Few meetings with some domain experts were conducted.
è The way the ontology was engineered was effective, mainly, because:
§ The ontology was modularized into several modules,
§ The notion of gloss, to also informally describe concepts,
§ The use of ORM, to model and graphically represent the ontology.
56. Government Ontology – What is it?
The Government Ontology is modularized into separate (but connected)
modules. Such modules are: Legal Person, Address, Organization, Car,
Land.
57. Government Ontology – How it was built?
The Government Ontology is modularized into separate (but connected)
modules. Such modules are: Legal Person, Address, Organization, Car,
Land.
Modules are:
1.
2.
3.
4.
Easier to reuse
Easier to build, maintain, and replace
Enable distributed development of modules
Enable the effective management and browsing
Modularization is based on (Modularity criteria):
1. Subject-oriented
2. Purpose/Task-oriented
3. Stability
59. Government Ontology (Example)
Each Module consists of three components: (1) ORM Diagram, (2)
Glossary, (3) Business Rules.
ORM Diagram
Glossary
Business Rules
60. Government Ontology (Example)
Each Module consists of three components: (1) ORM Diagram, (2)
Glossary, (3) Business Rules.
1- ORM Diagram
ORM Diagram
Glossary
Business Rules
61. Government Ontology (Example)
Each Module consists of three components: (1) ORM Diagram, (2)
Glossary, (3) Business Rules.
ORM Diagram
2- Glossary
Glossary
Business Rules
62. )Government Ontology (Example
)2( ,Each Module consists of three components: (1) ORM Diagram
.Glossary, (3) Business Rules
ORM Diagram
Glossary
3- Business Rules
ﻻ ﻳﺠﻮز ‹ﻤﻮﻋﺔ ﺗﻀﻢ أﻛﺜﺮ ﻣﻦ ﻋﺸﺮﻳﻦ ﺷﺨﺼﺎً أن ﺗﺘﻌﺎﻃﻰ ﻣﻌﺎُ أي ﻋﻤﻞ ﺑﻘﺼﺪ اﻟﺮﺑﺢ إﻻ إذا ﺳﺠﻠﺖ ﻛﺸﺮﻛﺔ ﻣﺴﺎﻫﻤﺔ
ﻣﺤﺪودة ﲟﻘﺘﻀﻰ اﻟﻘﺎﻧﻮن.
ﻣﻘﺪار رأس اﳌﺎل اﻷﺳﻬﻤﻲ ﻳﻜﻮن ﺑﺎﻟﻌﻤﻠﺔ اﻷردﻧﻴﺔ، وﻳﻘﺴﻢ إﻟﻰ أﺳﻬﻢ ﻣﺘﺴﺎوﻳﺔ اﻟﻘﻴﻤﺔ وﻻ ﺗﻘﻞ ﻗﻴﻤﺔ اﻟﺴﻬﻢ اﻻﺳﻤﻴﺔ ﻋﻦ
دﻳﻨﺎر واﺣﺪ وﻻ ﺗﺰﻳﺪ ﻋﻠﻰ ﻋﺸﺮة دﻧﺎﻧﻴﺮ.
Business Rules
