Tutorial semantic wikis and applications

12,003
-1

Published on

Tutorial on Semantic Wikis for SemTech 2010

Published in: Technology, Education
0 Comments
15 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
12,003
On Slideshare
0
From Embeds
0
Number of Embeds
4
Actions
Shares
0
Downloads
337
Comments
0
Likes
15
Embeds 0
No embeds

No notes for slide
  • Namemore limits* what are wikis not good at, like e.g.* implicit knowledge* “why”-questionsGive more questions* what are the research challenges?* what are good ideas for your PhD theses?why do we need semantics?what does semantic even mean here?, i.e. what kind of semantics?A more concise storyline, especially in the second halfWhat do you want to say?
  • Wikis started by adding a simple edit link to a website
  • What a semantic wiki is like
  • The same as the semantic web
  • So why does Wikipedia work, and wiki clock not?
  • How to combine these abilities?
  • Counter information overload with visualizations
  • But getting these visualizations is hard
  • Because then SMW can be used as a database where apps read from it
  • Because then SMW can be used as a database where apps read from it
  • The problem we are going to solve is “find the 0-60 times of all Porsche cars in Wikipedia”This is a sample Wikipedia page for the Porshe 996, showing its acceleration times in a performance data table.This table is manually built – all the table data exists as constants in the table.
  • This is a Wikipedia page showing 0-60 times for the Porsche Cayenne.If we have to manually go through every Porsche model to assemble the 0-60 data for each model and type, this is going to take a while.A better idea is to treat Wikipedia like a database, and simply query it. Enter Ultrapedia.
  • This is the Ultrapedia home page.
  • First notice that Ultrapedia can leverage all the data it extracts from Wikipedia to support a much more helpful UI.For example, Ultrapedia adds a manufacturer-based navigation system on the side, and show explanatory popups. These kinds of UI tweaks aren’t possible with MediaWiki now, and are an important benefit of having the semantic data.
  • Remember that we want to find the 0-60 acceleration data for all Porsche models that Wikipedia knows about.Let’s start by looking at a query generated table on the Ultrapedia Porsche 996 page. For comparison, Ultrapedia also includes the original performance table from Wikipedia (above)
  • This is Ultrapedia’sPorsche 996 performance table, built by a query to the Ultrapedia database of Wikipedia-extracted data.Notice that it has the same information that the original static table has, this is because we scrape the data from the static table.This table is dyamically generated at each page load out of the extracted Wikipedia data, so it is always up to date.It is sortable and also accepts feedback and ratings on individual data items.
  • Now we can answer our question about 0-60 times across all Porsche models with one simple query in Ultrapedia. We can make this an Ultrapedia-only page – the page itself just 5 queries on it (one for each acceleration range).We could also do this as one big table but it’s easier to read as 5 smaller tables.All the data here flows from Wikipedia.
  • Of course once you have data, Ultrapedia can support data visualizations. This is a simple Flash-based chart widget based on the same Porsche 996 data, and included in Ultrapedia’s Porsche 996 page.It shows us that while acceleration varies dramatically, top speed and peak engine power remain fairly constant across models.The chart was specified manually with a query. There are of course a huge number of possible ways to chart a set of data, and most of these ways are uninteresting.In the Ultrapedia concept, we rely on article authors to specify interesting charts for their readers that will support the particular points in the article.
  • We can also use the data to dynamically link to other data sources. In this case we have configured the Ultrapedia Porsche 996 article to include a live ebay query to find out what the Porsche 996 sells for today…We access the ebay data through a web services interface.We can do this for arbitrary other web-service-accessible data sources, like amazon or geonames.In a government or enterprise context, we would link articles to supporting data from appropriate systems of record.
  • I don’t think I’ll be buying one… I think I’d rather send my daughter to college.
  • Pictures automatically get metadata, so Ultrapedia can deliver an iPod-like “cover flow” browsing experience with images to augment the table data. We could also embed images or videos in the tables.
  • Since Ultrapedia includes some simple internal logic about time, we can generate simple browsable timelines and use them in articles.Here we see a timeline of VW models.
  • But, did you know that Uusikaupunki, Finland, is a major hub for Porsche manufacturing?Ultrapedia allows us to drill down to look at Finland’s contribution to Porsche production.
  • Suppose we notice in Ultrapedia that the city of manufacture for the BMW 8-series is not right. Wikipedia (as of our copy) just says “Germany”, so that’s also what Ultrapedia says. But in Ultrapedia we can pop up a data correction dialog, which allows us to comment on this specific piece of data. If we follow the “edit data in Wikipedia” link in the popup, Ultrapedia uses its provenance information to send us to the exact line in Wikipedia where it got the data.
  • Wikis, especially, semantic-enhanced wikis, are wonderful tools for collaboration and content management. Semantic MediaWiki Plus, with Halo and other useful extensions made it a great platform for web application development.
  • With all the semantic structures generated, it is important to empower more people with the magic of this platform. The more people use it, the better it will be.
  • With all the semantic structures generated, it is important to empower more people with the magic of this platform. The more people use it, the better it will be.
  • Microsoft Office application suite has more than 90% market share, generating billions of revenue for Microsoft. Many users are dependent on the application to get their things done, such as Excel, PowerPoint. Outlook, especially, is usually open all the time, and in fact, many people spend most of their work time a day with Outlook. So, if we can entice Microsoft Office users to use Semantic Wiki, it’ll be a great plus. 500 million users is from http://blogs.technet.com/office2010/archive/2009/10/07/new-ways-to-try-and-buy-microsoft-office-2010.aspx
  • WikiTags is here to bridge semantic wikis with more potential users, such as users of Microsoft Word, Outlook and Excel, with Microsoft SmartTag technology.
  • Let's at first take a look at some semantic wikis we have.
  • This is a bare-bone wiki for Sci-Fi movies, similar to Wikipedia except it contains extracted semantic information, shown here in the fact box.
  • Here is another semantic Wiki: a simple form-based proposal tracking application. This sample article is about building a fancy doghouse. You can see the semantic "Facts" too, the cooking ingredients for delicious presentations.
  • We also have a project management and feature documentation wiki , full of semantic templates and forms, so it is also "semanticated“, a wiki of us, for us, and by us.
  • Now, let's see how it works with Office applications.
  • WikiMail let users contribute to the wiki using their familiar tools
  • WikiMail let users contribute to the wiki using their familiar tools
  • WikiMail let users contribute to the wiki using their familiar tools
  • Now, let's see how it works with Office applications.
  • Now you see WikiTags connect multiple wikis to bring relevant info to you when you want it, in your familiar Microsoft Office applications
  • You discover rich and live semantic info, without search; you can further explore the wiki without actually going there.
  • Relevant, context sensitive, semantic actions lead to higher accuracy and productivity; moreover, the semantic action services can also be in the wiki.
  • WikiMail let users contribute to the wiki using their familiar tools
  • WikiMail let users contribute to the wiki using their familiar tools
  • Automatically uploaded and updated articles enable all team in sync with the latest info, and revision history.
  • Power users can have many settings to get the maximum power.
  • WikiTags can help wikis connecting to more people and releasing more power of semantic wikis, and it is available for free trial.
  • Because then SMW can be used as a database where apps read from it
  • Tutorial semantic wikis and applications

    1. 1. Tutorialon Semantic Wikis and Applications<br />Mark Greaves<br />Vulcan Inc.<br />markg@vulcan.com<br />Daniel Hansch<br />Ontoprise GmbH<br />hansch@ontoprise.de<br />Denny Vrandecic<br />Karlsruhe Institue of Technology<br />Denny.vrandecic@kit.edu<br />Jesse Wang<br />Vulcan Inc.<br />jessew@vulcan.com<br />
    2. 2. 2<br />Outline<br />Tutorial Introduction and Structure (Mark)<br />Introduction to Semantic MediaWiki (Denny)<br />Dive into Semantic MediaWiki (Denny)<br />Applications for Semantic Wikis (Mark)<br />Extensions for Semantic MediaWiki (Denny, Daniel, Jesse)<br />Connecting Semantic MediaWiki with MS Office (Jesse)<br />Augmenting Semantic MediaWiki with a Triple Store (Daniel)<br />Future Development (Denny, Daniel, Jesse)<br />Wrap Up and Q&A (Mark)<br />Break (30 mins)<br />
    3. 3. 3<br />Outline<br />Tutorial Introduction and Structure (Mark)<br />Introduction to Semantic MediaWiki (Denny)<br />Dive into Semantic MediaWiki (Denny)<br />Applications for Semantic Wikis (Mark)<br />Extensions for Semantic MediaWiki (Denny, Daniel, Jesse)<br />Connecting Semantic MediaWiki with MS Office (Jesse)<br />Augmenting Semantic MediaWiki with a Triple Store (Daniel)<br />Future Development (Denny, Daniel, Jesse)<br />Wrap Up and Q&A (Mark)<br />Break (30 mins)<br />
    4. 4. Context: Social Web, Semantic Web, and Semantic Wikis<br />4<br />SoftwareAgents<br />Expert Systems<br />Freebase<br />Schema Integration<br />Facebook<br />OpenGraph<br />Linked Data<br />Ontologies<br />SemanticWikis<br />Semantic <br />Desktops<br />Evri<br />Thesauri<br />Twine/T2<br />Prediction Markets<br />Increasing Data Interconnection<br />PIMs<br />Ning<br />Databases<br />FaceBook<br />SearchEngines<br />Amazon Reviews<br />Content Portals<br />Web sites<br />Wikipedia<br />File servers<br />Blogs<br />Twitter<br />Increasing Social Interconnection<br />Based on a diagram by Nova Spivak, Radar Networks<br />
    5. 5. A Range of Semantic Wiki Platforms<br />KiWi – Knowledge in a Wiki<br />Knoodl – Semantic Collaboration tool and application platform<br />Freebase - Collaborative platform for almanac data by Metaweb<br />OntoWiki<br />PhpWiki<br />Semantic MediaWiki - an extension toMediaWikithat turns it into a semantic wiki (and SMW extensions)<br />TikiWiki - CMS/Groupware integrates Semantic links as a core feature<br />Wikidsmart - adds semantics to Confluence (from zAgile)<br />5<br />5<br />
    6. 6. 6<br />Outline<br />Tutorial Introduction and Structure (Mark)<br />Introduction to Semantic MediaWiki (Denny)<br />Dive into Semantic MediaWiki (Denny)<br />Applications for Semantic Wikis (Mark)<br />Extensions for Semantic MediaWiki (Denny, Daniel, Jesse)<br />Connecting Semantic MediaWiki with MS Office (Jesse)<br />Augmenting Semantic MediaWiki with a Triple Store (Daniel)<br />Future Development (Denny, Daniel, Jesse)<br />Wrap Up and Q&A (Mark)<br />Break (30 mins)<br />
    7. 7. Semantic MediaWiki<br />Denny Vrandečić, KIT / ISI, USC<br />June 22 2010, San Francisco<br />
    8. 8. Wikis are great<br />Enable new scale of human collaboration<br />Everyone can read<br />Everyone can write<br />Everyone gets aggregated<br />Everyone is accountable for everything<br />But some things are better left to machines…<br />8<br />
    9. 9. edit<br />wow. I can change the web.<br />let’s write an encycolpedia!<br />
    10. 10.
    11. 11. Wiki Clock<br />http://pageoftext.com/wikiclock<br />
    12. 12. Wikis are great<br />Enable new scale of human collaboration<br />Everyone can read<br />Everyone can write<br />Everyone gets aggregated<br />Everyone is accountable for everything<br />But how are semantic wikis different?<br />Semantic<br />+ computer<br />v<br />12<br />
    13. 13. edit<br />edit<br />edit<br />Country<br />City<br />Population = 745,514<br />Area = 39 km2<br />capital<br />mayor<br />edit<br />edit<br />Birthdate =<br />1 April 1946<br />
    14. 14. edit<br />edit<br />edit<br />edit<br />edit<br />edit<br />May 27 1994, Tim Berners-Lee, Keynote at WWW1 <br />
    15. 15. edit<br />edit<br />
    16. 16. What humans are good at<br />What machines are good at<br />Understanding<br />“Why”<br />Tacit knowledge<br />Stories<br />Following hunches<br />Checking external refs<br />Executing<br />Facts and figures<br />Explicit knowledge<br />Keeping track and logs<br />Analyzing big style<br />Calling web services<br />
    17. 17.
    18. 18. Universal Access to<br />All Knowledge<br />
    19. 19. 19<br />What Wikipedia knows<br />Wikipedia has articles about…<br />… all cities<br />… their populations<br />… their mayors<br /> So can I ask for a list of the world’s ten largest cities with a female mayor?<br />
    20. 20. 20<br />Let’s see what happens…<br />
    21. 21. Wikipedia’s answer: lists<br />21<br />
    22. 22.
    23. 23.
    24. 24.
    25. 25.
    26. 26. 26<br />
    27. 27. 27<br />
    28. 28. 28<br />
    29. 29. 29<br />
    30. 30. 30<br />
    31. 31.
    32. 32. 32<br />
    33. 33.
    34. 34. Computers are stupid<br />34<br />
    35. 35. 35<br />What humans see<br />
    36. 36. What humans see<br />Karlsruhe<br />... has a population of 285,812<br />... is located inGermany<br />... was founded in 1715<br />... has mayor Heinz Fenrich<br />36<br />
    37. 37. What computers see<br />
    38. 38. What computers see<br />Karlsruhe<br />... 285,812<br />... Germany<br />... 1715<br />... Heinz Fenrich<br />38<br />
    39. 39. Computers don‘t make connections<br />39<br />
    40. 40. Computers need our help<br />40<br />
    41. 41. Karlsruhe<br />Karlsruhe is a city in<br />[[Germany]].<br />[[Country::Germany]].<br />Germany<br />Country<br />Karlsruhe<br />Country<br />Germany<br />Karlsruhe<br />Mayor<br />Heinz Fenrich<br />Heinz Fenrich<br />Gender<br />Male<br />41<br />
    42. 42.
    43. 43. {{#ask:<br /> [[Category:City]]<br /> [[located in::<br /> Baden-Württermberg]]<br /> | format=barchart<br /> | ?population<br />}} <br />
    44. 44. External data reuse<br />Export formats<br />RDF/XML<br />SPARQL<br />RDFa<br />CSV<br />JSON<br />iCal<br />vCard<br />Bibtex<br />44<br />
    45. 45.
    46. 46.
    47. 47. 47<br />Outline<br />Tutorial Introduction and Structure (Mark)<br />Introduction to Semantic MediaWiki (Denny)<br />Dive into Semantic MediaWiki (Denny)<br />Applications for Semantic Wikis (Mark)<br />Extensions for Semantic MediaWiki (Denny, Daniel, Jesse)<br />Connecting Semantic MediaWiki with MS Office (Jesse)<br />Augmenting Semantic MediaWiki with a Triple Store (Daniel)<br />Future Development (Denny, Daniel, Jesse)<br />Wrap Up and Q&A (Mark)<br />Break (30 mins)<br />
    48. 48. External data reuse<br />Computer understands wiki content<br />Knowledge based applications<br />A number of export formats<br />RDF/XML, SPARQL, RDFa, CSV, JSON, iCal, vCard, Bibtex, ...<br />RDF APIs in programming languages<br />Java, JavaScript, C/C++, Python, Ruby, Haskell, .Net, PHP, Common Lisp, Prolog, …<br />Standards based<br />URIs, XML, RDF, OWL, SPARQL, …<br />
    49. 49. importSemanticMediaWikias smw<br />wiki = smw.SMW("http://semanticweb.org/")<br />denny = wiki.load(“DennyVrandecic")<br />printdenny.affiliation<br />
    50. 50. Test wiki<br />Go to http://scratchpat.referata.com<br />Click on log in and then on “Create an account”<br />Suggestion: use your name as your login<br />Enter your eMail (for forgotten passwords)<br />
    51. 51. Editing the wiki<br />Go to your own page (page with your name)<br />Click on “edit”<br />Try to add or change text <br />You can cancel anytime, preview (just for you), or save the changes so that everyone can see them<br />
    52. 52. Quick overview of wiki markup<br />'''three apostrophes''' will make text bold<br />''two apostrophes''' will make text italic<br />[[Text in double square brackets]] will be links to the page named as the text in the brackets<br />[[Link target|link text]] will display a link that looks like link textbut links to link target<br />The wiki is case sensitve – but not on the first letter of a link<br />The wiki is Unicode<br />
    53. 53. Slide 53<br />Overview of semantic markup<br />To add a page P to category C type [[Category:C]] on page P<br />To make a typed link of type R from page P1 to page P2 type [[R::P2]] on page P1<br />To state the value V of an attribute A on page P type [[A::V]] on page P<br />Example: <br />
    54. 54. Data values and types<br />Attributes like [[birthdate::February 27 1978]] or [[population::3,635,389]] must know the type of the value<br />This is done by adding [[has type::T]] on the page of the attribute<br />Available, predefined types:<br />Telephone number<br />Record<br />URL<br />Email<br />Annotation URI<br />Geographiccoordinate (S Maps)<br />Enumeration<br />Customunits<br />Page<br />String<br />Number<br />Boolean<br />Date<br />Text<br />Code<br />Temperature<br />
    55. 55. Add your own information<br />Now add information about yourself<br />For example: nationality, affiliation, age, birthday, hair color, likes…<br />Save or preview to see if and how the information has been understood<br />Blue links mean there is a page about it<br />Red link means there is no page about it<br />
    56. 56. Collaborative ontology engineering<br />There are pages describing categories and properties<br />Informal description<br />Can be discussed<br />Can be edited<br />Extensional descript.<br />List of all instances<br />But: only direct ones<br />Supercategories<br />
    57. 57. Slide 57<br />Social aspects<br />Task: come up with a vocabulary and the relation between the vocabularies for the whole group, using the wiki<br />How to decide which properties and categories are important?<br />How to define the properties or categories?<br />How to ensure high quality data? What does it mean?<br />How to control the wiki knowledge base and its growth?<br />Browse the wiki to see the results and connections<br />
    58. 58. Querying the knowledge<br />Go to Special:Ask<br />Enter a query<br />Queries look like this:<br />Conditions on a category: [[Category:X]]<br />Conditions on a property: [[R::X]]<br />Property conditions can be ranges, [[R::>X]], [[R::<X]]<br />Property conditions: any value [[R::+]]<br />Print statements: ?R<br />Examples follow<br />See also online docs<br />
    59. 59. Query examples<br />[[population::>1,000,000]] anything with a population of over a Million<br />[[located in::Korea]] anything that is located in Korea<br />[[affiliation::+]] anything that has any stated affiliation<br />[[Category:Tutor]] all tutors<br />[[Category:Tutor||Student]] all tutors or students (logical or)<br />[[Category:Tutor]] [[Category:Student]] everyone who is both<br />
    60. 60. Querying and social aspects<br />Querying can only be done on aligned vocabularies<br />If half of the people use “affiliation” and the other half “works for” you cannot query the knowledge easily<br />Inside SMW, information integration usually happens with social tools, not with technology<br />Gardening tools can help with aligning vocabularies, but not replace them<br />Tools that allow you to rename a property throughout the wiki<br />Or to join two different names<br />
    61. 61. Querying the wiki<br />{{#ask:<br /> [[Category:City]]<br /> [[Mayor.Gender::Female]]<br />| sort=Population<br />}}<br />
    62. 62. Querying the wiki<br />{{#ask:<br /> [[Category:Country]]<br /> [[Continent::North America]]<br />|?Population<br />}}<br />
    63. 63. Result rendering<br />
    64. 64. Querying the wiki<br />{{#ask:<br /> [[Category:Country]]<br /> [[Continent::North America]]<br />|?Population<br />|format=piechart<br />}}<br />
    65. 65. Pie chart<br />
    66. 66. Querying the wiki<br />{{#ask:<br /> [[Category:Country]]<br /> [[Continent::North America]]<br />|?Population<br />|format=barchart<br />}}<br />
    67. 67. Bar chart<br />
    68. 68. 68<br />Outline<br />Tutorial Introduction and Structure (Mark)<br />Introduction to Semantic MediaWiki (Denny)<br />Dive into Semantic MediaWiki (Denny)<br />Applications for Semantic Wikis (Mark)<br />Extensions for Semantic MediaWiki (Denny, Daniel, Jesse)<br />Connecting Semantic MediaWiki with MS Office (Jesse)<br />Augmenting Semantic MediaWiki with a Triple Store (Daniel)<br />Future Development (Denny, Daniel, Jesse)<br />Wrap Up and Q&A (Mark)<br />Break (30 mins)<br />
    69. 69. SNPedia<br />
    70. 70. HL7 Healthcare Terminology Management<br />70<br />
    71. 71. Taaable<br />71<br />
    72. 72. Chickipedia<br />72<br />
    73. 73. Football Indexing Wiki<br /><ul><li>Non-Wikipedia Look/Feel
    74. 74. Play-by-play video search
    75. 75. Highlight reel generation
    76. 76. Search on crowd-defined patterns (“touchdowns with big hits”)
    77. 77. Tree-based navigation widget</li></li></ul><li>Metacafe Video Indexing and Tagging Wiki<br />
    78. 78. SMW+ with Automatic Document Annotation<br />75<br />
    79. 79. Collaborative Proposal Management at BT with SMW+<br />76<br />Active Bid Viewer<br /> Service Desk Selector<br />
    80. 80. Lightweight Project Management with SMW+<br />77<br /><ul><li>Automatically populate tables
    81. 81. Just the data you want, at the level you want
    82. 82. Calendars and timelines
    83. 83. Workflows
    84. 84. Custom Reports
    85. 85. Form-oriented inputs
    86. 86. Notifications via email/RSS
    87. 87. MS Office integration</li></li></ul><li>Shared Documentation in SMW+<br />
    88. 88. Wiki-based Communities of Interest with SMW+<br />79<br />
    89. 89. Employee Skill Registries with SMW+<br />80<br />
    90. 90. Employee Home Pages in SMW+<br />81<br />
    91. 91. Community Maintained Resource Portals<br />82<br />
    92. 92. Timelines in the LiDAR Portal<br />83<br />
    93. 93. Social Networks in the LiDAR Portal<br />84<br />
    94. 94. Google Maps<br />
    95. 95.
    96. 96. SMW+ Extended Example: An Analytic Encyclopedia<br />Ultrapedia: An SMW demo built to explore data and text in a wiki<br />Wikipedia merged with the power of a database<br />Data extracted from Wikipedia Infobox and Table data; stored in RDF<br />For Authors: tools to create more compelling articles<br />Great visualizations: charts, tables, timelines, photos, analytics<br />Always up-to-date across the Encyclopedia<br />Encourage data consistency and find data errors<br />Link in other web data sources<br />For Readers: <br />Enhanced articles and data interaction<br />Faceted navigation<br />Sophisticated queries (both standing and ad-hoc)<br />Maintenance via the Wikipedia update process<br />Data is from the article text, with simple ways for article authors to maintain and extend it.<br />Authors and readers always in the loop for merging, updating, validating, mapping<br />87<br />
    97. 97. Title<br />Description<br />Languages<br />Further Down<br />Web Links<br />Categorization<br />Domain specific<br />Data<br />Images<br />Infobox<br />Properties<br />Sources of Structured Data in Ultrapedia<br />
    98. 98. Ultrapedia Data from Wikipedia Tables<br />89<br />Table<br />Data<br />
    99. 99. Ultrapedia: An Analytic Encyclopedia<br />Goal: Prototype a small semantic encyclopedia<br />Create an semantic version of a part of Wikipedia<br />Software is SMW+, Ontobrokertriplestore, DBpedia<br />Show what a data-aware encyclopedia might look like<br />Ultrapedia Prototype Details<br />Test domain is German cars<br />~2500 Wikipedia pages, ~40000 triples<br />Features<br />Similar look and feel to Wikipedia<br />Dynamic tables and charts<br />Powerful queries<br />Navigation beyond search<br />Edit, discuss and rate data<br />SPARQL-based queries<br />Derived assertions (via OntoBroker)<br />
    100. 100. Wikipedia for Porsches (Acceleration Data Example)<br /><ul><li>Information Need: All Porsche models that accelerate 0-100kph in under 5, 6, and 7 seconds</li></li></ul><li>More Porsche Acceleration Data in Wikipedia<br />
    101. 101. Main Page<br />Ultrapedia Main Page<br />
    102. 102. Tree View Control<br />Abstract/Summary quick preview<br />Semantics for Improved Wiki Navigation<br />
    103. 103. The Porsche 996 Acceleration Table In Ultrapedia<br />
    104. 104. Same Table as a Query<br />
    105. 105. Which Porsches accelerate fast?<br />Dynamically-Generated Tables for Queries<br /><ul><li>Information Need: All Porsche models that accelerate 0-100kph in under 5, 6, and 7 seconds</li></li></ul><li>Graph Views of the Acceleration Data<br />
    106. 106. External Data via a Live Ebay Query<br />
    107. 107. Linking to External Ebay Data<br />
    108. 108. Mercedes-Benz E-class W212 Gallery Section<br />Photos in Wiki Articles as Data<br />
    109. 109. Volkswagen Production Timeline View<br />Timelines from Data<br />
    110. 110. Dynamic Mapping and Charting<br />
    111. 111. Editing Wiki Data In Place<br />
    112. 112. 105<br />Wrap-Up Part 1: Managing Data in the 21st Century<br />A New Kind of Knowledge Management<br />Structured and unstructured data together in one tool<br />Built with Semantic Web standards, and with web energy<br />Empower users with lightweight, web-friendly tools<br />Data sharing from the start: not just another silo<br />Built for collaboration on the web<br />Example: Semantic MediaWikiand SMW+<br />Open-source semantic wiki software<br />Wiki-style text/article authorship based on MediaWiki<br />Lightweight enterprise-scale data publishing <br />Collaborative, user-governed structured and unstructured data curation<br />A comfortable tool users to own their data<br />A variety of applications and uses<br />
    113. 113. 106<br />Break<br />
    114. 114. 107<br />Outline<br />Tutorial Introduction and Structure (Mark)<br />Introduction to Semantic MediaWiki (Denny)<br />Dive into Semantic MediaWiki (Denny)<br />Applications for Semantic Wikis (Mark)<br />Extensions for Semantic MediaWiki (Denny, Daniel, Jesse)<br />Connecting Semantic MediaWiki with MS Office (Jesse)<br />Augmenting Semantic MediaWiki with a Triple Store (Daniel)<br />Future Development (Denny, Daniel, Jesse)<br />Wrap Up and Q&A (Mark)<br />Break (30 mins)<br />
    115. 115. Extensions<br />Halo<br />S Forms<br />S Result Formats<br />S Layers<br />S Tasks<br />S Calendar<br />MokiWiki<br />External Data<br />Maps and S Maps<br />S Drilldown<br />Woogle<br />Innsbruck Ontology Editor<br />P2P Extension<br />RDFaExporter<br />and others<br />
    116. 116. Extension architecture<br />Built firmly on top of MediaWiki<br />Core SMW to be small<br />Provide extension hooks of its own<br />Allow apps on top of it<br />
    117. 117. The suite of halo extensions for Semantic MediaWiki<br />Daniel Hansch, „Semantic Wikis and Applications“ tutorial, semtech 2010<br />hansch@ontoprise.de<br />
    118. 118. Agenda<br />Who is ontoprise?<br />The halo extensions<br />Vision<br />Benefits<br />How to get it?<br />
    119. 119. ontoprise: leader in semantic technologies and solutions<br /><ul><li> +50 employees in Karlsruhe, Germany
    120. 120. software vendor (more about us on: http://www.ontoprise.com)
    121. 121. flagship product: rdf-store with reasoning capabilities (OntoBroker)
    122. 122. selected customers
    123. 123. selected partners</li></li></ul><li>Building the best Semantic Wiki in project halo[1]<br />SMW+<br />halo extensions<br />1. http://wiki.ontoprise.com/wiki/index.php/Faq/project_halo<br />
    124. 124. halo extensions - vision<br />Leverage adoption of Semantic MediaWiki by <br />domain experts in scientific and commercial environments <br />by improving key product features.<br />Usability<br />Retrieval<br />Security<br />SemanticMediaWiki<br />Data <br />processing<br />Data re-use<br />and<br />consistency<br />Administration<br />
    125. 125. Improve usability <br />Enable a non-tech savvy Wiki community to efficiently use <br />Wiki- and semantic features with minimal training time.<br />
    126. 126. Improve usability <br />Ontology browser<br />
    127. 127. Improve usability <br />Ontology browser<br />Enable a non-tech savvy Wiki community to efficiently use <br />Wiki- and semantic features with minimal training time.<br />
    128. 128. Improve usability <br />Graphical query interface<br />
    129. 129. Improve usability <br />Graphical query interface<br />Ontology browser<br />Enable a non-tech savvy Wiki community to efficiently use <br />Wiki- and semantic features with minimal training time.<br />
    130. 130. Improve usability <br />Annotation mode<br />
    131. 131. Improve usability <br />Graphical query interface<br />Annotation mode<br />Ontology browser<br />Enable a non-tech savvy Wiki community to efficiently use <br />Wiki- and semantic features with minimal training time.<br />
    132. 132. Improve usability <br />WYSIWYG editor<br />
    133. 133. Improve usability <br />Graphical query interface<br />Annotation mode<br />Ontology browser<br />WYSIWYG editor<br />Enable a non-tech savvy Wiki community to efficiently use <br />Wiki- and semantic features with minimal training time.<br />
    134. 134. Get better search results<br />Augmented search results<br />Path search<br />Semantic tree view<br />SMW blends text and data; this requires augmenting classic retrieval<br />and navigation features with semantic data. <br />
    135. 135. Enforce security policies for text and data <br />Protection of content and data<br />Protection of annotations and queries<br />User group management<br />Commercial environments require integration with central directory <br />services and fine grained access rights to semantic data and content.<br />
    136. 136. Leverage data re-use and improve consistency <br />2. Select available webservices<br />Import legacy data and tab data from web services to embed the Wiki<br />into a team’s data-environment. Data inconsistencies are automatically <br />detected to improve data quality.<br />3. Embedding webservices in articles<br />1. Attach webservices using GUI<br />
    137. 137. Powerful data processing <br />Enhanced data model<br />Professional Wiki communities request the ability to formulate complex<br />relationships in the Wiki (e.g. rules), which are processed automatically.<br />Form based rule editor<br />
    138. 138. Reduced administration overhead<br />Reduce the efforts for checking for compatible upgrades to a <br />SMW installation and for downloading and installing new <br />extensions.<br />
    139. 139. Where to get it?<br />Get a copy: http://sourceforge.net/projects/halo-extension/<br />User forum: http://smwforum.ontoprise.com<br />It‘s all for free and GPL!*<br />*) Except OntoBroker and Triple store connector which are ontoprise licenses.<br />
    140. 140. too complicated?<br />then get all these features within 5 minutes:<br /> Product home page: http://wiki.ontoprise.com<br />
    141. 141. Semantic Forms<br />Utilizing the semantics<br />Facilitating data input<br />
    142. 142. Benefits of Semantic Forms<br />To make MediaWiki templatesbetter to use<br />To provide a form-like User Interfaces for inexperienced users to input data<br />To associate forms with a category<br />Have a helper form to help wiki admins or advanced userscreate forms<br /> Variations to provide further usability enhancements<br />
    143. 143. Image: Using a (basic) Form<br />
    144. 144. Image: Using a (long) form<br />
    145. 145. Image: Form with a (simple) style<br />http://www.thethirdturn.com/w/index.php?title=Form:Driver&action=edit<br />
    146. 146. Image: Form with auto-completion<br />Advanced Auto-Completion on Customized Query Results<br />Basic Auto-Completion on Static Permitted Values<br />
    147. 147. Remember Special Properties?<br />“Has type” is a special property<br />a pre-defined property for meta-data<br />Example: [[Has type::Type:Date]]<br />“Allows value” is another special property<br />To specify the permitted values for the property<br />Example: <br />[[Allows value::Low]]<br />[[Allows value::Medium]]<br />[[Allows value::High]]<br />
    148. 148. Form Field Input Types<br />String, Page, Number – text entry <br /> Text – TextArea<br /> Boolean – checkbox<br /> Date – date input or Javascriptdatepicker<br /> “Enumeration” (Page or String with “allowed values”) - DropDown list or RadioButton<br />List of "Enumerations" - ListBoxor CheckBoxes<br />
    149. 149. Creating Forms: on Form Page<br />
    150. 150. More On Auto-Completion<br />Basic auto-completion is on “Allowed values”<br />Current standard is on either category or property<br />Advanced auto-completion is based on queries<br />{{{field|story|autocomplete on query=[[Category:Project stories]]<br />[[Project sprint::<q><br />[[Sprint start date::<{{CURRENTYEAR}}/{{CURRENTMONTH}}/{{CURRENTDAY}}]]<br />[[Sprint end date::>{{CURRENTYEAR}}/{{CURRENTMONTH}}/{{CURRENTDAY}}]]<br /></q>]]}}}<br />
    151. 151. Helper Forms<br />
    152. 152. Helper Form : Create a Template<br />
    153. 153. Helper Form: Create a Form<br />
    154. 154. Helper Form: Create a Class<br />
    155. 155. Special Pages:<br />Special:CreateForm - lets a user create a new form for adding/editing data. (See example of page)<br />Special:CreateTemplate - lets a user create a new template. (See example of page)<br />Special:CreateProperty - lets a user create a new property. (See example of page)<br />Special:CreateCategory - lets a user create a new category. (See example of page)<br />Special:CreateClass - a page that creates all the elements for a single "class" at the same time - properties, template, form and category (See example of page). Access to this page is dictated by the 'createclass' MediaWiki permission; by default, it is available to all logged-in users.<br />Special:FormEdit - lets a user either create or edit a page using a user-defined form. (See example of page.) (This page was, until version 1.9, two separate pages: "Special:AddData" and "Special:EditData".)<br />Special:FormStart - used to route a user to either 'FormEdit' or the relevant page's "edit with form" tab. This page should not be accessed directly by users. (This page was known until version 1.9 as "Special:AddPage".)<br />Special:Forms - lists all form pages on the site. (See example of page)<br />Special:RunQuery - lets a user run a query, using a form (See example of page)<br />Special:Templates - lists all templates on the site. (See example of page)<br />Special:UploadWindow - lets a user upload a file; very similar to the standard Special:Upload page, but without the skin. This page is called from within a form, and should not be accessed directly by users.<br />
    156. 156. More Info<br />On MediaWiki.org <br />http://www.mediawiki.org/wiki/Extension:Semantic_Forms<br />SMW User Forum (ontoprise GmbH) http://smwforum.ontoprise.com/smwforum/index.php?title=Help:Creating_Semantic_Forms&context=Help%3ASMW%2B+1.5.0<br />
    157. 157. 147<br />Outline<br />Tutorial Introduction and Structure (Mark)<br />Introduction to Semantic MediaWiki (Denny)<br />Dive into Semantic MediaWiki (Denny)<br />Applications for Semantic Wikis (Mark)<br />Extensions for Semantic MediaWiki (Denny, Daniel, Jesse)<br />Connecting Semantic MediaWiki with MS Office (Jesse)<br />Augmenting Semantic MediaWiki with a Triple Store (Daniel)<br />Future Development (Denny, Daniel, Jesse)<br />Wrap Up and Q&A (Mark)<br />Break (30 mins)<br />
    158. 158. SMW:: powerful tools and contents<br />Semantic MediaWiki and related extensions have more potential power<br />
    159. 159. Need Release ::The (more) Power<br />Be used by morepeople<br />Content in moreplaces<br />Accessible via moreapplications<br />Enhanced with moresemantics<br />The more users<br />The better<br />
    160. 160. Need ::Workflow Integration + Usability Enhancements<br />InfrequentWiki users frequentlyforget where the wiki pages are located<br />Search is a break from current workflow <br />Search result can be noisyorirrelevant<br />Usability: <br />Wiki/Template/SF markup syntax is not extremely hard, but enough to turn off many users<br />To locate and consume info in SMW is just not easy enough, need something better<br />Why don’t we leverage Microsoft Office suite?<br />
    161. 161. Microsoft Office ::The Most Popular Productivity Suite<br />
    162. 162. WikiTags:: How It Works<br />Leverage Microsoft SmartTags technology<br />Bring SMW info to Office applications on-demand<br />API for semantic data I/O<br />Utilize semantics to improve relevance<br />Smart actions for semantic properties<br />SmartTag<br />Add-ins<br />API<br />API<br />Connections<br />Smarts<br />
    163. 163. Some Semantic Wikis<br />Before the demo, let’s look at<br />For more info, go to <br />http://wiking.vulcan.com/dev/<br />
    164. 164. Wiki:: Semantic Sci-Fi Movie<br />Familiar content just like another wiki<br />Semantic markups shown in fact box<br />
    165. 165. Wiki:: NGT - Proposal Handling<br />
    166. 166. Wiki :: Agile Project Management<br /><ul><li>Project Wiki for Milestones, User Stories, Developer Tasks, etc.
    167. 167. Page is form- based, with queries and semantics built-in</li></li></ul><li>Live actions<br />Now see the demo<br />For more info, go to <br />http://wiking.vulcan.com/dev/ <br />
    168. 168. Backstage::WikiTags Extension<br />Wiki Validation<br />Authentication<br />To get the categories<br />And descriptions<br />To get the article titles<br />To get the semantic properties<br />To get page info<br />Get all available forms<br />Save page as a form<br />Save page with dataset<br />Set form of a page<br />Create form templates<br />To upload into the Wiki<br />http://wiking.vulcan.com/dev/index.php/SMW_Webservice_APIs<br />
    169. 169. Extension to facilitate semantic data exchange<br />Web UI to make semantic schema mapping for semantic wiki templates and forms<br />Web service APIs to do the same<br />http://wiking.vulcan.com/dev/index.php/SemanticConnector_extension<br />Backstage::Semantic Connector<br />
    170. 170. Special:ApiTest :: Results in JSON<br />
    171. 171. Recap of demo<br />What to take away from the demo<br />For more info, go to <br />http://wiking.vulcan.com/wikitags/<br />
    172. 172. Semantic Info::Across Office Apps<br />Dynamic Query Results from the article page<br />Outlook<br />Multiple Wiki Sites supported<br />Excel<br />Via SmartTags<br />WikiTags recognizes smartly the keywords or phrases relevant to you<br />
    173. 173. Semantic Info::In Real-time<br />Explore related real-time semantic info across the links in article<br />See articles in categories live<br />
    174. 174. WikiTags::Semantic Actions<br />Semantic actions are based on semantic services of properties<br />
    175. 175. Wiki Forms::In Microsoft Office<br />View Semantic Content in familiar forms<br />Contribute into Wiki articles back<br />
    176. 176. Screenshots::WikiMail<br /><ul><li>Upload Emails into Wiki
    177. 177. Manual upload
    178. 178. Automatic upload by folder mapping
    179. 179. Conflict handling
    180. 180. Heuristic category
    181. 181. Use recipients, folders and text</li></ul>Shortcut to create wiki articles<br />Customize Categories<br />Conflict Resolution<br />
    182. 182. Screenshot::Email in Wiki<br />Attachments automatically uploaded too<br />
    183. 183. Screenshots::Settings<br />Option to choose categories of interest<br />and more<br />
    184. 184. WikiTags::Smart Connections<br /><ul><li>Consume relevant, targeted information
    185. 185. With the tools you are already familiar with
    186. 186. In the context – better relevance and productivity
    187. 187. Only when you need it – no information overload
    188. 188. In place – no search overhead to break workflow
    189. 189. In real time – data from wiki is live
    190. 190. Let you contribute to Wiki
    191. 191. Without knowing where the content is
    192. 192. Without learning wiki/template syntax</li></li></ul><li>170<br />Outline<br />Tutorial Introduction and Structure (Mark)<br />Introduction to Semantic MediaWiki (Denny)<br />Dive into Semantic MediaWiki (Denny)<br />Applications for Semantic Wikis (Mark)<br />Extensions for Semantic MediaWiki (Denny, Daniel, Jesse)<br />Connecting Semantic MediaWiki with MS Office (Jesse)<br />Augmenting Semantic MediaWiki with a Triple Store (Daniel)<br />Future Development (Denny, Daniel, Jesse)<br />Wrap Up and Q&A (Mark)<br />Break (30 mins)<br />
    193. 193. Making SMW smarter - Agenda<br />RDF and Semantic MediaWiki (SMW)<br />Current limitations of SMW<br />What is a triple store?<br />What is the Triple Store Connector?<br />Examples<br />Derived properties<br />Semantic data integration (demo!)<br />Where to get it?<br />Wrap up<br />
    194. 194. RDF and Semantic MediaWiki<br />RDF (Resource Description Framework) is the underlying data model of the Semantic Web and essentially also for SMW.<br />RDF is a graph-base datamodel, i.e. all data is represented in the form or nodes that are connected via directed, labeled arcs. Two nodes connected by a arc should be interpreted as a subject-predicate-object statement (triple).<br />Examples of three triples.<br />SMW stores such triples in the underlying relational database<br />
    195. 195. Current limitations of SMW<br />SMW is a great semantic Web application, in the sweet spot between feature richness and engineering complexity.<br />Limitations:<br />Triple stores overcome these limitations.<br />
    196. 196. What is a triple store?<br />A triple store is a dedicated database for storing and retrieving RDF data.<br />Features:<br />Ontoprise’s “Triple store connector" creates a bridge between SMW and a triple store.<br />
    197. 197. What is the Triple Store Connector?<br />Triple Store Connector<br />Semantic MediaWiki<br />halo Extension<br />Triple Store<br />The Triple Store Connector[1] is a ready-to-use product from ontoprise which is installed along with SMW and attaches it to Jena[2] or OntoBroker[3].<br />[1] http://smwforum.ontoprise.com/smwforum/index.php/Triple_store_connector<br />[2] Open source triple store with reasoning capabilities, http://www.openjena.org/<br />[3] Highly scalable semantic Web middleware, http://www.ontoprise.de/en/home/products/ontobroker/<br />
    198. 198. Examples<br />Derived properties<br /> We formulate a rule in the Wiki to derive a property value from other properties (e.g. calculation).<br /> Advantage: reduced amount of annotations, improved data consistency and enriched knowledge.<br />Semantic data integration<br /> An enterprise integrates sources of legacy data into one single source and publishes this data in the Wiki.<br /> Advantage: data from rigid legacy systems is available for highly collaborative and flexible workflows.<br />
    199. 199. First example – derived properties<br />We have a Wiki which is used for generating bids; the project team wants to calculate the estimated costs of each task from the estimated work efforts which are given in person days.<br />Want to try out this example by yourself?<br />Go to our online demo installation and create an account:<br />http://smwdemo.ontoprise.com<br />
    200. 200. Preparing the ontology<br />
    201. 201. Preparing the ontology<br />
    202. 202. Formulating the calculation rule<br />
    203. 203. Formulating the calculation rule<br />
    204. 204. Formulating the calculation rule<br />
    205. 205. Applying the rule<br />
    206. 206. Applying the rule<br />
    207. 207. Applying the rule<br />
    208. 208. Benefits<br />We learn from this example:<br />Authoring rules in a triple store connector-backed Wiki is making it a powerful data processing tool.<br />
    209. 209. Second example: semantic data integration<br />Large corporations have to deal with data silos making integrated views onto data hard to achieve.<br />Resulting problems:<br />We require a Wiki which is giving access to semantically integrated legacy data.<br />
    210. 210. Architecture (draft)<br />Ontology engineering application (OntoStudio)<br />Semantic MediaWiki<br />Triple Store Connector<br /> OntoBroker<br />Web <br />services<br />RDBMS<br />RDBMS<br />RDBMS<br />RDBMS<br />
    211. 211. Demonstration: Workflow<br />We want to provide a Wiki community with legacy data about book titles[1], the community queries the data in the Wiki and enriches it with socially curated metadata.<br />Steps:<br />Integrate relational data: the knowledge manager uses the ontology engineering tool „OntoStudio“ to attach the RDBMS to OntoBroker and to generate the ontology integrating the data about book titles into the Wiki.<br />Query the integrated data: the user queries the Wiki for the book titles to generate a personalized views which can be embedded into articles.<br />Curate the integrated data: the user tags (“annotates”) individual book titles with new meta data which can be used in queries again.<br />[1] http://msdn.microsoft.com/en-us/library/aa238305(SQL.80).aspx<br />
    212. 212. Demonstration<br />
    213. 213. Benefits from integrating legacy data into the Wiki<br />We learn from this example:<br />Data from rigid legacy systems are available in highly collaborative and flexible workflows.<br />
    214. 214. Where to get it?<br />Option 1: You are a beginner and just want to give it a try:<br /><ul><li>study examples online in the smwforum: ref. [1]
    215. 215. try them out in the online demo system: ref. [2]</li></ul>Option 2: You want to make your SMW installation smarter:<br /><ul><li>get the halo extension for free: ref. [3]
    216. 216. get the Triple store connector basic for free: ref. [4]</li></ul>Option 3: You require a smart Wiki for your team or department:<br /><ul><li>get SMW+, the Semantic Enterprise Wiki: ref. [5]
    217. 217. get the Triple store connector basic for free: ref. [4]</li></ul>Option 4: You to go enterprise level?<br /><ul><li>get SMW+, the Semantic Enterprise Wiki: ref. [5]
    218. 218. get the Triple store connector professional: shop@ontoprise.com</li></ul>[1] http://smwforum.ontoprise.com/smwforum/index.php?title=Help:Creating_rules&context=Help%3ARule+Knowledge+Extension+1.1.0<br />[2]http://smwdemo.ontoprise.com<br />[3]http://smwforum.ontoprise.com/smwforum/index.php/Help:Halo_Extension_User_Manual<br />[4]http://smwforum.ontoprise.com/smwforum/index.php/Help:Installing_the_Basic_Triplestore_1.2_with_Installer<br />[5]http://smwforum.ontoprise.com/smwforum/index.php/Download<br />
    219. 219. Take home message<br /><ul><li>Semantic MediaWiki is a great tool! But it has limitations with regard to the query language, data processing and data integration capabilities.
    220. 220. SMW can be improved by further semantic extensions, such as the HALO extensions.
    221. 221. SMW becomes versatile and smarter by using a triple store with reasoning capabilities, e.g. for reasoning and semantic data integration*
    222. 222. Interconnect an entry-level triple store or an enterprise-level triple store to SMW with ontoprise‘s Triple store connector.
    223. 223. Read more here: http://wiki.ontoprise.com</li></ul>*) With OntoBroker.<br />
    224. 224. 194<br />Outline<br />Tutorial Introduction and Structure (Mark)<br />Introduction to Semantic MediaWiki (Denny)<br />Dive into Semantic MediaWiki (Denny)<br />Applications for Semantic Wikis (Mark)<br />Extensions for Semantic MediaWiki (Denny, Daniel, Jesse)<br />Connecting Semantic MediaWiki with MS Office (Jesse)<br />Augmenting Semantic MediaWiki with a Triple Store (Daniel)<br />Future Development (Denny, Daniel, Jesse)<br />Wrap Up and Q&A (Mark)<br />Break (30 mins)<br />
    225. 225.
    226. 226.
    227. 227.
    228. 228.
    229. 229.
    230. 230. Better Wiki I/O<br />Better workflow integration<br />On-demand client UI using wiki data<br />Smarter WikiTags matching (IR tricks)<br />Subversion and other tools integration<br />Multi-model authentication support (NTLM etc.)<br />Automatic and more powerful forms<br />For more info, visit http://wiking.vulcan.com/dev/Wiking<br />
    231. 231. SMW+ and the halo extensions<br />We make SMW a citizen of the Web of Data<br />import (or remote query) and map linked data sources in the Wiki<br />use data in queries<br />publish data<br />Jesse Wang & Daniel Hansch - SemTech 2010<br />
    232. 232. SMW+ and the halo extensions<br />Usability improvements<br />Renovated graphical query interface<br />Faceted browsing<br />Notifications on semantic data<br />Jesse Wang & Daniel Hansch - SemTech 2010<br />
    233. 233. SMW+ and the halo extensions<br />Easier knowledge formulation<br />Tabular forms<br />Easier semantic forms<br />Generating forms automatically<br />..and much much more!<br />Jesse Wang & Daniel Hansch - SemTech 2010<br />
    234. 234. 204<br />Thank You<br />Questions?<br />
    1. A particular slide catching your eye?

      Clipping is a handy way to collect important slides you want to go back to later.

    ×