{"id":116,"date":"2014-10-18T07:46:45","date_gmt":"2014-10-18T07:46:45","guid":{"rendered":"http:\/\/www.w3.org\/community\/owled\/?p=116"},"modified":"2014-10-18T14:36:31","modified_gmt":"2014-10-18T14:36:31","slug":"owled-2014-day-2-liveblogging","status":"publish","type":"post","link":"https:\/\/www.w3.org\/community\/owled\/2014\/10\/18\/owled-2014-day-2-liveblogging\/","title":{"rendered":"OWLED 2014: Day 2 LiveBlogging"},"content":{"rendered":"<p>I was a bit late, but here we go!<\/p>\n<p>Chris Mungal asked yesterday for a link to the papers and\/or slides. Here&#8217;s the link to proceedings:<\/p>\n<p><a href=\"http:\/\/ceur-ws.org\/Vol-1265\/\" target=\"_blank\" rel=\"nofollow\">http:\/\/ceur-ws.org\/Vol-1265\/<\/a><\/p>\n<p>I&#8217;ll try to go back and link through directly and call for slides.<\/p>\n<hr \/>\n<p><strong>Tahani Alsubait, Bijan Parsia and Uli Sattler. <a href=\"http:\/\/ceur-ws.org\/Vol-1265\/owled2014_submission_11.pdf\" target=\"_blank\" rel=\"nofollow\">Generating Multiple Choice Questions From Ontologies: Lessons Learnt<\/a> presented by Tahani<\/strong><\/p>\n<p>What is a MCQ and it&#8217;s parts (stem, key, distractors)<br \/>\nExample of good and bad distractors.<br \/>\nWhat makes a good one: Item response theory: Tuned difficulty, low guess ability, and right discrimination.<\/p>\n<p>MCQ generation is difficult and time consuming and you need a lot of them (exam coverage, security, and practice exams).<\/p>\n<p>Automation!<br \/>\nDifficulty prediction. Needed to increase validity and exam quality. People are bad at it.<\/p>\n<p>Similarly conjecture (degree of similarity between keys and distractors is proportional to difficulty). Existing measures didn&#8217;t work so we developed new ones (see ISWC poster).<\/p>\n<p>Key questions: Can we control difficulty? Can we generate exams? Is it cost effective?<\/p>\n<p>Experiment description: 1) Build ontology. 2) Generate questions. 3) Expert (3 &#8212; Two instructors and one domain expert) review. 4) Test with students.<\/p>\n<p>Two rounds of student tests (in review session and online).<\/p>\n<p>Usefulness rating: High heterogenity (only 1 question agreed upon by all reviewers).<br \/>\nDistractor utility: For all 6 questions, 2 out of 3 distractor.<br \/>\n5 out of 6 questions the key was picked more frequently than the distractors.<br \/>\nDiscrimination: in class better than online<br \/>\nDifficulty: 4 out of 6 correctly predicted by tool.<\/p>\n<p>Check out the tool:<br \/>\nhttp:\/\/edutechdeveloper.com\/MCQGen<\/p>\n<p><strong>QA<\/strong><\/p>\n<p>QUESTION: About reusability: Often the labels are general and not specific for domains, so may not be suitable. I.e., reusability in general might hurt applicability.<\/p>\n<hr \/>\n<p><strong>Catherine Chavula and C. Maria Keet. <a href=\"Is%20lemon Sufficient for Building Multilingual Ontologies for Bantu Languages? \" target=\"_blank\" rel=\"nofollow\">Is Lemon Sufficient for Building Multilingual Ontologies for Bantu Languages?<\/a> presented by Maria.<\/strong><\/p>\n<p>Need to be able to write things in one&#8217;s own language (and there are a lot of languages).<\/p>\n<p>OWL has challenges (e.g., Manchester syntax not suitable for Spanish).<br \/>\nWe need a lot more linguistic annotation than alternative terms.<\/p>\n<p>Some approaches separate linguistic and ontological layer. Community Group ontolex-lemon.<\/p>\n<p>Bantu langauges: spoken by &gt;200 million. Being picked up by the likes of Microsoft, Google, and Facebook.<\/p>\n<p>Each noun (in Bantu) \u00a0(class in OWL) have between 10 and 23 noun classes. Complexity which must be captured!<\/p>\n<p>&#8220;Concordial agreement of verb with nc of noun of OWL class)<\/p>\n<p>No Semantic Web stuff for Bantu. Some XML. Some work on multilingual ontologies.<\/p>\n<p><em>lemon<\/em> defines verbalisation of ontological elements in a particular language.<br \/>\n<i>lemon\u00a0<\/i>advocates GOLD and ISOcat which don&#8217;t do the job for Bantu noun classes. E.g., \u00a0nc is like gender but with semantic significance.<\/p>\n<p>To address this, developed a Noun Class Ontology (small, e.g., 42 classes, 6 op, and 130 axioms.).<\/p>\n<p>Word variation.\u00a0<em>lemon<\/em> generally uses Perl like regexs. Chichewa has too much complexity for this.<\/p>\n<p>Agglutination is a challenge.<\/p>\n<p>Application: Lexicalise FOAF and GoodRelations in Chichewa.<\/p>\n<p>(foaf:knows requires a big chunk of rules!)<\/p>\n<p>FOAF: 1:1 correspondence for classes; some odd things; object properties are usually verb phrases; data properties are easier. FOAF <i>lemon <\/i>covers 90% of foaf.<\/p>\n<p>GoodRelation: Very domain specific thus difficult due to lack of terms in Chichewa. Only 25% of the entities were lexicalized.<\/p>\n<p><a href=\"http:\/\/www.meteck.org\/files\/ontologies\/\" target=\"_blank\" rel=\"nofollow\">http:\/\/www.meteck.org\/files\/ontologies\/<\/a><\/p>\n<p><strong>QA<\/strong><\/p>\n<p>QUESTION: What are the actual remaining problems with OWL re: multilingualism? Annotations don&#8217;t quite do it. Like name of the OP property varying with type of object.<br \/>\nQUESTION: Is this a problem with programming languages as well? Yes, people are tackling it.<br \/>\nQUESTION: You mentioned issues with Manchester Syntax, can we localise it by varying things a bit? No, it&#8217;s much harder. [Ed; Much much harder!]<\/p>\n<hr \/>\n<p><strong>Matteo Matassoni, Marco Rospocher, Mauro Dragoni and Paolo Bouquet. <a href=\"http:\/\/ceur-ws.org\/Vol-1265\/owled2014_submission_8.pdf\" target=\"_blank\" rel=\"nofollow\">Authoring OWL 2 ontologies with the TEX-OWL syntax<\/a> presented by Mauro.<\/strong><\/p>\n<p>Motivation: Write onts quicky; XML syntaxes are verbose; don&#8217;t want to learn heavy tool.<\/p>\n<p><a href=\"https:\/\/github.com\/matteomatassoni\/TexOwl\/blob\/master\/docs\/grammar.pdf\" target=\"_blank\" rel=\"nofollow\">https:\/\/github.com\/matteomatassoni\/TexOwl\/blob\/master\/docs\/grammar.pdf<\/a><\/p>\n<p>Example animal \\c == Class(Animal).<br \/>\nanimal \\cdisjoint plant.<br \/>\nbranch \\cisa \\oforall{is_part_of}{tree}<\/p>\n<p>Evaluation:<\/p>\n<p>Two task:<br \/>\nsurveys\u00a0<a href=\"http:\/\/goog.gl\/Cjpqtg\" target=\"_blank\" rel=\"nofollow\">http:\/\/goog.gl\/Cjpqtg<\/a>\u00a010 examples for intuitiveness, conciseness, and understandability<br \/>\nusability for writing\u00a0small ontology<\/p>\n<p>Results: Latex near as good s Manchester on intuitiveness and better than everything else. Concision, latex was way ahead with functional next (9.7;5.3)<\/p>\n<p>re ont building: Difficulty 3.5, syntax easy to remember 3.17. Compare to prior syntax 3.67 (all on 5 point scale).<\/p>\n<p>Come see the poster!<\/p>\n<p><a href=\"http:\/\/dkmlab.fbk.eu:8080\/converter-webapp\" target=\"_blank\" rel=\"nofollow\">http:\/\/dkmlab.fbk.eu:8080\/converter-webapp<\/a><\/p>\n<p><strong>QA<\/strong><\/p>\n<p>QUESTION: Does it work with latex files? Nope!<br \/>\nQUESTION: What are\u00a0the characteristics of the participants? See poster!<br \/>\nPOINT: The fragments displayed are non equivalent in many ways.<br \/>\nQUESTION: Do you need declarations in your syntax? Need to check grammar.<\/p>\n<hr \/>\n<p><strong>Alessandro Solimando, Ernesto Jimenez-Ruiz and Giovanna Guerrini. <a href=\"http:\/\/ceur-ws.org\/Vol-1265\/owled2014_submission_2.pdf\" target=\"_blank\" rel=\"nofollow\">A Multi-strategy Approach for Detecting and Correcting Conservativity Principle Violations in Ontology Alignments<\/a>\u00a0<\/strong><strong>presented by Alessandro.<\/strong><\/p>\n<p>Ontology matching problem (same domain, variant modelling, how to align?)<\/p>\n<p>Three matching principles: consistency principle (no new incoherent classes), conservatively principle (no new entailments inside a single signature), locality (map neighbourhoods)<\/p>\n<p>Conservativity (Deductive)\/Deductive differnce (are there different entailments over a given signature).<\/p>\n<p>Approach: Approx diff (atomic); use modularisation, projection to propositional horn, reuse semantic\u00a0indexing from LogMap to help scalability; disjointness assumption [Sch05] helps basic violation reduction to sat; equivalence violations detected using answer set programming<\/p>\n<p>[[sorry, had to prepare for covering the next talk![[<\/p>\n<p>Lots of violations in experiments. Reasonable computation time (80secs)<br \/>\nFully automated and &#8220;conservative&#8221; repair (as well as detection)<\/p>\n<p>30 million violations in some cases!!!<\/p>\n<hr \/>\n<p><strong>Birte Glimm, Yevgeny Kazakov, Ilianna Kollia and Giorgos Stamou. <a href=\"http:\/\/ceur-ws.org\/Vol-1265\/owled2014_submission_1.pdf\" target=\"_blank\" rel=\"nofollow\">OWL Query Answering based on Query Extension<\/a>\u00a0<\/strong><strong>presented by Bijan<\/strong><\/p>\n<p>(Links to slides and explanatory text coming soon)<\/p>\n<hr \/>\n<p><strong>Marcelo Arenas, Bernardo Cuenca Grau, Evgeny Kharlamov, Sarunas Marciuska and Dmitriy Zheleznyakov. <a href=\"http:\/\/ceur-ws.org\/Vol-1265\/owled2014_submission_17.pdf\" target=\"_blank\" rel=\"nofollow\">Enabling Faceted Search over OWL 2 with SemFacet<\/a> presented by Evgeny<\/strong><\/p>\n<p>Tons of data and ontologies.<br \/>\nWhat can we do with it? SPARQL Queries (yeek!); Controlled Natural Languages for query (e.g., Quelo); Visual Query formulation (geek); and Faceted Search!<\/p>\n<p>Lots of work on faceted search on semantic web. What&#8217;s the common principle?<br \/>\nFaceted Search over RDF<\/p>\n<ul>\n<li>Search over several sets of items<\/li>\n<li>Progressive filters (which extend a query)<\/li>\n<li>output a user-chosen subset of items<\/li>\n<\/ul>\n<p>Variance in systems is within this paradigm (what you can filter, what filters to add, etc.)<\/p>\n<p>Existing Solutions: Don&#8217;t use ontologies but are data driven; no theoretical underpinnings (e.g., what fragments of SPARQL are covered; complexity of those fragments; formal capture of update)<\/p>\n<p>Formalised faceted interface tailored toward RDF and OWL abstracted from GUI.<br \/>\nStudy expressive power and complexity<br \/>\nStudy interface generation and update<br \/>\nResult: SemFacet system (scales to millions of triples).<\/p>\n<p>Simple mapping of facets to predicates and conjunctions and disjunctions. Then translate to FO (i.e., positive Existential formulas, monadic, directed tree rooted at free variable; disjunctive connected share one variable).<\/p>\n<p>Combined complexity: Faceted query answering over RDF datasets is tractable. WRT to \u00a0(active domain) RL (p-Complete), EL p-complete, QL, in P; (classic semantics) RL: P-complete; EL (guarded) P-Complete; QL NP-complete.<\/p>\n<p>Bottom up evaluation.<\/p>\n<p>Interface generation &amp; update. Algos guided by ontology and data. Every facet in the initial interface is justified by an entailment.<\/p>\n<p>Each update is semantically justified&gt;<\/p>\n<p>Facet graph. Project ont and data on graph. Nodes are possible facet values. Edges are facet names. Every edge must be justified by an entailed axiom or fact.<\/p>\n<p>Systesm (SemFacet) combines keyword and faceted search.<br \/>\nAuto generation of f-search<br \/>\nIn memory<br \/>\nonline and off lien reasoning<br \/>\nScales to millions of triples<br \/>\nConfigurable<\/p>\n<hr \/>\n<p><strong>Keynote: Claudia d\u2019Amato. Machine Learning for Ontology Mining: Perspectives and Issues<\/strong><\/p>\n<p>Use ML for Ontology mining<br \/>\nInductive learning (robust)<br \/>\nSupervised, Unsupervised &amp; semi-supervised\u00a0concept learning (basic refresher)<\/p>\n<p>Instance retrieval regarded as a classification problem; challenging for State of the Art\u00a0ML Classification<\/p>\n<ul>\n<li>SOTA applied to feature vector representation\u00a0(not relational DL expressivity)<\/li>\n<li>Implicit closed world assumption (unlike DLs)<\/li>\n<li>SOTA treat classes as disjoint (unlike DLs)<\/li>\n<\/ul>\n<p>Solutions: New semantic similarity measures for DL representations; cope with all problems<\/p>\n<p>Problem Definton: Given a populated ontology, a query concept, and training set with +1 0 -1 as targets learn a classification st f(a) = +1 if a in Q, -1 if in ~Q, and 0 otherwise.<br \/>\nDuel problem, given individual find all C it bellows to<\/p>\n<p>Example, nearest neighbour (given a similarity metric) voting.<\/p>\n<p>How to evaluate classifiers.<br \/>\nCompare to standard reasoner (Pellet) but this didn&#8217;t help with the &#8220;new&#8221; knowledge<br \/>\nAdded evaluation parameter, match rate, omission error rate, commission error rate, induction rate: Key bit: classic reasoner is indecisive and Classifier is determined<\/p>\n<p>Commission and omission rates are basically null; induction rate is not null! New knowledge (perhaps supporting semi-automated ontology population)<br \/>\nMost of the time the most effective method is relational K-NM<br \/>\nMost scalable kernal method embedded in blah balh<\/p>\n<p>Concept Drift and Novelty Detection via Conceptual clustering methods<\/p>\n<p>Clustering: Intra-cluster similarity is high and inter-cluster similarity is low.<\/p>\n<p>(Key idea: Global Decision boundary; if new candidate cluster is out side, then it&#8217;s either novel or drift depending how it relates to existing clusters)<\/p>\n<p>Evaluation needs domain expert \ud83d\ude41<\/p>\n<p>How to learn intensional description of the new clusters (separate and conquer vs. divide and conquer)<\/p>\n<p>Ontology enrichment as pattern discovery problem<\/p>\n<p>[[holy moly, a lot more stuff; learning DL Safe rules for a variety of things using a variety of techniques]]<\/p>\n<p>Data driven tableaux &#8212; drive\/guide the reasoning process using data induced rules.<\/p>\n<p><strong>QA<br \/>\n<\/strong>QUESTION: Is the data driven tableau for unsound inferences or for optimisation? Both!<br \/>\nQUESTION: Tell us a bit more about scalability? What&#8217;s the size of the ontologies? Started with toy onts with 1000s of individuals. Scaling up!<\/p>\n<hr \/>\n<p><strong>ORE report slides and stuff coming<\/strong><br \/>\n&nbsp;<\/p>\n<hr \/>\n<p><strong>Feature popularity contest<\/strong><br \/>\n&nbsp;<\/p>\n<hr \/>\n<p>&nbsp;<\/p>\n","protected":false},"excerpt":{"rendered":"<p>I was a bit late, but here we go! Chris Mungal asked yesterday for a link to the papers and\/or slides. Here&#8217;s the link to proceedings: http:\/\/ceur-ws.org\/Vol-1265\/ I&#8217;ll try to go back and link through directly and call for slides. &hellip; <a href=\"https:\/\/www.w3.org\/community\/owled\/2014\/10\/18\/owled-2014-day-2-liveblogging\/\">Continue reading <span class=\"meta-nav\">&rarr;<\/span><\/a><\/p>\n","protected":false},"author":2410,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_s2mail":"yes","footnotes":""},"categories":[5],"tags":[],"class_list":["post-116","post","type-post","status-publish","format-standard","hentry","category-owled-2014"],"_links":{"self":[{"href":"https:\/\/www.w3.org\/community\/owled\/wp-json\/wp\/v2\/posts\/116","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.w3.org\/community\/owled\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.w3.org\/community\/owled\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.w3.org\/community\/owled\/wp-json\/wp\/v2\/users\/2410"}],"replies":[{"embeddable":true,"href":"https:\/\/www.w3.org\/community\/owled\/wp-json\/wp\/v2\/comments?post=116"}],"version-history":[{"count":13,"href":"https:\/\/www.w3.org\/community\/owled\/wp-json\/wp\/v2\/posts\/116\/revisions"}],"predecessor-version":[{"id":119,"href":"https:\/\/www.w3.org\/community\/owled\/wp-json\/wp\/v2\/posts\/116\/revisions\/119"}],"wp:attachment":[{"href":"https:\/\/www.w3.org\/community\/owled\/wp-json\/wp\/v2\/media?parent=116"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.w3.org\/community\/owled\/wp-json\/wp\/v2\/categories?post=116"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.w3.org\/community\/owled\/wp-json\/wp\/v2\/tags?post=116"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}