Ontology For EGov Services
Questions
- What is a service?
- Should we model everything?
Ethos
If we imagine an information space we have services in the middle as the things we want to find. Surrounding this are axis of access, or the ways we want to find these services. Defining this access axis helps to define the ontology as its the ontology that allows services to be connected into these other axis.
Axis of Access
- Who. (Who is responsible for the service, Who has deployed the service)
- What governemnt areas is it related to.
- What standards does it use.
- What Software platform(s) does it use.
- What dependencies does it haveon other services
- What documents are related to the serice (case studies, design documents, trial results)
- What funding model was used to build the service
Structuring the Axis
The axis points in a way define the set of properties that a service should have (or in topic map terms) associations to other topics. However, the axis themselves have structure.
- people could be organised into the organisation or departments that they work for.
- Government areas should / could be one or more taxonomies of concepts.
- Software platforms could again be defined as a taxonomy.
Thoughts on this
While this is very high level it still reveals several complentary axis of access that appropriately populated would provide a very useful classification of egov services that could be found by slicing and dicing through the different axis.
[[Category:Ontology][:Category:Ontology:Category:Ontology]