A Next Wave of Challenges in the Junction of Information Management (esp. Integration) and the Web Yannis Papakonstantinou Associate Prof., CSE, UCSD

Involvement with Enterprise Information Integration Enosys Software in 2000 –Enosys = greek for “union, merge, fusion” Enterprise Information Integration product –XML virtual view –Thanks to great fundamental discoveries of IDM field Product also sold under BEA’s Liquid Data brand since 2002 –Acquired by BEA in 2003 As conventional EII is under way we may want: –A myriad communities of myriads of sources –And easy to build corresponding portals

Information + Service Source Local (XML) View + Methods (Web )Client Application Mediator Integrated (XML) Global Schema/Ontology + Services Wrapper Information + Service Source Wrapper Local (XML) View + Methods Architecture for Unified Access to Data & Services Cache & Replication

Integration by whom and how? Current EII’s status: Small Domain, Vertical Partition, Primarily Application-Driven, Propeler-head saves the day by elaborately mapping each source into global schema Sales Marketing Service Integrated Global View Schema V(M, S, E) Mediator (run time) View Builder (design time) SchemasData Application developer Local View MLocal View S Local View E Well under-way: years of research, startups, moving well into mainstream (BEA Liquid Data, IBM DB2, …) GAV View V

Approaches towards View-Based Data Integration Local As View (LAV) Global As View (GAV) GAV + LAV Integration Specification Method Info model & Query Language Relational (SQL) XML (XQuery) Object-Oriented On-Demand (virtual views) Warehousing (materialized views)

Integration by whom and how? Myriad Domains, Myriad Clients, Sources, “Moderators”, Horizontal Partition, Source Owner Participation Local XML View S 1 Client Application 1 Global Schema/Ontology G Local XML View S n Q/V: V 1 a Q/V: V m a View/Query V 1 a (G) Reg: W 1 Reg: W n View/Query V m a (G) Client Application m Integrated View Owner’s Domain Registration Builder Query/VIew Builder Source Owner

Visual Tools Matter! C:\Enosys\projects\allPONS.qpr* - Enosys Query Builder OPEN & VIEW SOURCE SCHEMAS IN XML DRAG & DROP TO CREATE TARGET XML VIEW TARGET SCHEMA (XML VIEW) AUTOMATICALLY GENERATED MAPS 1 2

C:\Enosys\projects\allPONS.qpr* - Enosys Query Builder XML RESULT XQUERY BASED ON DESIGN SPECS RUN & TEST XQUERY 3

Semi-Automation of Registering Queries and Sources The full automation of many mapping and matching problems is risky –Yet its study provides great fundamental discoveries Tools that provide guidance and semi-automate –Integration’s QBE: What types of meaningful queries can I formulate on the view using available data and services? –Integration’s Registration Tool: Does it worth it to clean up attribute X and register it? If so, give a ranked list of target global schema attributes Compare amount of data one has to absorb and time he has to spend with/without tool

Portal Building Made Easy Site Structure –WebML, Strudel Forms –QURSED

Beyond Accessing Data: High Level Specifications of the Business Logic Access to databases and information: IDM did and keep doing great work Web design tools address the look-and-feel requirements Business logic specification: We are mostly absent!