Use Cases

From W3C eGovernment Wiki
Revision as of 08:25, 21 April 2009 by Josema (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Use Case Index

under discussion: please see http://lists.w3.org/Archives/Public/public-egov-ig/2008Oct/0034

see also in StratML format: http://xml.gov/stratml/crane/WEIGUCF.xml

Use Case Framework

The aim is for everyone in the working group to pick and write up a use case in one of the areas in the framework - for review at the face to face. Some areas are more important than others, for example delivering public services using the web, so would potentially bear more than one draft use case.

Use Cases could be divided into the “provide, engage, enable” modalities for government on the Web

  • Provide: public services on the web, either transactional or information services
  • Engage: with citizens and businesses, on government terms or on the citizens terms
  • Enable: public sector information re-use

These roughly approximate to the task force areas of interest: Usage of Web Standards, Transparency and Participation, Seamless Integration of Data. The related task force areas are given for each candidate use case. These necessarily overlap, but ideally each use case should focus primarily on one task force area of interest.

Topic Areas

From F2F discussion: http://www.w3.org/2008/10/24-egov-minutes#topics

Candidate Use Cases

This is a draft index for the Use cases identified. Use cases should be written in the standard Use Case Template.

To add a use case in this section, please add a page and link it from the list below.

Provide: Using the web to deliver public services

  1. Transactional services (simple), involving communication between citizen and one agency of government e.g. completing a tax return.
    Relates to task force areas: Usage of Web Standards (e.g. Mobile, Accessibility, Security)
  2. Transactional services (complex), involving back office integration by three or more agencies (public or private), e.g. renewing vehicle tax disc, involving data sharing between government, insurance companies and garages.
    Relates to task force areas: Seamless Integration of Data, Usage of Web Standards (e.g. Policy – especially privacy and consent, Accessibility, Security, Semantic Web).
  3. Information services (simple), involving the provision of basic information to the citizen in ways they can more easily interpret, e.g. interactive crime maps (as opposed to presenting tables of figures), or exposing data directly to the public. Open Government: Linked Open Data, A Use Case in Transparency and Participation (by Rick Murphy)
    Relates to task force areas: Usage of Web Standards, Transparency and Participation
  4. Information services (complex), providing a persistent, 'citable', authoritative source of information, e.g. legislation on the web, or long term availability of web only official publications. Formal Specification of the U.S. Privacy Act of 1974 in OWL-DL, A Use Case in Transparency and Participation (by Rick Murphy)
    Relates to task force areas: Usage of Web Standards (e.g. Web Architecture), Transparency and Participation
  5. Plain language (by Rachel)
    How to match the language the government use with that the citizens use. See related SWEO use case (by Jose)

Engage: Using the web to interact with citizens and businesses

  1. Government to citizen – e.g. blogs by ministers and officials, or, publishing consultation documents as wikis or with a “comment on this” facilities.
    Relates to task force area: Transparency and Participation
  2. Intervening in citizen to citizen dialogues – e.g. interacting with (non government / 3rd sector) online communities e.g. providing advice and support to parents via an online parents forum.
    Relates to task force area: Transparency and Participation
  3. Of paramount importante here are Trust issues, where identification and authentication mechanisms are usually involved. The Identification and Authentication Use Case provides an overview on this topic.
    Relates to task force areas: Usage of Web Standards.

Enable: Using the web as a platform to deliver data for re-use

  1. Structuring data using standards (e.g. setting out strategic objectives in XML – StratML Use Case, or extending information sharing capabilities U.S. Federal Information Sharing with Shared Concepts Using the Federal Enterprise Architecture Reference Model Ontology (FEA-RMO) in OWL-DL, A Use Case in Seamless Integration of Data (by Rick Murphy))
    Relates to task force areas: Seamless Integration of Data, Transparency and Participation
  2. Making structured data re-usable (e.g. building an API)
    Relates to task force areas: Web Standards (Web Services), Seamless Integration of Data
  3. Making semi-structured data re-usable (e.g. Your Website is your API, publishing statutory notices or job advertisements using RDFa and/or GRDDL)
    Relates to task force areas: Web Standards (Semantic Web), Seamless Integration of Data
  4. Licensing the re-use of government data (e.g. rights expression and indication of third party rights)
    Relates to task force areas: Web Standards (Policy, Semantic Web), Seamless Integration of Data
  5. Specifying a data reference model (DRM) to enable achievement of this objective
  6. Data sharing policy expression

Pending Cases

These potential use cases have shown up during next calls and mails and need to be discussed and added to the categories above

  1. Enhancing citizens search. "Semantic MyPage" - automatic legal assistance for citizens (by Kjetil Helberg (kjetil@helberg.no) and Steinar Skagemo (sskagemo@gmail.com))
  2. Search across government organizations and levels (by Martin)
    There is a research going on in the netherlands, on the search engine for citizens to browse through all different government organisations, aiming to provide the correct information.
  3. Trust/provenance (all)
  4. U.S. federal Web Content Managers strategic plan (by Owen)
    http://xml.gov/stratml/WCMstratplan.xml
    could it bring a set of use cases??
  5. U.S. federal CIO Council's strategic plan (by Owen)
    http://xml.gov/stratml/CIOCstratplan.xml
    four success stories there. See May 5, 2008 update, including reference to Government 2.0
  6. List of W3C and OASIS recommendations not in FEA TRM (by Owen)
    http://lists.w3.org/Archives/Public/public-egov-ig/2008Oct/0010
  7. SIOC (Semantically Interlinked On-line Communities) (by Vassilios)
    SIOC is an attempt to create a simple ontology for linking the blog sphere and web-based discussions. Recently adopted by Yahoo [1].
    May fit to “Transparency and Participation” and more specifically to Engage: Using the web to interact with citizens and businesses, 1. Government to citizen - e.g. blogs by ministers and officials, or, publishing consultation documents as wikis or with a "comment on this" facilities.
  8. Common Service Model (also .doc) (by Vassilios)
    Past communication http://lists.w3.org/Archives/Public/public-egov-ig/2008Nov/0002
    The approach is similar to SIOC: a simple and easy to be used ontology which could give unifying semantics (annotations) to service descriptions based on different perspectives by service providers. We already have an RDFa based prototype on this that uses an (eGov) extension of SA-REST as the annotation vocabulary.
    This could fit to both Provide: Using the web to deliver public services and Enable: Using the web as a platform to deliver data for re-use