|CSE Home||About Us||Search||Contact Info|
Project proposals are due Monday, 4/22. Each proposal must be at most one page, and include:
Below are some projects ideas, but anything goes and you are welcome to come up with your own problem. Some of the problems below refer to a Peer Data Management project, called Piazza, while others refer to the XML Toolkit project. First a brief description of these two projects, then the project ideas.
A. Peer Data Management. Background: What can databases do for peer-to-peer? Grant proposal
A dynamic community of users wishes to exchange and share data. Think of Napster for sharing data in databases instead of sharing songs. Assume for the moment that all peers have relational data to exchange (the alternative is XML data). Some characteristics of such a system:
There is no central schema. The best one can hope for is for users, when they join, to explicitly state how their schema relates to other schemas in the community. For example, when I join the community I may have relational data with schema:
MyStamp(name, size, topic, sellPrice)
then I may wish to integrate my schema with others schemas on stamps, e.g. from http://www.usps.com/ or http://www.the-stamp-collector.com/, e.g.:
MyStamp.topic := uspsStamps.subject
MyStamp.sellPrice := the-stamp-collector.catalogValue * 1.5
B. The XML Toolkit. Background: VLDB Submission XMLTK
The toolkit defines an API for highly scalable processing of XPath exrpessions on an XML data stream. Currently it evaluates up to 1,000,000 linear XPath expressions on XML data at 5.6 MB/s. The API can be used in any applications that require efficient access to streaming XML data. In the toolkit we have used it to build some simple, but highly scalable, Unix commands for processing XML data: xsort, xtail, xagg(regate).
Grades(cid, courseName, sid, studentName, grade). You want to make this available to the peer community, but don't want to allow everyone to access the students' grades: only users who know the Student ID (sid) AND the student's name can access their grades (the assumption is that such a user can only be the student herself, hence it's OK for her to see the grades). Such access control policies can be enforced by encrypting data in a certain way. The problem here is to built tools that encrypt XML data according to certain encryption policies, and other tools that decrypt data that is accessed according to those policies.
Department of Computer Science & Engineering|
University of Washington
Seattle, WA 98195-2350
(206) 543-1695 voice, (206) 543-2969 FAX
[comments to pmork]