1 / 6

Understanding User Roles ( in ontologizing the Ontolog body of knowledge)

This article explores the various user roles within the field of ontology and their goals in utilizing the Ontolog body of knowledge. It also discusses potential community building and knowledge sharing activities.

speralta
Download Presentation

Understanding User Roles ( in ontologizing the Ontolog body of knowledge)

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Understanding User Roles(in ontologizing the Ontolog body of knowledge) Lisa Dawn Colvin April 20, 2006

  2. Potential Community is Broad • Ontology practitioners are from AI to IA • A small sample of people who use the word “ontology”: Information Architects, Librarians, Logicians, Information Scientists, Application Developers, Computer Scientists, AI Researchers, Knowledge Engineers, Subject Matter Experts, Computational Linguists, Standards Developers, Metadata and Data Architects and Modelers, Business Analysts, Philosophers, Innovators, Venture Capitalists, Futurists, Taggers …

  3. Goals may be similar across groups* • Browse: Want to learn more about a particular area or become familiar with the content available • Search : Find a particular piece of Information • Fully-specified in Wiki. (Seeking a list of all participants in an Ontolog conference call on 01/02/04) • Under-specified in Wiki, but easy to see how to specify (Seeking an expert in a particular area of ontological engineering) • Under-specified in Wiki, but more difficult to specify (Seeking solutions to particular problems in ontological engineering.) • Create: Generate new knowledge based on existing knowledge • Knowledge Maps of ontological expertise within the community • Social Networking maps • Annotations of discussions and problem solving *Source: D.Bedford slides from 04.13.06

  4. Mapping Goals to Reference Sources • FIND people who participated in a discussion • Agents (people, organizations, etc.) • Agent Roles* (participant, observer, etc.) • Activities or Events (conference calls, discussions) • Time (“now”, dates, date ranges) (*Agent roles could be represented as nodes in the ontology OR as relationships between nodes OR as attributes in some other schema. No representational formalization is specified.)

  5. Reference Sources within Ontolog • Many Ontolog WikiWords and links are instances of Reference Sources • Agents (people <PeterYim>, organizations they work for <ontolog-forum>) • Agent Roles (speaker <OntologSpeaker>) • Events (conference calls <ConferenceCall_2006_04_20>) • Information Assets (presentation slides <DeniseBedford_20060413.ppt> and podcasts (<DeniseBedford_Recording.mp3>)

  6. What’s next? • Leverage tools to help build our reference model and architecture • Level of granularity and complexity of representation will depend on the user goals we are trying to meet • Challenges present in any ontology build: • Extensible representation that isn’t overly complex • Knowledge governance (preventing “semantic shift”) • Boot strapping to encourage utility

More Related