http:^^www.cs.indiana.edu^hyplan^gandhim^c690.html

This data set contains WWW-pages collected from computer science departments of various universities

"markups" have majorly changed this situation, and tagged electronic
texts are becoming more and more widespread as sources of information.
  <P>
Markup languages such as SGML (Standard Generalized Markup Language)
<!WA80><A HREF="#referencessl">Goldfarb, Charles 1990</A> have been introduced
for creating structured documents, but extracting the information
based on the structures in the documents is still not a very simple
issue, and in most cases, it is ad hoc and based on primitive word
searches.
  <P>
This talk would introduce structured documents and SGML, and discuss
some of the ways of extracting information out of tagged documents. In
particular, some present directions toward this area would be
discussed, along with examples, advantages and disadvantages.
<DT> <I>Lincoln Carr: </I>Querying SGML Documents
<DD> 
The Standard Generalized Markup Language, or SGML, and the data type
definitions, or DTDs, built up from it provide the basis for storing
documents in a way that allows complex querying.  The Text Encoding
Initiative, or TEI, uses SGML to create standard DTDs for such
document types as poetry and drama.<!WA81><A HREF="#referencessl">TEI,
1994</A> Currently, TEI has encoded a large body of poetry using its
standards into the English Poetry Database, for which a simple query
engine is available.  However, since the poems are not marked up using
the fullest potential of TEI's standard, many useful, more complex
types of queries are not presently possible.
</DL>

<A NAME="ls0301">
<DT> <STRONG>March 1</STRONG>
<DL>
<DT> Logic Seminar
</DL>


<A NAME="ls0306">
<DT> <STRONG>March 6</STRONG>
<DL>
<DT> <I>Bob Penrod: </I>The Evolution of Visualization Tools for Large 
Information Spaces
<DD> 
Large information spaces present several problems for
visualization. Such spaces require tools that visualize <I>all</I> the
necessary data and facilitate comprehension of global structure. Most
traditional tools provide a simple window that displays a limited
extent of data. This is problematic because (1) not all the data is
concurrently visible, (2) navigation through the data is slow, and (3)
no attempt at providing context is made.
 <P> The <I>Perspective Wall</I> <!WA82><A HREF="#referencessl">Mackinlay,
J.D., Robertson, G.G., Card, S.K, 1991</A> attempts to handle these
problems by integrating detail and context. We will examine two
precursors to the <I>Perspective Wall</I>, "generalized fisheye views"
<!WA83><A HREF="#referencessl">Furnas, G.W., 1986</A> and the "bifocal
display" <!WA84><A HREF="#referencessl">Spence, R., Apperley, M., 1982</A>,
focusing in particular on the application of those ideas to <I>
linear</I> information spaces.

<DT> <I>Weizhen Hu: </I>Interactive Video Technology
<DD>
Ordinary video applications only allow users to access and
replay movies passively. Interactive Video technology
introduced in 
<!WA85><A HREF="#referencessl"> Yoshinobu Tonomura, et al. 1994</A>
allows users to do more operations about the
video, such as grasping the main idea of the video (fast
browsing), searching, analyzing, and editing. Three topics are
talked about here: 1. video segmentation and feature extraction;
2. Fast Browing method; 3. new video interfaces.
</DL>

<A NAME="ls0308">
<DT> <STRONG>March 8</STRONG>
<DL>
<DT> <I>Torrin Sanders: </I>Hypermedia Product Evaluation
<DD> ???
<DT><I>Xingchun Zheng: </I>An Intelligent Multimedia System
<DD>
Hypermedia provides poeple with a new way to combine different media into 
single artefacts.  These can be developed and marketed in the style of 
conventional media publications.  Multimedia technologies not only being the 
presentation of data stored as images, sound and video but also allow the 
incorporation of media specific input modes(eg. natural language, speech, 
pen gesture), and the generation of images, sound and video from more 
abstract formats. <P>
In <I>Using an Intelligent Agent to Mediate Multibase Information Access </I>
<!WA86><a href="http://web/inf/rl/ac/uk/people/mdw/42.ps">W Behrendt, E Hutchinson, 
KG Jeffrey, CA Macnee, MD Wilson (1993)</a>, the MIPS Project 
<!WA87><a href="http://www.cee.hw.ac.uk/Database/mips/mips.html"> (multimedia 
presentation system)</a> is introduced in the paper as  a presentation of  
an open pre-authored hypermedia network stored in the HyTime standard 
format with  dynamically created web nodes containing answers to conventional 
database queries. This illustrates how conventional hypermedia tools can be 
extended to include intelligent automatic generation of multimedia 
presentations from retrieved data. An example multimodel system(MMI2) is 
described to illustrate the technologies which could be brought to the 
market independently. <p>

The above concepts and ideas are still in the research stage.
</DL>

<A NAME="ls0320">
<DT> <STRONG>March 20</STRONG>
<DL>
<DT> 
<I>Qizhen Zhang: </I>Video-on-Demand and Database Related Issues: An
Introduction 
<DD> 
Video-on-demand features a new form of information delivery that is
causing a great commotion in the industries of cable TV,
telecommunications, personal computers, and software.  In this
revolution, multimedia database design and management play an
indispesable role.  This talk briefly describes the architecture, the
technology, and the experimental implementations of this emerging
application.  By means of the description, potential database issues
are explored.  As an example, I am going to discuss <!WA88><A
HREF="#referencessl">Network Support for Dynamically Scaled Multimedia
Data Streams</A> in some depth.

<DT> <I>Robert Fahey </I>Video Object Servers and Video On-Demand
<DD>
Recently, video on-demand has received quite a bit of attention in the
media.  However, the media rarely discuss how it will be implemented.
In this talk, I shall examine the requirements needed to support
real-time video, and how current technology meets these requirements.
I will also describe several approaches to providing on-demand video.
Some issues which will be investigated are: throughput requirements for
video, throughput and seektime for several secondary storage devices,
optimization/organization techniques to improve throughput/response time,
and several types of architectures to support video objects.
<P>
This presentation is based on five different papers, ranging from continuous
media storage to the cost effectiveness of Video On-Demand systems.  These
papers are: <!WA89><A HREF="#referencessl">Lougher, P. and Shepherd, D. 1993</A>, 
<!WA90><A HREF="#referencessl">Rangan, P. and Vin, H. 1993</A>,
<!WA91><A HREF="#referencessl">Federighi, C. and Rowe, L. 1994</A>,
<!WA92><A HREF="#referencessl">Ghandeharizadeh, S. and Ramos, L. 1993</A>, and
<!WA93><A HREF="#referencessl">Doganata, Y. and Tantawi, A. 1994.</A>.

</DL>

<A NAME="ls0322">
<DT> <STRONG>March 22</STRONG>
<DL>
<DT> <I>Kaushik Mody:</I> An Introduction to ATM - Asynchronous Transfer Mode
<DD>

Computer networks have revolutionized the way we communicate and
interact the data around the world. However with Distributed
Multimedia becoming norms rather than exception, the existing networks
are not able to support the high bandwidth and low latency
requirements of its applications. Asynchronous Transfer Mode, a
switching and multiplexing technique is described as a technology that
will allow total flexibility and efficiency to be achieved in
tomorrow's high speed, multi-service, multimedia networks.  This
presentation is based on the work by <!WA94><a href="#referencessl"> Ronald
J. Vetter; David H. C. Du 1995</a> and <!WA95><a
href="#referencessl">B. G. Kim and P. Wang 1995</a>.

<DT> <I>Alan Keahey:</I> Multi-Resolution Information Display
<DD> 
This talk will take a look at some techniques for displaying
information at more than one level of resolution
simulataneously. While similar in scope to the recent talk given by
Bob Penrod, the focus will be more on the details of hyperbolic or
fisheye views, implementation issues, and possibilities for future
systems such as multi-focus systems.

</DL>

<A NAME="ls0327">
<DT> <STRONG>March 27</STRONG>
<DL>
<DT> <I>Yong Jiang: </I>Matadata in Video Databases
<DD> 
Video is composed of audio-visual information. Providing content based 
access to video data is essential for the sucessful integration of video 
into computers. Organizing video for content based access requires the use 
of video matadata. This papter explores the nature of video matadata. A data 
model for video databases is presented based on a study of the applilcations 
of video, the nature of video retrieval requests, and the features of video. 
The data model is used in the architectural framework of a video database. 
The current state of technology in video databases is summarized and research 
issues are highlighted.

<DT> <I>Aditya Khosla: </I>Towards an optimal operating system for multimedia
<DD> 
My talk will be based on a survey paper that addresses key issues that an operating system
needs to possess in order to efficiently handle multimedia systems. The aspects that
I will discuss include <B>Process Management</B> and related scheduling strategies. I will
further talk about <B>Resource Management</B> , <B>File Management</B> and <B>Memory
Management</B> issues in this context, with  alternative algorithms
examined, and the options that best suit such systems.
</DL>

<A NAME="ls0329">
<DT> <STRONG>March 29</STRONG>
<DL>
<DT> <I>Chia-Lin Chou: </I>???
<DD> 
<DT> <I>Julia Dymshitz: </I> Approaches to database interface design
<DD> Approaches to human-computer interaction (HCI) can be broadly
classified into four categories:empirical, predictive modelling,
cognitive and anthropomorphic <!WA96><A HREF="#referencessl">Eberts,
R.E. 1994</A>.  Each of these approaches emphasizes a different aspect
of HCI, although many research studies fall into more than one
category.<P> Cognitive and anthropomorphic approaches were applied
extensively to database interface design, producing a number of design
guidelines.  The usefulness of these guidelines for actual design will
be discussed in the context of advantages and disadvantages of each
approach. In addition, two articles (<!WA97><A HREF="#referencessl">Williams,
M.D. 1984</A> and <!WA98><A HREF="#referencessl">Eberts, R.E. and Bittianda,
K.P. 1993</A>) will be described in greater detail to illustrate the
application of cognitive and anthropomorphic methods to database
interface issues.
</DL>

<A NAME="ls0405">
<DT> <STRONG>April 5</STRONG>
<DL>
<DT> <I>Arijit Sengupta</I>
<DT> <I>Lincoln Carr</I>
</DL>

<A NAME="ls0410">
<DT> <STRONG>April 10</STRONG>
<DL>
<DT> <I>Aditya Khosla</I>
<DT> <I>Yong Jiang</I>
</DL>

<A NAME="ls0412">
<DT> <STRONG>April 12</STRONG>
<DL>
<DT> <I>Bob Penrod</I>
<DT> <I>XingChun Zheng</I>
</DL>

<A NAME="ls0417">
<DT> <STRONG>April 17</STRONG>
<DL>
<DT> <I>Weizhen Hu</I>
<DT> <I>Torrin Sanders</I>
</DL>

<A NAME="ls0419">
<DT> <STRONG>April 19</STRONG>
<DL>
<DT> <I>Kaushik Mody</I>
<DT> <I>Alan Keahey</I>
</DL>

<A NAME="ls0424">
<DT> <STRONG>April 24</STRONG>
<DL>
<DT> <I>Julia Dymshitz</I>
<DT> <I>Chia-Lin Chou</I>
</DL>

<A NAME="ls0426">
<DT> <STRONG>April 26</STRONG>
<DL>
<DT> <I>Bob Fahey</I>
<DT> <I>Qizhen Zhang</I>
</DL>

</DL>


<HR>
<A NAME="pschedule">
<H3 ALIGN=CENTER>Project schedule (overview)
<BR><!WA99><A NAME=1 HREF="#toc">(TOC)</A>
</H3>
</A>

<DL>
<DT> <STRONG>Week 2: Selection</STRONG>
<DD> Select a project.

<DT> <STRONG>Week 4: Proposal</STRONG>
<DD> Propose the goals for the project

<DT> <STRONG>Week 6: Iteration 1</STRONG>
<DD> Write a user manual, implement critical elements

<DT> <STRONG>Week 8: Iteration 2</STRONG>
<DD> Refine user manual, implement significant elements

<DT> <STRONG>Week 10: Iteration 3</STRONG>
<DD> Implement almost all elements, measure performance

<DT> <STRONG>Week 12: Iteration 4</STRONG>
<DD> Restructure (if necessary) and complete the implementation.

<DT> <STRONG>Week 14: Integration </STRONG>
<DD> Integrate system

<DT> <STRONG>Week 16: Delivery </STRONG>
<DD> Deliver system and user manual
</DL>

<HR>
<A NAME="projecthomes">
<H3 ALIGN=CENTER>Project home pages
<BR><!WA100><A NAME=1 HREF="#toc">(TOC)</A>
</H3>

<UL>
<LI> 
<!WA101><A
HREF="http://www.cs.indiana.edu/hyplan/torsande/MMDbasestuff/c690homepage.html"
>
Kiosk Enhancements</A>
<LI> 
<!WA102><A HREF="http://www.cs.indiana.edu/hyplan/tkeahey/mmdb.html">
MovieSpace</A>
<LI> 
<!WA103><A HREF="http://www.cs.indiana.edu/hyplan/xczheng/moviewall.html">
MovieWall</A> 
<LI> 
<!WA104><A HREF="http://www.cs.indiana.edu/hyplan/faheyr/c690.html">
PerformanceTrack</A> 
<LI> 
<!WA105><A HREF="http://www.cs.indiana.edu/hyplan/asengupt/mmdb/texttrack.html">
TextTrack</A> 
<LI> 
<!WA106><A HREF="http://www.cs.indiana.edu/hyplan/chichou/TDBM/TDBMS.html">
Track Database Management System (TDBMS)</A>
</UL>

If you are new to HTML, you may want to look at 
<!WA107><A HREF="http://www.cs.indiana.edu/hyplan/gandhim/authoring.html">
A Guide to Authoring HTML Documents</A>.

<HR>
<A NAME="deliverables">
<H3 ALIGN=CENTER>Project deliverables
<BR><!WA108><A NAME=1 HREF="#toc">(TOC)</A>
</H3>
</A>

<DL>
<DT> <STRONG>February 1</STRONG>
<DD> <I>Brief proposal</I>

<DT> <STRONG>February 15</STRONG>
<DD> 
<DL>
<DT> <I>User manual</I>
<DD> The user manual will serve two purposes.  First, it will
serve as a guide for the user using your system.  Second, it will
serve as a precise specification of your project.  The manual should
have the following sections which answer the indicated questions

<DL>

<DT> <KBD>System overview</KBD>
<DD> What does your system do? What does the user gain by using your
system?

<DT> <KBD>Audience</KBD>
<DD> Who are the users of your system? Why should the person reading your
manual read any further?

<DT> <KBD>Graphical user interface</KBD> (for systems with a graphical
interface) 
<DD> What are the different areas on the interface? What elements
exist in each area? How is each element manipulated and how does the
system respond to each manipulation?  What functionalities is the user
interface capable of performing?  How does the user interact with the
interface to achieve each of these functionalities?

<DT> <KBD>Programming interface</KBD> (for systems with a programming
interface) 
<DD> What functions are available?  What do they do?  What parameters
do they take? What is the effect of each parameter? What values are
returned? 
</DL> 

<DT> <I>Implementation: Iteration 1</I>
 <DD> First, identify a set of capabilities to be implemented in this
iteration.  Second, ensure that your supervisor agrees with you on the
capabilities by February 8. Finally, implement the functionality by
the due date. <BR> 
Here are some criterion which may be used in choosing the capabilities
for implementation in iteration 1:
<UL>
<LI> they must be implementable by the due date,
<LI> they should constitute a significant element of your system.  
<LI> they should attack the high risk elements of your system.
</UL>
</DL>
<DT> <STRONG>March 19</STRONG>
<DD> 
<DL>
<DT> <I>User manual</I>
<DD> Complete your user manual to follow the guidelines above.
<DT> <I>Implementation: Iteration II</I>
<DD> Implement <I>more than half</I> of the required functionality.
</DL>
<DT> <STRONG>April 2</STRONG>
<DD> 
<DL>
<DT> <I>Design document</I>
<DD> Prepare your design document
<DT> <I>Implementation: Iteration III</I>
<DD> Implement <I>almost all</I> of the desired functionality.
</DL>
<DT> <STRONG>April 26</STRONG>
<DD> 
<DL>
<DT> <I>Handin</I>
<DD> Handin your user manual, design document, and implementation.
</DL>
</DL>

<HR>
<A NAME="tools"><H3 ALIGN=CENTER>Development tools
<BR><!WA109><A NAME=1 HREF="#toc">(TOC)</A>
</H3>
</A>

Here are some starting points for each of the development tools that
will be used in the projects.

<DL>
<DT> 
<STRONG>Digital Media Libraries</STRONG>
<DD> 

The IRIS Media Libraries provide a digital media software development
environment that includes audio, video, movie and compression
libraries. Check out the <I>IRIS Digital Media Programming Guide</I>