|
|
XIME-P Program
XIME-P aims to be a forum for fruitful
exchanges between the language specification authors, researchers from
the industry and academia, and user communities, around the topic of
XQuery.
XIME-P consists of 3 sessions: Standards,
Industry, and Prototype/Research/Applications. A first component of the
workshop are its high-quality selected papers, reflecting industrial and
research efforts around XQuery. To allow for lively interactions, XIME-P
devotes important time to three panels. The panels will focus
respectively on language issues; industrial support; and perspectives of
XQuery from the viewpoints of database research, user adoption, and
engineering.
XIME-P participants are particularly encouraged to come and voice out
their questions, critiques, comments and concerns along these
directions. XQuery is getting closer to completing
its first standard. This is an important milestone, comparable to the
SQL86 standard milestone, but the journey is still ahead of us. The
purpose of the XIME-P workshop is to gather researchers and
practitioners from academia and industry together leading to a deeper
understanding of what the research areas should be and what we need to
do in creation of research prototypes and products which will
enable critical applications of XQuery, to propose where we go
from here regarding the language functionality and focus on the XML data
store architectural alternatives.
The workshop has a rich program including two invited speakers,
7 accepted papers, 6 posters, 3 panels, use case studies and demos. A tentative program is
attached.
KEYNOTES
June 16 (joint with WebDB) C. M. Sperberg-McQueen, World Wide Web Consortium / MIT Computer Science and Artificial Intelligence Laboratory
What does XML have to do with Immanuel Kant? What is XML? Where does it come from? Why should you care?
June 17 Michael Kay, Saxonica XQuery: how will the users react?
This talk attempts to
predict the way that users will react to XQuery, once production
implementations are available. What features will they say they like,
what complaints will they make? What will they try to use the language
for, and will they succeed? What are the ten most common mistakes likely
to be? Which will be more significant:
memory-based applications or database applications? To what extent will
the XQuery user community overlap with (or be at tribal war with) other
communities such as SQL users or XSLT users?
The predictions will be based in part on extrapolating from the XSLT
scene. Some of the frustrations experienced by new and not-so-new XSLT
users over the last five years will be shared by new and not-so-new
XQuery users over the next five years, while others will be different -
either because the languages are different, or because the users are
different, or because the problems they are trying to solve are
different.
And how will users play the market? Will they go for the freedom of the
open-source world, or cling to the apron strings of their favorite
database vendors? Will they go for the products that offer the most
features, the fastest performance, or the best standards compliance?
I can guarantee that many of my predictions will be wrong, but I hope
that they will be thought-provoking.
Biography:
Michael Kay started his career in the database field, moving from a
Ph.D. at the University of Cambridge to work as a software developer
with the UK mainframe manufacturer ICL, where over a period of 20 years
he led the design teams on a wide variety of projects including Codasyl,
relational, text, and object-oriented databases. Having risen to the
position of ICL Fellow he decided it was time to return to coding, and
set about the development of Saxon, initially as a feasibility prototype
for a specific customer bid. In quick succession he then wrote the Wrox
XSLT Programmer's Reference book, joined the XSL Working Group in W3C,
left ICL to join the Tamino team in Software AG, became editor of the
XSLT 2.0 specification, joined the XQuery working group, and added
XQuery support to Saxon's growing list of capabilities. Since early 2004
Michael has been running his own company, Saxonica Limited, which
markets a commercial version of Saxon alongside the open-source product,
and provides associated consultancy services.
PANELS
Is it worth doing XQuery research today, and why ?
Organizer: Ioana Manolescu (INRIA)
The
purpose of the panel is to discuss the involvement of researchers from
academia and industry in XQuery research work, and to discuss their
viewpoint on where these research efforts are going.
Some questions to be asked of the panelists are:
* Are (were) you involved in XQuery research ? Why ?
* Would you orient a PhD thesis starting in 2005 on an XQuery topic ?
* Quid of the parallel evolution of industrial product, freelance
implementations, W3C standards, and academia results ? Are they
converging ?
* Which XML data management aspects do you think stringently need
attention ? Are they covered by XQuery ?
Our distinguished panelists are:
* Stefano Ceri (Politecnico di Milano, Italy)
* Don Chamberlin (IBM Almaden, USA)
* Alon Halevy (U. Washington, USA)
* Zachary Ives (U. Pennsylvania, USA)
* Tamer Ozsu (U. Waterloo, Canada)
* Divesh Srivastava (AT&T, USA)
XQuery implementation challenges Organizer: Fatma Ozcan (IBM Almaden)
Some
questions to be asked of the panelists are:
* What are the features
most difficult to implement ?
* What are the query optimization challenges?
* What about indexing?
* What is the existing (early) development feedback ?
* Should feature sets of XQuery and related standards be limited? (one
thing that has dragged these standards for so long is the amount of
stuff in V1
of these standards).
* Is XQuery missing something? (tuples, nested sequences?)
Our distinguished panelists are:
* Eugene Kogan
(Microsoft)
* Kevin S Beyer (IBM)
* George Feinberg (Sleepycat)
* Muralidhar Krishnaprasad (Oracle)
* Till Westmann (BEA)
What is the future of XQuery ? Organizer: Donald Kossmann (ETH Zurich) Participants: Mary Fernandez (ATT Research), Michael Rys (Microsoft), Michael Carey (BEA), Jonathan Robie (DataDirect), Paul Pedersent (MarkLogic), Hamid Pirahesh (IBM)
GENERAL TALKS
Jim Melton, Oracle SQL and XQuery
Jayavel Shanmugasundaram, Cornell univ. XQuery and Information Retrieval
ACCEPTED PAPERS
*Lopsided Little Languages: Experience with XQuery Bard Bloom (IBM)
*XML Access Modules: Towards Physical Data Independence in XML Databases Andrei Arion (INRIA), V eronique Benzaken (LRI), Ioana Manolescu (INRIA)
*Adding Updates to XQuery: Semantics, Optimization, and Static Analysis
Michael Benedikt (Bell Labs), Angela Bonifati (Icar CNR), Sergio Flesca
(University of Calabria), Avinash Vyas (Bell Labs)
*GalaTex: A Conformant Implementation of the XQuery Full-Text Language
Emiran Curtmola(UCSD), Sihem Amer-Yahia (AT&T Labs Research), Philip Brown (AT&T), Mary Fernandez (ATT)
*Purely Relational FLWORs Torsten Grust (Clausthal University of Technology)
*Updating the Pre/Post Plane in MonetDB/XQuery Peter Boncz (CWI Amsterdam), Stefan Manegold (CWI), Jan Rittinger (University of Konstanz)
*Building a Scalable Native XML Database Engine on Infrastructure for a Relational Database Guogen Zhang (IBM Silicon Valley Lab)
*Adaptive XML Storage or The Importance of Being Lazy Cristian Duda (ETH Zurich), Donald Kossmann (ETH Zurich)
*XPath 2.0: It Can Sort! Pavel Hlousek (Charles University)
*NaXDB - Realizing Pipelined XQuery Processing in a Native XML Database
System Jens HŸndling (University of Potsdam), Jan Sievers (University of
Potsdam), Mathias Weske (University of Potsdam)
*
Deep Set Operators for XQuery Bo Luo (School of Information Sciences and Technology), Dongwon Lee (The Pennsylvania State University), Wang-Chien Lee (The Pennsylvania State
University), Peng Liu (The Pennsylvania State University)
*Combining a Publish and Subscribe Collaboration Architecture with XQuery Approaches
M. Brian Blake (Georgetown University), David Fado (SAIC), Gregory Mack
(SAIC)
*Trading Precision for Throughput in XPath Processing Engie BASHIR (American University of Beirut), Jihad BOULOS (American
University of Beirut)
JUNE 16, 2005
XIME-P registration
|