Vue packageConception applicable sur {'class': u'package'}
<html>
<head>
<title>Advene demo - package conception</title>
<link href="http://liris.cnrs.fr/advene/nelson.css" type="text/css" rel="stylesheet" />
</head>
<body>
<h1> Work with Advene: how this package was constructed</h1>
<p>This document is a summary of the construction of the package <code>nelson.xml</code>: schema design, annotations, view design. </p>
<h2> First step: a short summary of the video </h2>
<p>We have defined a first schema, named <code><a href="Summary">Summary</a></code>, that contains two annotation types: <code><a href="PartOfSpeech">PartOfSpeech</a></code> (text/plain) and <code><a href="TalkDescription">TalkDescription</a></code> (application/x-advene-structured) with <code>speaker</code>, <code>date</code>, <code>place</code>, <code>event</code> attributes. We also defined a relation type : <code><a href="NextPart">NextPart</a></code> (text/plain)</p>
<p>We have the defined annotations: first <a href="TalkDescription_annotations">one annotation</a> of type <code><a href="TalkDescription">TalkDescription</a></code>, then <a href="PartOfSpeech_annotations">11 annotations</a> of type <code><a href="PartOfSpeech">PartOfSpeech</a></code>. 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. <a href="relations">11 relations</a> have also been defined between the annotations, the last one being linked to the first.</p>
<p>We then defined </p>
<ul>
<li>a static view named <code><a href="view_S_Summary.html">S_Summary</a></code> which presents summary informations (from the 1 + 11 annotations)</li>
<li>a dynamic view named <code>D_Summary </code>that contains 3 rules:
<ul>
<li> caption of the title of the <code>PartOfSpeech</code> </li>
<li> push the URL of the part on the URL stack </li>
<li> navigation popup with two links, one to the next part of speech,
the other to the previous part of speech, taking advantage of the nextPart relatio</li>
</ul>
</li>
</ul>
<h2> Second step: linking transcription to the video </h2>
<p> We first made a <a class="twikiLink" href="textualTranscription.html">transcription</a> of Ted Nelson speech. </p>
<p> Then we linked the transcription to the video, which means: </p>
<ul>
<li> Defining a new schema <code>DiscourseAnalysis</code>. </li>
<li> Defining a textual annotation type <code><a href="utterance">utterance</a></code>. </li>
<li> Synchronizing with the video using the import transcription GUI. The chosen granularity has the "subtitling" use in mind : short utterances, but not too short. The interested reader can download the <a href="http://liris.cnrs.fr/advene/download/Nelson-HT03/nelson-transcription-utterances.txt">transcription import work saved file</a>, and open it into the import transcription GUI (here is a <a href="/application/adhoc/transcribe?url=http://liris.cnrs.fr/advene/download/Nelson-HT03/nelson-transcription-utterances.txt"> shortcut</a>).</li>
</ul>
<p> Some views have then been defined : </p>
<ul>
<li> The obvious "utterance subtitling" dynamic view <code>D_Utterance</code> </li>
<li> The ad-hoc transcription view can be used with the <a href="utterance">utterance</a< annotation type so as to provide a classical text/video synchronisation </li>
<li> The static view <code><a href="view_S_Utterance.html">S_Utterance</a></code> displays the transcription, temporally linked with the video. </li>
</ul>
<p> Adding some relations: </p>
<ul>
<li> <code><a href="internal_reference">internal_reference</a></code> inside the discourse. </li>
<li> adding a rule to the <code>D_Utterance</code> dynamic view taking advantages of these relations by proposing to jump to it. </li>
</ul>
<p> Designing a <code><a href="view_S_part_details.html">S_part_details</a></code> view that presents the utterances temporally contained in the part of speech it is applied to. For this, </p>
<ul>
<li> a <code>containedUtterances</code> query was defined (specialization of the <code>containedAnnotations</code> query, which returns the annotations that are stricly temporally contained in it)</li>
<li> the <code>S_part_details</code> view itself loops on all the utterances annotations that are returned, and present them using the pre-defined <code><a href="view_v_enriched_link.html">v_enriched_link</a></code> annotation view. Applying it to an utterance annotation generates HTML code with a link to an annotation, that uses the annotation default view.</li>
</ul>
<h2> Third step: Linking the video to the world (wide web) </h2>
<p>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 <code>outsideWeb</code> schema. </p>
<p> We define several annotation types in this schema: </p>
<ul>
<li> <code><a href="assistant">assistant</a></code> with <code>name</code>, <code>URL</code>, <code>description</code>, <code>image</code> attributes (we use here the simple <code>application/x_advene-structured</code> annotation MIME-type where each line contains "att_name=att_value") </li>
<li> <code><a href="operatingSystem">operatingSystem</a></code> with <code>name</code>, <code>description</code>, <code>URL</code> attributes </li>
</ul>
<p> After annotating the document, we can define several views related to the <code>outsideWeb</code> schema: </p>
<ul>
<li>a dynamic view <code>D_assistantsLoop</code> that plays in loop the excerpt of the speech dedicated to assistants (<code>PartOfSpeech</code> annotation with id <a href="a3">a3</a>)
<li> a static view <code><a href="view_assistants.html">assistants</a></code> on the fine assistants Ted Nelson talks about, and what they have become. This view is not a generic one, and is directly related to the very video. It uses the <code>D_assistantsLoop</code> to play the corresponding sequences.</li>
<li> a dynamic view <code>outsideURLs</code> that uses the URL stack to propose links about the concepts at hand </li>
<li> a dynamic view <code>stopAndBrowse</code> that automatically loads the browser with interesting URL, and pauses the player at the end of the annotation. The <code>BulgariaSpecial</code> rule uses an utterance annotation. </li>
</ul>
<p> A <code><a href="People">People</a></code> annotation type is added to the <code><a href="Summary">Summary</a></code> schema. Keynote speakers appareances in the film are annotated using this annotation type (with two attributes <code>name</code> and <code>URL</code>). The <code>People</code> dynamic view captions the name of the speaker, and proposes web links to personal homepages in the URL stack.</p>
<h2> Fourth step: virtual montage </h2>
<p> A <code>D_abstract</code> dynamic view has been defined, that consists in designing a fragment trail using the <code>utterance</code> annotation, designing several rules for jumping over non needed parts of the video. We could have done it differently, designing for instance a <code>summaryCuttingRelation</code> in the <code>speech</code> schema, setting up relations between utterances annotations, and designing a <code>summaryCutting</code> dynamic view that uses the relations to automatically jump in the video. Feel free to experiment with this (better) approach.</p>
<p>At the end, the <code>D_Summary</code> view is loaded and the reader is warned of it using an information popup. </p>
<p>The <code>D_laughTour</code> view jumps from on laugh annotation to the following. It uses the <code>followingSameType</code> query. </p>
<h2>Fifth step</h2>
<p>Designing the general form of the demonstration and the explanations (much more like classical website design)</p>
<ul>
<li>the <code><a href="view_index.html">index</a></code> static view, that presents the package, gives some explanations about views, presents all the views in the package, and gives access to other views. This view was set as default static view for the package (no default dynamic view was set, though it is possible)</li>
<li>the <code><a href="view_packageConstruction">packageConstruction</a></code> and the <code><a href="view_textualTranscription.html">textualTranscription</a></code> static view </li>
<li>the <code><a href="view_doItYourself.html">doItYourself</a></code> view </li>
</ul>
<p>Adding hyperlinks between views.</p>
<h2>And now?</h2>
<p>You can modify this package. The <a href="doItYourself.html">doItYourself</a> view aims at giving you some directions.</p>
<p>You can also <a href="index.html">go back</a> to the main index view.</p>
</body>
</html>