Testing W6 XOW Motivation simple Knowledge acquisition problem Slow adoption Relatively complex conceptually Wide domain coverage Complex implementation (limited application) simple e.g. OPML, XML-based structured data Easy implementation Rapid adoption Simple conceptually Narrow domain coverage Simple implementation (limited application) XHTML etc XHTML Outlines Where? Right here! Simple Hierarchical Structures Simple Conceptually Familiar view Convenient viewer (browser) Easy to author in XHTML Easy to style using CSS Easy to make dynamic using Javascript XSLT allows format alchemy W6 W6 http://purl.org/ibis/w6 W6 OWL Ontology W6 Facets Who? ==> Agent What? ==> Object Why? ==> Cause When? ==> Time Where? ==> Location How? ==> Process Simple Conceptually Easy to express in XHTML RDF RDF from XOW Loops OK (URIs in link elements) bnodes OK? - maybe W6 with other vocabs W6 and Friends W6 and inference --think we know the type of the thing at the end of the property facets - Indian whatsisname W6 Facets w6:who rdfs:range w6:Agent w6:what rdfs:range w6:Object w6:why rdfs:range w6:Cause w6:when rdfs:range w6:Time w6:where rdfs:range w6:Location w6:how rdfs:range w6:Process Querying W6 RDQL Data reuse Currently: HTML is available (XHTML) XML is available (XHTML) RDF is available (RDF/XML) Slides Bookmarks disposable languages Simple mappings : XHTML <=> RDF relatively easy to define e.g. CSS @class = rdfs:Class add new values to XHTML doc tweak the XSLT check the output! Easy enough to be domain/task-specific Future Directions Does it work? Is it useful? Need more data! Is the overall approach useful? RDF to XHTML programming API? XSLT? Snail! About blah blah W6 Facets What? Why? Where? Danny Ayers How? 2004 Simple Conceptually Easy to express in XHTML