Finding the Story — Generating Large- Scale Document Structure in Semantics-to-Hypermedia Transformation Lloyd Rutledge CWI, Amsterdam

The Topia Project ● Principles and Goals – Topiary Hypermedia: plant once and trim – Presentation generation – User-controlled and on-demand – Automated propogation of each author change – Structure-focussed – Domain-independence and facilitated specificity Topia project partners: Telematica InstituutTechnische Universiteit Eindhoven

Document Request ala Google find existing document generate new multimedia

The Topia Demo

Document Engineering “Triangle” document search retrieval structure the engineer style the stylist content the archivist topic the user

Document Engineering History paper author read find the past 5000 years Web author choose style surf read universally applicable the past 10 years search database post/archive browse results select archive enter query the past 5 years presentation creator select/control presentation generated by the end of this talk universally applicable

user topic engineer clustering stylist style sheet archivist selectionstructurepresentationsemantics The Topia Architecture online picks

Principles ● User Control – pick expert – set options – become author ● Cross-applicability – each expert’s contribution applies to any from the others ● Show what and why – why archivist selected content for user request – why engineer put concept where it is in structure – why stylist picked each media for its concept

Archivist’s Responsibilities ● To user – reasonable (amount of) content for reasonable requests ● To engineer – enough relations between subset to derive structure ● To stylist – media for presenting concepts in different structural context ● Node-based interaction with all levels

Pinks in the Breakers along the beach by horses. Scheveningen did not... Oil on canvas 90 x 181 cm... Archival RDF Code concept text media # text property type concept type

ARIA Concept Map

User's Request Interface

Concept Property String... &ARIA;#ArtefactSK-A along the beach by horses. Scheveningen did not Selection SeRQL Result Code

Clustering for Structure original selection cluster node

recurrence sequence parent-child hierarchical nodes leaf nodes from clustering from user query form introduction and summary displays form main displays Document Structure

Proximity Principle ● Proximity Matrix – each pair of selected concepts has a proximity measure ● Matching conceptual and structural proximity – grouping, sequence and recurrance convey proximity ● Let’s not forget why – presentation should convey why structurally proximate concepts were measured as proximate

Engineer's Interface

Concept Lattices

Beyond Lattices ● Inferred properties to beef up the link metrics – we use art genre sub-class inheritence – rules provided by archivist as domain-specific ● Relational clustering – property (ie lattice) functional subset of relational – Can infer relations just like properties ● Axial (numeric) clustering – creates virtual group nodes, without RDF resource

<concept property="type" resource="&ARIA;#BroaderTerm24480"/> Structure Code

Make it Presentable

Stylist Responsibilities ● Good presentation of each concept – retrieval of good media ● Good presentation of structure – global view and local context ● Use media, layout and timing to show why – why primary content in presentation – why structure was chosen – group, sequence, (adjacency) and recurrence

One Example of Style outline (structure) main display (node) original user request default progression contextual recurrence access seen current recurrence

Media for the Stylist ● Dublin Core for Main Display Text – title, description, date, creator ● Media URI’s for Main Display ● Titles and thumbnails for outline and context ● for why – describes what type of concept a concept is – describes property types, thus relations – “Titus is the son of the painter Rembrandt” conceptproperty typeconcept typeconcept

<xsl:variable name="server" select='sesame:setServer(" <sesame:serql query=" SELECT DISTINCT desc FROM { } {desc} USING NAMESPACE topia = "/> <xsl:apply-templates select="xalan:nodeset($desc)/tableQueryResult/tuple"/> character escaping removed Media Selection XSLT

New Topia Domain: Google

New Topia Interface: Spectacle

DISC: Domain-specific Discourse

SampLe: More User Control

Topia Take-home Message ● Content/Style/Structure all separate – defined apart and interchangable – full user control from selection as such ● Structure is current challenge for generation – can be defined apart and domain-independent – facilitated user/engineer control ● Result is user-controlled on-demand hypermedia generation