Presentation is loading. Please wait.

Presentation is loading. Please wait.

WebScripter Status Briefing University of Southern California Information Sciences Institute Pedro Szekely, Robert Neches Martin Frank, Juan Lopez, Baoshi.

Similar presentations


Presentation on theme: "WebScripter Status Briefing University of Southern California Information Sciences Institute Pedro Szekely, Robert Neches Martin Frank, Juan Lopez, Baoshi."— Presentation transcript:

1 WebScripter Status Briefing University of Southern California Information Sciences Institute Pedro Szekely, Robert Neches Martin Frank, Juan Lopez, Baoshi Yan 13 February 2002

2 Executive Overview n WebScripter is a report/portal generator which is easy-to-use and scalable to present large DAML data sets. n Special benefit of approach is that aligning multiple source ontologies is an effortless side effect of populating a report. n Next issue: not enough DAML content out there, need much more (but theres lots of legacy materials without mark-up). n Next step: extend WebScripter to support collaborative DAML production – both creation of new DAML and mark-up of existing materials – as a similarly low-effort side effect of report creation.

3 WebScripter Accomplishments: Introduction n Easy-to-use interactive report/portal generator l Users lay out skeleton DAMLized presentation l Start populating by dragging sample content l DAML retrieval finishes populating, keeps it live l Product: DAMLized report, useful as-is or for driving a portal n Users implicitly align multiple ontologies l Sample content dragged in from many sources l Usage produces mapping

4 Accomplishments: Software n WebScripter 1.0 released Aug 2001 l Solid report generation from textual report definitions, for small DAML files l Alpha-quality report generation GUI n WebScripter 2.0 released Feb 2002 l 10X + faster report generation l Handles DAML input files over 10MB l Solid report generation GUI: practical for external users to create usable products 1. View and select candidate knowledge sources 2. View source ontology 3. Drag content into report

5 Accomplishments: Applications Outside Our Group SWOBIS Project tools.semanticweb.org World-wide inventory of semantic web software n Multiple versions: varying granularity, look-and-feel n Illustrates ease of use: external WebScripter 1.0 user created a number of report of their DAML data University of Vienna data vienna html Front-end to DAMLized DB: 30+ yrs. of people/project records n ~10MB DAML, ~90K RDF triples n WS helped in cleaning up DAML n Gives equiv. functionality of a DB viewer to the DAML world CAMERA Bugs List snapv1/v1/bugs.htm Distributed mgt of bug reports, programmer tasks, status n Shows power of DAML for collaboration: continuous update, anyone can contribute, everyone sees, no central maintainer n Highlights importance of ease of contributing DAML content

6 Proposed WebScripter Contribution to ONA Experiment Plans, Phase 1: Tiger Team Support n Contribution to exercise l Produce a useful app. l Enable group editing and schema development l Eliminate bottleneck of requiring single ontology n Benefits to be shown l Ease-of-use: ontology editing via visual editing by domain experts l Simple division of labor: team can split data horizontally, vertically, or overlapping l Rapid closure: work accelerated by grass roots alignment ontology Faster Development, Improved Usability for Military Users Integrated, DAMLized Portal, for Both Agents and Humans, Built by Distributed Team

7 Proposed WebScripter Contribution to ONA Experiment Plans, Phase 2: Mark-Up of Legacy Sources n Contribution to exercise l Rapid content generation l Fills need for tools for retrofitting DAML to pre- existing materials n Benefits to be shown l Low-cost: extends the grass roots development model from ontologies to content creation/mark-up l Collaborative: extends the collaborative editing paradigm to content creation and mark-up DAML in reports propagates back to source documents -- and DAMLizes them, too Rapid, low-cost DAMLization of legacy sources: Entire user community does mark-up just by doing their everyday work Plain HTML Page DAML-Wrapped HTML Page Automatic DAML Back-Propagated DAML

8 2002 Deliverables n 3.0 release May: WebScripter as Collaborative DAML Editor l Users can create a simple WebScripter report that is a DAML source itself without any external source (single class, 1 attribute per column) l Users can make assertions in several external ontologies at once by providing a value for a report hole l Users can collaboratively edit a WebScripter report, including adding new columns, without any software installation (servlet-based) n 4.0 release August: WebScripter as Legacy Source Mark-up Tool l Users can paste URLs of legacy material intro reports, this automatically creates DAML meta-data about it (used by whom when, is related to which attribute of which instance) l Users can paste fragments of dynamic Web pages into reports, leading to similar meta-data creation; can be used to construct DAML-driven portal pages for humans and machines

9 Internal Metrics External l Collaborative DAML Editing u How long does it take a group of 2 to divide their work, create two reports, and combine them into a human-usable composite report/portal? u How long does it take to make that report feed into the ONA agent correctly? l Mark-Up of Legacy Sources u How much DAML is generated about how many previously unDAMLized documents (measured in RDF triples)? u How useful is this generated mark-up in producing a new report that uses the same source documents (measured in time saved as compared to not having the auto- generated mark-up). l DAML+WebScripter vs. the world without u Claim: More people doing mark-up (DAML+WS) s Measure # of people contributing mark-up used by others vs. KB experts doing same. u Claim: More mark-up produced (DAML+WS) s Count # of documents with mark-up used by others vs. KB experts doing same. u Claim: More useful mark-up ( WS in particular ) s Compare % of mark-up actually used by anyone vs. KB experts doing same. u Claim: Less skill needed ( WS in particular ) s Compare the minimal educational level needed to produce mark-up used by others. u Claim: Less time spent doing mark-up s Measure the cumulative time explicitly spent on mark-up vs. what KB experts would have spent.

10 WebScripter Summary n Accomplishments: As-is, WebScripter is a useful and easy-to-use tool for combining data from multiple sources and for auto-alignment of the underlying ontologies. n 2002 Plans: Focus on producing more DAMLized sources with military utility, by support for browser-based collaborative editing and DAMLization of legacy sources (key idea: automatically inferring and propagating DAML from HTML fragment copy-and-paste actions). n 2002 Deliverables: May: collaborative DAML editing, August: legacy source mark-up n Proposed Metrics: collaborative editing: time to first human portal, time to first ONA-tool-readable data, DAMLization of legacy sources: quantity and re-use counts of generated DAML WebScripter reports collect information that people want; thus WebScripter mark-up creates DAML that people need.


Download ppt "WebScripter Status Briefing University of Southern California Information Sciences Institute Pedro Szekely, Robert Neches Martin Frank, Juan Lopez, Baoshi."

Similar presentations


Ads by Google