OWL Use Cases: Collection Management

Use Case 2: "EDS Corporate Web Page Landfill"

Status: Revised document post face-to-face meeting of Jan 14-15

Version: January 28, 2002


Michael K. Smith, Electronic Data System (EDS), michael.smith@eds.com


Guus Schreiber, IBROW / University of Amsterdam, schreiber@swi.psy.uva.nl


Use Case 2: "EDS Web Page Landfill"


Support for corporate communication and corporate memory.


Organizing a massive web page land-fill into hierarchical categories.

Example domain

Press releases, product offerings and case studies, corporate procedures, internal product briefings and comparisons, white papers, and offering process descriptions.

Typical users

Ontology samples

Below is an outline of a portion of the EDS internal web site primarily devoted to sales support. It includes descriptions of offerings, proposal preparation and review procedures, templates for client facing and internal documents, and data sources convering clients and industries.
Internal Resources
  What we sell
    Sales help
      Sales practices
	Technical review of proposals
      Virtual Support Center
	Proposal Warehouse
	  Numerous proposals by name, client and client industry.
      Client Information Repository
	Client Detail

There are multiple places to find information about how we do things, work we have performed and about the clients we have performed it for. Keyword search is sometimes adequate. But when it is not, this single taxonomy can be difficult to navigate to the most useful document.

It is important to note that numerous large ontologies are being constructed today for use across the web. They are XML based and their semantic content is defined by shared use. The complex project plans that have been left in our repository will eventually be described using some standard, XML-based workflow vocabulary. Simple OWL assertions regarding the components of this flow would mean that a broad range of tools could reason about aspects of these plans without having to support a complete cability to interpret the workflow dialect. At a minimum , this would seem to require support of XML structures as literals. More useful would be the integration of XPATH style references into the literal space of OWL so that we could make formal descriptive statements about sub-elements of XML structures.

OWL requirements