Work with Advene: how this package was constructed

This document is a summary of the construction of the package nelson.xml: schema design, annotations, view design.

First step: a short summary of the video

We have defined a first schema, named Summary, that contains two annotation types: PartOfSpeech (text/plain) and TalkDescription (application/x-advene-structured) with speaker, date, place, event attributes. We also defined a relation type : NextPart (text/plain)

We have the defined annotations: first one annotation of type TalkDescription, then 11 annotations of type PartOfSpeech. These latter cover all the video, and annotation was done using the "on the fly" annotation mode from the main Advene view, then adjusted with the timeline view time setting facilities. 11 relations have also been defined between the annotations, the last one being linked to the first.

We then defined

Second step: linking transcription to the video

We first made a transcription of Ted Nelson speech.

Then we linked the transcription to the video, which means:

Some views have then been defined :

Adding some relations:

Designing a S_part_details view that presents the utterances temporally contained in the part of speech it is applied to. For this,

Third step: Linking the video to the world (wide web)

Ted Nelson not only makes self references in his speech. He also makes references to the outside web. So as to be able to develop views and usages related to such analyses, we have defined a outsideWeb schema.

We define several annotation types in this schema:

After annotating the document, we can define several views related to the outsideWeb schema:

A People annotation type is added to the Summary schema. Keynote speakers appareances in the film are annotated using this annotation type (with two attributes name and URL). The People dynamic view captions the name of the speaker, and proposes web links to personal homepages in the URL stack.

Fourth step: virtual montage

A D_abstract dynamic view has been defined, that consists in designing a fragment trail using the utterance annotation, designing several rules for jumping over non needed parts of the video. We could have done it differently, designing for instance a summaryCuttingRelation in the speech schema, setting up relations between utterances annotations, and designing a summaryCutting dynamic view that uses the relations to automatically jump in the video. Feel free to experiment with this (better) approach.

At the end, the D_Summary view is loaded and the reader is warned of it using an information popup.

The D_laughTour view jumps from on laugh annotation to the following. It uses the followingSameType query.

Fifth step

Designing the general form of the demonstration and the explanations (much more like classical website design)

Adding hyperlinks between views.

And now?

You can modify this package. The doItYourself view aims at giving you some directions.

You can also go back to the main index view.