. "2011-01-24T15:44:12"^^ . "<#\n#>\n\n<#      \n#>\n\n==Agile Knowledge Engineering and Semantic Web (AKSW)==\nThe Research Group **Agile Knowledge Engineering and Semantic Web (AKSW)** is hosted by the Chair of ((http://bis.informatik.uni-leipzig.de Business Information Systems)) (BIS) of the ((http://www.informatik.uni-leipzig.de Institute of Computer Science)) (~IfI) / ((http://www.uni-leipzig.de University of Leipzig)) as well as the ((http://infai.org Institute for Applied Informatics)) (~InfAI). It consists of the three subgroups ((Groups/ES Emergent Semantics)), ((Groups/MOLE Machine Learning and Ontology Engineering)), and ((Groups/SIMBA Semantic Abstraction)).\n{{feed title=\"News\" divclass=\"floatbox\" url=\"http://blog.aksw.org/feed/\" max=\"3\"}}\n\n===Goals===\n * Development of methods, tools and applications for adaptive Knowledge Engineering in the context of the Semantic Web\n * Research of underlying Semantic Web technologies and development of fundamental Semantic Web tools and applications\n * Maturation of strategies for fruitfully combining the Social Web paradigms with semantic knowledge representation techniques\n<##> AKSW is committed to the ((http://www.opensource.org/ open source)), ((http://www.soros.org/openaccess/ open access)) and ((http://okfn.org open knowledge)) movements.\n\n===Projects===\nAKSW has launched a number of high-impact R&D projects:\n * ((http://triplify.org Triplify)) tackles the chicken-and-egg problem of the Semantic Web by providing a building block for the \"semantification\" of Web applications.\n * ((Projects/SoftWiki SoftWiki)) - distributed, end-user-centred Requirements Engineering for evolutionary software development\n * ((http://ontowiki.net OntoWiki)) is a Semantic Data Wiki as well as an Application Framework providing support for agile, distributed knowledge engineering scenarios.\n * ((Projects/dbpedia DBpedia)) is a community effort to extract structured information from Wikipedia and make this information available on the Web.\n * ((Projects/DL-Learner DL-Learner)) tackles the problem of learning concepts / class expressions in Description Logics / OWL from examples.\n\nPlease look at the ((Projects projects page)) for a comprehensive description of AKSW's funded as well as community and open source projects.\n\n===Demos===\nPlease have a look at our demos:\n<#\n\n
\n
\nDBpedia.org: Querying Wikipedia like a knowledge base.\n
\n\n
\n
\nLinkedGeoData.org: adding the spatial dimension to the Semantic Web.\n
\n\n
\n
\nTriplify.org: Make Web applications better mashable by exposing semantics.\n
\n\n
\n
\nxOperator: Interconnecting the Semantic Web with Instant Messaging Networks.\n
\n\n
\n
\nWikipedia Query Builder: Query the over 10M facts extracted from Wikipedia\n
\n\n
\n
\nOntoWiki: Use social semantic collaboration to build comprehensive knowledge bases
\n\n
\n
\nDL-Learner: Earn class descriptions by semantically analysing objects\n
\n\n
\n
\nDBpedia Relationship Finder: Allows you to explore the DBpedia dataset to find relationships between two things\n
\n\n
\n
\nDBpedia Navigator: Search/browse in DBpedia and get recommendations on what you may be looking for\n
\n\n#>" . . . . "2006-01-17T10:59:05"^^ . "{{RecentChanges}}" . . . . "2006-01-17T10:59:05"^^ . "{{RecentlyCommented}}" . . . . "2006-01-17T10:59:05"^^ . "{{PageIndex}}" . . . . "2006-01-17T10:59:05"^^ . "{{ChangePassword}}" . . . . "2006-01-17T10:59:05"^^ . "{{Search}}" . . . . "2006-01-17T10:59:05"^^ . "{{Login}}" . . . . "2006-01-17T10:59:05"^^ . "{{UserSettings}}" . . . . "2007-02-23T12:14:51"^^ . "==R2D2 - RDF to Database too==\nThe Semantic Web aims at giving data more structure and computer understandable meaning. For that ((http://www.w3.org/RDF/ RDF)) enables to add metadata to the unmanageable mass of data in the World Wide Web. Hence, the transformation of data located in relational databases to RDF plays an essential role. To provide such functionality our implementation R2D2 maps an RDF query to a legacy relational database without having to replicate the data. \n\nR2D2 is be implemented in PHP and uses the ((http://www.wiwiss.fu-berlin.de/suhl/bizer/rdfapi/ RDF API for PHP (RAP) )) for querying a virtual R2D2-Graph. An R2D2-Graph is read only and may be used like other models in RAP by instantiating a new model named R2D2model. An R2D2model rewrites find(spo) and sparql() queries to SQL queries and transforms the SQL result set back into RDF triples. A database schema is mapped by the ((http://www.wiwiss.fu-berlin.de/suhl/bizer/d2rq/spec/index.htm D2RQ Mapping Language)) - a declarative mapping language for describing the relation between an ontology and an relational data model.\n\n**R2D2 supports:**\n * querying a non-RDF database using ((http://www.w3.org/TR/rdf-sparql-query/ SPARQL)) or find(spo).\n * publishing the content of a non-RDF database in RDF using the RAP ((http://www.wiwiss.fu-berlin.de/suhl/bizer/rdfapi/tutorial/netapi.html NetAPI)).\n * automatic generation of a mapping file for any database so you can query it in RDF\n\n**Detailed information:**\n * R2D2 user manual (soon here - see below for a simple example)\n * Benchmark results in comparison to the RAP database backend (soon here)\n * R2D2 PHPDocs (soon here)\n * ((http://www.wiwiss.fu-berlin.de/suhl/bizer/d2rq/spec/index.htm D2RQ Language Specification)) for creating a mapping file\n\n===News===\n * 08/20/2006: currently we implement a plug-in for the ((www.wordpress.org WordPress)) blog system. This first practical example will integrate header information in a wordpress post for the FOAF, SIOC and ATOM vocabulary. The header will contain a sparql-search-query so you can query a model through the PHP NetAPI from other web applications\n\n===Download===\nThe current version is available at Sourceforge-CVS, click ((http://powl.cvs.sourceforge.net/powl/r2d2/ here)).\n\n===History===\n#|\n|| Version | Comment | Date ||\n|| V0.1 | first version of R2D2 | 01.10.2006 || \n|#\n\n**R2D2 Developers**\n * Christian Lehmann (Mail: ((mailto:Lehmann.Christian@gmx.net Lehmann.Christian@gmx.net)))\n\n**Thanks to**\n * Sebastian Dietzold for his great ideas and support\n * Sören Auer for making all this possible\n * the D2RQ Developers for the base implementation and the D2RQ Mapping language\n * the RAP Developers for the API\n\n\n===Installation and Use===\nR2D2 is a RAP PlugIn. So first, you need to download RAP.\nFor installing R2D2 you simple have to copy the R2D2 directory into the main RAP folder.\n\nSome example scipts are stored in folder testR2D2. You can copy this folder into the main RAP folder, too. After this you can use them with your mapping files .\nTo include R2D2 you have to add the class R2D2Model (in R2D2/R2D2Model.php) into RAP. After this you are able to create a new virtual RDF-graph by \n$model = new R2D2Model($mapFile). \n\nA map is represented as an RDF-graph. So if you want the RAP database to manage your map you can copy a map to RAP by RAP-methods.\nMaps that are stored in RAP are used my $model = new R2D2DbModel($db,$modelName). \n\nFor more information check the manual (coming soon).\n\n===Example===\nThis short examle script shows how user information in a ((http://wordpress.org/ WordPress)) is mapped to the FOAF vocabulary.\n\n * Mapping file: file:wordpressd2rq.n3\n * Database dump: file:wordpressMySQL.sql (MySQL database)\n * foaf vocabulary: ((http://xmlns.com/foaf/0.1/ foaf-specification))\n * find(spo) results of different queries against the database: TestFind.txt\n * SPARQL results of queries against the database: TestRDQL.txt\n\nExample Query: Find all user names\n\n%%(php)\nenableDebug();\n\n$s = null;\n$p = new Resource('http://xmlns.com/foaf/0.1/name');\n$o = null;\n\n$result = find($s,$p,$o);\n\n// the same in SPARQL\n\n$sparqlQuery = \"PREFIX foaf: \nSELECT DISTINCT ?resource ?name WHERE {\n ?resource foaf:name ?name .\n} ORDER BY ?name\";\n\n$result = $R2D2Model->sparqlQuery($sparqlQuery);\nSparqlEngine::writeQueryResultAsHtmlTable($result);\n?>\n%%\n\nUsing these parts of the D2RQ map\n\n%%\n:CMUser rdf:type d2rq:ClassMap; \n d2rq:class foaf:Person;\n d2rq:uriPattern \"//data#user@@wp_users.ID@@\";\n d2rq:dataStorage :database;\n .\n\n:UserDisplayName rdf:type d2rq:DatatypePropertyBridge;\n d2rq:property foaf:name;\n d2rq:column \"wp_users.display_name\";\n d2rq:belongsToClassMap :CMUser;\n%% .\n\nboth find and sparql query will be translated into following SQL command:\n\n%%(sql)\nSELECT wp_users.ID, wp_users.display_name FROM wp_users\n%%\n\nthe result set may contain following lines:\n\n#|\n|| wp_users.ID | wp_users.display_name ||\n|| 1001 | Christian Lehmann ||\n|| 1002 | Bob Wheeler ||\n|#\n\nand is translated into the RDF result triple:\n\n\n#|\n|| Subject | //data#user1001||\n|| Predicate| http://xmlns.com/foaf/0.1/name||\n|| Object| Christian Lehmann||\n|#\n\n\n#|\n|| Subject | //data#user1002||\n|| Predicate| http://xmlns.com/foaf/0.1/name||\n|| Object| Bob Wheeler||\n|#\n\n===Known Issues===\n * R2D2 implements a new SPARQL2SQL rewriter. This feature is still in progress and buggy. Up to now only group patterns are supported! (for more information see the ((http://aksw.informatik.uni-leipzig.de/Projects/R2D2/SPARQLquerycatalog SPARQL complexity catalog)) (german version)\n * Regular expressions in find(spo) or SPARQL are not yet supported." . . . . "2011-10-05T13:50:40"^^ . "{{toc divclass=\"floatbox\"}}\n==Projects==\n===Funded Projects===\n\nASKW is funded by regional, national and European research funding programmes.\n\n====LOD2 – Creating Knowledge out of Interlinked Data====\nThe goal of the LOD2 project is to develop infrastructure technology and best practices that fill the chasm between structured-linked-data and applied model logic & reasoning, en route redefining the Web as we know it. In doing so, LOD2 will integrate and syndicate linked data with large-scale existing applications and showcase the benefits in three application scenarios including Media & Publishing, Corporate Data Intranets and eGovernment.\n\n * //Partners:// Centrum Wiskunde & Informatica (NL), National University of Ireland, Galway (IRL), Freie Universität Berlin (D), OpenLink Software (GB), Semantic Web Company (A), TenForce (B), Exalead (F), Wolters Kluwer Deutschland (D), Open Knowledge Foundation (GB) \n * //Duration:// 2010-2014\n * //Funding Programme:// FP7-ICT-2009-5 (Collaborative Project)\n\nMore information: http://lod2.eu\n\n\n====LATC – LOD Around-the-Clock====\nThis EU-funded support action aims at making it easier for data owners to publish Linked Data and interlink it with other data sources. A user-friendly 24/7 interlinking engine is developed within the project, allowing to compute and update interlinks as well as to assess their quality.\n\n * //Partners:// National University of Ireland, Galway (IRL), Vrije Universiteit Amsterdam (NL), Freie Universität Berlin (D), Talis Ltd. (GB) \n * //Duration:// 2010-2012\n * //Funding Programme:// FP7-ICT-2009.4.3 (Support Action)\n\nMore information: http://latc-project.eu\n\n\n====SCMS – Semantic Content Management Systems====\n((http://scms.eu SCMS)) aims at combining automatic knowledge discovery and participative, end-user-driven knowledge curation and extension techniques through Social Semantic Web approaches so as to create novel applications in Enterprise Knowledge Management and real-time News Mining.\n\n * //Partners:// Punk.Netservices ~GmbH (A), OpenLink Software Ltd. (UK), Netresearch ~GmbH & Co. KG (D), Digital Trowel Inc. (IL)\n * //Duration:// 2010-2012\n * //Funding Programme:// Eurostars\n\nMore information: http://www.scms.eu\n\n\n====Social Semantic Collaboration for EKM, E-Learning & E-Tourism====\nAim of the project is to advance and apply adaptive database and knowledge base techniques as well as user interface techniques to enable large-scale, end-user-driven semantic collaboration in the three application domains Enterprise Knowledge Management, E-Learning and E-Tourism.\n\n * //Partners:// FH Kärnten (A), OpenLink Software Ltd. (UK), B2 d.o.o. (SLO), Vakantieland (NL)\n * //Duration:// 2008-2010\n * //Funding Programme:// FP7-SME\n\nMore information: http://ontowiki.eu\n\n\n====LE4SW Regional Technology Platform for Social Semantic Collaboration====\nAim of the project is to (further) develop AKSW's semantic data wiki technology platform by integrating view maintenance, query subsumption and schema evolution algorithms for the RDF data model and adopt it towards the requirements of business information systems and Web content management.\n\n * //Partners:// Ebrosia ~GmbH, Business Intelligence ~GmbH (D), Netresearch ~GmbH & Co. KG (D)\n * //Duration:// 2009-2011\n * //Funding Programme:// WK Potential, German Ministry of Education and Research (BMBF)\n\nMore information: http://le4sw.de\n\n\n<##>\n====~SoftWiki - Semantics- & Community-Based Requirements Engineering====\nThe project delivers fundamental building blocks for early phases of Requirements Engineering by establishing a stakeholder-driven knowledge engineering process for requirements elicitation, organisation and management.\n\n * //Duration:// 2006-209\n * //Funding Programme:// ((http://www.softwarefoerderung.de/ research initiative “Software Engineering 2006”)), German Ministry of Education and Research (BMBF)\n * //Partners:// Universität Duisburg-Essen, T-Systems MMS, ~ProDV AG, ~LeCoS ~GmbH, QA Systems ~GmbH, ISA Tools ~GmbH\n\nMore information: http://softwiki.de\n\n\n===Open-Source & Community Projects===\n\nAKSW has launched a number of high-impact R&D projects.\n\n\n<##>\n====~LinkedGeoData====\n((http://LinkedGeoData.org LinkedGeoData)) is an effort to add a spatial dimension to the Web of Data / Semantic Web. ~LinkedGeoData uses the information collected by the OpenStreetMap project and makes it available as an RDF knowledge base according to the Linked Data principles. It interlinks this data with other knowledge bases in the Linking Open Data initiative.\n\n\n<##>\n====~OntoWiki====\n((Projects/OntoWiki OntoWiki)) is a semantic collaboration platform implementing the Web 2.0 idea of an architecture of participation for the collaborative development of Semantic Web knowledge bases. ~OntoWiki is implemented as an alternative user interface for Powl and included into the latest Powl distribution.\n\n**Impact:** ((http://sourceforge.net/project/stats/?group_id=99425&ugn=powl&type=&mode=year more than 8.000 downloads of the OntoWiki software (since 2004) / 773 in Sep 2007)), on average 3.000 monthly visitors at http://Ontowiki.net, serving a broad variety of industrial and academic users.\n\n<##>\n====Triplify====\n((http://triplify.org Triplify)) tackles the chicken-and-egg problem of the Semantic Web by providing a building block for the \"semantification\" of Web applications. Triplify provides small, light-weight plugins for database-backed Web applications and exposes semantics as RDF, Linked Data and JSON.\n\n\n====Cofundos====\n((http://Cofundos.org Cofundos.org)) is a platform for community innovation and funding of open source software; many individual donations and contributions are pooled together in order to realize intelligent software ideas.\n\n**Impact:** more than 10.000 visitors in Oct 2007, ((http://technorati.com/search/cofundos?authority=n&language=n 62 Blog posts (according to Technorati))), News about Cofundos in major news channels (e.g. ((http://www.heise.de/newsticker/meldung/97846 Heise.de)), ((http://www.golem.de/0710/55592.html Golem.de)), ((http://www.linux.com/feed/119980 Linux.com))), more than 300 registered users, more than 5k<#€#> pledged donations in Oct 2007.\n\n\n<##>\n====DBpedia====\n((Projects/dbpedia DBpedia)) is a community effort to extract structured information from Wikipedia and make this information available on the Web. DBpedia allows you to ask sophisticated queries against Wikipedia and to link other datasets on the Web to Wikipedia data.\n\n**Impact:** ((http://technorati.com/search/dbpedia 300 posts about DBpedia in the Blogosphere (according to Technorati))), ca. 100.000 visitors at the DBpedia website in 2007, on average 350 daily visitors. DBpedia has become the most popular dataset used with Semantic Web applications and research prototypes.\n\n\n<##>\n====DL-Learner====\n((Projects/DL-Learner DL-Learner)) is a tool for learning concepts in Description Logics (DLs) from user-provided examples. Equivalently, it can be used to learn classes in OWL ontologies from selected objects. The goal of DL-Learner is to support knowledge engineers in constructing knowledge and learning about the data they created.\n\n<##>\n====~Relation Annotation in GENIA====\nThe aim of the ((http://www-tsujii.is.s.u-tokyo.ac.jp/GENIA/home/wiki.cgi?page=Relation+annotation GENIA relation ontology)) is to provide a set of relations which define a detailed and broadly applicable set of relation types based on accepted domain standard concepts for use in corpus annotation and domain information extraction approaches. To ensure that the meaning of the relationships is explicit, the relations are specified in OWL (see download section). We integrate categories and relations from several domain ontologies including IAO, OBI, GO and the GENIA ontology for maximal compatibility.\n\n<#\"BorderFlow\"#>\n====~Border~Flow====\n((http://borderflow.sourceforge.net/ BorderFlow)) is a general-purpose graph clustering tool. It uses solely local information for clustering and achieves a soft clustering of the input graph. It maximizes intra-cluster density and inter-cluster sparseness simultaneously. The default setting of BorderFlow implements a fast heuristic for maximal usability. Border~Flow also implements several heuristics, optimal versions and hardening approaches.\n\n<#\"LIMES\"#>\n====LIMES====\n((Projects/LIMES LIMES)) is a link discovery framework for the Web of Data. It implements time-efficient approaches for large-scale link discovery based on the characteristics of metric spaces. It is easily configurable via a web interface. It can also be downloaded as standalone tool for carrying out link discovery locally.\n\n<#\"FOX\"#>\n====~FOX====\n((Projects/FOX FOX)) is a framework for extracting RDF out of unstructured data. It combines functionality for Named Entity Recognition, Relation Extraction and Keyword Extraction via ensemble learning to ensure high-precision and high-recall extraction.\n\n<#\"ALOE\"#>\n====~ALOE====\n((Projects/ALOE ALOE)) is a linked data consumption engine that provides assistance to its user by suggesting class, property and consumption settings automatically. \n\n<##>\n====DBPSB====\n((Projects/DBPSB)) is a pure RDF benchmark based on actually posed queries.\nIt provides insight view over the performance of Virtuoso, Sesame, Jena-TDB, and BIGOWLIM.\n\n====NLP2RDF====\nNLP2RDF is a LOD2 Community project that is developing the NLP Interchange Format (NIF). NIF aims to achieve interoperability between Natural Language Processing (NLP) tools, language resources and annotations.\n\nMore information on ((http://nlp2rdf.org/about))\n\n\n===Incubator Projects===\n====Mobile Social Semantic Web Client (MSSW)====\nThe Mobile Social Semantic Web Client (mssw) is an Android-based social web client as well as a contacts provider, which integrates your distributed FOAF/WebID social network into your mobile phone.\n\nMore information: http://aksw.org/Projects/MobileSocialSemanticWeb\n\n====~ReDD Observatory====\nThe Research-Disease Disparity Observatory is a project about evaluating the health-care disparity between active areas of biomedical research and the global burden of disease, using Linked Data and data-driven discovery. \n\nMore information: ((Projects/ReDDObservatory))\n\n====~RDFaCE====\nRDFaCE is an RDFa Content Editor based on TinyMCE. It supports different views for semantic content authoring and uses existing Semantic Web APIs to facilitate the annotation and editing of RDFa contents.\n\nMore information: ((Projects/RDFaCE))\n\n<##>\n====~SINA a semantic search engine====\nSINA is a search engine that tranforms keyword based-query to SPARQL query.\nCurrently it is running on DBpedia knowledge base.\n\nMore information: ((Projects/lodquery))\n\n====~Stats2RDF====\n~Stats2RDF is an effort to represent multi-dimensional statistical data as RDF using the ((http://publishing-statistical-data.googlecode.com/svn/trunk/specs/src/main/html/cube.html RDF Data Cube Vocabulary)) by importing CSV files in a plug-in in ((http://aksw.org/Projects/OntoWiki OntoWiki)). \nMore information: ((Projects/Stats2RDF))\n\n====LESS - Syndicate Linked Data Content====\nLESS is an end-to-end approach for the syndication and use of linked data based on the definition of templates for linked data resources and SPARQL query results. As a result, LESS allows to integrate Linked Data into your website, blog, wiki ...\n\nMore information: http://less.aksw.org\n\n\n====Catalogus Professorum - Leipzig Professors Catalog====\nAn adapted ~OntoWiki with accompanying vocabularies for managing historic information related to the professors working at the University of Leipzig in its 600-year history.\n\nMore information: http://www.uni-leipzig.de/unigeschichte/professorenkatalog/\n\n\n====Erfurt - PHP Semantic Web API====\nComprises the API underneath ~OntoWiki, which can be used to build sophisticated Semantic Web applications.\n\nMore information: http://aksw.org/Projects/Erfurt\n\n\n====Adaptive Caching SPARQL Proxy====\nThe Adaptive Caching SPARQL Proxy improves the performance of triple stores by caching query results and even complete application objects. The selective invalidation of cache objects, following updates of the underlying knowledge bases, is based on analyzing the graph patterns of cached SPARQL queries in order to obtain information about what kind of updates will change the query result.\n\nMore information: http://aksw.org/Projects/QueryCache\n\n\n<##>\n====xOperator - Semantic Instant Messaging ====\n((Projects/xOperator xOperator)) combines advantages of social network websites with instant messaging. It represents a semantic agent for xmpp / jabber network which finds and shares content about resources (using RDF/SPARQL) for you and your jabber friends.\n\n\n<##>\n====od@fmi - Open Data for the University of Leipzig's Math and Computer Science Faculty====\nThe aim of this project is to provide all relevant data about the faculty infrastructure and courses as linked open data. \n\nMore information: ((Projects/odfmi od@fmi))\n\n\n\n\n\n====OpenResearch.org====\nA semantic Wiki for collecting and sharing scientific meta-data such as ~CfPs, tool descriptions, research profiles, conference statistics etc.\n\nMore information: http://OpenResearch.org\n\n\n<##>\n====RDFauthor—edit distributed, structured content on the Web====\nRDFauthor is a system able to extract structured information from RDFa-enhanced websites and to create an edit form based on this data. To this end, it makes use of semantics-aware editing widgets that hide most of the RDF data model from the user, thus allowing more people to author semantic content. If the embedded data does not suffice to create a rich user-supporting editing view, the underlying Semantic Web infrastructure is used to retrieve additional schema-related information about the elements used.\n\nMore information: ((Projects/RDFauthor))\n\n\n====SPARQL Trainer====\nA configurable Java servlet for SPARQL training.\n\nMore information: ((Projects/SparqlTrainer Projects/SparqlTrainer))\n\n\n====Semantic Pingback====\nThe Semantic Pingback mechanism is an extension of the well-known Pingback method, a technological cornerstone of the blogosphere, thus supporting the interlinking within the Data Web.\n\nMore information: ((Projects/SemanticPingBack))\n\n===Project Alumni===\n\nSome projects have reached a stable state, but are currently not actively maintained and further developed.\n\n\n====Powl - Semantic Web Development Plattform====\nThe aim of the Powl project is to deliver a PHP and web-based ontology editing and management solution to the OpenSoure community.\n\nMore information: Projects/Powl\n\n====R2D2 - RDB2RDF Mapping====\nPHP implementation of the D2RQ Mapping Language.\n\nMore information: http://aksw.org/Projects/R2D2\n\n\n====Semantic LDAP====\nConsisting of LDAP2SPARQL and LDAP2OWL modules.\n\nMore information: http://aksw.org/Projects/LDAP\n\n\n====XML2OWL XSLT====\nConfigurable XSLT stylesheet, which transforms XML documents into OWL.\n\nMore information: http://xml2owl.sourceforge.net\n\n\n" . . . . "2007-03-13T17:35:17"^^ . "==Powl - Semantic Web Development Plattform==\n<##>\n===Overview===\nThe broad application of ontologies as shared terminological knowledge representations is one of the main strategies of the Semantic Web paradigm. With ((http://www.w3.org/RDF/ RDF/S)) (Resource Description Framework) and ((http://www.w3.org/2004/OWL/ OWL)) (Web Ontology Language) there exist W3C standards for defining web enabled ontologies which fit in the semantic layering of web languages.\n\nAlthough there is a bunch of OWL ontology editing and management solutions available, some of them are complicated to deploy or handle, some do not support strategies for collaborative, distributed development of ontologies, some are not Open Source or not available for the most distributed web technologies.\n\nSince ((http://www.php.net/ PHP)) is by far the most distributed web development technology (as regularly confirmed by ((http://www.netcraft.com/ Netcraft))), the Semantic Web paradigm will probably only be successful in a large scale if there are applications and tools available tightly interacting with this language. The aim of the Powl project is thus to deliver a PHP and web-based ontology edititing and management solution to the OpenSoure community.\n\n===Architecture===\n\nPowl consists of the following components:\n * RAP - RDF API for PHP an independent project by Chris Bizer, Radoslaw Oldakowski and others (thanks here for their great work)\n * RDFS and OWL API for PHP - integral part of Powl\n * Powl Webapplication framework:\n * Tabplugins, as Models, RDF-Triples, Classes, Properties, Instances - future releases may include e.g. export or visualisation plugins\n * Widgetplugins for data editing - widgets for comfortable editing of WYSIWIG-HTML, Dates, Tree-Selects are planned\n\nPowl requires a PHP (greater 5.0.1) enabled webserver and a database backend for storing model data (MySQL, Postgres, Oracle and others - see ADODB Documentation for supported RDBMS).\n\nPlease have a look at the planned Powl architecture description for details.\n\n===Features===\n\n * Powl supports viewing, editing of RDFS/OWL ontologies of arbitrary size. It is even quite fast with the largest available models (e.g. NCI Cancer Ontology containing about 28,000 classes).\n * Sophisticated widgets for data editing such as widgets for editing HTML in a WYSIWIG manner or for dates are integrated.\n * Questioning the knowledge base. Powl currently offers an RDQL query builder as well as a full-text search for literals and resources.\n * Plugin concept. Powl is easy extensible, unfortunately still laking exhaustive documentation on this - please have a look at the source code and pester the developers. :-)\n * Powerful object oriented API. All functionality is accessible by a clean application programming interface.\n * Authentification scheme. Fine grained exposition of features and model data: Privileges (view, edit) for users and groups are planned to be assigned to Models, Classes and Properties.\n * Versioning. All edits of a knowledge base may be logged and rolled back (depending on time, user and edit action).\n * Powl is fast. Models are stored in database tables and only those parts of the model are loaded into main memory which are actually needed. Thus Powl is scalable and fast.\n * Multi language support. Powl comes with English and German translations of the user interface. If you would like to provide a translation please contact us!\n\nYou miss a feature? Please submit a feature request at the ((http://sourceforge.net/projects/powl Sourceforge Project Page))." . . . . "2012-01-20T14:04:16"^^ . "{{toc divclass=\"floatbox\"}}\n==Contact==\nPlease send emails to ((mailto:aksw@informatik.uni-leipzig.de aksw@informatik.uni-leipzig.de)).\n\nIf you would like to visit us, directions, information on accommdation and address details can be found ((http://aksw.org/FindUs?v=htx here)).\n\n===Team===\n\nhttp://aksw.org/Team/files?get=img_0988_cutted_resized.png\n{{vcard name=\"sn\" value=\"Auer\"}}\n{{vcard name=\"sn\" value=\"Bühmann\"}}\n{{vcard name=\"sn\" value=\"Ermilov\"}}\n{{vcard name=\"sn\" value=\"Frischmuth\"}}\n{{vcard name=\"sn\" value=\"Gerber\"}}\n{{vcard name=\"sn\" value=\"Heino\"}}\n{{vcard name=\"sn\" value=\"Hellmann\"}}\n{{vcard name=\"sn\" value=\"Jänicke\"}}\n{{vcard name=\"cn\" value=\"Jens Lehmann\"}}\n{{vcard name=\"sn\" value=\"Khalili\"}}\n{{vcard name=\"sn\" value=\"Martin\"}}\n{{vcard name=\"sn\" value=\"Morsey\"}}\n{{vcard name=\"sn\" value=\"Ngonga Ngomo\"}}\n{{vcard name=\"sn\" value=\"Riechert\"}}\n{{vcard name=\"sn\" value=\"Shekarpour\"}}\n{{vcard name=\"sn\" value=\"Stadler\"}}\n{{vcard name=\"sn\" value=\"Tramp\"}}\n{{vcard name=\"sn\" value=\"Unbehauen\"}}\n{{vcard name=\"sn\" value=\"Zaveri\"}}\n\n===Student Assistents===\nJonas Brekle\nClemens Hoffmann\nQuan Nguyen\nRené Speck\nKlaus Lyko\n\n===Bachelor / Master Students===\n\n#|\n|| **Student** | **Degree** | **Topic** ||\n|| Rene Speck | Diplom | Caching for Seed-Based Graph Clustering ||\n|| Julian Hesselbach | Diplom | Entwicklung eines Werkzeuges zur Exploration von Diebstahlereignissen ||\n|| Eduard Metzler | Master | Supervised Analyses of Diseases (with University of Cambridge) ||\n|| Jan Demter | Master | LODStats ||\n|| Sebastian Lippert | Bachelor | Semantischer Editor für Trainingsdaten ||\n|#\n\n\n===Former Bachelor / Master Students===\n====2011====\nStanley Hillner: LIMES M/R\nQuan Nguyen: An Interlnking Game\nTom-Michael Hesse: Master: Analyse und visuelle Exploration statistischer semantisch annotierter Daten\nFlorian Agsten - Master: Entwicklung und Evaluation eines Modells zur Erzeugung materialisierter Sichten für RDF\nChristian Hippler - Diplom: Resource Linking Extension für OntoWiki\n====2010====\nJan Rausch - Diplom: Using Graph Cluster Mixtures for Evolution Algorithms\nNatanael Arndt - Bachelor: Mobile Social Semantic Web Client\nChristoph Riess - Diplom: RDF Knowledge Base Evolution and Refactoring based on Patterns\nLorenz Bühmann - Master: Reparatur und Erweiterung von OWL Ontologien\nDaniel Gerber - Master: Entwicklung und Anwendung von Strategien zum Semantische MultimediaManagement\nMarvin Frommhold - Master: Modellierung von touristischen Merkmalen in RDF und Evaluation am Anwendungsfall Vakantieland\nClaudius Henrichs - Bachelor: Semantisches Geodatenmanagement\n\n\n====2009====\nRaphael Doehring - Diplom: Entwicklung und Realisierung einer Strategie zur Syndikation von Linked Data. ((http://lips.informatik.uni-leipzig.de/pub/2010-0 LIPS))\nElias Theodorou - Master: Semantifizierung von Web-Applikationen mit Triplify.\nChaofeng Yang - Master: Faceted Browsing für DBpedia.\n((/JiaXie Jia Xie)) - Market Potential of the Semantic Web Technologies ((/JiaXie Workpage))\nChen Yue - Ausnutzung von Mehrsprachigkeit für die DBpedia Infobox Extraktion ((/ChenYue Workpage))\nKatrin Baasch - Implementation of the Softwiki Use Case: Citizen Office ((/KatrinBaasch Workpage))\nFriederike Bulka - Leipzig-Professors-Ontology in Co-Operation with the ((http://www.uni-leipzig.de/~historik/ Historical Seminar))\nLydia Steiner - Leipzig-Professors-Ontology\nSteffen Becker - Musikempfehlungen im Semantic Web\nMartin Weise - Bachelor: Entwicklung und Integration eines Map Abstraction Layers für Vakantieland\n\n====2008====\nSebastian Hellmann - Comparison and Benchmarking of DL-Learning Approaches ((http://lips.informatik.uni-leipzig.de/pub/2008-3 LIPS))\nJörg Unbehauen - Master: xOperator - An Extensible Semantic Agent for Instant Messaging Networks.\nMichael Martin - Master: Charakterisierung semantischer Web-Applikationen und Vorstellung eines Anwendungsfalles ((http://lips.informatik.uni-leipzig.de/pub/2008-169 LIPS))\nAron Schneider - Diplom: Entwicklung semantischer Webapplikationen auf Basis des agilen Vorgehensmodels Scrum.\nChristian Kötteritzsch - Bachelor: Entwicklung eines DL-Learner Plugins für Protégé\nLorenz Bühmann - Erweiterung und Reparatur von Ontologien\nSebastian Knappe - Navigation in DBpedia mit Hilfe maschinellen Lernens\n\n====2007====\nChristian Weiske - Efficient Database Implementation and Enhancements for SPARQL ((http://lips.informatik.uni-leipzig.de/pub/2007-4 LIPS))\nJörg Schüppel - Extraction of Semantic from Wikipedia\nAnke Gonschorreck - Partial Translation of Wikipedia Categories into OWL Classes\nJan Fienhold - Tagging on e-Learning Objects by Advanced e-Learning Communities ((/JanFienhold Workpage))\nLeszek Kotas - Development Environment on Eclipse for PHP, UML, CVS, Unit-Test ((/LeszekKotas Workpage))\nGerrit Mattausch - Implementation of a Social Network on the Semantic-Requirements-Model ((/GerritMattausch Workpage))\nKristian Völpel - Design and Implementation of an RDF-Template Language\nThorsten Berger - Domain Requirements Engineering ((http://bis.informatik.uni-leipzig.de/de/Abschlussarbeiten/2006/ThorstenBerger Workpage))\n\n====2006====\nDenis Gärtner - Diploma: LDAP Query to SPARQL Transformation.\nTorsten Hein - Diploma: Entwicklung und Evaluation von Caching-Strategien für Anfragen an RDF-Triple-Stores.\nChristian Lehmann - Diploma: Implementierung eines D2RQ Mapping Backends für RAP (RDF API for PHP).\nMartin Peklo - Bachelor: Semantische Supportdatenbank.\nEnrico Popp - Diploma: WebDAV Dateisystem für RDF Modelle und tagged Files.\nJan Kunze - Diploma: Spezifikation eines Archivierungsformats für Daten einer Arztpraxis in HL7 Version 3 und dessen Umsetzung als Ontologie.\n\n====2005====\nHannes Bohring - Diploma: Mapping XML to OWL Ontologies.\n\n====2004====\nMarco Schütt - Diploma: Entwicklung einer Strategie zur semantischen Contentrepräsentation für Community Content Management Systeme.\nNorman Beck - Diploma: Entwicklung und Implementierung von Strategien zum Ontologie-gestützten Web Content Management.\n\n\n===Interns===\nJakub Klimek (summer intern 2012)\nIvan Ermilov (winter intern 2011-12)\nDarya Tarasowa (winter intern 2011-12)\nJinesh George (summer intern 2009)\nTimofey Ermilov (summer intern 2009)\n\n===Alumni===\n{{vcard name=\"sn\" value=\"Aslam\"}}\n" . . . . "2012-01-05T09:41:45"^^ . "{{Include page=\"/Projects/OntoWiki/Teaser\" nomark=\"1\"}}\n 2011-09-01: All pages for developer are moved to ((https://github.com/AKSW/OntoWiki/ github)).\n{{a name=\"News\"}}\n{{feed title=\"Project Updates\" divclass=\"floatbox\" url=\"https://github.com/AKSW/OntoWiki/commits/develop.atom\" max=\"10\"}}\n{{feed title=\"Project News\" divclass=\"afloatbox\" url=\"http://blog.aksw.org/category/projects/ontowiki/feed/\" max=\"5\"}}\n\n" . . . . "2006-12-04T15:08:08"^^ . "===Komplexitätskatalog von SPARQL-Anfragen===\n\nDer folgende Anfragekatalog zeigt SPARQL-Beispielanfragen steigender Komplexität, beginnend\nmit mit einer einfachen Anfrage. Die Komplexität wird hierbei durch den nötigen Transformationsaufwand\neine SPARQL-Anfrage in eine SQL-Anfrage gemessen. Weiterhin wird der Transformationsaufwand\nnicht an einer Umwandlung einer SPARQL-Anfrage auf eine einzige Tabelle mit RDF-Informationen\n(beispielsweise eine Tabelle mit den Spalten Subject, Predicate, Object) gemessen,\nsondern auf mehrere Tabelle, die Informationen enthalten können.\n\nDie hier aufgezeigten Beispiele nutzen standardmäßig jeweils den foaf- bzw. atom-Namensraum\n(, ), welcher der Einfachheit halber\nin einer Anfrage nicht per PREFIX-Definition festgelegt wird.\n\nSPARQL-Anfragen werden mittels Graph Patterns ausgedrückt. Diese können aus einem Basic Graph\nPattern (Zusammenstellung eines Triple Patterns), Group Graph Pattern (Verknüpfung mehrere\nGraph Patterns), Value Constraints (Werteinschränung), Optional Graph Pattern (optionale Graph\nPatterns), Union Graph Pattern (Vereinigung von Graph Patterns) und RDF Dataset Graph Pattern\n(Graph Patterns einzelner RDF-Datensätze) bestehen.\n\nDer nachfolgende Katalog zeigt keinesweg die vollständige Nutzung sämtlicher in der SPARQL-Spezifikation\ndefinierten Konstrukte, sondern soll lediglich Aufschluss über mögliche Komplexitätssteigerungen\ngeben.\n\n1. Basic Graph Pattern\n SELECT ?x WHERE\n { ?x foaf:name \"Christian Lehmann\" .}\n\n2. dto.\n SELECT ?x ?predicate WHERE\n { ?x ?predicate \"value\" .}\n\n3. dto.\n SELECT ?s ?p ?o WHERE\n { ?s ?p ?o .}\n\n4. dto.\n SELECT ?x WHERE\n { ?x ?foaf:name \"Christian Lehmann\" .} ORDER BY ?x\n bzw.\n SELECT DISTINCT ?x WHERE\n { ?x ?foaf:name \"Christian Lehmann\" .} LIMIT \"50\"\n\n5. Group Graph Pattern\n SELECT ?name ?mail WHERE\n { ?x foaf:name ?name.\n ?y foaf:mail ?mail.}\n\n6. dto.\n SELECT ?name ?mail WHERE\n { ?x foaf:name ?name.\n ?x foaf:mail ?mail. }\n\n7. dto.\n SELECT ?name ?mbox WHERE\n {?chris foaf:name \"Christian Lehmann\".\n ?chris foaf:knows ?friend .\n ?friend foaf:mbox ?mbox .\n ?friend foaf:name ?name .\n }\n\n8. Group Graph Pattern + Value Contraints\n SELECT ?name ?mail WHERE\n { ?x foaf:name ?name.\n FILTER (?name = \"Christian Lehmann\").\n ?x foaf:mail ?mail. }\n\n9. Union Graph Pattern\n SELECT ?name ?mail WHERE\n { {?x foaf:name ?name. }\n UNION\n {?x atom:author ?name.}\n }\n10. Union Graph Pattern + Group Graph Pattern\n SELECT ?name ?mail WHERE\n { {?x foaf:name ?name. ?x foaf:mail ?mail.}\n UNION\n {?x atom:author ?name. ?x atom:email ?mail.}\n }\n\n11. Optional Graph Pattern\n SELECT ?name ?mail WHERE\n { ?x foaf:name ?name.\n OPTIONAL{ ?x foaf:mail ?mail.}\n }\n\n12. Optional Graph Pattern + Value Constraint\n SELECT ?name ?mail WHERE\n { ?x foaf:name ?name.\n OPTIONAL{ ?x foaf:mail ?mail.}\n FILTER {?mail = \"mail@mail.de\"} \n }\n\n13. Optional Graph Pattern\n SELECT ?name ?mail WHERE\n { ?x foaf:name ?name.\n OPTIONAL { ?x foaf:mail ?mail.}\n OPTIONAL {?x foaf:givenname ?gname\n OPTIONAL {?x foaf:homepage ?hp.}\n }\n }\n\n14. RDF Dataset Graph Pattern\n SELECT ?src ?nick WHERE\n {\n GRAPH ?src\n {?x foaf:nick \"bob\".}\n }\n\n15. dto.\n SELECT ?src ?nick WHERE\n {\n GRAPH ?src\n {?x foaf:nick ?nick .\n ?x foaf:name \"Bob Wheeler\" .}\n }\n\n16. dto.\n PREFIX data: . . . "2007-03-10T14:54:49"^^ . "==~SoftWiki - Distributed, End-user Centered Requirements Engineering for Evolutionary Software Development==\n<##>The aim of the cooperative research project ~SoftWiki is to support the collaboration of all stakeholders in software development processes in particular with respect to software requirements. Potentially very large and spatially distributed user groups shall be enabled to collect, semantically enrich, classify and aggregate software requirements. The solution will be founded on the Semantic Web standards for terminological knowledge representation. The implementation will base on generic means of semantic collaboration using next generation Web user interfaces (in the spirit of Social Software and the Web 2.0) thus fostering completely new means of Requirements Engineering with very large user groups. \n\n((http://softwiki.de The official web site of the project consortium))\n\n//National research project, funded by the German Federal Ministry of Education and Research, part of the// ((http://www.bmbf.de/foerderungen/3326.php research initiative “Software Engineering 2006”))\n\nhttp://www.bmbf.de/_img/common/bmbf_logo.gif" . . . . "2007-09-03T18:16:31"^^ . "==Thomas Riechert==\n\n{{vcard name=\"sn\" value=\"Riechert\"}}\n\n\n\n((!/workspace Workspace))" . . . . "2007-01-18T16:27:35"^^ . "==WASWIE - Network==" . . . . "2011-07-11T10:30:51"^^ . "==DBpedia - Querying Wikipedia like a Semantic Database==\n{{feed title=\"Latest dbpedia news\" divclass=\"floatbox\" url=\"http://blog.aksw.org/category/projects/dbpedia/feed/\" max=\"5\"}}\n<##>\n===Overview===\nDo you know all mayors from towns elevated higher than 1000m, all sitcoms set in New York, or all philosophers that were influenced by Friedrich Nietzsche?\n\nWikipedia contains information required for answering such questions, but has the problem that its constricted search capabilities only allow very limited access to this valuable knowledge-base. The Semantic Web still lacks a critical mass of RDF data online and up-to-date terms and ontologies are missing for many application domains.\n\nThe dbpedia.org project approaches both problems by extracting structured information from Wikipedia and by making this information available on the Web. dbpedia.org allows you to ask sophisticated queries against Wikipedia (like the ones mentioned above) and to link other datasets on the Web to dbpedia data.\n\n===Features===\n<##>\ndbpedia.org features at the moment:\n\n * two large extracted datasets for different purposes\n * a SPARQL endpoint and a data browser\n * a visual query builder available at: http://wikipedia.aksw.org\n\nMore information about the project can be found at: ((http://dbpedia.org))\n\n===Publications===\n\nAuer, S. and Lehmann, J., ((http://www.informatik.uni-leipzig.de/~auer/publication/ExtractingSemantics.pdf What have Innsbruck and Leipzig in common? Extracting semantics from wiki content.)) In: Franconi, E., Kifer, M., May, W. (Eds.), Proceedings of the 4th European Semantic Web Conference (ESWC).\n\n===AKSW Contributors===\n\n * ((/SoerenAuer Sören Auer))\n * ((/JensLehmann Jens Lehmann))\n * ((/SebastianHellmann Sebastian Hellmann))\n * ((/ClausStadler Claus Stadler))\n" . . . . "2007-02-13T21:45:53"^^ . "==Seminarbericht Entwicklung von Computerspielen==\nThomas Riechert\n\nEgal, ob es sich um um Spiele, Betriebssysteme oder Anwendungssysteme handelt, die Entwicklung von Software ist ein umfassender und komplexer Prozess. Aus diesem Grund widmet sich die Disziplin des Software-Engineerings der ingenieurmäßigen und durchgängigen Unterstützung des Entwicklungsvorgangs mit Hilfe geeigneter Vorgehensweisen,\nMethoden und Werkzeuge. Wenngleich eine Vielzahl von Gemeinsamkeiten existiert, können sich Spezifika im Entwicklungsprozess je nach Art der geplanten Software unterscheiden. Es wurden daher im Rahmen des Games Summercamps die speziellen Anforderungen, die sich für die Entwicklung von Spielen ergeben, untersucht.\n\nEine mögliche Herangehensweise an diese Thematik war die Aufteilung der Arbeiten in die verschiedenen Software-Entwicklungsphasen [((#Ba96))]:\n\n * Anforderungsanalyse\n * Modellierung\n * Architekturkonzepten\n * Implementierung\n * Einführung\n * Wartung und Pflege\n\nZiel dieser Aufteilung war die Schaffung eines Überblicks über den gesamten Entwicklungsprozess. Die Arbeitsgruppe „Agile Knowledgement and Semantic Web“ [((#AKSW))] am Institut für Informatik, welche das Seminarthema betreute, hat einen Forschungsschwerpunkt im anwenderorientiertem, stark verteiltem Anforderungsmanagement mit Fokus auf Endbenutzer Interaktion und Plattformstrategie. Die Entwicklung von Spielen ist eine Anwendungsdomäne der gegenwärtigen Forschung und zeichnet sich insbesondere durch folgende Eigenschaften aus:\n\n * eine große Anzahl von Stakeholdern bei der Erhebung von Anforderungen,\n * überwiegend IT- unterstütze Dokumentation,\n * umfangreiche Endbenutzertests, sowie\n * kurze Entwicklungszyklen\n\nErreicht wird dies vor allem durch plattformgestützte Entwicklung und die Einbeziehung große Nutzergemeinschaften (Communities).\n\nIm Rahmen eines vom Bundesministerium für Forschung und Bildung geförderten Verbundprojektes SoftWiki wurden die Anforderungsanalyse, Einführung, Wartung und Pflege als die Phasen im Software-Entwicklungsprozess definiert, die eine Interaktion mit dem Endanwender bzw. Benutzer erfordern [((#ARI06))].\n\nDarauf aufbauend wurden folgende Themen innerhalb des Seminars vergeben, von denen zwei als Beitrag in diesem Buch vertreten sind.\n\n * Lebenszyklusmodelle (Autor: Jun Xie)\n * Architekturen (Autor: Hannes Niederhausen)\n * Werkzeuge und Entwicklungsplattformen (Autor: Jörn Hoffmann)\n * Requirements-Engineering (Autor: Sebastian Knappe)\n * Qualitätsmanagement (Autor: Paul Schöber)\n\n\n-----------\nAn dieser Stelle kann die Einführung enden!\n-----------\n\n\nDas folgende Kapitel gibt einen Überblick über die Ergebnisse der einzelnen thematischen Arbeiten.\n\n\n====Überblick über die thematischen Arbeiten====\n\n=====1. Lebenszyklusmodelle=====\nAutor: Jun Xie\n\n=====2. Architekturen=====\nAutor: Hannes Niederhausen\n\n\n=====3. Werkzeuge und Entwicklungsplattformen (Jörn Hoffmann)=====\nAutor: Jörn Hoffmann\n\n\n=====4. Requirements-Engineering=====\nAutor: Sebastian Knappe\n\n=====5. Qualitätsmanagement=====\nAutor: Paul Schöber\n\n\n====Ausblick====\n\n\n-----------\n{{a name=\"Ba96\"}} [Ba96]\nBalzert, H.: Lehrbuch der Software-Technik: Teil 1: Software-Entwicklung. Spektrum Akademischer Verlag 1996, Heidelberg, Germany.\n{{a name=\"AKSW\"}} [AKSW]\nhttp://aksw.informatik.uni-leipzig.de\n{{a name=\"ARF06\"}} [ARF06]\nAuer, S.; Riechert, T.; Fähnrich, K.-P.: SoftWiki – Agiles Requirements-Engineering für Softwareprojekte mit einer großen Anzahl verteilter Stakeholder. Ge Ne Me' 06 – Gemeinschaft in neuen Medien, 29. Sep. 2006, Dresden, Germany." . . . . "2011-07-11T10:33:32"^^ . "<#\n
\n

DL-Learner

\n\n\n

is a tool for supervised Machine Learning in OWL and Description Logics.

\n

The DL-Learner software learns concepts in Description Logics (DLs) from user-provided examples. Equivalently, it can be used to learn classes in OWL ontologies from selected objects. It extends Inductive Logic Programming to Descriptions Logics and the Semantic Web. The goal of DL-Learner is to provide a DL/OWL based machine learning tool to solve supervised learnings tasks and support knowledge engineers in constructing knowledge and learning about the data they created. Read more ...

\n

Download DL-Learner

\n
\n
\n{{Include page=\"/Projects/DLLearner/Menu\" nomark=\"1\"}}\n
\n
\n#>\n\n{{a name=\"News\"}}\n{{cofundos tag=\"DL-Learner\" divclass=\"floatbox\"}}\n{{feed title=\"News\" divclass=\"box\" url=\"http://blog.aksw.org/category/projects/dl-learner/feed/\" max=\"5\"}}\n\n" . . . . "2009-01-06T16:54:13"^^ . "{{Include page=\"/Projects/DLLearner/Menu\" divclass=\"floatbox\" nomark=\"1\"}}\n==Features==\nFeatures of DL-Learner:\n * implements different algorithms:\n * two refinement operator based algorithms\n * a genetic programming algorithm\n * a hybrid algorithm using genetic refinement operators\n * (random learning, brute force learning)\n * supports different kinds of learning problems:\n * learning concept definitions and inclusion axioms\n * learning from positive and negative examples as well as only from positive examples\n * supports different input formats:\n * OWL files\n * N-triple files\n * internal representation in config files\n * SPARQL endpoints \n * different reasoner adapters:\n * DIG interface: allows all major reasoners\n * OWL API interface (alpha): ~FaCT++, Pellet\n * KAON2: direct Java API access (may be removed in the future, because KAON2 is not open source)\n * different user interfaces:\n * command line\n * web service\n * Java Swing based GUI\n * easily extensible through a component model\n * 4 types of components: knowledge sources, reasoners, learning problems, learning algorithms\n * to implement a new component of one of the above types you only have to extend the correct class in org.dllearner.core and add the name of your file to the components.ini file\n * allows a wide range of configuration options" . . . . "2007-08-23T17:23:56"^^ . "{{Include page=\"/Projects/DLLearner/Menu\" divclass=\"floatbox\" nomark=\"1\"}}\n==Screenshots==\n(click to enlarge)\n\n===PHP Client===\n1. startup screen of the client\n<#
#>\n\n2. client after loading an ontology with a tooltip\n<#
#>\n\n\n3. shows a learned definition for the chosen examples\n<#
#>\n\n===Command Line===\n1. the command line interface after succesfully learning a concept\n<#
#>\n" . . . . "2011-07-08T12:57:41"^^ . "{{Include page=\"/Projects/DLLearner/Menu\" divclass=\"floatbox\" nomark=\"1\"}}\n==Demos==\n\nThe following tools use DL-Learner:\n\n * AutoSPARQL: ((http://autosparql.dl-learner.org))\n * ORE: ((http://web.ore-tool.net))\n * HANNE: ((http://hanne.aksw.org))\n * DBpedia Navigator: ((http://navigator.dbpedia.org))\n" . . . . "2009-04-03T10:13:13"^^ . "{{Include page=\"/Projects/DLLearner/Menu\" divclass=\"floatbox\" nomark=\"1\"}}\n==First Steps==\n\n * to run the father example:\n * ./dllearner examples/father.conf in Linux and other systems\n * dllearner.bat examples/father.conf in Windows\n * If you see Male AND hasChild some Thing (or something similar) as solution, then DL-Learner is working.\n\nWe recommend to read the ((http://dl-leaner.org/files/dl-learner.manual.pdf manual)) when using DL-Learner for the first time.\n" . . . . "2009-02-18T13:34:41"^^ . "{{Include page=\"/Projects/DLLearner/Menu\" divclass=\"floatbox\" nomark=\"1\"}}\n==Installation==\n * ((http://www.java.com Java)) version 6 or higher needs to be installed\n * download ((http://sourceforge.net/project/showfiles.php?group_id=203619 DL-Learner))\n * extract DL-Learner\n * run dllearner.bat (Windows) or dllearner (other systems) and give it one of the conf files (in the examples directory) as argument, e.g. \"./dllearner examples/father.conf\"\n * more infos can be found in the DL-Learner README and INSTALL files\n\nFor instructions on installing the DL-Learner web service, see the wiki page on ((WebServiceInstallation Web Service Installation)).\n\n%%(comments //optional:// download and install a DIG compatible reasoner like Pellet, ~FaCT, Racer Pro, and ~KAON2 (see ((ReasonerInstallation Reasoner Installation)) for details) - you can also use the OWL API reasoner interface, which uses Pellet by default and doesn't require any further download )%%" . . . . "2010-12-17T14:36:19"^^ . "==Publications==\n\n~BibTeX entries for all AKSW publications can be found at ((http://www.bibsonomy.org/user/aksw Bibsonomy)).\n\n%%(exhibit jsonp=\"http://docs.aksw.org/BibsonomyProxy/exhibit-proxy.php?suffix=user/aksw/group_aksw&callback=cb\")\n\n
\n
Navigation
\n\n\n\n\n\n\n
\n\n
\n\n

\n\n :\n\n\n\n(Editors: )\n\n\n\nlink\n\n

\n\n\n%%\n" . . . . "2007-02-06T11:58:29"^^ . "===Elastic Web Application Cloud===" . . . . "2007-02-08T21:53:38"^^ . "==Semantic Media Wiki==\nAgile collaboration for widely distributed Document Management\nCollaborative creation of ontologies/taxonomies for document/content annotation\n\n===Target Outcomes===\n\n**Large-scale European-wide digital libraries with innovative access services that support communities of practice in the creation, interpretation and use of cultural and scientific content, including multi-format and multi-source digital objects. They should be combined with robust and scalable environments which include semantic-based search capabilities and essential digital preservation features. Particular attention is given to** costeffective digitisation processes and to the **use of digital resources in multilingual and multidisciplinary contexts.**\n\n====Workpagages====\nMethodology\n\nMultilinguality\n\nSemantic Media Management Wiki\n\nProvenance/Trust and Access Controll\n\nLearning of DL-Ontologies for Document Annotation/Description\n\nUse-case: Media archive RBB (Rundfunk Berlin Brandenburg)\n\nUse-case: Slavonic Church Documents" . . . . "2007-03-27T15:37:27"^^ . "==SABRE Conference on Social Semantic Web (CSSW 2007)==\nThe concept of Social Software was coined to characterize a variety of software and services on the Web, which enable new ways of communication and exploit social interactions for creating large content bases from a multitude of user contributions. The Semantic Web is a extension of the current Web aiming at enhanced search and navigation facilities and at integrating information from multiple sources. A question at the moment actively discussed in conference panels, visionary papers and project proposals is how the different approaches Social Software and Semantic Web can be combined in a synergetic way. \n\nCSSW will provide a podium for the rapidly emerging field of approaches aiming at exploiting Social Software concepts for the bootstrapping of the Semantic Web and lifting Social Software to the semantic collaboration level. CSSW aims at combining three different perspectives on the Social Semantic Web: the business and entrepreneurial perspective focusing the added value of specific social semantic web applications, the technical perspective enables and supports the exploitation of the \"ant intelligence\" of social networks and last but not least the social perspective, which explores motivations, benefits and emergent effects. CSSW targets to bring these three perspectives together, to widen existing horizons, to create novel ideas and to find new ways of understanding this emerging field. \n\nCSSW is supported by the following organizations and projects:\n#||\n||\n<# #>\nGI-Fachgruppe Methoden und Werkzeuge zur Entwicklung interaktiver Systeme (INSYDE)|\n<# #>\nLeipziger Informatik Verbund|\n<# #>\nProject, funded by ~BmBF as part of the research initiative “Software Engineering 2006”\n||\n||#\n\nPlease also have a look at the ((http://www.sabre-conference.eu/ SABRE (Software, Agents, and Services for Business, Research, and E-Sciences) website)) for further information.\n\n===Invited Talk===\n((http://www.openlinksw.com/blog/~kidehen Kingsley Idehen)) will give an invited talk on \"Hello Data Web - Exposing the Data Web\". Kingsley is Founder, President and CEO of ((http://www.openlinksw.com OpenLink Software)), a leading provider of high-performance Universal Data Access, Data Integration, Hybrid Database Engine technology and developer of the ((http://en.wikipedia.org/wiki/Virtuoso_Universal_Server Virtuoso Server)). With his entrepreneurial experience, his contributions to the technical foundations of the future Web and his backing of the Open Data initiatives he ideally combines the different perspectives on the Social Semantic Web.\n\n===Topics of Interest===\nCSSW covers all topics related to Social Semantic Collaboration (SSC) in Web based environments. Typical topics of interest include (but are not limited to):\n\n**Economic / Entrepreneurial Perspective**\n * Business aspects of SSC\n * Economies of \"attention\" for semantic collaboration\n * Business models for SSC\n * Models measuring costs/benefits of SSC\n * Authentication, authorization and accounting - policies, charging and billing models for social software\n * Experimental use cases involving social software in areas of telecommunications, dating, recruitment, eTourism, eBusiness, eGovernment, etc.\n\n**Technical Perspective**\n * Applying Social Software strategies such as tagging, mashups for SSC\n * Semantic Data Web: browsers and end-points\n * Extracting semantic content from existing information sources, e.g. Wikipedia\n * Collaborative, community-driven ontology construction\n * Combining existing ontologies and schemata, social ontology sharing and matching techniques\n * Reasoning supporting adaptive semantic collaboration, e.g. Description-Logic-Learning\n * Storage, inference and caching for scalable SSC\n * Exposing and interconnecting Web-APIs as light-weight Semantic Web Services\n * Social Semantic Web and Mobile services\n * User-interface components, template languages supporting SSC \n\n**Social Perspective**\n * Analysis, visualization, presentation of social networks\n * Approaches combining Social Software & Semantic Web\n * Group management, presence, social interaction enablers in mobile service platforms\n * Strategies for implementing architectures of semantic participation\n * Trust and privacy issues in social software\n * Implementation of gratification and reward systems\n * Quality analysis of socially generated semantic content\n * Analysis of motivations and behavior of social software users\n * Knowledge acquisition and ontology management in SSC\n * Analysis of emergent effects within social software\n\n===Submission types===\nAuthors are invited to submit original papers. \n * Research papers - maximum 10 pages\n * Posters - 4 pages\n * Demos - 4 pages\n\nPapers for submissions should be formatted according to ((http://www.gi-ev.de/fileadmin/redaktion/2005_LNI/PDF/LNILaTeX-Vorlage.zip GI-LNI style)) and submitted in PDF format. Submission details will be announced here shortly.\nAll papers will be published in ((http://www.gi-ev.de/service/publikationen/lni/ Lecture Notes in Informatics (LNI))). Best papers from CSSW 2007 will be considered for revision, extension, and publication in a special issue of the Journal of Online Engineering.\n\n===Dates and Conference Format===\n**Paper, demo, poster submission: June 1st**\nThe submission deadline is strict, no extensions will be given.\n\nNotification of acceptance: July 25th\n\nConference: September 26-28th \n\nCSSW will be a two day conference with possible accompanying workshops:\n * First day / 26th: 3 research paper sessions, demo and poster session\n * Second day / 27th: invited speaker, 2 research paper sessions, concluding panel discussion\n * Third day / 28th: workshops\n\nPaper acceptance is strictly limited to maximum 18 research papers. Additionally, poster and demo submissions are possible.\n\n===Committees===\n**Conference Organizers**\n((http://www.informatik.uni-leipzig.de/~auer/ Sören Auer)), Universität Leipzig, Germany and University of Pennsylvania, USA\n((http://bizer.de Chris Bizer)), FU Berlin, Germany\n((http://wi.uni-potsdam.de/homepage/potsdam.nsf?Open&ID=2329CF98EDE2BBCBC125710F00396936&Key=&Sel=&Lang=de Claudia Mueller)), Universität Potsdam, Germany\n((http://www.ee.surrey.ac.uk/Personal/A.Zhdanova/ Anna V. Zhdanova)), University of Surrey, UK\n\n**Program Committee**\n((http://sw.deri.org/~jbreslin/ John G. Breslin)), DERI, Ireland\n((http://dme.uma.pt/jcardoso/ Jorge Cardoso)), University of Madeira, Spain\n((http://richard.cyganiak.de/ Richard Cyganiak)), FU Berlin, Germany\n((http://www.l3s.de/~diederich Jörg Diederich)), L3S, Germany\n((http://bis.informatik.uni-leipzig.de/SebastianDietzold Sebastian Dietzold)), Universität Leipzig, Germany\n((http://www.wim.uni-koeln.de/Dr-Kai-Fischbach.23.0.html Kai Fischbach)), Universität Köln, Germany\n((http://tilab.com Walter Goix)), Telecom Italia, Italy\n((http://sw.deri.org/~aharth/ Andreas Harth)), National University of Ireland, Ireland\n((http://kmi.open.ac.uk/people/tom/about/html Tom Heath)), Open University, UK\n((http://web.iwi.unisg.ch/org/iwi/iwi_web.nsf/wwwTeamGer/HeideckeFlorian.htm Florian Heidecke)), Universität St. Gallen, Switzerland\n((http://www.vakantieland.nl Ceriel Jacobs)), Vakantieland, The Netherlands\n((http://www.kunsan.ac.kr/english/ Dongwon Jeong)), Kunsan National University, Korea\n((http://www.intelligent.pe.kr Jason J. Jung)), Inha University, Korea\n((http://www.t-systems-mms.com Berit Jungmann)), T-Systems MMS, Germany\n((http://www.aifb.uni-karlsruhe.de/Personen/viewPersonenglish?id_db=2107 Markus Krötzsch)), AIFB - University of Karlsruhe, Germany\n((http://bis.informatik.uni-leipzig.de/JensLehmann Jens Lehmann)), Universität Leipzig, Germany\n((http://pipek.uni-siegen.de/ Volkmar Pipek)), Universität Siegen, Germany\n((http://www.polleres.net Axel Polleres)), Universidad Rey Juan Carlos, Spain\n((http://bis.informatik.uni-leipzig.de/ThomasRiechert Thomas Riechert)), Universität Leipzig, Germany\n((http://www.minet.uni-jena.de/~sack Harald Sack)), Hasso Plattner Institut, Germany\n((http://www.dfki.uni-kl.de/~sauermann Leo Sauermann)), DFKI, Germany\n((http://www.schaffert.eu Sebastian Schaffert)), salzburgresearch, Austria\n((http://www.bamberg-gewinnt.de/wordpress/lebenslauf-und-aktivitaten/buch-weblogs/ Jan Schmidt)), Bamberg, Germany\n((http://www.t-systems-mms.com Frank Schönefeld)), T-Systems MMS, Germany\n((http://user.uni-frankfurt.de/~chris/ Christian Stegbauer)), Goethe-Universität, Frankfurt, Germany\n((http://www.comp.lancs.ac.uk/~strohbach Martin Strohbach)), NEC Europe, Europe\n((http://www.seco.tkk.fi/u/kimvilja Kim Viljanen)), Helsinki University of Technology, Finnland\n((http://jakobvoss.de Jakob Voss)), Wikimedia e.V., Germany\n((http://www.interactivesystems.info Jürgen Ziegler)), Universität Duisburg-Essen, Germany\n\nto be completed.\n%%(comments)\nSocial\n((http://blog.mathemagenic.com Lilia.Efimova)) Lilia.Efimova@telin.nl\nvolkmar.pipek@uni-siegen.de\nstegbauer@soz.uni-frankfurt.de\n jan.schmidt@bnv-bamberg.de\n\n\nTechnical\n Harald.Sack@hpi.uni-potsdam.de\n((http://www.cs.vu.nl/~pmika/ Peter Mika)) pmika@cs.vu.nl\n andreas.harth@deri.org\n axel.polleres@urjc.es\n((http://kmi.open.ac.uk/people/domingue John Domingue)) j.b.domingue@open.ac.uk\ndiederich@l3s.de \n((http://www.comp.lancs.ac.uk/~strohbach Martin Strohbach @ NEC Europe)) Martin.Strohbach@netlab.nec.de\n(( Walter Goix @ Telecom Italia)) laurentwalter.goix@telecomitalia.it\n((http://webode.dia.fi.upm.es/Asun/Asun.html Asunción Gómez-Pérez)) asun@fi.upm.es\n((http://www.isi.edu/~timc Timothy Chklovski)) timc@isi.edu\n j2jung@intelligent.pe.kr\n((http://www.stefandecker.org Stefan Decker)) Stefan.Decker@deri.org\n\nEconomical\nfischbach@wim.uni-koeln.de\nFlorian.Heidecke@unisg.ch\n((http://fbstaff.cityu.edu.hk/iscw Christian Wagner)) fbcw@cityu.edu.hk\n\n%%\n\n===Related Events===\n\n((http://www.i-semantics.tugraz.at/ I-SEMANTICS '07)) International Technology Conference, 5th - 7th of September 2007 in Graz, Austria.\n\n((http://semanticscripting.org/SFSW2007/ 3rd Scripting for the Semantic Web)) at June 6th, European Semantic Web Conference (ESWC 2007) in Innsbruck, Austria.\n\n((http://km.aifb.uni-karlsruhe.de/ws/ckc2007/ Workshop on Social and Collaborative Construction of Structured Knowledge)) at 16th International World Wide Web Conference (WWW2007) Banff, Canada, May 8, 2007.\n\n((http://www.semanticdesktop.org/xwiki/bin/view/SemanticDesktopWS2006/ Semantic Desktop and Social Semantic Collaboration Workshop)) at the International Semantic Web Conference, 5 November 2006, Athens, GA, USA\n\n2nd Workshop on Semantic Wikis: WibKE2006: Wiki-based Knowledge Engineering at WikiSym 2006 - International Symposium on Wikis, August 21-23, 2006, Odense, Denmark\n\nSemWiki2006 - From Wiki to Semantics at European Semantic Web Conference (ESWC 2006)\n\n1st International Workshop on Semantic Technologies in Collaborative Applications STICA 06 at 15th International Workshops on Enabling Technologies: Infrastructures for Collaborative Enterprises.\n\n((http://lsdis.cs.uga.edu/~aleman/efw2007/ 1st International ExpertFinder Workshop)), 16 January 2007, Berlin, Germany." . . . . "2009-11-16T13:24:43"^^ . "==Projects==\n((/projects/SoftWiki SoftWiki))\n((/projects/Powl Powl))\n((/projects/OntoWiki OntoWiki))\n((/projects/DLLearner DL-Learner))\n((/projects/R2D2 R2D2))\n((/projects/LDAP Semantic LDAP))\n((/projects/Atuin ATUIN))\n((/projects/xOperator xOperator))\n((/projects/odfmi od@fmi))" . . . . "2010-07-05T14:36:12"^^ . "{{Include page=\"/Projects/OntoWiki/Menu\" divclass=\"floatbox\" nomark=\"1\"}}\n ATTENTION: THIS PAGE IS OUTDATED - FOR A CURRENT VERSION, HAVE A LOOK AT http://code.google.com/p/ontowiki/wiki/CommandLineInterface\n==Command Line Interface (owcli)==\nThe OntoWiki Command Line Interface (##owcli##) is a php-based command line tool to administrate and manipulate OntoWiki Knowledge Bases.\n\n{{toc}}\n\n===Installation===\nInstall a command line php5 and pear (on debian/ubuntu: ##sudo apt-get install php5-cli php5-pear##).\nInstall required pear packages (on debian/ubuntu: ##sudo pear install Console_Getargs Config##).\nDownload, Install and configure the OntoWiki Command Line Interface:\n%%\nsvn co https://powl.svn.sourceforge.net/svnroot/powl/trunk/owcli owcli\ncd owcli\ncp owcli.php /usr/local/bin/owcli && chmod a+x /usr/local/bin/owcli\ncp Subscription.php /usr/local/bin/\ncp owcli.1 /usr/local/man/man1/\ncp dot.owcli ~/.owcli\nvi ~/.owcli\n%%\n\n===Examples===\nSet the variable OWMODEL (to change the default model): \n##export OWMODEL=\"\"http://localhost/model1#\"\" ##\n\nDrop a model (delete statements, popularities, etc.): \n##owcli -m \"\"http://localhost/model1#\"\" --drop##\n\nCreate a new Model and add tripels from a file:\n##owcli -m \"\"http://localhost/model1#\"\" --create --add -i model.rdf##\n\nCreate a new Model and add tripels from a mapping (hint: use the variable ##OWMODEL## so you dont need ##-m## everytime):\n##export OWMODEL=\"\"http://localhost/model1#\"\"; owcli --map Mapping.n3 | owcli --create --add##\n\nExport the default model, put it to cwm and add the inferred statements from the rule file:\n##owcli --export | cwm --rdf --n3 --filter=Rules.n3 --rdf | owcli --add##\n\nGeocode all values of the foaf:based_near attribute in the default model and add it to the default model:\n##owcli -d --geocode \"\"http://xmlns.com/foaf/0.1/based_near\"\" | owcli --add##\n\n{{a name=\"sub\"}}\n===Subscriptions===\nTo be able to use the update-subscriptions option you have to subscribe to at least one content resource. Content resource means any document holding information in RDF, N3, N-Triples or xhtml containing RDF. Subscribing is managed by storing information regarding this resource in a certain (or any other) model in your Onto Wiki installation. \n\nFor a simple example just download ((http://powl.svn.sourceforge.net/viewvc/*checkout*/powl/trunk/models/Subscriptions/example.rdf this)) file and import it into your Onto Wiki:\n##owcli --create --add -i example.rdf -m \"\"http://ns.ontowiki.net/Subscriptions/\"\" ##.\n\nAfter that you can update this subscription:\n##owcli -us -m \"\"http://ns.ontowiki.net/Subscriptions/\"\"##.\n\nYou can check the result:\n## owcli -l ##\nThe name of the example model \"\"http://ns.ontowiki.net/Subscriptions/exampleModel\"\" should occur in the list now.\n\nThe mandatory attributes for a subscription are: \n * storeModel - where to store the subscribed information \n * updateInterval - in minutes\n * updateModus - ##new## or ##add##, while ##add## means that any information is just added to the model and ##new## means old information is deleted first.\n\nThe optional attribute is:\n * query - where you can specify a SPARQL-CONSTRUCT-query to select certain information from the content resource to be stored into the model.\n\n===Parameters===\n##-w --wiki=## - Set OntoWiki database which should be used (default is ##default## or the value of the environment variable ##OWWIKI##)\n##-m --model=## - Set model which should be used (default is ##\"\"http://localhost/SysOnt/0.1#\"\"## or the value of the environment variable ##OWMODEL##)\n##-i --input=## - input model file (- for STDIN) (default is STDIN)\n##-o --output=## - output model file (- for STDOUT) (-)\n##-l --list## - List models from a specific OntoWiki database\n##--create## - Creates a new model\n##--drop## - Deletes the model\n##--export## - Exports the model\n##--empty-cache## - Empty the model cache only\n##--empty-popularity## - Empty the model popularity only\n##--empty-ratings## - Empty the model ratings only\n##--empty-namespaces## - Empty the model namespaces only\n##--add## - Adds all statements from input to the model\n##--geocode=## - Outputs a model with geocoded (address) values from a given datatype property\n##--map## - Takes a D2RQ mapping model in N3 from input and outputs the mapped model in RDF/XML\n##-us --update-subscriptions## - Update all subscriptions\n##-c --config=## - Set a config file (default is ~/.owcli or the value of the environment variable ##OWCONFIG##)\n##-d --debug## - Output some debug infos\n##-q --quiet## - Do not output info messages\n##-h --help## - Show help screen\n" . . . . "2007-03-13T13:23:56"^^ . "{{toc divclass=\"floatbox\" to=\"h3\"}}\n==Google Summer Of Code==\nThe workgroup AKSW with its ~OntoWiki project is participating in the ((http://code.google.com/soc/ Google Summer Of Code )) and is looking for students to contribute. We are looking for enthusiastic students (see ((http://code.google.com/support/bin/topic.py?topic=10727 SoC student requirements))) with a solid knowledge of PHP, who are interested in Semantic Web, Agile Knowledge Engineering and Folksonomy and Social Software Apps. \n\n===About AKSW===\nAKSW is leading several large open-source and community projects in the context of the upcoming Social Semantic Web:\n * ((projects/Powl Powl)) is an development framework for Semantic Web applications used in many industrial and research applications. Powl has a strong developer and user community (it is currently downloaded over 200 times per month with a strong increasing tendency).\n * ((projects/OntoWiki OntoWiki)) (demo at http://3ba.se/screencast) is our next generation social collaboration tool for the Semantic Web based on Powl. ~OntoWiki is used in many domains aiming at supporting social semantic collaboration.\n * ((http://dbpedia.org dbpedia.org)) is a community effort (co-led by AKSW and partially based on Powl/~OntoWiki) to extract structured information from Wikipedia and to make this information available on the Web. dbpedia.org gains at the moment enormous attention (e.g. in ((http://radar.oreilly.com/archives/2007/03/different_appro_1.html Tim O'Reilly's Radar))), since the extracted datasets allow the answering of previously not easily answerable questions (see http://wikipedia.aksw.org) and creation of semantic Mashups based on Wikipedia knowledge.\nIn addition to that the AKSW workgroup is embedded in the Semantic Web and research community. For example, we organize the yearly ((http://semanticscripting.org/SFSW2007/ workshop on Scripting for the Semantic Web)) and this year AKSW will host the first ((http://aksw.org/cssw Conference on Social Semantic Web)) in Leipzig.\n\n===Why work on ~OntoWiki?===\n~OntoWiki is a next generation, social knowledge engineering tool for the Semantic Web. It is downloaded monthly over 200 times and used for knowledge engineering applications in science (e.g. for the development of bio-medical ontologies), industry (as a tool for developing semantic web business applications) and for virtual organizations and online communities. You can find more information on ~OntoWiki on ((Projects/OntoWiki our project overview page)) or at the ((http://sf.net/projects/powl Sourceforge project page)). Since in the field of the Semantic Web there is still a lack of demos and applications clearly showing its benefits, we have the vision that Powl/~OntoWiki could be the nucleus of a healthy eco-system of open-source applications and mashups integrating the social \"ant-intelligence\" dimension into the Semantic Web.\n\n===Dates===\n * 05.03.2007 - 12.03.2007: Mentor Application\n * 14.03.2007 - 23.03.2007: Student Application\n * Summer 2007: Coding and communicating\n * 26.09.2007 - 27.09.2007: Conference on Social Semantic Web including GSoC track\n\n===GSoC track at CSSW===\nDespite the advantages of online communities and Internet communication it is sometimes important to meet in person. In the end of September we are organizing a conference on ((http://aksw.org/cssw Social Semantic Web)) in Leipzig. It will include scientific paper presentations, demos, posters, social events and keynote talks by senior scientists, business people and entrepreneurs. The central persons of the open-source communities around Powl, ~OntoWiki and dbpedia.org will attend the conference and we would like to use the chance to also invite all successful GSoC participants we mentored to meet each other and to present their projects in a special GSoC demo session. The conference fee for students will be very low (Euro 10) and additionally we will try to acquire travel funds for the GSoC students mentored by us.\n\n===Project Ideas===\nIn the following we collected some ideas for GSoC projects which will support the technologies and approaches we are working on. However, we will be happy to mentor every project with relations to Social Software, the Semantic Web or PHP based Web applications in general. Feel free to describe your project idea!\n\n====Expose Web 2.0 APIs as Semantic Web Services====\nOther than Web Services Javascript APIs as well as JSON and REST interfaces are widely deployed on the Web (see ((http://programmableweb.com))). However, new applications on the basis of those could be much simpler developed, if inputs and outputs of the function and method calls would be uniquely identified. This would allow to automatically compose existing Web 2.0 APIs resulting in completely new Web 2.0 mashups. A Javascript application is envisioned allowing the annotation of inputs and outputs of APIs function and method calls as well as their dynamic composition. For example the result of DBPedia query for birthplaces of people born in Germany the 18th century could be combined with information from Geonames returning geo-coordinates and finally mapped using a map API (such as Yahoo or Google maps).\n**Tags:** Web 2.0 APIs, mashups, Javascript, Semantic Web Services\n**Mentor:** SoerenAuer\n\n====~OpenID Service====\nAs a tool for knowledge engineering, OntoWiki can also used for the management of account information. The idea is about the integration of an ((http://en.wikipedia.org/wiki/OpenID OpenID)) server for providing identification and authentification service against the managed RDF model.\n**Tags:** OpenID, PHP, OntoWiki, RDF\n**Mentor:** SebastianDietzold\n\n====Reasoning Integration====\nOWL ontologies have a formal semantics, which allows to infer implicit information from ontologies. This process is called reasoning. There are several different reasoning possibilities e.g. finding out whether an ontology contains contradictions, finding all instances of a given class, or infering a hierarchy of all classes in an ontology. Since OWL (more specifically its most prominent variant OWL DL) is based on Description Logics, there are several different efficient and highly-optimised reasoners available (((http://www.cs.man.ac.uk/~sattler/reasoners.html list of reasoners))).\n\n//Although reasoning procedures have been investigated in depth and several OWL reasoners exist, there have been very few efforts to use reasoning in web applications.// We want to extend ~OntoWiki with powerful reasoning procedures. Technically, this will be realised by implementing an ~OntoWiki DIG client. ((http://dl.kr.org/dig/ DIG)) is an interface to communicate with Description Logics and OWL reasoners, which is supported by all popular reasoners. This allows to use all DIG capable reasoners within ~OntoWiki.\n**Tags:** OWL, PHP, OntoWiki, Description Logic\n**Mentor:** JensLehmann\n\n====~OntoWiki-Exhibit Integration====\n((http://simile.mit.edu/exhibit/ Exhibit)) is a lightweight structured data publishing framework that lets you create web pages with support for sorting, filtering, and rich visualizations by writing only HTML and optionally some CSS and Javascript code. The content created within ~OntoWiki could be easily represented in Exhibit.\n**Tags:** Exhibit, Javascript, PHP, OntoWiki, RDF\n**Mentor:** SoerenAuer\n\n====Instance Based Learning of Classes====\nWhile the benefits of using ontologies are now well understood, their creation and maintenance is still a burdensome task. Knowledge engineers need more powerful tool support to evolve and manage ontologies. One of the main objectives of our research is to develop learning tools, which aid the knowledge engineer by suggesting modifications of an ontology in an automatic or semi-automic way. The usage of these tools will ensure that the developed ontologies will be consistent and have the desired semantics. Additionally, we want to offer support for data analysis and data mining in ontologies to reveal interesting and beneficial information about the relation of elements within an ontology.\n\nWe aim to integrate our learning tool in ~OntoWiki, thereby building a bridge between Artificial Intelligence algorithms and end user applications. Our goal is that the user will be able to learn (possibly complex) definitions of new classes just by selecting some objects in the ontology, which should belong to the new class (positive examples), and other objects, which should not belong to the new class (negative examples). This helps knowledge engineers to construct ontologies even if they are not OWL experts.\n**Tags:** OWL, PHP, OntoWiki, Description Logic\n**Mentor:** JensLehmann\n\n====DBPedia Query Builder and Browser====\n((http://dbpedia.org dbpedia.org)) is a community effort to extract structured information from Wikipedia and to make this information available on the Web. dbpedia allows you to ask sophisticated queries against Wikipedia and to link other datasets on the Web to Wikipedia data. Currently, the DBPedia extraction contains more than 40M RDF triples. A prototype for querying these is available at http://wikipedia.3ba.se. This should be revised and extended to allow non expert users to query the DBPedia extraction and to store, tag, categorize and annotate existing queries.\n**Tags:** PHP, JavaScript, OntoWiki, Wikipedia\n**Mentor:** SoerenAuer\n\n====Mapping of Relational Databases====\n((/Projects/R2D2 R2D2)) is an interpreter for the ((http://sites.wiwiss.fu-berlin.de/suhl/bizer/D2RQ/spec/ D2RQ Mapping Language)) and based on RAP, the RDF API for PHP. The idea is to expand the ~OntoWiki backend layer so that it is possible to interpret mapping models and access a virtual model which is mapped from a relational database.\n**Tags:** PHP, SQL, OntoWiki, Databases\n**Mentor:** SebastianDietzold\n\n====Personal Knowledge Management====\n~OntoWiki is primarily used for collaborative knowledge engineering. We want to extend ~OntoWiki for Personal Knowledge Management in the Semantic Web.\n**Tags:** PHP, OntoWiki, Personal Information Management, RSS, FOAF, iCal\n**Mentor:** SebastianDietzold\n\n====Design of a new ~OntoWiki core theme====\nOntoWiki is in dire need of more graphical design talent... and the goal of SoC is to involve more people in open source. Designers can be a part of that. Not only will you need to design a modern, pleasing, eye-catching and flexible design, you'll also have to implement it in HTML/CSS. A generic OntoWiki theme needs to be flexible enough to accomodate a wide variety of content and user interfaces. It needs to be accessible and structured, and preferably have clean markup.\n**Tags:** HTML, CSS, OntoWiki, Graphic Design\n**Mentor:** ThomasRiechert\n\n====Collaborative Requirements Engineering====\nStakeholders have to work in a collaborative environment to find out requirements for Software-Systems (this is also true for other domains). Typically, this involves meetings and discussions. Therefore, the number of involved stakeholders is usually limited (for reasons of efficiency). ~OntoWiki may be used as the foundation for a tool to enable a large number of spatially distributed stakeholders to take part in this process. The tool will be based on an OWL requirements model.\n**Tags:** PHP, OntoWiki, Requirements Engineering, OWL\n**Mentor:** ThomasRiechert\n" . . . . "2007-03-09T16:33:06"^^ . "==Google Summer of Code 2007==\nThe ~OntoWiki project is participating in the ((http://code.google.com/soc/ Google Summer Of Code )) and is looking for students to contribute. We are looking for enthusiastic students (see ((http://code.google.com/support/bin/topic.py?topic=10727 SoC student requirements))) with a solid knowledge of PHP, who are interested in Semantic Web, Agile Knowledge Engineering and Folksonomy and Social Software Apps. \n\n((../SummerOfCode Implementation Ideas))\n\n===Student Application Form===\n{{gsocform}}" . . . . "2007-05-18T14:46:32"^^ . "==RWT: RDF/OWL-Web-Template-Engine==\nA template-engine for Semantic Web applications.\n\n{{toc from=h2 to=h4}}\n\n===Download==\nThe current version is available at the ((http://powl.svn.sourceforge.net/viewvc/powl/trunk/rwt/ Sourceforge-SVN))\n\n===Installation==\nRequirements: \npowl has to be installed\nPHP Version >= 5.2\n\nTo use the RWT you have to do this:\n%%(php)\nload_Template(\"../templates/example1.rwt\", \"../data/PeriodicTable.owl\", true); # Load the Template\n?>\n%%\n\n===Tutorial==\n\n====Basic structure of the RWT-files====\nThe RWT-files contain a fragment of a HTML-file with some additional ####-tags to start queries, these tags can also be nested and some command-lines enclosed by { } to edit or just print out the data as HTML-code\n\nIt is also possible to insert php-code in the template by using #### (like in a normal php-script)\n\nThe RWT-command-lines(##{...}##) can appear theoretically almost everywhere in the template, but not in the php-code\n(there they will treated as normal php-code and will probably cause an error) and \nwithin a ####-tag only in the attribute-strings: i.e. ##xml:lang = \"{ $language }\"## or ##limit = \" {$offset } { $count }\"##\n\n====Description of the ##load_Template##-function====\n##load_Template( $filename , $default_source = \" \", $load_post_get_vars = false)##\n\nfilename - name and path of the template-file\n(optional) default_source can be an RDF/OWL-model-object, name of a powl-model, a web-address or path/filename to an RDF/OWL-File it will be the default-source in the templates, replaces eventually an other default-source\n\n(optional) ##$load_post_get_vars## - if true, then the content of the _POST/_GET - array can be used as variables inside the templates\n\narray-keys considered as variable-names, if there are already variables with the same name, they will be replaced\n\n====Structure and function of the ####-tag====\n%%(html)\n\n...\n\n%%\n\nAt the position of this tag, the query stored in the ##query## attribute will performed immediately on the given source in the language given by the ##language## attribute. The results of the query can be filtered by using the ##xml:lang##, ##rdf:datatype##, ##distinct## and the ##limit## attribute. The behavior can controlled by the ##debug## and the ##loop## attribute.\n\n#|| \n|| **attributes** | **Description** ||\n||//source//|filename or URI\nRDF/OWL-source if there is a default-source given and you want to query the default-source then the attribute 'source' is not necessarily||\n\n||//language// | \"triple\" or \"sparql\"\n\"triple\" is the default-query-language, so you want to use this language then this attribute is not necessarily||\n\n|| //query// | The query, which you want to do\nif the language is \"triple\" , it has this format: $subject $predicate $object\nif the language is \"sparql\", it must be a valid sparql-query-string\ndefault: \"?subject ?predicate ?object\" - get all triples of the given model||\n\n|| //xml:lang// | if some of the data has an language-flag ,which should be taken? i.e. \"de\", \"en\", \"nl\" etc.\ndefault: empty||\n\n|| //rdf:datatype// | URI + dataytpe ( integer, float etc.) or namespace-prefix:datatype\ndefault: empty||\n\n|| //debug// | if \"on\" shows some more error-messages, if an error occur. \"off\" is default||\n\n|| //distinct// | \"all\" - all complete datasets in the query-results are unique\n\"variable_name1, variable_name2, ...\" - the values of the given\nvariable-combination are unique\ndefault: empty||\n\n|| //limit// | \"count\" - how many values are needed (at most)\n\"offset count\" - how many values are needed (at most) from the given \noffset, if 'offset' + 'count' > number of values then the returned number of values will be less then 'count'\ndefault: empty||\n\n|| //loop// | \"on\"/\"off\" - \"on\" is default\n\"on\" - for each returned dataset from a query the source-code between the current -tag and\nthe respective will be repeated and the variables filled by the query-result contain only the values of the current dataset\n\"off\" - the ...- block will not repeated and the variables filled by the query-result contain an array of all respective values in the datasets ||\n||# \n\n====First Steps with the RWT====\n=====A simple example=====\nTo initialize the RWT-classes and to load a Template we need a php-script:\n%%(php)\n\n\n \n A Simple Example for RWT\n \n \nload_Template(\"../templates/example1.rwt\", \"../data/PeriodicTable.owl\", true);\n?>\n\n%%\n\nThe file ##\"\"PeriodicTable.owl\"\"## contains data we want to query and ##example1.rwt## is our template-file, it contains following code:\n%%(html)\n

Element: { $elements }

\n%%\n\n##\"\"PeriodicTable.owl\"\"## contains information about some chemical elements the information block for every element is an instance of the class ##Element## in the namespace ##\"\"http://www.daml.org/2003/01/periodictable/PeriodicTable#\"\"##.\n\nOur template just prints out the name of every element listed in this file (actually URI+element-name) the ####-tag contains the query that is necessarily to get this information.\n\nThe query is:\n%%prefix table: http://www.daml.org/2003/01/periodictable/PeriodicTable#>\n$elements rdf:type table:Element’%%\n\nOur source is ##\"\"PeriodicTable.owl\"\"## but since we already have set this file as the default-source by passing its to the function ##load_Template## we don’t need the attribute.\n\nThe code between #### and #### will repeated as many times as values were returned by the query and the variables defined by the query-result (here: ##$elements## ) contains in every iteration the current value. The generated HTML-code of our example looks like this:\n%%(html)\n

Element: http://www.daml.org/2003/01/periodictable/PeriodicTable#H

\n

Element: http://www.daml.org/2003/01/periodictable/PeriodicTable#He

\n...%%\n\nBut a line like: ##http://www.daml.org/2003/01/periodictable/PeriodicTable#H## doesn’t look readable for many people so we change the line ##{ $elements }## to ##{ $elements | cut_URI }## and it looks better. ##cut_URI## is a modifier and removes the namespace-URI or the prefix at the beginning of a string. For a description of modifiers look to paragraph ((#stdmodifiers Standard modifiers)).\n\n=====A little more complicated example=====\nNow we can list all elements but we want to know also the details about them We must make a query of every single element to get the properties and their values. So we can use nested ####-tags:\n%%(html)\n $elements rdf:type table:Element \" >\n
\n
\n

Element: { $elements | cut_URI }

\n
\n
\n \n \n \n { $property $value | trow }\n \n \n
\n
\n
\n%%\n\nThe first query is limited to 10 datasets for the result, and the 'distinct'-attribute we have set to \"all\" to make sure all datasets are distinctive. The query in the inner ####-tag (the 2nd tag) means: get all properties (stored in ##$property##) and values (stored in ##$value##) of all resources that are equal to the values of ##$elements##, in our case there is only one value at a time, this is the current element the line ##{$property $value | trow }## means: build a HTML table-row with the current values of the variables ##$property## and ##$value## as table column; ##trow## is another modifier.\n\nThe generated output is the a list of all element-names on the left side and for each element a table with detailed information on the right side.\n\n=====Sparql query-example=====\nWe take a part of the template-file ##example3.rwt##\n%%(html)\n \n { $property | cut_URI | $label }\n\n \n \n\n { $label $value | trow \"noempty\" \"align=\\\"left\\\" style='font-weight: bold'\" }\n \n
%%\n\nThe query in the first #### tag means: Get the value of certain properties (stored in ##$address_prop##) of a certain resource (stored in ##$selectedInstance##). The part after the ##;## is useful to list explicitly the properties again (and only these, for which the query was successful). The quotes before the { and } are necessarily, because without it the RWT-parser treated it as a RWT-command-line and it will cause an error.\n\nWith the command-line ##{ $property | cut_URI | $label }##, we assign the shortened value of $property to the variable ##$label##. The 2nd query is to obtain the label for the current property, by setting the ##xml:lang##-attribute we set the language filter for the label (possible here: ##nl## or ##en##). If this inner query fails (because there is no label in a certain language for that property) the value of the variable ##$label## is not changed. So we would still have a valid value to work with.\n\nThe line ##{$label $value | trow \"notempty\" \"align=\\\"left\\\" style='font-weight: bold'\" }## builds a table-row.\n\nFor more a detailed information of the SPARQL-query-language see here:\nhttp://www.w3.org/TR/rdf-sparql-query/\nhttp://www.dajobe.org/2005/04-sparql/SPARQLreference-1.8.pdf\nhttp://www.xml.com/pub/a/2005/11/16/introducing-sparql-querying-semantic-web-tutorial.html\n\n====='Minimum-query' example=====\nIf the ##triple##-queries and the sparql-queries are still to complicated, then we can use the ##->## operator: ##resource->property## (both ##resource## and ##property## can be a variable or a constant like ##foaf:name##).\nThe operator means: Get the values for the given property of the given resource.\n\nWe could do the last example also with:\n##{ $language | $DEFAULT_LANGUAGE }## - necessarily make the ##->##-operator to filter the languages of the labels\n##{ $address_prop->'rdfs:label' $selectedInstance->$address_prop | trow \"notempty\" \"align=\\\"left\\\" style='font-weight: bold'\" }##\n\nSpecial cases:\n##resource->*## gets the values of all properties of this resource\n##resource->?## gets all properties of this resource\n\n====Variables====\nVariables in the RWT can be strings, objects one-dimensional arrays of these datatypes\n\n=====Query-Results=====\nThe Results of each query are stored in ##$variables##. These variables are instances of the class ##Crwt_object##. Right now, these objects contain three variables: ##value##, ##language## and ##datatype##. ##language## means not the query-language, but the language of text in ##value##. If the values of any variables are printed or used for operations, only ##value## is used.\n\n=====Using external variables=====\nIf we want to use data from the php-script inside the templates then we uses the function ##set_var##:\n##$rwt->set_var( $var_name , $var_value );##\n\n##$var_value## can be a string, an object or an one-dimensional array with elements of these datatypes.\n\n=====Variable operations=====\nThese operators between variables are allowed so far:\n\n#||\n|| **Operation** | **Operator** | **Description** ||\n|| Difference | / | $var1 / $var2 removes all elements from var1, which \nalso elements of var2 ||\n|| Intersection | & | $var1 & $var2 removes all elements which are not elements of both var1 and var2 ||\n|| Merge | + | $var1 + $var2 merges all elements of both variables ||\n|| Query | -> | $var1 -> $var2 - performs a 'simple'-query (var1,var2 can also be constant values of the format: namespace-prefix:property)\nlook for the simple query -description ||\n|| Assignment | \"\"|\"\" | this operator is actually meant to pass values in the execution-pipe, but if an variable is part of the pipe then the operator is equal to an assignment ||\n||#\n\nInstead of ##$var1## or ##$var2##, it is also possible to use a string-constant enclosed in ##'...'##.\n\n=====Variable modifiers=====\nModifiers are used to change the value or the format(##cut_URI##, ##transform_URI##) of variable generate often used HTML-elements (##select_list##, ##trow##, ##set_links##) with the values of these elements.\nYou can build a modifier-pipe: ##{ $var1 $var2 | cut_URI | trow }##\nIf you put a variable name at the end of a pipe, then you make an assignment: ##{ $var1 | cut_URI | $var2 }##\nIf there is more than one source-variable, then the other variables will be ignored for the assigment.\n\n{{a name=\"stdmodifiers\"}}\n======Standard-modifiers======\nList and description of the standard-modifiers for the RWT:\n\n#||\n|| **Modifier** | **Description** ||\n|| //list// | just prints all values from the given argument ||\n|| //select// | creates a HTML-select-list\nhas one optional argument: a string that contains the name of this element in a HTML-Form without this argument the name 'select_list'+select-list-nr is default (select-list-nr is a internal counter) ||\n|| //set_links// | if the data is an internet- or email-address it creates a link .... ||\n|| //trow// | prints the data as table-rows value \nhas optional arguments: \n1. \"notempty\" or ''\n'' if \"notempty\" is set, all cells may not contain the empty string\n2.-n+1.: attribute-string for the -tags, where n is the number of cells in a row\nexample: { $var1 $var2 \"\"|\"\" trow \"\"|\"\" \"notempty\" \" style=\\\"font-weight: bold\\\" \" }\nthe text in the left column is written bold, and no cell may contain '' ||\n|| //transform_URI// | \"\"if data has the format \"namespace-URI/predicate\" then it changes the URI(if known) to the respective prefix\"\" ||\n|| //cut_URI// | \"\"if data has the format \"namespace-URI/property\" or \"prefix:property\" then it removes the URI or the prefix from the beginning of the data-string\"\" ||\n||#\n\n======Define your own modifier======\nTo define a modifier we use this function: ##$rwt->define_modifier( $modifier_name, $modifier_function, $modifier_class = NULL)##\n\n##modifier_name## - string\n##modifier_function$$ - string, if this function is a method of a class, ##modifier_class## may not be ##NULL##\n(OPTIONAL) ##modifier_class## - object, if != ##NULL## ##modifier_functionname## must be a method of this class\n\nThe ##modifier_function## needs at least two arguments: \n1st - a reference to the rwt-object, to have acces to some internal function like ##get_var_values##\n2nd - an array of values of RWT-variables\nIf you just want to print out the content of some variable, then you dont need to return any value.\n\nBut if you want to use the result of a modifier as input for another one or to assign a value to a variable then you must return these values in the same format as the 2nd argument, but with changed values of course.\n\nExample 1: This function just prints a table, a column for each variable in ##value_arr##:\n\n%%(php)\\n\";\n foreach ($value_arr as $column) {\n echo \"

\\n\";\n $i=0;\n foreach ($rwt->get_var_values($column) as $value) {\n if ($i>0) echo \"
\";\n echo $value;\n $i++;\n }\n echo \"

\\n\";\n }\n echo \"\\n\";\n}\n?>%%\n\nNow we define a modifier, using this function. You dont have to choose the same name for the modifier as for the function: ##$rwt->define_modifier( \"table\" ,\"table_func\");##\n\nNow we can use this modifier in a template: ##{ $var1 $var2 ... | another_table }##\n\nExample 2: This is the ##cut_URI## modifier that already is available in the RWT\n\nIt doesn’t print out anything, but changes the input-values and returns it with changed values.\n%%(php) $orig_value) {\n $temp = $rwt->get_var_values($orig_value);\n foreach ($rwt->RDF_prefixes_default as $prefix => $URI) {\n $pattern[] = '/^'.preg_quote( $prefix, \"/\").'[:](.*)/';\n $replace[] = '\\\\1';\n $pattern[] = '/^'.preg_quote( $URI, \"/\").'(.*)/';\n $replace[] = '\\\\1';\n }\n $temp = preg_replace( $pattern, $replace, $temp);\n $rwt->set_var_values( $columns[$key], $temp);\n }\n return $columns;\n}\n?>%%\n\nBecause this function is a method of the class ##Cmodifiers##, you need to pass an instance of this class along with the function-name to ##define_modifier##- \n\n##$this->rwt_modifiers = new Cmodifiers();##\n##$this->define_modifier( \"cut_URI\", 'cut_URI', $this->rwt_modifiers );##\n\n=====Standard variables=====\nThere are a couple variables already defined by the rwt-class. Because they're needed for some functions.\n#|| \n||variable-name | content||\n|| //THIS_FILE// | contains the value of the php-variable \"$_SERVER['PHP_SELF']\" ||\n|| //EMPTY// | '' ||\n|| //DEFAULT_LANGUAGE// | contains a language shortcut, like in the xml:lang-attribute of the -tag important only for the 'minimum'-queries\ndefault: '' ||\n|| //DEFAULT_DATATYPE// | contains the datatype-URI, like in the rdf:datatype-attribute of the -tag important only for the 'minimum'-queries\ndefault: '' ||\n ||#\n\n===RWT - Developers===\nKristian Völpel (Mail: mailto:voelpel@nullacht.biz )\n\n**Thanks to**\nSören Auer\nMichael Martin\n" . . . . "2011-02-01T09:50:53"^^ . "{{vcard name=\"sn\" value=\"Dietzold\"}}\n\n==Publications==\n%%(exhibit jsonp=\"http://docs.aksw.org/BibsonomyProxy/exhibit-proxy.php?suffix=user/aksw/tramp&callback=cb\")\n\n
\n
Navigation
\n \n\n \n \n \n \n \n \n \n \n \n
\n\n
\n\n

\n\n :\n\n\n\n(Editors: )\n\n\n\nlink\n\n

\n\n\n%%\n" . . . . "2008-12-08T18:33:39"^^ . "{{vcard name=\"sn\" value=\"Auer\"}}\n\nPlease see my homepage at: http://www.informatik.uni-leipzig.de/~auer" . . . . "2007-03-13T00:28:16"^^ . "{{vcard name=\"cn\" value=\"Jens Lehmann\"}}" . . . . "2010-02-14T15:55:08"^^ . "{{Include page=\"/Projects/Box\" divclass=\"floatbox\" nomark=\"1\"}}\n==Downloads==\n{{toc}}\n{{a name=\"OntoWiki\"}}\n===~OntoWiki===\nOntoWiki can be downloaded at our \n<#OntoWiki Download Area#>\n\nEvery ~OntoWiki Release contains all necessary components (Erfurt, Zend, RAP, ...) in one single package so you don't need to download another file for using ~OntoWiki.\n\nIf you want to use a bleeding edge version, you can install ~OntoWiki from our ((http://code.google.com/p/ontowiki/wiki/InstallFromMercurial Mercurial Repository)).\n\n{{a name=\"xOperator\"}}\n===~xOperator===\nxOperator, our semantic agent for xmpp / jabber network can be downloaded at the\n<#xOperator Download Area#>\n\nIf you want to use a bleeding edge version, you can install ~xOperator from our ((/Projects/xOperator/InstallFromSubversion Subversion Repository)).\n\n===Powl===\nIf you want to use a stand-alone Powl, you can download it form our\n((http://sourceforge.net/project/showfiles.php?group_id=99425&package_id=106662 SourceForge Project Space)).\n\n{{a name=\"LDAP2SPARQL\"}}\n===LDAP2SPARQL===\n((/Projects/LDAP/Backend LDAP2SPARQL)) can be downloaded at the\n<#LDAP2SPARQL Download Area#>\n\nIf you want to use a bleeding edge version, you can install LDAP2SPARQL from our ((/Projects/LDAP/Backend/Installation Subversion Repository)).\n\n\n===R2D2 / ...===\nAll unreleased software can be downloaded from our ((http://sourceforge.net/svn/?group_id=99425 SubVersion Repository)).\n\n===Latest Releases===\n{{feed title=\"no\" divclass=\"box\" url=\"http://blog.aksw.org/feed/atom/?cat=3\" max=\"5\"}}\n" . . . . "2008-07-17T15:37:20"^^ . "{{Include page=\"/Projects/OntoWiki/Menu\" divclass=\"floatbox\" nomark=\"1\"}}\n==Access Control==\n{{toc from=h2 to=h3}}\n\nAll access control configuration statements are saved in your system config model (Model URI: ##\"\"http://localhost/OntoWiki/Config/\"\"##).\n\n===Basic Concepts===\n**Account**s (foaf:Agent) are the entities which are able to use the ~OntoWiki. We do not distinguish between different types of accounts like Users and Agents. To use OntoWiki, an account has to provide his user name (foaf:nick) and his password (SysOnt:userPassword). The special resource SysOnt:Anonymous represents the anonymous user which is used in the absence of a named user (i.e. not logged in). The special resource SysOnt:SuperAdmin represents an administration account which uses the database connection login and pass and which ignore every access control config (!). \n\n**Group** (foaf:Group): Accounts can be member of one or more groups. If an account is member of a group (foaf:member), all rights and restrictions of this group are applied to the account.\n\n**Model** (SysOnt:Model): A model is a single knowledge base in OntoWiki which is identified by a model URI. The special resource SysOnt:AnyModel represents any available model.\n\n**Action** (SysOnt:Action): An action is an application specific function or a group of functions. They are identified by an URI and are used to manage special rights of an account or group in OntoWiki. An example of an action is SysOnt:RegisterNewUser, which is the privilege to create a new account. The special resource SysOnt:AnyAction represents any available action. Plugin developer can create their own actions to represent the new plugin capabilities.\n\n===Access Control Setup===\n{{a name=\"ModelBased\"}}\n====Model Based====\nFrom Version 0.7 on, you can manage a detailed model based access control in ~OntoWiki. Access to a model can be granted or denied. We distinguish two types of access:\n * read access - the account can read statements from the model\n * write access - the account can read, add and delete statements\n\nThese user/group to model relations represent denote the four possible types of model based access control:\n * SysOnt:grantModelEdit - grant write (and read) access to a model\n * SysOnt:grantModelView - grant read access to a model\n * SysOnt:denyModelEdit - deny write access to a model\n * SysOnt:denyModelView - deny read (and write) access to a model\nThe OWL representation of these relations is available in the ((http://ns.ontowiki.net/SysOnt/ OntoWiki System Ontology)).\n\nThe evaluation of the AC statements is done in this order:\n * Collect all granted models from the account and the accounts groups.\n * Collect all denied models from the account and the accounts groups and substract them from the grant list.\nThis means **deny statements overwrite grant statements**.\n\nThe default access control configuration of a new OntoWiki installation is described in the ((FirstSteps first steps document)).\n\n{{a name=\"ActionBased\"}}\n====Action Based====\nAccess to actions can be granted or denied only. To describe this, these two relations can be used:\n * SysOnt:grantAccess - grant access to a specific action \n * SysOnt:denyAccess - deny access to a specific action\nThe OWL representation of these relations together with a list of all used actions in a default ontowiki installation is available in the ((http://ns.ontowiki.net/SysOnt/ Ontology)).\n\nThe evaluation of the AC statements is done in this order:\n * Collect all granted actions from the account and the accounts groups.\n * Collect all denied actions from the account and the accounts groups and substract them from the grant list.\nAgain: **deny statements overwrite grant statements**.\n\nThe default access control configuration of a new OntoWiki installation is described in the ((FirstSteps first steps document)).\n\n{{a name=\"StatementBased\"}}\n====Statement Based====\nStatement Based Access Control (SBAC) is a time-consuming feature. It was firstly released with OntoWiki 0.8 but for the time being it is not enabled by default.\n\n===Schema Configuration===\nThe schema URI's which are used to represent the basic concepts of access control in OntoWiki, can be changed in the Erfurt default config (##./lib/Erfurt/erfurt.ini##). In most use-cases thats not necessary. The default schema uses FOAF resources, where possible.\n\n**ac.model **- Access Control Model - where do you want to read and save user and group statements from? Normally, this is your local ~SysOnt model so the default value is: ##\"\"\"http://localhost/OntoWiki/Config/\"\"\"##. In some cases, you want to change this, e.g. if your user statements come from another data source and you transform it to an RDF model.\n\n**ac.user.* **- Schema URIs which define properties and classes for authentication and registration:\n##ac.user.class = \"\"\"http://xmlns.com/foaf/0.1/Agent\"\"\"##\n##ac.user.name = \"\"\"http://xmlns.com/foaf/0.1/nick\"\"\"##\n##ac.user.pass = \"\"\"http://ns.ontowiki.net/SysOnt/userPassword\"\"\"##\n##ac.user.mail = \"\"\"http://xmlns.com/foaf/0.1/mbox\"\"\"##\n##ac.user.superAdmin = \"\"\"http://ns.ontowiki.net/SysOnt/SuperAdmin\"\"\"##\n##ac.user.anonymousUser = \"\"\"http://ns.ontowiki.net/SysOnt/Anonymous\"\"\"##\n\n**ac.group.* **- Schema URIs which define properties and classes for grouping:\n##ac.group.class = \"\"\"http://xmlns.com/foaf/0.1/Group\"\"\"##\n##ac.group.membership = \"\"\"http://xmlns.com/foaf/0.1/member\"\"\"##\n##ac.group.subgroup = \"\"\"http://ns.ontowiki.net/SysOnt/subGroup\"\"\"##\n\n**ac.models.* **- Schema URIs which define the model class and model access control relations:\n##ac.models.class = \"\"\"http://ns.ontowiki.net/SysOnt/Model\"\"\"##\n##ac.models.grantEdit = \"\"\"http://ns.ontowiki.net/SysOnt/grantModelEdit\"\"\"##\n##ac.models.grantView = \"\"\"http://ns.ontowiki.net/SysOnt/grantModelView\"\"\"##\n##ac.models.denyEdit = \"\"\"http://ns.ontowiki.net/SysOnt/denyModelEdit\"\"\"##\n##ac.models.denyView = \"\"\"http://ns.ontowiki.net/SysOnt/denyModelView\"\"\"##\n##ac.models.anyModel = \"\"\"http://ns.ontowiki.net/SysOnt/anyModel\"\"\"##\n\n**ac.action.* **- Schema URIs which define the action class and action access control relations:\n##ac.action.class = \"\"\"http://ns.ontowiki.net/SysOnt/Action\"\"\"##\n##ac.action.deny = \"\"\"http://ns.ontowiki.net/SysOnt/denyAccess\"\"\"##\n##ac.action.grant = \"\"\"http://ns.ontowiki.net/SysOnt/grantAccess\"\"\"##\n##ac.action.anyAction = \"\"\"http://ns.ontowiki.net/SysOnt/anyAction\"\"\"##\n##ac.action.config = \"\"\"http://ns.ontowiki.net/SysOnt/rawConfig\"\"\"##\n" . . . . "2007-05-04T17:04:33"^^ . "==Professor Catalog Leipzig + Atuin ==\n\nStart: 01.03.2007\nFinished: 31.07.2007\n\n===Material===\n\nhttp://www.foaf-project.org/\n\n====Modelling tools====\n\n * ((http://protege.stanford.edu/ Protégé - ontology editor and knowledge-base framework)) - Freeware\n * ((http://www.altova.com/products/semanticworks/semantic_web_rdf_owl_editor.html Altova Semantic Works)) - Shareware (Demoversion for 1 month)\n\n====Dokumentationen====\n\nhttp://www.co-ode.org/resources/tutorials/ProtegeOWLTutorial.pdf\n\n ====Relatated Papers====\n\n * Ein Überblick über RDF und RDFS. (Enrico Hörnig, Jörn Hoffmann); Universität Leipzig 2006 (((http://aksw.org/Internal/StudentsProjects/ProfessorCatalog/files?get=hoffmann_hoernig_rdf_rdfs.pdf Seminararbeit)))" . . . . "2010-08-10T13:26:19"^^ . "==Changelog==\n{{toc}}\n\n{{a name=\"0.9.5\"}}\n===~OntoWiki 0.9.5===\n * ((http://blog.aksw.org/2010/ontowiki-095-available/ Release Notes))\n * Support for Semantic Pingback, a protocol which enables OntoWiki to communicate named links from linked data resources or blog systems like WordPress.\n * Support for the publication of provenance information via Linked Data.\n * A new navigation module which support the configuration and usage of arbitrary navigation hierarchies (e.g. based on classes, SKOS elements, geospatial entities or FOAF groups).\n * A bookmarklet for collecting RDFa-based information into a specific OntoWiki knowledge base.\n * More editing widgets, e.g. for phone number and mailto: resources.\n * A new mapping module for the resource visualisation and filtering based on maps.\n * Attribute / Tag clouds based on selected RDF properties.\n * A GUI for complex SPARQL filter (contains, larger, smaller, between and bound)\n * A JSON/RPC server as an additional interface (e.g. for the command line client)\n * A plugin to create nice URIs based on the content of a new resource.\n * ((http://code.google.com/p/ontowiki/issues/list?can=1&q=milestone=OntoWiki-0.9.5 complete 0.9.5 issue list))\n\n{{a name=\"0.9\"}}\n===~OntoWiki 0.9===\n * ((http://blog.aksw.org/2009/ontowiki-09-available/ Release Notes))\n * RDFa widget editing\n * Extension architecture with support for components, themes, datawrapper, translations and generic plugins\n * Authentication support for local sioc:Users, FOAF+SSL WebIDs and OpenIDs\n * Support for LinkedData both as server and consumer\n * Translations in English, German an Chinese\n * Separation of the Semantic Web API Erfurt from the OntoWiki core\n * Support for multiple SPARQL RDF stores: Implementations are available for Virtuoso and ZendDB (i.e. MySQL)\n * Pattern based query cache\n * Data gathering backends e.g. for LinkedData gathering\n\n{{a name=\"0.8.6\"}}\n===~OntoWiki 0.8.6===\n * ((http://blog.aksw.org/2008/ontowiki-086-released/ Release Notes))\n * ((issue:140 enhancement:)) Support for HTTP via SSL (HTTPS)\n * ((issue:128 enhancement:)) History sortable\n * ((issue:131 fix:)) URI fix for ressources that do not match a model's base URI\n * ((issue:138 fix:)) wrong isSubClass result\n * ((issue:109 fix:)) update service now with http auth\n * ((issue:133 fix:)) db table update problem on windows servers\n * ((issue:110 fix:)) inconsistent API fix (emtpy URIs)\n * ((http://code.google.com/p/ontowiki/issues/list?can=1&q=milestone:OntoWiki-0.8.6&colspec=ID%20Type%20Status%20Owner%20Priority%20Milestone%20Summary%20Browser complete 0.8.6 issue list))\n\n===~OntoWiki 0.8.5===\n * ((http://blog.aksw.org/2008/ontowiki-085-released/ Release Notes))\n * A plug-in and event architecture\n * A file / document manager\n * Rest webservices for login / query / export databases\n * WebDAV support for browsing and exporting resources\n * A new JSON exporter that uses the RDF JSON specification draft from talis\n * New Plugins: Semantic Sitemap and Container Manager\n * ((http://code.google.com/p/ontowiki/issues/list?can=1&q=status:Verified%20milestone:OntoWiki-0.8.5&colspec=ID%20Type%20Status%20Owner%20Priority%20Milestone%20Summary%20Browser a bunch of bug fixes))\n\n\n{{a name=\"0.8\"}}\n===~OntoWiki 0.8===\n * ((http://blog.aksw.org/2007/ontowiki-08-and-owcli-02-released/ Release Notes))\n * Complete new default theme\n * Smarter html structure\n * Desktop like style with windows and menus\n * ((/Projects/OntoWiki/AccessControl#StatementBased Statement Based Access Control)) (experimental)\n * New GUI features:\n * Improved RDF/XML exporter for resources and models\n * Support for ((/Projects/OntoWiki/Help/Classes hidden classes))\n * Menu entries for deleting resources, models and class description\n * Menu entry for adding content to existing models\n * Menu entry for deleting a models cache\n * New OntoWiki_View class that supports rendering of a (virtually) unlimited number of nested views\n * New Features ((/Projects/OntoWiki/CommandLineInterface Command Line Interface)) (0.2):\n * Support for SPARQL queries (table and graph output)\n * New commands for content subscriptions, geocoding, bash autocompletion, ...\n * ((http://powl.svn.sourceforge.net/viewvc/*checkout*/powl/trunk/owcli/ChangeLog complete owcli changelog))\n\n{{a name=\"0.7\"}}\n===~OntoWiki 0.7===\n * ((http://blog.aksw.org/2007/ontowiki-07-released/ Release Notes))\n * Access Control at ((/Projects/OntoWiki/AccessControl#ModelBased Model)) and ((/Projects/OntoWiki/AccessControl#ActionBased Action)) level\n * Enhancements in System Ontology ((http://powl.svn.sourceforge.net/viewvc/*checkout*/powl/trunk/erfurt/SysOnt.rdf http://ns.ontowiki.net/SysOnt/))\n * User Data is now FOAF compatible and managed as RDF Knowledge Base\n * New ((/Projects/OntoWiki/Features#AdvancedInterface SPARQL Query Shell)) together with a brand new ((http://blog.aksw.org/2007/sparqlers-best-choice-sparqlenginedb/ SPARQL Engine))\n * New URI Routing (list, (class) view)\n * GUI enhancements\n * Several bug fixes\n * Environment Changes:\n * New Zend 1.0.0\n * New RAP 0.9.5\n * Separation from Powl\n\n{{a name=\"0.6\"}}\n===~OntoWiki 0.6===\n * ((http://blog.aksw.org/2007/ontowiki-06-released/ Release Notes))\n * first ((http://framework.zend.com/ zended)) version\n * first stand-alone version\n * first theme-able version\n * guided installation\n * basic access control at model scope\n\n{{a name=\"0.5\"}}\n===~OntoWiki 0.5 aka Powl / ~OntoWiki 0.95===\n * ((http://blog.aksw.org/2007/ontowiki-powl-095-released/ Release Notes))\n * system ontology translation updates (nl)\n * code and gui cleanups (OntoWiki)\n * installation improvements\n * further steps towards MSIE compatibility\n * shipping with newest RAP version\n * some bugfixes (Powl API, OntoWiki)\n" . . . . "2007-04-19T22:02:09"^^ . "{{Include page=\"/Projects/OntoWiki/Menu\" divclass=\"floatbox\" nomark=\"1\"}}\nOntoWiki.png\n\n==CKC Challenge Page==\nDear OntoWiki User,\n\nthank you for participating in the ((http://km.aifb.uni-karlsruhe.de/ws/ckc2007/challenge.html CKC Challenge)). This FAQ wiki page is intended to support you in your challenge tasks. The page is editable for all so please ((http://aksw.org/Projects/OntoWiki/CKC/edit ask your question)) - we will answer them.\n{{toc divclass=\"nobox\" notitle=true}}\n\n===Frequently Asked Questions===\n====Why is my new property or instance not visible in the drop down list?====\nIn order to find a resource in the drop down list it needs at least one literal value so OntoWiki can search this value. Typical this is rdfs:label but any other property is also ok.\n\nIn order to find a property in the property drop down list in inline editing mode or edit tab, a correct type has to be added to this property (e.g. ((http://ckc.ontowiki.net/resource/view/rdf:Property rdf:Property)) or ((http://ckc.ontowiki.net/resource/view/owl:ObjectProperty owl:ObjectProperty)) ).\n\n====How can I use the map tab?====\nA resource is displayed on the ((http://ckc.ontowiki.net/resource/map/Person map)) either if it use the geo properties geo:lat and geo:long directly or if it is in ((http://ckc.ontowiki.net/resource/view/foaf:based_near foaf:based_near)) relation to a resource with these geo properties. \n\n====How can I use the calendar tab?====\nA resource is displayed in the calendar tab if it uses a literal property with the range of xsd:date.\n\n====How can I register?====\nYou find a link to the registration form for creating an OntoWiki account on the left hand side in the login box." . . . . "2009-05-08T18:14:17"^^ . " 1. About\n - ((/Projects/OntoWiki#Overview Overview))\n - ((/Projects/OntoWiki#News News))\n - ((/Projects/OntoWiki/Features Features))\n - ((/Projects/OntoWiki/Screenshots Screenshots))\n - ((/Projects/OntoWiki#Publications Publications))\n 2. Get started\n - ((/Projects/OntoWiki/Demo Demos / Screencast))\n - ((/Projects/Downloads#OntoWiki Download))\n - ((/Projects/OntoWiki/FirstSteps First Steps))\n - ((http://groups.google.com/group/ontowiki-user User Mailinglist))\n - ((/Projects/OntoWiki/Help Online Help))\n - ((http://code.google.com/p/ontowiki/issues/list Report a bug))\n 3. Specials\n - ((/Projects/OntoWiki/CommandLineInterface Command Line))\n - ((/Projects/LDAP/Backend LDAP Integration))\n - ((/Projects/OntoWiki/WebDAV WebDAV Support))\n - ((/Projects/OntoWiki/AccessControl Access Control))\n - ((/Projects/OntoWiki/WebServices Web Services))\n" . . . . "2009-08-02T03:56:21"^^ . "==Demo / Screencast==\nA demonstration platform can be accessed at ((http://demo.ontowiki.net/)) (current stable release) and ((http://trunk.ontowiki.net/)) (current developer version).\n\nScreencasts explaining the tool are available too:\n * ((http://docs.ontowiki.net/ontowiki/screencasts/2009-06-17/ Version 0.9 - Sindice Integration / RDFa Widgets / Data Wrapper))\n * ((http://docs.ontowiki.net/ontowiki/screencasts/2008-01-22/ Version 0.8 - demo.ontowiki.net Session))\n * ((http://docs.ontowiki.net/ontowiki/screencasts/2006-07-05/ Version 0.5 - local installation))\n" . . . . "2010-02-14T15:55:57"^^ . " ATTENTION: THIS PAGE IS OUTDATED - FOR A CURRENT VERSION, HAVE A LOOK AT http://code.google.com/p/ontowiki/wiki/InstallFromMercurial\n\n{{Include page=\"/Projects/OntoWiki/Menu\" divclass=\"floatbox\" nomark=\"1\"}}\n==Install a bleeding edge ~OntoWiki from Subversion==\nThis wiki page documents the installation on a ubuntu linux box. You have to adapt it for other distributions or operating systems.\n\n{{toc}}\n\n===Requirements===\nIn order to install OntoWiki from SubVersion you need:\n * PHP 5.2\n * ((http://httpd.apache.org/docs/2.0/mod/mod_rewrite.html mod_rewrite)) allowed in target directory\n * ((http://httpd.apache.org/docs/2.0/configuring.html#htaccess .htaccess)) allowed in target directory\n * An installed ((http://mysql.com MySQL Server)), a created database on that server and an account which is able to read and write that database\n\n===Download===\nAn ~OntoWiki installation can be downloaded by only one checkout. This checkout downloads ~OntoWiki, Erfurt, RAP and Zend.\n\n##svn co \"\"https://powl.svn.sourceforge.net/svnroot/powl/trunk/ontowiki\"\" /path/to/ontowiki##\n\nDuring the checkout process, you have to confirm SSL certificates ...\n\n===Configuration===\nThe most important configuration step is the database configuration. First you have to copy these files:\n\n%%\ncd /path/to/ontowiki\ncp htaccess.dist .htaccess\ncp config.ini.dist config.ini\n%%\n\nThen you need to change the database configuration in your config.ini:\n%%\ndatabase.params.host = localhost\ndatabase.params.username = owuser\ndatabase.params.password = owpass\ndatabase.params.dbname = ontowiki\n%%\n\nAfter that, go to your ~OntoWiki URL in your browser (e.g. ##\"\"http://localhost/ontowiki/\"\"##). There will be an info page that you do not have the ontowiki tables and data in your database (if not, have a look at the ~TroubleShooting section). The page will be reloaded several times and after the last reload you will see a fresh and clean ~OntoWiki :-) If you are new to OntoWiki you can read the ((FirstSteps First Steps Documentation)) now.\n\n===TroubleShooting===\nPlease make sure that Apache reads the .htaccess file. (see http://httpd.apache.org/docs/2.2/howto/htaccess.html#troubleshoot) and the rewrite engine (module rewrite load) is enabled. Otherwise, URI rewrites will not work.\n" . . . . "2011-02-21T19:41:13"^^ . "==First Steps==\nThis guide is intended to provide support for first time ~OntoWiki users. It assumes that you have a working installation either from a ((http://code.google.com/p/ontowiki/downloads/list released archive)) or from the ((http://code.google.com/p/ontowiki/wiki/InstallFromMercurial code repository)).\n\n===First Login===\nIf you start with a new ontowiki installation, you have only one pre-created account: ##Admin##. This account does not have a password, so you need to change this!!\n * Login with ##Admin## and no pass\n * Click on \"User\" -> \"Preferences\" Main Box (upper left side)\n * Change the password and email\n\n===First Model===\nAfter that, you should create a new knowledge base. A good example is our conference model. The model URI is ##\"\"http://3ba.se/conferences/\"\"## and the model has this ((http://ontowiki.googlecode.com/svn/trunk/models/Conferences/conferences.rdf Download Link)):\n * Login with ##Admin## user (if not already done)\n * Click on the menu entry \"Edit -> Create Knowledge Base\" in the Knowledge Bases box\n * Fill in the Model URI and the \"alternative location\"\n * Submit (depending on your server, this can last up to 10-20 sec)\n\nAfter importing the conference model, you can browse conferences, persons and topics. If your OntoWiki has another installation URI than ##http://localhost/...##, you have to configure another ((http://www.google.com/apis/maps/ Google Maps API Key)) in your ##config.ini##.\n\nBy default, every new user (and the anonymous user) can read every model but the two system models. So if you logout now, you have anonymous access to your new model. If you don't like that, you need to change that in your configuration model.\n\n===Preconfigured Knowledge Bases===\nA new ~OntoWiki has two installed Knowledge Bases:\n * ##\"\"http://ns.ontowiki.net/SysOnt/\"\"## is the global system ontology which describe OntoWiki configuration concepts.\n * ##\"\"http://localhost/OntoWiki/Config/\"\"## is your local configuration model. It imports the global system ontology. Registered Users and ((AccessControl access control configuration)) will be saved here.\n" . . . . "2010-08-10T13:22:05"^^ . "==Features==\n\nOntoWiki provides sophisticated means for navigating, visualising and authoring of RDF-based Knowledge Bases. It serves and consumes Linked Data and comprises a comprehensive middleware API for building custom Semantic Web applications.\n\nWe refer to it as a Wiki, since our focus is on simplicity, adaptability and collaboration. However, other than annotating text-based Wiki pages with a special syntax (as suggested by text-based Semantic Wiki approaches), OntoWiki uses RDF in the first place to represent information. For human users, OntoWiki allows to create different views on data, such as tabular representations or maps. For machine consumption it supports various RDF serialisations as well as RDFa, Linked Data and SPARQL interfaces. Since its introduction in 2006, the application has evolved into a framework for building Semantic Web applications and was recently updated to support the collaboration across multiple domains and application via Semantic Pingback and RDFauthor\n\n{{toc}}\n\n===Navigation and Visualisation===\nOntoWiki provides a number of ways for navigating through RDF knowledge bases.\nThese include **taxonomy and hierarchy browsing** (e.g. via SKOS taxonomies or the class hierarchy), **facet-based browsing** (with **complex filter** conditions and **attribute based tag clouds** and **full-text search**. These different navigation facilities can also be used as a **combined navigation**, for example a user can start with a full-text search and **refine the results** using faceted-search or restrict them to a certain part of the selected hierarchy.\nOntoWiki translates these different navigation features into a single SPARQL query. In addition to rendering the results of such a query as a **resource list**, OntoWiki provides an **extension mechanism** for implementing dedicated views like **maps and calendars**. Once a specific entity has been selected, the **resource view** displays all available information for that entity. Besides rendering this information generically in a tabular way, ~OntoWiki can be extended with **domain specific resource views** (i.e. vocabulary).\n\n===Authoring===\nAll views in OntoWiki can be equipped with corresponding **RDFa annotations**. OntoWiki employs the **RDFauthor mechanism** to automatically transform these views into **editable forms**. As a consequence, all information items displayed in OntoWiki can be directly edited in place. This allows ~OntoWiki users to edit the knowledge base even without being acquainted with the RDF, RDF-Schema or OWL data models. Following the Wiki approach all changes are put under **version control** and can be easily **rolled back**.\n\nIn addition to this, the integration of RDFauthor as our main authoring mechanism led to two additional usage options:\n * By using OntoWiki's RDFauthor **bookmarklet**, users can **collect data from different web pages** and import it directly into their personal knowledge bases (e.g. contacts or events).\n * OntoWiki can be used as a service for hosting **editable mash-ups**. These mash-ups use data from OntoWiki's **SPARQL endpoint** and other data sources (which are interpreted as named graphs) and provide a merged view on this data. The bookmarklet is able to distinguish the statements from these named graphs and allow the user to edit these data directly inside the mash-up as well as to **propagate the changes back to the different sources**.\n\n===Knowledge Base Evolution===\nOntoWiki tries to support the creation of RDF **Knowledge Bases from the scratch** (rather than using predefined ontologies only) in a wiki way. This means that our users often follow the learning by doing path, where requirements and priorities change over time. Our **evolution framework** allow OntoWiki users to apply predefined **evolution pattern** from a **pattern repository** to their data, as well as to create their own pattern in order **maintain the data quality** of their Knowledge Base with little effort. Examples for such evolution patterns include the **splitting of classes by using their property values** or the **transition from a data property to an object property** (e.g. the transition from literal based tags to resource based tags).\n\n===Linked Data & Semantic Pingback===\nOntoWiki acts as a **Linked Data server** as well as an **Linked Data client**. Entities that use identifiers being governed by the OntoWiki installation are automatically served as Linked Data. OntoWiki supports **access control** on Linked Data employing the **FOAF+SSL protocol** as well as traditional local account based authentication. References to entities using foreign identifiers can be de-referenced (i.e. consumed by OntoWiki) in order to **obtain additional information** from the original source. Even non-linked data resources can be consumed by utilising **specific data-wrapper**, that allow the **generation of RDF data** (e.g. from images, videos or web services).\n\nOften it is beneficial for the owner of a Linked Data resource to be informed about the usage of their resources. When **publishing a FOAF profile**, for example, it is useful to get notified when others establish a foaf:knows relation. We therefore developed the **Semantic Pingback** protocol. By employing Semantic Pingback, OntoWiki users can communicate RDF statements across domains and applications.\n" . . . . "2007-04-29T20:05:27"^^ . "{{tree page=\"/Projects/OntoWiki/\"}}" . . . . "2009-05-08T18:08:15"^^ . " ATTENTION: THIS PAGE IS OUTDATED - FOR A CURRENT VERSION, HAVE A LOOK AT http://code.google.com/p/ontowiki/wiki/Roadmap\n{{Include page=\"/Projects/OntoWiki/Menu\" divclass=\"floatbox\" nomark=\"1\"}}\n\n==Roadmap==\n * Delivering markup as application/xhtml+xml with XHTML+RDFa dtd (to browsers accepting it)\n * Usage of [[http://www.w3.org/TR/xhtml-rdfa-primer/|RDFa]] vocabulary (XHTML 2.0)\n * Drag & Drop\n * Consolidation of Widget API and included widgets\n * Increasing extendibility by simplifying and robustifying the scheme by which editing actions are passed between ~OntoWiki and the Erfurt API\n * Template usage for rendering instance data (currently done through static method calls)\n * Generic SPARQL Filters\n * List Template Rewrite\n * Tag-Cloud-Filter (M.Haschke)\n * Generic SPARQL Filters (Norm, Seebi)\n * Blank Nodes\n" . . . . "2007-06-06T15:45:29"^^ . "<#\n
\n

LDAP 2 SPARQL

\n

Accessing RDF Knowledge Bases via LDAP Clients

\n

In order to exploit the client support of LDAP directories with the semantic expressivity of RDF knowledge bases, we aim at integrating RDF knowledge bases into LDAP directory services.

\n

LDAP 2 SPARQL is a Backend to the widely used OpenLDAP server. It translates LDAP queries into SPARQL queries, asks a SPARQL endpoint and translates the result back to LDIF.

\n

Download LDAP 2 SPARQL 0.2

\n
\n
\n{{Include page=\"/Projects/LDAP/Backend/Menu\" nomark=\"1\"}}\n
\n
\n#>\n===News==={{a name=\"News\"}}\n{{feed title=no divclass=\"box\" url=\"http://blog.aksw.org/feed/?cat=8\" max=\"2\"}}\n===Introduction==={{a name=\"Introduction\"}}\nLDAP based directory services are an important part in the IT infrastructure of most organisations and enterprises. They act as a central service for integrating new applications into an IT infrastructure and can be accessed by many different types of clients ranging from content management systems to personal email tools.\n\nIn order to exploit the client support of LDAP directories with the semantic expressivity of RDF knowledge bases, we aim at integrating RDF knowledge bases into LDAP directory services. The ultimate goal is to use standard LDAP clients such as e-mail and address book software as well as software relying on LDAP authentication with RDF knowledge bases as backends.\n\n===Publications==={{a name=\"Publications\"}}\n**Dietzold, S.; Auer, S.:**\n((http://www.eswc2007.org/pdf/demo-pdf/LDAP2SPARQL.pdf Integrating SPARQL Endpoints into Directory Services)). Accepted Demo at the 4th European Semantic Web Conference 2007, Innsbruck, Austria.\n\n**Dietzold, S.:**\n((http://CEUR-WS.org/Vol-135/paper3.pdf Generating RDF Models from LDAP Directories)). In: S. Auer, C. Bizer and L. Miller (ed.) Proceedings of the SFSW 05 Workshop on Scripting for the Semantic Web, Hersonissos, Crete, Greece, May 30, 2005. CEUR Workshop Proceedings, ISSN 1613-0073, online \n\n===Developer===\n * ((/SebastianDietzold Sebastian Dietzold))\n * Denis Gärtner\n" . . . . "2011-10-04T05:46:40"^^ . "{{vcard name=\"cn\" value=\"Sebastian Hellmann\"}}\n\n=== This page is just a stub, please have a look at my ===\n===((http://bis.informatik.uni-leipzig.de/SebastianHellmann Workpage))===\n\n\n\n{{tree}}\n\n" . . . . "2012-01-05T09:42:36"^^ . "<#\n
\n

OntoWiki

\n\"OntoWiki\n

is a tool providing support for agile, distributed knowledge engineering scenarios.

\n

OntoWiki facilitates the visual presentation of a knowledge base as an information map, with different views on instance data. It enables intuitive authoring of semantic content, with an inline editing mode for editing RDF content, similar to WYSIWIG for text documents.

\n

Download OntoWiki

\n
\n
\n#>" . . . . "2010-06-16T20:35:08"^^ . "==OntoWiki Related Publications==\n\n%%(exhibit jsonp=\"http://docs.aksw.org/BibsonomyProxy/exhibit-proxy.php?suffix=user/aksw/ontowiki&callback=cb\")\n\n
\n
Navigation
\n\n\n\n\n\n
\n\n
\n\n

\n\n :\n\n\n\n(Editors: )\n\n\n\nlink\n\n

\n%%" . . . . "2010-12-23T01:34:36"^^ . "==Screenshots==\nThis page contains selected screenshots showing ~OntoWiki in action. If you want to try ~OntoWiki check our ((/Projects/OntoWiki/Demo demo page)).\n\n{{toc}}\n===Resource Editing===\n<##>\n\n===Russian Localization===\n<##>\nShows a class based list of LOD2 working packages with two attribute clouds added for start and endmoth (of the working package) (OntoWiki 0.9.5)\n\n===Contact management with ~OntoWiki===\n<##>\nContact management with ~OntoWiki 0.8 (FOAF / SWRC vocabularies)\n\n" . . . . "2007-05-24T12:48:20"^^ . "==RSS-Feed Management System==\n\n" . . . . "2007-08-25T19:26:28"^^ . "==ATUIN==\n**Atuin the unique innovation network**\n\n((https://sourceforge.net/projects/atuin page on sourceforge))\n\n\nAtuin is a object oriented software that is written in PHP5*. The main data is stored in RSS-Feeds* in version 1.0.\n\nThe internet today is a huge collection of knowledge and information. But most of them can not be accessed directly. You need search engines which are collecting and sorting the information to make it accessible for humans. Unfortunately the engines are not able to edit all the data and can not put them in the right context. This dificiency can not be solved with the contemporary implementation of the internet. \n\nVersatileness of data storage is also a obstacle for the search engines. There are no well mellowed ways to read the whole internet correct by an engine and to put all gathered information in a correct context to each other. \n\nSearch engines can not distinguish between real information and false ones. In that case, the quality of the search hits depends on the query of the user and his ability to rate the information by its content. \nToday, some projects are trying to avoid false information spreading by using the social phenomenon collective wisdom. A well known example is the knowledge-portal wikipedia.org. \n\nBut there ist no possibility to assign the concept of wikis to the whole internet. Thus there is no way to edit the information by another person than the main author.\n\nAtuin tries to close this gap. It stores its data into the XML* based RSS* 1.0 suggestion by W3C*. The advantages are clear. A standartized format gives the possibility for automatic systems to collect all the information and metainformatin out of defined fields. The content and the information are stored in special fields to access them directly without the need of any text scanning program which may be needed otherwise to extract the information.\n\nAtuin seizes the concepts of the wiki und admits users the variation and amending of other data in case the author permits that. Furthermore simple comments refering to a problem can be mad.\n\nEach answer is seen as a question itself. It is saved independently but with a link to the original question.\nThe author may also quote additional links. The linking in the background prevents the loss of the context of an information. It is also easier for search engines to scan the network. So there must just been excerised detection routines for cycles (which should already excist)." . . . . "2007-06-28T09:18:31"^^ . "{{Include page=\"/Projects/LDAP/Backend/Menu\" divclass=\"floatbox\" nomark=\"1\"}}\n==Installation==\nThis wiki pages describes how to integrate the SPARQL Backend into an OpenLDAP Server and how to configure the SPARQL Endpoint and mappings.\n===Download===\nFor now you have to download the backend from our subversion repository:\n##svn co \"\"https://powl.svn.sourceforge.net/svnroot/powl/trunk/ldap2sparql\"\" /path/to/backend##\n\nAfter that, you need a copy of the RAP API in your ##api## directory:\n%%\ncd /path/to/backend\ncvs -z3 -d:pserver:anonymous@rdfapi-php.cvs.sf.net:/cvsroot/rdfapi-php co -P rdfapi-php/api\nmv rdfapi-php/api api\nrm -rf rdfapi-php\n%%\n\n===Server Integration===\nThe SPARQL Backend uses the shell backend extension so you need to load the shell backend module in ##/etc/ldap/slapd.conf##.\n##moduleload back_shell##\n\nAn example slapd.conf configuration snippet is listed here:\n%%\n### LDAP2SPARQL Shell Backend ###\ndatabase shell\nsuffix \"ou=ldap2sparql,dc=localdomain\"\nsearch \"/path/to/backend/shell.php\"\n#subordinate\n%%\n\n===Configuration===\n====External Endpoint and pre-mapped data====\nThis ##example.ini## uses a local Joseki 3.0 to query an RDF document with pre-mapped ldap data:\n%%\n[SPARQL_ENDPOINT]\nserver = localhost:2020/sparql\ndefaultgraph = file:/path/to/backend/data/ldap.rdf \n\n[NAMESPACES]\nrdf = http://www.w3.org/1999/02/22-rdf-syntax-ns#\nldap = http://purl.org/net/ldap#\nrdfs = http://www.w3.org/2000/01/rdf-schema#\nfoaf = http://xmlns.com/foaf/0.1/\n\ndata = ldap://example.com/people/\n\n[MAPPING]\nmapping = external\n%%\n\n====External endpoint and on-the-fly mapping====\nThis example uses a local Joseki 3.0 to query an RDF document with data from the ((http://swrc.ontoware.org/ontology# SWRC namepspace)). The data is mapped top ##inetOrgPerson## according to the ((#mapping_swrc.ini mapping file)).\n\n%%\n[SPARQL_ENDPOINT]\nserver = localhost:2020/sparql\ndefaultgraph = file:/path/to/conferences.rdf\n\n[NAMESPACES]\nrdf = http://www.w3.org/1999/02/22-rdf-syntax-ns#\nldap = http://purl.org/net/ldap#\nrdfs = http://www.w3.org/2000/01/rdf-schema#\nfoaf = http://xmlns.com/foaf/0.1/\nswrc = http://swrc.ontoware.org/ontology#\nconf = http://3ba.se/conferences/\n\n[MAPPING]\nmapping = internal\nmapping_file = mapping_swrc.ini\nbase = \"ou=people,dc=localdomain\"\n%%\n\n{{a name=\"mapping_swrc.ini\"}}Here is the mapping file ##mapping_swrc.ini##:\n%%\n[OBJECTS&ATTRIBUTES]\ninetOrgPerson = swrc:Person\norganizationalPerson = swrc:Person\ncn = rdfs:label\nsn = swrc:lastName\ntelephoneNumber = swrc:phone\nmail = swrc:email\nobjectClass = rdf:type\nl = conf:country\n\n[inetOrgPerson]\ndnName = cn\ndnValue = cn\ndnFunction = plain\n%%\n\n====OntoWiki backend-ed and on-the-fly mapping====\n...soon...\n\n\n" . . . . "2007-06-06T15:14:50"^^ . " 1. About\n - ((/Projects/LDAP/Backend#Introduction Introduction))\n - ((/Projects/LDAP/Backend#News News))\n - ((/Projects/LDAP/Backend#Publications Publications))\n 2. Get started\n - ((/Projects/Downloads#LDAP2SPARQL Download))\n - ((/Projects/LDAP/Backend/Installation Installation))\n - ((/Projects/LDAP/Backend/Installation Configuration))\n 3. More ...\n - ((http://eswc2007.ontowiki.net/ldap2sparql/ Demo))\n - ((http://sourceforge.net/projects/ldap2sparql SF.net))\n" . . . . "2007-06-01T01:27:55"^^ . "<#\n
\n

Semantic LDAP

\n\"Screenshot\"\n

Bringing together LDAP and the Semantic Web.

\n

LDAP 2 SPARQL is a backend to the widely used OpenLDAP server. It translates LDAP queries into SPARQL queries, asks a SPARQL endpoint and translates the result back to LDIF.

\n

LDAP 2 OWL converts a directory information tree (DIT) complete with schema information (which will translated into an OWL ontology) and directory objects to an RDF model.

\n
\n
\n#>\n" . . . . "2010-04-07T16:13:48"^^ . "==Michael Martin==\n\n{{vcard name=\"sn\" value=\"Martin\"}}\n\nfor further Information please visit ((http://bis.informatik.uni-leipzig.de/MichaelMartin my Workpage at BIS))" . . . . "2009-05-08T17:46:49"^^ . " ATTENTION: THIS PAGE IS OUTDATED - FOR A CURRENT VERSION, HAVE A LOOK AT http://code.google.com/p/ontowiki/wiki/CodingStandard\n{{Include page=\"/Projects/OntoWiki/Menu\" divclass=\"floatbox\" nomark=\"1\"}}\n==Coding Style Guide==\nIn the hope that more of you will contribute code to the OntoWiki project we are providing a coding style guide with this release. It mainly follows the ((http://pear.php.net/manual/en/standards.php PEAR Coding Standards)) so we only point out the differences in this document.\n{{toc}}\n\n===Indentation and Line Length===\nIndentation level should be 4 spaces or 1 tab if you like. An average line should not be longer than 100 characters with 120 characters beeing the maximum.\n\n===Function Definitions===\nFunction definitions follow the SUN/Java style:\n%%(php)\n\n%%\n\n===Operators===\nAll operators **have to be surrounded with spaces**.\n%%(php)\ngetFooVar();\n$bar = $this->getBarVar() . ' appended to bar';\n\nfor ($i = 0; $i < 100; ++$i) {\n echo ($i + 7 % 3);\n}\n?>\n%%\n\n===Type Hinting===\nYou are highly encouraged to use ((http://www.php.net/manual/en/language.oop5.typehinting.php type hinting)) that was introduced with PHP 5. Type hinting allows you to request function parameters passed to be of a certain type. If a wrong type is passed, PHP throws a runtime error. Type hinting only works with objects or arrays, i.e. you can specify the exact class name of which passed objects need to be an instance or you use the type array.\n%%(php)\n\n%%\n\n===Class Naming===\nIn order to make classes auto-loadable, please use the following scheme for class-names:\n\n%%(php)\n\n%%\n * Every class starts with the ##Erfurt## prefix followed by an underscore.\n * The second part of the name is the name of the package the class belongs to (in this case ##examplepackage##).\n * The third part of the name is the real name of your class (in this case ##~ExampleClass##).\n\nPlease also note the following:\n\n * The name of a class and it's position in the file system should directly adhere, i.e. for the above example, the corresponding class should be located in ##~Erfurt/ExamplePackage/ExampleClass.php##.\n * In case a class should belong to the default package (erfurt) the class would be named as followed:\n%%(php)\n\n%%\n * Each file correspondends to exactly one class.\n\n===Inline Documentation===\n====Classes====\nEvery class should be documented as followed:\n\n%%(php)\n\n * @author MaybeAnotherAuthor \n * @copyright Copyright (c) - , {@link http://aksw.org AKSW}\n * @license http://opensource.org/licenses/gpl-license.php GNU General Public License (GPL)\n * @see http://example.com/doc/ExternalLibraryClass.html\n * @version $Id: $\n */\nclass Erfurt_ExamplePackage_ExampleClass extends ExternalLibraryClass {\n// ..\n}\n?>\n%%\nPlease note the following:\n\n * The first sentence of the comment is always the short description.\n * Each following sentence belongs to the detailed description of the class. \n * Please insert an empty line between short description and detailed description and between detailed description and following tags.\n * Always use the ##@package## tag. In case the class belongs to the default package use ##@package erfurt##.\n * Use a new ##@author## tag for each author.\n * Use the ##@copyright## tag as above, but just use the current year in case current year and year of creation are equal.\n * Always use the ##@license## tag, for we do without the GPL preamble.\n * In case your class extends or implements a unknown class (e.g. the class/interface belongs to an external library) use the ##@see## tag together with an URL pointing to the documentation of that class or interface.\n * Use the ##@version## tag as above, but also set the ##svn:keywords## property if you are adding a new class: ##svn propset svn:keywords Id Erfurt/ExamplePackage/ExampleClass.php##\n\n" . . . . "2007-06-21T21:59:06"^^ . "==Tripleize==\n===Problem===\nA large part of Web content is generated by database driven web-applications. The structure and semantics encoded in relational database schemes, however, unfortunately is not accessible to Web search engines. Within the Semantic Web initiative a number of standards and techniques were developed supporting the encoding and exchange of structured information and knowledge on the web. The aim of tripleizer is to reveal the semantic structures behind web-applications and to make them accessible on the Web and thus to enable semantic based Web searches. The following table contains the most popular ((http://sourceforge.net SourceForge)) web application projects according to download figures.\n\n#|\n|| **Project** | **Area** | **Downloads in May '07** ||\n|| ((http://sourceforge.net/projects/phpbb phpBB)) | discussion forum software | 235480 ||\n|| ((http://sourceforge.net/projects/gallery Gallery )) | photo gallery | 166005 ||\n|| ((http://sourceforge.net/projects/xoops XOOPS )) | CMS | 115807 ||\n|| ((http://sourceforge.net/projects/coppermine Coppermine )) | photo gallery | 113854 ||\n|| ((http://sourceforge.net/projects/typo3 Typo3 )) | CMS | 63641 ||\n|| ((http://sourceforge.net/projects/lportal Liferay Portal )) | Portal | 39615 ||\n|| ((http://sourceforge.net/projects/egroupware eGroupWare )) | enterprise collaboration | 33865 ||\n|| ((http://sourceforge.net/projects/alfresco Alfresco )) | CMS | 31914 ||\n|| ((http://sourceforge.net/projects/e107 e107 )) | CMS | 19996 ||\n|| ((http://sourceforge.net/projects/lifetype Lifetype )) | Blogging | 16730 ||\n|| ((http://sourceforge.net/projects/plone Plone )) | CMS | 13993 ||\n|| ((http://sourceforge.net/projects/compiere Compiere )) | ERP + CRM | 13718 ||\n|| ((http://sourceforge.net/projects/webcalendar WebCalendar )) | Calendar | 12832 ||\n|| ((http://sourceforge.net/projects/nucleuscms Nucleus )) | Blogging | 12739 ||\n|| ((http://sourceforge.net/projects/tikiwiki Tikiwiki )) | Wiki | 6368 ||\n|| ((http://sourceforge.net/projects/phpnuke PHPNuke )) | Web portal | 1654 ||\n|#\n\n\n===Solution===\n\nThe tripleize solution to reveal the structured is to generate relational database queries for a specific web-application in order to retrieve valuable information and to convert the results of these queries into RDF. Experiences showed, for most web-applications a relatively small number of queries (5-10) is sufficient to extract the important information. After generating such DB views the tripleizer software can be used to convert the view into an RDF representation, which can be shared on the web.\n\n====View structure====\nIn order to minimize the effort needed to \"tripleize\" a new web-application the query results are required to have a certain structure:\n * the first column must contain strings which can be used to generate instance URIs\n * column names will be used to generate predicate URIs\n * the individual cells of the query result contain data values or references to other instances and will eventually constitute the objects of resulting triples\nA query result will be converted into RDF triples using the following (optional) additional parameters:\n * a URI prefix for prefixing instance identifiers\n * a mapping which is used to map column names into URIs\n * a map which assigns URI prefixes or data-types to columns, in case the column values represent references to other instance or typed literal values\n\n====Vocabulary reuse====\n\n\n====Sharing and distributing====\nPush vs. pull\n\n\n===Example: OpenConf===\n\n((http://www.openconf.org OpenConf)) is a conference management software developed in PHP backed by a MySQL database. Google currently finds approx. ((http://www.google.com/search?hl=en&lr=&client=firefox-a&rls=org.mozilla%3Ade%3Aofficial&as_qdr=all&q=allintitle%3A%22+-+OpenConf++Conference+Management+System%22&btnG=Search 500 OpenConf installations)) online. The valuable meta-data about these conferences and workshops as well as their authors, publications and reviewers are not accessible.\n\nFive queries select relevant informations from the OpenConf database schema regarding papers, authors, PC members, topics and paper-topics relationships." . . . . "2007-07-06T19:12:23"^^ . "==How to Describe Research Projects on Wikipedia?==\n\n{{ToC}}\n\n===Introduction===\n\nIn order to create awareness about research projects and their results it is important to publicizes relevant information. [[http://wikipedia.org Wikipedia]] is one of the Top 10 information sources on the Internet and hence a good candidate to inform a wider public about research projects and their results.\n\nHowever, just creating some Wikipedia page for your project might probably not have the desired result. This article describes how you can describe your research project on Wikipedia better and thus better inform other researchers in your field and reach a larger public.\n\n===Your project at a glance - the Research-Project infobox template===\n\nInfoboxes aim at generating consistently-formatted boxes for certain content\nin articles describing instances of a specific type. Hence, an infobox allows viewers to instantly grasp important facts about a research project.\n\nIn order to nicely display important facts about a research project we created the [[http://en.wikipedia.org/wiki/Template:Research-Project Research-Project infobox template]]. Just copy the following code into the article about your research project.\n\n%%\n{{Research-Project|\n name=|\n title=|\n keywords=|\n fundingAgency=|\n frameworkProgramme=|\n image=|\n projectType=|\n researchObjective=|\n projectReference=|\n coordinator=|\n participants=|\n budget=|\n funding=|\n start=|\n end=|\n website=\n}}\n%%\n\nWe describe the meaning of the individual Research-Project infobox attributes:\n\n * **Name** refers to the short name or acronym of your project.\n * **Title** usually is a short (max. one sentence) description of the project\n * **Keywords** link the project with relevant standards or techologies\n * **FundingAgency** names the agency funding the project, e.g. EU, NSF, DARPA; use Wikipedia links to link to the respective Wikipedia article\n * **Image** is the name of a project logo, which should be uploaded to [[http://commons.wikipedia.org Wikipedia Commons]]\n * **ProjectType** refers to an instrument of the funding agency which the project belogs to, for EU FP7 projects these are STReP, IP, NoE, CSA\n * **ResearchObjective** names general research objectives of the funding agency which the project targets\n * **ProjectReference** is a project identifier (or contract number) asigned to the project by the funding agency\n * **Coordinator** names the organization coordinating the research project\n * **Participants** lists the projects participants; try to link them to their corresponding Wikipedia pages\n * **Budget** refers the overall project budget\n * **Funding** is the funding provided by the funding agency\n * **Start** contains the start date of the project, **End** the prospective end date\n * **Website** names the URL of the project Website\n\nAttributes which are not relevant for your project can be omited.\nThe completed template might look as follows:\n\n%%\n{{Research-Project|\n name=TAO|\n title=Transitioning Applications to Ontologies|\n keywords=[[Semantic Web]], [[Web Services]]|\n fundingAgency=[[European Union]]|\n frameworkProgramme=[[FP6]]|\n image=|\n projectType=[[Specific Targeted Research Project]]|\n researchObjective=[[IST-2004-2.4.7]]|\n projectReference=IST-2004-026460|\n coordinator=[[University of Sheffield]]|\n participants=\n [[University of Southampton]],
\n [[Jožef Stefan Institute]],
\n [[Dassault Aviation]],
\n [[Atos Origin]],
\n [[Mondeca]],
\n [[Ontotext]]\n |\n budget=4.2 M [[Euro]]|\n funding=2.8 M [[Euro]]|\n start=[[1 March]] [[2006]]|\n end=[[28 February]] [[2009]]|\n website=http://www.tao-project.eu\n}}\n%%\n\nThe rendered infobox on the Wikipedia page will look as follows:\n\nhttp://aksw.org/SoerenAuer/HowToDescribeResearchProjectsOnWikipedia/files?get=super.jpg\n\nIn addition to giving readers a brief fact sheet of the projects, the information contained in infoboxes can be extracted from Wikipedia articles and can be used for querying or facet-based browsing (see e.g. [[http://DBpedia.org DBpedia]]). Adding such structured information thus can contribute to creating a new level of transparency about what research is conducted in which parts of the world.\n\n===Categorize your project===\n\nIn order that information about your project can be found together with related information you should categorize your article. For example, you should add the category Research Project to your project or if it is funded in the course of one of the EU's framework programs the corresponding sub-category. To do so, just add the following Wikipedia markup to your article:\n\n%%[[Category:FP7 Projects]]%%\n\n===What to write===\n\nStart your article with a short paragraph summarizing the project. This project abstract will be shown at the very beginning of the article and is often used by other websites and databases referencing Wikipedia articles.\n\nStructure your article, so readers find the relevant information fast. A suggested structure could be:\n\n * Motivation - why is the project important\n * Aim - what shall be achieved during the project\n * Methodology - how do you proceed\n * Mention the workpackages\n * Partners - describe shortly the partners and their roles\n * Impact - what will be the expected result of the project\n * References\n * Related Technologies and Standards\n * Related Projects\n\nPlease keep in mind Wikipedia is an encyclopedia and hence articles should be concise, avoid marketing terminology and reference its sources. Also try to link important concepts in the text with the corresponding Wikipedia articles and try to improve these articles, too. If a field of research is nicely described also the related research projects will gain more attention and will be better covered in other media.\n\n===Keep the Article up-to date===\n\nWatch the article for discussions on its discussion page and changes by other users. Wikipedia offers to notify you once changes to articles were made. In case other users contributed to the article about your project, try to be as neutral as possible - it is not your article, but an article from the Wikipedia community about your project.\n\n\n===References===\n\n * DBpedia: http://DBpedia.org\n * Usage of the Research-Project infobox template at the SUPER project description: http://en.wikipedia.org/wiki/SUPER\n * Wikipedia category for FP6 projects: http://en.wikipedia.org/wiki/Category:FP6_Projects\n * Wikipedia category for FP7 projects: http://en.wikipedia.org/wiki/Category:FP7_Projects" . . . . "2007-07-18T14:11:20"^^ . "==Vision==\nThe OntoWiki vision is situated at the intersection of several trends.\n\n{{toc}}\n\n===The Evolution of the Web===\n\nWe currently experienced a paradigm shift on the Web: more end-user integration, exploitation of recent technological developments (AJAX etc.), higher content concentration. Another one is to come:\n\nhttp://ontowiki.net/Projects/OntoWiki/Vision/files?get=web3vision1.jpg\n\nInitially, the Web consisted of many Websites containing only unstructured/textual content. The Web 2.0 extended this traditional Web with few extremely large Websites specializing on certain specific content types. Examples are:\n * Wikipedia for encyclopedic articles,\n * Del.icio.us for Web links,\n * Flickr for pictures,\n * YouTube for Videos,\n * Digg for news.\nThese websites provide specialized searching, querying, sharing, authoring specifically adopted to the content type of their concern.\n\n===Semantification===\nWe currently observe a trend from rigid information structures (such as Relational Databases, LDAP directories, fixed forms) towards more flexible information structures (tags, taxonomies, ontologies), where new entities, attributes and associations can be easily created by domain experts and non-expert users. However, there is a clear lack for applications providing on the one hand expressiveness beyond simple tags and on the other hand being easy to use and simple to understand.\n\n===Collaboration===\nAlready some years ago started a trend towards increased, more spatially distributed and larger scale collaboration scenarios. The most prominent example with this regard is the Wikipedia project, which succeeded in creating the worlds-largest encyclopedia, is currently (according to alexa.com) one of the 10 most visited websites and attract hundred thousands of volunteer editors.\n\n===Future Needs===\nOntoWiki’s aim is to create another layer on the Web: the one of large scale distributed knowledge engineering. The rationale behind this is that for companies, organizations, associations, communities it is crucial to base on:\n * Easy-to-use, low-effort techniques for content creation and knowledge representation (as on the Web 2.0)\n * Support for arbitrary content and knowledge types. Other than specialized for specific content types the representation of arbitrary content and knowledge should be possible.\n * Preservation of the corporate identity. Tools should be installable on company servers, seamlessly integratable into existing infrastructures or leasable as private corporate knowledge & data space.\n * Access rights and IPR. Strictly enforce access rights & IPR definitions for content & knowledge, contrary to the free-for-all culture of the Web 2.0.\n * Semantics-based authoring, exchange & search for knowledge and content objects.\nHence, OntoWiki has the potential to dramatically improve the support for different content, information and knowledge types beyond the simple and high-interest ones currently supported on the Web.\n\nhttp://ontowiki.net/Projects/OntoWiki/Vision/files?get=longtail.png\n\nPopular content types such as pictures, movies, calendars, encyclopedic articles, news recipes etc. are already sufficiently well supported on the Web. However, there is a long tail of special-interest content (profiles of expertise, historic data and events, bio-medical knowledge, intra-corporational knowledge etc.) which has very low or no current support (for filtering, aggregation, searching, querying, and collaborative editing) on the Web." . . . . "2007-07-16T22:09:59"^^ . "==~OntoWiki Users==\n\nThis page contains selected ~OntoWiki users and short descriptions of their ~OntoWiki usage. **Feel free to add yourself!** If possible add a screen shot as well as name and email of a contact person.\n\n{{toc}}\n\n\n===T-Systems===\n((http://www.mms-dresden.de T-Systems Multimedia Solutions GmbH)) uses ~OntoWiki within the research project SoftWiki and internally to evaluate new ways of intra-corporate semantic collaboration.\n\n===~ProDV AG===\n<##>\n((http://www.prodv.de ProDV)) collaborates with AKSW with regard to the application of ~OntoWiki in emergency management and eGovernment settings.\n\n===Vakantieland.nl===\n((Vakantieland.nl Vakantieland)) creates an collaborative portal for tourism related information on the basis of the ~OntoWiki technology.\n\n===QA-Systems===\n<##>\n((http://www.qa-systems.de QA-Systems)) works together with the AKSW-team towards application of ~OntoWiki for large-scale distributed Requirements Engineering.\n\n===Medical University of Vienna===\nThe ((http://neuroscientific.net Medical Expert and Knowledge-Based Systems group)) at Medical University of Vienna, Austria uses OntoWiki as a ontological collaboration platform. See also their screenshots ((http://neuroscientific.net/res/ontowiki-screenshots showing OntoWiki with loaded BioZen ontologies)).\n\n===~LeCoS ~GmbH===\n((http://www.lecos-gmbh.de LeCoS)) uses ~OntoWiki as an intranet knowledge base.\n\n===ISA Informationssysteme ~GmbH===\n<##>\n((http://www.isa-tools.de ISA)) is integrating textmining technologies into ~OntoWiki." . . . . "2012-04-12T17:11:10"^^ . "<#\n
\n

DBpedia SPARQL Benchmark (DBPSB)

\n\"RDFauthor\n

a pure RDF benchmark based on actually posed queries

\n

Triple stores are the backbone of increasingly many Data Web applications.\nIt is evident that the performance of those stores is mission critical for individual projects as well as for data integration on the Web in general.\nAssessing the performance of current triple stores is, therefore, important to observe weaknesses and strengths of current implementations. \nDBPSB is a general SPARQL benchmark procedure, which we apply to the DBpedia knowledge base.\nThe benchmark is based on query-log mining, clustering and SPARQL feature analysis.\nIn contrast to other benchmarks, we perform measurements on actually posed queries against existing RDF data.\nPrevious approaches often compared relational and triple stores and, thus, settled on measuring performance against a relational database, which has been converted to RDF, using SQL like queries.\nWe argue that a pure RDF benchmark is more useful to compare between existing triple stores and provide results for Virtuoso, Sesame, Jena TDB, and BigOWLIM.\n

\n
#>\n\nBelow, we provide an overview of steps required to create the benchmark. The methodology can in principle be applied to all RDF knowledge bases. It allows the benchmark to be updated as the knowledge bases and queries to it evolve.\n\n{{toc}}\n\n==== Source Code ====\nThe source code of DBpedia SPARQL Benchmark can be found at https://akswbenchmark.svn.sourceforge.net\n\n==== Dataset Generation ====\nBase Data: DBpedia 3.5.1 with all data sets mentioned at http://wiki.dbpedia.org/DatasetsLoaded\nIn order to generate a dataset of specific size, do the following steps: - \n 1. In benchmark.xml file set the tag to the dataset size required e.g. 10, 20, ....\n 1. In benchmark.xml file set the tag to either 'RandomInstance' or 'RandomTriple'.\n 1. In benchmark.xml file set the tag to the name of the required output file.\n 1. In benchmark.xml file set the tag to the address of your endpoint.\n 2. Call function generateData() from function main, and it will generate the data.\n\nGenerating data using RandomTriple method is much faster than generation by RandomInstance. \n\nDatasets are available for download ((http://dbpedia.aksw.org/benchmark.dbpedia.org/ here))\n\n==== Query Generation ====\n\nQuery Log: ftp://download.openlinksw.com/support/dbpedia/\n\nIn order sort the query log by frequency of queries, do the following steps: -\n 1. In benchmark.xml file set the tag to the folder in which the query log files exist. Log files are assumed to have .log extension.\n 2. In benchmark.xml file set the tag to the output file in which the sorted queries along with the frequency of each query.\n 3. In benchmark.xml file set the tag to the value below which the query is discarded.\n 3. Call function 'sortQueries' in 'ClusterProcessor' class in order to sort the queries and write the output to the file specified in benchmark.xml, and it will also discard the queries whose frequencies are below the specified value.\n 4. (Optional) this step is optional but it is recommended in order to accelerate the clustering step. Call function 'makeIDs' in 'ClusterProcessor' class in order to give each query a unique ID and remove the common keywords e.g. from , and where, that will not affect the clustering process and will also make the clustering faster, as the strings will be shorter.\n \n Approximate time for that step is 2.5 hours.\n \nClustered Query Log:\n\n 1. Feed the file containing the queries along with their IDs to 'BorderFlow' application.\n 2. From 'BorderFlow' you will get a file containing the 'clusterID' and the queries belonging to that cluster.\n 1. By clustering you get several clusters, each cluster contains a similar set of queries, i.e. queries belonging to the same cluster should to some extent contain similar SPARQL features.\n\n\nI'm not sure of the time this step takes, probably Axel knows.\n\n\nList of Benchmark Queries: \n\nTo avoid caching of query results we should introduce a small difference in each run of the query in order to force the triplestore not fetch the query result from its cache.\nThe required steps to get our set of queries are as follows: -\n 1. Identify SPARQL-features of interest e.g. UNION, DISTINCT, OPTIONAL, ...\n 2. Select one of the queries satisfying the feature of interest using the following methodology: -\n 3. Sort the clusters descendingly by their total frequency, i.e. the cumulative sum of frequencies of all queries belong to that cluster.\n 4. Traverse the clusters in order of their total frequency, for each cluster in order select the query with the highest frequency within the cluster with the highest total frequency on condition that this query satisfies one of SPARQL feature or combination of features.\n 5. Inspect each one of the selected queries, in order to identify some static term(s), i.e. URI or literal, that can be used as a content placeholder(s).\n 6. Replace the selected static term in each query with a variable(s) and make a select query for that variable(s) only with DISTINCT in order to avoid repetition and with LIMIT to get a specific number of allowed values, this query is called 'Auxiliary Query'.\n 7. Perform the auxiliary query to get a list of allowed values for placeholder(s).\n 8. During each run of the original query replace its placeholder(s) with some random value out of its list of allowed values.\n\nThe time for selecting the queries and their auxiliary queries is approx. 3 days\n\nThe list of queries can be found in file Queries.txt, available ((http://dbpedia.aksw.org/benchmark.dbpedia.org/ here))\n\n\n\n==== Benchmark Execution ====\n\nLoading Procedures:\n\nIn order to upload data into the 3 different triplestores do a step of the following: -\n 1. For loading data to Virtuoso, there is a shell script called 'virtload.sh'. Call this shell script as './virtload.sh inputfile.nt http://dbpedia.org 1111 dba pwd' .\n 2. For loading data to Sesame, set the 'sesameInputTriplesFile' tag in benchmark.xml file to the name of the N-TRIPLES file to read from, set 'sesameServerAddress' tag to the address of the Sesame server, and set 'sesameRepositoryID' tag to the ID of the repository to which you want to upload data. Call SesameDataLoader.loadData(), and it will load the data to the store specified.\n 3. For loading data to JenaTDB, set the 'jenaTDBInputTriplesFile' tag in benchmark.xml file to the name of the N-TRIPLES file to read from, set 'jenaTDBDatasetGraph' tag to the path of 'JenaTDB' dataset. Call JenaTDBDataLoader.loadData(), and it will load the data to the dataset specified.\n 4. Since BigOWLIM, uses Tomcat and OpenRDF-Workbench like Sesame, so same settings can be used for loading data to BigOWLIM store.\n\nFor loading dataset of size 100% into virtuoso it takes approx 10 Hrs, 8 Hrs for JenaTDB, 14 Hrs for Sesame, and 8 Hrs for BigOWLIM.\n\nBenchmark Procedures:\n\nThere are 4 classes called 'VirtuosoQueryExecutor', 'JenaTDBQueryExecutor', 'SesameQueryExecutor', and 'BigOWLIMQueryExecutor' for each type of triplestore, each one of them contains a function called 'executeQuery' that takes the SPARQL query as parameter and returns the execution time of that query against the triplestore of interest in micro-seconds.\nThis function is called within a loop that works for 20 minutes for warm-up, adn then for 60 minutes for actual calculation .\n\n-----------\n\n\n=== Results ====\n\n==== June 2011 ====\n\n\n#|\n|| | | | | | |**10%** | | | | | | ||\n|| | |**Virtuoso**| | |**Sesame**| | |**Jena-TDB**| | |**BigOWLIM**| ||\n|| Query # | QpS | SD | GM | QpS | SD | GM | QpS | SD | GM | QpS | SD | GM||\n|| 1 | 261.6 | 45.3 | 250.1 | 466.3 | 136.2 | 428.8 | 330.4 | 155.5 | 258.9 | 63 | 8.9 | 61.9||\n|| 2 | 450.9 | 59 | 445.6 | 427.7 | 15.5 | 427.4 | 255.1 | 80.4 | 236.5 | 64.7 | 4.1 | 64.4||\n|| 3 | 82.8 | 16.2 | 81.3 | 348.3 | 97.3 | 320.7 | 1.4 | 1.9 | 0.6 | 55.3 | 14.8 | 52.4||\n|| 4 | 138.1 | 48.9 | 122.6 | 10 | 60 | 0.2 | 71.3 | 61.1 | 52.7 | 20.6 | 21.4 | 11.6||\n|| 5 | 67.7 | 10.9 | 67 | 287.9 | 65.3 | 269.6 | 116.1 | 70.5 | 93.3 | 46.6 | 17.5 | 42.1||\n|| 6 | 60.5 | 17.9 | 58 | 49.4 | 5.5 | 48.2 | 82.5 | 58.1 | 65.2 | 19.2 | 5.1 | 18.5||\n|| 7 | 28.5 | 8.5 | 26.7 | 207.1 | 79 | 183.7 | 1.6 | 2.5 | 0.5 | 26.5 | 13.9 | 22.7||\n|| 8 | 52.8 | 67.4 | 24.4 | 65.7 | 112.9 | 23.6 | 134 | 75.1 | 108 | 18 | 21.9 | 9.1||\n|| 9 | 22.9 | 3.9 | 22.7 | 226.9 | 86.8 | 197.8 | 0.6 | 0.6 | 0.4 | 48.9 | 9.1 | 47.4||\n|| 10 | 8.1 | 0.4 | 8.1 | 1.4 | 0.4 | 1.4 | 0.1 | 0.04 | 0.1 | 2.8 | 0.1 | 2.8||\n|| 11 | 176 | 36.2 | 171 | 289.7 | 80 | 265.8 | 125.3 | 67 | 104.9 | 51.5 | 12.6 | 49.3||\n|| 12 | 124.8 | 20.2 | 123.1 | 309.9 | 118 | 264.8 | 1 | 3 | 0.1 | 59.6 | 12.3 | 57.2||\n|| 13 | 129.3 | 16.5 | 128.3 | 367.2 | 101.4 | 337.3 | 190.1 | 77.3 | 157.9 | 46.7 | 16.4 | 43||\n|| 14 | 83.1 | 29.8 | 74.1 | 179.2 | 134.6 | 116 | 96.2 | 69 | 74 | 25.8 | 20.5 | 16.8||\n|| 15 | 128.1 | 67.6 | 90.3 | 162.6 | 148.5 | 72.6 | 97.3 | 100.2 | 43.9 | 43.1 | 23.9 | 28.4||\n|| 16 | 121.5 | 23.6 | 118.7 | 249.9 | 67.6 | 236.4 | 28.8 | 30.5 | 19.9 | 39.8 | 15.7 | 35.5||\n|| 17 | 102.2 | 29.8 | 95.7 | 186.2 | 109.5 | 135.8 | 115.6 | 63.6 | 97.6 | 42.8 | 18.9 | 36.1||\n|| 18 | 182.8 | 33.1 | 179.1 | 0.5 | 0.1 | 0.5 | 178.3 | 52.6 | 168.1 | 23.3 | 15.5 | 18.3||\n|| 19 | 199.8 | 47.9 | 191.1 | 302.5 | 69.9 | 286.7 | 200.8 | 88.9 | 174.5 | 62.2 | 4.7 | 61.9||\n|| 20 | 18.9 | 4.1 | 18.6 | 221 | 63.3 | 203.7 | 0.1 | 0.3 | 0.02 | 50.6 | 8.1 | 49.5||\n|| 21 | 483 | 48 | 480.6 | 459.4 | 16.7 | 459.1 | 289.6 | 92.5 | 224.9 | 66.1 | 1.8 | 66.1||\n|| 22 | 206.1 | 60.6 | 190.2 | 241.4 | 173.8 | 140.6 | 38 | 86 | 8.4 | 52.8 | 19.3 | 44.7||\n|| 23 | 140.3 | 27.4 | 137.1 | 354.7 | 116.9 | 315.3 | 23.9 | 39.7 | 12.6 | 64.1 | 6.1 | 63.6||\n|| 24 | 1.2 | 0.7 | 0.8 | 32.4 | 100.2 | 3.7 | 173 | 88.1 | 146.4 | 0.3 | 0.2 | 0.2||\n|| 25 | 62.8 | 19 | 59.2 | 259.8 | 120.6 | 209.5 | 110.5 | 99.8 | 68 | 52.3 | 12.5 | 49.7||\n|#\nAverage number of queries per second (QpS), standard deviation for queries per second (SD), and geometric mean for queries per second (GM), for all triplestores for 10% dataset size.\n\n------------------------------------------------------------------------------------------------\n\n#|\n|| | | | | | |**50%** | | | | | | ||\n|| | |**Virtuoso**| | |**Sesame**| | |**Jena-TDB**| | |**BigOWLIM**| ||\n|| Query # | QpS | SD | GM | QpS | SD | GM | QpS | SD | GM | QpS | SD | GM||\n|| 1 | 264.5 | 76.1 | 242 | 153.5 | 136.3 | 116.9 | 64.8 | 13.6 | 63.2 | 56.7 | 10.1 | 55.5||\n|| 2 | 22.4 | 3.2 | 22.2 | 137 | 98 | 109.9 | 87.6 | 87.9 | 68.6 | 27.7 | 12.7 | 25.6||\n|| 3 | 55.4 | 19.7 | 51.8 | 81.1 | 92 | 52.6 | 0.1 | 0.1 | 0.1 | 29.4 | 18.9 | 23.3||\n|| 4 | 44 | 62.7 | 17.6 | 0 | 0 | 0 | 41.7 | 19.5 | 38.4 | 3.9 | 3.3 | 3||\n|| 5 | 60.3 | 14 | 58 | 46.6 | 70 | 24.8 | 40.2 | 32 | 30.6 | 21.5 | 15.4 | 16.9||\n|| 6 | 14 | 7.3 | 12.3 | 6.2 | 2 | 5 | 162.5 | 69.8 | 141.3 | 5 | 2.3 | 4.3||\n|| 7 | 23.1 | 7.9 | 21.8 | 62.2 | 52.3 | 42.3 | 0.2 | 0.5 | 0.02 | 10.7 | 5.8 | 9.2||\n|| 8 | 32.5 | 46.9 | 5 | 15.6 | 39.4 | 2.7 | 88.2 | 67.3 | 67.8 | 8.2 | 13.9 | 1.7||\n|| 9 | 20.4 | 5.3 | 19.9 | 42.3 | 35.3 | 29.1 | 2.3 | 3.8 | 0.8 | 27.2 | 15.1 | 22.4||\n|| 10 | 1 | 0.1 | 1 | 0.2 | 0 | 0.2 | 4.3 | 3 | 1 | 0.28 | 0.02 | 0.28||\n|| 11 | 97.7 | 56.9 | 73.9 | 45.2 | 48.1 | 36.3 | 37 | 7.1 | 36.3 | 27 | 10.1 | 24||\n|| 12 | 62.3 | 22.2 | 57.6 | 56.3 | 58.2 | 42.4 | 0.02 | 0.02 | 0.02 | 34.1 | 18.9 | 28.7||\n|| 13 | 105.1 | 52.1 | 91.7 | 97.5 | 60.4 | 86.8 | 105 | 94.3 | 44.9 | 19.9 | 10.4 | 17.9||\n|| 14 | 53.9 | 40 | 38 | 20.4 | 17.6 | 12.3 | 42.8 | 13.2 | 40.9 | 7.9 | 10.6 | 3.3||\n|| 15 | 51.9 | 32.7 | 33.4 | 33.5 | 66.1 | 11.5 | 43.1 | 38.9 | 32.8 | 8.6 | 13.7 | 2.2||\n|| 16 | 106.7 | 25.4 | 103.4 | 87.7 | 75.4 | 64.8 | 73.2 | 48.3 | 63 | 38.7 | 12.9 | 36.7||\n|| 17 | 33 | 11.2 | 30.6 | 20.9 | 19.9 | 13.3 | 31.9 | 9.5 | 30.5 | 10.3 | 8.5 | 6||\n|| 18 | 203.9 | 57.9 | 190.4 | 0.1 | 0 | 0.1 | 57.6 | 9.6 | 56.9 | 29 | 12.7 | 26.4||\n|| 19 | 106.6 | 53.6 | 93.5 | 46.1 | 38.1 | 39.7 | 26.8 | 10.2 | 25.3 | 33.7 | 16.9 | 29.9||\n|| 20 | 15 | 4 | 14.5 | 37.7 | 30.6 | 28.9 | 0.01 | 0 | 0.01 | 20.5 | 16.2 | 15.2||\n|| 21 | 189.1 | 138.3 | 135 | 105.6 | 87.3 | 84.3 | 50 | 16.2 | 46.4 | 28.1 | 13.4 | 25.7||\n|| 22 | 109.1 | 43.9 | 90.3 | 29.5 | 41.4 | 14 | 1.2 | 1.5 | 0.7 | 15.7 | 15.9 | 6.1||\n|| 23 | 81.2 | 31.4 | 74.4 | 78.3 | 97.4 | 47 | 1.5 | 2.4 | 0.4 | 32.4 | 18.2 | 27.9||\n|| 24 | 0.2 | 0.1 | 0.2 | 0.9 | 0.4 | 0.7 | 53.7 | 39.3 | 43.6 | 0.06 | 0.05 | 0.04||\n|| 25 | 35.6 | 10.9 | 33.3 | 45.2 | 57.4 | 26.4 | 37.1 | 16 | 32.4 | 11.5 | 7.6 | 8.6||\n|#\nAverage number of queries per second (QpS), standard deviation for queries per second (SD), and geometric mean for queries per second (GM), for all triplestores for 50% dataset size.\n\n------------------------------------------------------------------------------------------------\n\n#|\n|| | | | | | |**100%** | | | | | | ||\n|| | |**Virtuoso**| | |**Sesame**| | |**Jena-TDB**| | |**BigOWLIM**| ||\n|| Query # | QpS | SD | GM | QpS | SD | GM | QpS | SD | GM | QpS | SD | GM||\n|| 1 | 245.9 | 30.9 | 240.9 | 112.7 | 47.1 | 103.9 | 54.5 | 5.9 | 54.2 | 58.3 | 6.1 | 57.9||\n|| 2 | 3.6 | 0.1 | 3.6 | 81.1 | 45.9 | 69.8 | 67.1 | 40 | 60 | 31 | 11.8 | 28.7||\n|| 3 | 42.8 | 21.8 | 37.8 | 32.1 | 14.5 | 28.9 | 0.02 | 0.03 | 0.01 | 23.9 | 7.7 | 22.8||\n|| 4 | 34 | 50.2 | 14.4 | 0.03 | 0.01 | 0.02 | 4.6 | 9.1 | 0.3 | 29.4 | 22.4 | 18.8||\n|| 5 | 47.9 | 19.7 | 41.7 | 10.7 | 10.6 | 7.6 | 12.5 | 4.9 | 11.5 | 16.1 | 14.5 | 11.1||\n|| 6 | 8.6 | 2.3 | 8.3 | 4.2 | 2.4 | 2.8 | 45.5 | 46.9 | 9.6 | 4.9 | 2.3 | 4.1||\n|| 7 | 21 | 12.1 | 18.2 | 21.5 | 37.4 | 13.8 | 0.04 | 0.03 | 0.03 | 7.4 | 4.5 | 6.1||\n|| 8 | 38.3 | 47.7 | 4.8 | 17.8 | 33.7 | 2.7 | 27.1 | 36.7 | 1.3 | 8.3 | 14.5 | 1||\n|| 9 | 17.8 | 5.7 | 17.1 | 23.3 | 15.9 | 19.5 | 0.01 | 0 | 0.01 | 15.9 | 6.3 | 14.9||\n|| 10 | 1 | 0.1 | 0.9 | 0.1 | 0 | 0.1 | 0.01 | 0 | 0.01 | 0.16 | 0.01 | 0.16||\n|| 11 | 115.7 | 31.7 | 100.2 | 48.5 | 41.9 | 39.4 | 2.9 | 5.7 | 0.2 | 36.2 | 14.4 | 33.2||\n|| 12 | 47.1 | 25.4 | 41.7 | 25.4 | 12.9 | 21.7 | 0.01 | 0 | 0.01 | 24.6 | 9.7 | 22.9||\n|| 13 | 89.5 | 73.6 | 64.6 | 43.1 | 41.4 | 28.6 | 0.2 | 0.2 | 0.1 | 38.1 | 17.9 | 33.6||\n|| 14 | 25.1 | 37.3 | 6 | 3.4 | 5.2 | 1 | 26.3 | 15.7 | 23 | 28.1 | 26.8 | 8.5||\n|| 15 | 48.4 | 33.2 | 31.1 | 3.1 | 4.7 | 1.3 | 0.04 | 0.04 | 0.02 | 7.9 | 12.2 | 2.5||\n|| 16 | 137.3 | 14.4 | 136.7 | 98.8 | 49.4 | 89.7 | 29.3 | 30.8 | 6.2 | 48.5 | 10.4 | 47.1||\n|| 17 | 32.8 | 9.3 | 31.2 | 6.3 | 6.5 | 2.7 | 21.7 | 8.1 | 20.3 | 21.5 | 14.8 | 12.3||\n|| 18 | 208.3 | 27.1 | 205.6 | 0.1 | 0 | 0 | 44.8 | 34.8 | 9.2 | 47 | 8.3 | 46.1||\n|| 19 | 99.2 | 67.3 | 81.8 | 40.3 | 20.6 | 35.8 | 46.5 | 24.6 | 40.9 | 34.9 | 7 | 34.2||\n|| 20 | 14.1 | 4.1 | 13.5 | 8.2 | 6.6 | 6.8 | 0.01 | 0 | 0.01 | 15.1 | 8.3 | 13.5||\n|| 21 | 98.8 | 76.2 | 78.3 | 85.7 | 69 | 69.2 | 0.1 | 0.1 | 0.1 | 31.3 | 10.5 | 29.7||\n|| 22 | 115.1 | 52.9 | 93.6 | 5.5 | 8.5 | 2 | 9.5 | 13.3 | 0.6 | 9.5 | 10.6 | 4.6||\n|| 23 | 76.7 | 38.9 | 67.8 | 41 | 17.8 | 37.6 | 20.2 | 34.4 | 0.8 | 29.1 | 8.4 | 28.2||\n|| 24 | 0.2 | 0.1 | 0.1 | 0.7 | 0.4 | 0.4 | 17.4 | 15 | 3.7 | 0.05 | 0.05 | 0.03||\n|| 25 | 30.1 | 11 | 27.1 | 16.5 | 14.5 | 10.3 | 18.1 | 22.5 | 1.2 | 14.3 | 9.4 | 11||\n|#\nAverage number of queries per second (QpS), standard deviation for queries per second (SD), and geometric mean for queries per second (GM), for all triplestores for 100% dataset size.\n\n------------------------------------------------------------------------------------------------\n\n#|\n|| | | | | | |**200%** | | | | | | ||\n|| | |**Virtuoso**| | |**Sesame**| | |**Jena-TDB**| | |**BigOWLIM**| ||\n|| Query # | QpS | SD | GM | QpS | SD | GM | QpS | SD | GM | QpS | SD | GM||\n|| 1 | 247.1 | 44.4 | 229.9 | 93.2 | 39.2 | 84.4 | 226.9 | 465.5 | 36.6 | 54.5 | 13.4 | 47.7||\n|| 2 | 1.8 | 0.1 | 1.8 | 45.7 | 27.4 | 39.9 | 17.6 | 6.4 | 16.6 | 26.8 | 11.2 | 24.5||\n|| 3 | 42.8 | 21.1 | 36.6 | 19.8 | 9.1 | 17.7 | 0.03 | 0.02 | 0.02 | 18.1 | 8.2 | 16.7||\n|| 4 | 26.8 | 46.1 | 12.1 | 0 | 0 | 0 | 45.9 | 33.6 | 34.4 | 6.8 | 9 | 4.1||\n|| 5 | 52.7 | 19.8 | 47.4 | 5.5 | 2.7 | 4.7 | 5.7 | 4.3 | 3 | 11.8 | 10.4 | 8.7||\n|| 6 | 9.4 | 6.1 | 7.6 | 2.4 | 2 | 1.4 | 34.6 | 47 | 15.1 | 2.9 | 1.3 | 2.6||\n|| 7 | 14.3 | 9.3 | 11.7 | 7.1 | 2.4 | 6.6 | 0.01 | 0 | 0.01 | 8.7 | 5.3 | 7||\n|| 8 | 33.6 | 42.9 | 2.8 | 3.8 | 6.7 | 0.4 | 21.8 | 19.9 | 13.9 | 8.8 | 15.7 | 1||\n|| 9 | 16.1 | 6 | 15.1 | 9.9 | 3.2 | 9.5 | 0.02 | 0.04 | 0.01 | 14.5 | 5.1 | 13.6||\n|| 10 | 0.5 | 0 | 0.5 | 0.1 | 0 | 0 | 0.01 | 0 | 0.01 | 0.16 | 0.02 | 0.16||\n|| 11 | 114.7 | 57.5 | 73 | 34.3 | 17.2 | 30.5 | 15.9 | 2.7 | 15.6 | 21 | 7.9 | 19.2||\n|| 12 | 43.8 | 31.8 | 36.1 | 18 | 8.1 | 15.7 | 0.01 | 0 | 0.01 | 21.1 | 5.4 | 20.4||\n|| 13 | 64.7 | 51.8 | 48.6 | 21.7 | 13.2 | 18.5 | 13.6 | 9.5 | 11.1 | 20.1 | 10.3 | 18.2||\n|| 14 | 23.9 | 29.5 | 11.4 | 1.7 | 2.8 | 0.4 | 7.2 | 2.9 | 6.5 | 6.3 | 6.5 | 3.4||\n|| 15 | 65.1 | 51.5 | 36.9 | 3.3 | 4.5 | 1.4 | 1.8 | 1.6 | 1.2 | 3.8 | 8.8 | 0.8||\n|| 16 | 191.2 | 24.1 | 189.8 | 83.6 | 40.3 | 74.9 | 11.1 | 3.1 | 10.6 | 45.4 | 10.6 | 44||\n|| 17 | 24.1 | 12.2 | 19.4 | 1.6 | 1.8 | 0.8 | 6.9 | 1.7 | 6.8 | 9.1 | 6.7 | 6.8||\n|| 18 | 212 | 35.8 | 207.3 | 0 | 0 | 0 | 19.7 | 7.9 | 17.5 | 44 | 8.3 | 43.1||\n|| 19 | 84.8 | 62.5 | 69 | 15.9 | 4.3 | 15.3 | 22.4 | 13 | 19.6 | 34 | 8.9 | 32.7||\n|| 20 | 13.6 | 4.4 | 12.9 | 8.6 | 17.5 | 4.5 | 0.01 | 0 | 0.01 | 13.1 | 8.2 | 11.5||\n|| 21 | 93.8 | 77 | 73.7 | 53.6 | 20.8 | 50 | 15.9 | 4.9 | 15.2 | 26.5 | 6.3 | 25.7||\n|| 22 | 120 | 80.5 | 74.3 | 20.7 | 66.2 | 2.1 | 0.6 | 0.6 | 0.4 | 11.1 | 11.5 | 5.9||\n|| 23 | 67.6 | 33.3 | 60.1 | 30.3 | 16.7 | 26.9 | 9.2 | 5.9 | 6.9 | 24.1 | 5.5 | 23.6||\n|| 24 | 0.1 | 0 | 0.1 | 0.3 | 0.2 | 0.2 | 8.3 | 4.8 | 6.4 | 0.05 | 0.05 | 0.02||\n|| 25 | 23.5 | 15.2 | 19 | 8.1 | 7.8 | 5.2 | 9.2 | 1.6 | 9 | 11.6 | 9.5 | 8.6||\n|#\nAverage number of queries per second (QpS), standard deviation for queries per second (SD), and geometric mean for queries per second (GM), for all triplestores for 200% dataset size.\n" . . . . "2007-08-18T10:14:32"^^ . "((DL-Learner DL-Learner))" . . . . "2008-08-05T15:44:45"^^ . "{{Include page=\"/Projects/DLLearner/Menu\" divclass=\"floatbox\" nomark=\"1\"}}\n==Overview==\nDL-Learner is a tool for learning concepts in Description Logics (DLs) from user-provided examples. Equivalently, it can be used to learn classes in OWL ontologies from selected objects. The goal of DL-Learner is to support knowledge engineers in constructing knowledge and learning about the data they created.\n\n===Learning Problem===\nGiven: background knowledge base, positive + negative examples (for a not yet defined concept)\nGoal: a concept definition, such that when the definition is added to the background knowledge all positive examples follow and none of the negative examples follow\n\nSee also the ((http://en.wikipedia.org/wiki/Inductive_logic_programming Wikipedia entry for ILP)) (Inductive Logic Programming). What DL-Learner considers is the the ILP problem applied to Descriptions Logics / OWL.\n\n===Architecture===\nThe following figure gives an overview of the \"generate and test\" approach used in DL-Learner and other inductive learning tools:\n\nhttp://aksw.org/Projects/DLLearner/Overview/files?get=architecture.png\n\nInput for the learning algorithm are examples and background knowledge. DL-Learner itself is a framework for several learning algorithms like a refinement operator based algorithm and a genetic programming based algorithm (see publications for details). These algorithms use a generate and test approach. This means they generate concepts, which appear to be useful to them. They evaluate them using a concept quality measure (a heuristics). To measure the quality a Description Logic reasoner is required. The DL-Learner uses the so-called DIG interface to communicate with reasoners. This means that all DIG capable reasoners, i.e. alle popular reasoners, can be used. The concept generation procedure is repeated until a solution (or a sufficiently good concept) has been found.\n\n===Learning Example===\nOne of the simplest examples for concept learning is to learn the concept \"father\". Assume the following background knowledge is given (Description Logic syntax):\n\nhttp://aksw.org/Projects/DLLearner/Overview/files?get=father_example_small.png\n\nIn this case, an ontology learning system could learn the concept definition \"Male AND EXISTS hasChild.TOP\", i.e. all objects, which are male and have at least one child." . . . . "2007-08-27T18:44:14"^^ . "{{Include page=\"/Projects/DLLearner/Menu\" divclass=\"floatbox\" nomark=\"1\"}}\n==Related Work==\n\nRelated Systems:\n * ((http://www.di.uniba.it/~iannone/yinyang/ YinYang)) - also learns OWL class definitions from examples\n\nRelated Projects:\n * ((http://kater.uni-koblenz.de/~openconf/multipla/ Multi-Ontology Learning))\n\nLibraries:\n * ((http://www.neon-toolkit.org/ NEON Toolkit))\n * ((http://owlapi.sourceforge.net/ OWL API))\n * ((http://jena.sourceforge.net/ Jena))\n\nUsed Reasoners:\n * ((http://pellet.owldl.com/ Pellet))\n * ((http://owl.man.ac.uk/factplusplus/ FaCT++))\n * ((http://www.racer-systems.com Racer Pro))\n * ((http://kaon2.semanticweb.org/ KAON2))\n" . . . . "2007-08-23T17:23:13"^^ . "{{Include page=\"/Projects/DLLearner/Menu\" divclass=\"floatbox\" nomark=\"1\"}}\n==Ontology Learning==\n===Motivation===\nWithin the last decade, ontologies have emerged as a powerful standard for representing computer-tractable knowledge. Amongst others, the Semantic Web initiative is one of the driving forces behind this development. Current ontology languages like OWL-DL have stable, well-founded and expressive semantics using Description Logics as underlying knowledge representation standard. While the benefits of using ontologies are now well understood, their creation and maintenance is still a burdensome task. Knowledge engineers need more powerful tool support to evolve and manage ontologies.\n\n===Research===\nOne of the keys for designing learning algorithms in Description Logics are refinement operators. They allow for an efficient traversal of the subsumption hierarchy of concepts. One way to assess the suitability of a refinement operator for learning algorithms is to look at its properties. We analyse the properties (completeness, weak completeness, properness, redundancy, finiteness, minimality, and their combinations) and show theoretical limitations.\n\nLearning algorithms can be designed by combining a refinement operator with a a search heuristic. We are interested in designing operators which are close to the best one can hope for and combine them with intelligent search heuristics.\n\nAs a second approach we investigate the use of Genetic Programming (GP) to solve the learning problem in Description Logics. In particular, we are interested in hybrid technologies combining the evolutionary inspired GP with refinement operator based search." . . . . "2008-07-30T17:11:05"^^ . "{{Include page=\"/Projects/DLLearner/Menu\" divclass=\"floatbox\" nomark=\"1\"}}\n==DIG Reasoner Installation==\nWe can recommend the usage of ((http://owl.man.ac.uk/factplusplus/ FaCT++)) (recommended: latest version) and ((http://pellet.owldl.com/ Pellet)) (recommended: latest version) as reasoners. **Note that you can also use the OWL API reasoner interface, so installing a DIG reasoner is optional.**\n\n===Installation of ~FaCT++===\nLinux:\n * download and extract ~FaCT++\n * use a shell and change to the bin subdirectory of ~FaCT++\n * execute e.g. \"./~FaCT++.Server -port 8081\" to get ~FaCT++ runnning on port 8081\nWindows:\n * download and extract ~FaCT++\n * run \"~FaCT++.Server.exe\" -port 8081 in a console\n\n===Installation of Pellet===\nLinux:\n * download and extract Pellet\n * use a shell and change to the Pellet directory\n * execute e.g. \"./pellet-dig.sh\" to get Pellet runnning on port 8081\nWindows:\n * download and extract Pellet\n * run pellet-dig.bat in the Pellet directory\n" . . . . "2011-03-29T16:00:12"^^ . "{{Include page=\"/Projects/DLLearner/Menu\" divclass=\"floatbox\" nomark=\"1\"}}\n==Developing DL-Learner using Eclipse==\nInstructions on how to prepare Eclipse for developing DL-Learner:\n\n 1. Make sure you have Java 6, Maven 2 and Eclipse installed. \n 2. Install the ((http://subclipse.tigris.org/ Subclipse plugin)) for Subversion support.\n 3. Install the ((http://m2eclipse.sonatype.org/sites/m2e Eclipse m2e Maven plugin )) for Maven support and ((http://m2eclipse.sonatype.org/sites/m2e-extras m2e extras)) \"Maven SCM handler for Subclipse\".\n 4. \"File >> New >> Other...\" >> \"Checkout Maven Projects from SCM\"\n 5. Set SCM URL type to \"svn\" and enter https://dl-learner.svn.sourceforge.net/svnroot/dl-learner/trunk as URL\n 6. Choose \"Finish\"\n\nYou should now be ready to develop DL-Learner in Eclipse. DL-Learner uses the standard code conventions with the only difference that the maximum line length is 100 instead of 80 (Project >> Properties >> Java Code Style >> Formatter >> Edit >> Line Wrapping Tab >> enter \"100\" as maximum).\n\nSome Java 6 versions ship with restrictions of the internal com.sun.net classes, since there is no long term support for those classes. If you see access restriction errors in Eclipse, then go to \"Window\" >> \"Preferences\" >> \"Java\" >> \"Compiler\" >> \"Errors/Warnings\" >> \"Deprecated and Restricted API\" >> \"Forbidden Reference\" and set to \"Ignore\" instead of \"Error\". This is only necessary in some Java 6 JDKs.\n\nSimilar instructions apply to other IDEs.\n\nHint: DL-Learner is a Maven multi module project. If you have several such projects in Eclipse, the package explorer can become cluttered. We recommend to put all DL-Learner modules in a working set. We also recommend to use the hierarchical view in the package explorer, because DL-Learner contains many nested packages.\n\n%%(comments)\n * Download and install the ((http://subclipse.tigris.org/ Subclipse Plugin)) for Subversion support.\n * Create a new Subversion project with URL https://dl-learner.svn.sourceforge.net/svnroot/dl-learner -> select trunk folder.\n * The files classpath.dist and project.dist are contained in the Subversion Repository (directory /doc/eclipse). If you rename them to .classpath and .project and move them in your project directory (you should be overwriting the existing files there - make sure you exit Eclipse first) then the libraries and project properties will be set up for you. Alternatively, you can configure the classpath and project settings yourself within Eclipse.\n * --Download ((http://kaon2.semanticweb.org/ KAON2)) and place kaon2.jar in the /lib folder, pay attentation to the KAON2 license - KAON2 is not freely distributable and therefore cannnot be included in DL-Learner.-- (no longer necessary)\n * You may have to add tools.jar to your class path, tools.jar is in the lib directory of your JDK directory (the best way to do this, is to go to \"Window\" >> \"Preferences\" >> \"Java\" >> \"Installed JREs\" and add it to the JRE you use).\n\nSimilar instructions apply to other IDEs.%%" . . . . "2008-05-21T19:17:37"^^ . "{{Include page=\"/Projects/DLLearner/Menu\" divclass=\"floatbox\" nomark=\"1\"}}\n==Writing Clients==\n\n===Starting the Web Service===\nThe Web Service currently starts its own mini-server which runs at a certain address, e.g.\nhttp://localhost:8181/services\nIt automatically creates a wsdl file which can then be found at http://localhost:8181/services?wsdl\n\n===PHP Clients===\n====Existing Client====\n--The DL-Learner comes with an existing php-client. It is based upon the soapclient package, which comes with the php distribution. It is supposed to have an MVC architecture, but currently the M and the V are mixed. Future work will be to separate the model and the view to allow easier and faster client developement and integration into other applications like OntoWiki.-- \nThe PHP client is now deprecated. OntoWiki will be used as a client in the future and there is a complete Java GUI for DL-Learner.\n\n====How to start writing a client====\nThe PHP SOAP library allows to write clients in any standard PHP installation. The src/php-examples subversion directory contains small examples of how to access and use the DL-Learner web service.\n%%(comments)\nCurrently there is a class LearnerClient.php which mirrors the functions provided by the java Web-Service. There are some problems though with the communication between a java SOAP-server and a PHP SOAP-client so that there is a work around for automatic WSDL acquisition. Later work will provide a full library which abstracts further from the single web service functions.\n%%\n\n===Clients in any other language===\nSince the web service is based on standards like WSDL, it can be accessed using any programming language. All you need is basic support for web services, such that the WSDL service description can be interpreted.\n\n%%(comments)\n===Java Clients===\nSince the Web-Service is written in Java, it \"should\" be easily accessible with a Java Client. Currently though, this feature is not supported and plans to support it do as of now not exist. See maybe ((http://users.skynet.be/pascalbotte/rcx-ws-doc/seiclient.htm here)) or else try and google.\n%%\n" . . . . "2012-01-03T08:10:07"^^ . "==Publications==\n\n**Note on Citing**: If you want to refer to the software DL-Learner, please cite the ((http://jens-lehmann.org/bibtex.php?document_id=49 Journal of Machine Learning Research (JMLR) article)), which appeared in the open source track. If you want to refer to the algorithms and methods used in DL-Learner, please cite the ((http://jens-lehmann.org/bibtex.php?document_id=48 Machine Learning journal (MLj) article)).\n\n%%(exhibit jsonp=\"http://www.bibsonomy.org/json/user/aksw/dllearner?items=1000&callback=cb\")\n\n \n \n \n \n \n
\n

\n\n:\n\n\n\n(Editors:\n\n)\n\n\n\n\n

\n 		\n

\n\n\n\n\n

\n
\n\n%%\n\nFurther lists:\n * ((http://www.bibsonomy.org/user/jens/concept_learning list of related publications))\n * ((http://jens-lehmann.org/index.php?content=dl_learning list of related publications authored by Jens Lehmann))\n" . . . . "2011-11-30T12:52:25"^^ . " 1. About\n - <# Overview #>\n - <# Ontology Learning #>\n - <# Features #>\n - <# Screenshots #>\n - <# Demo #>\n - ((http://sourceforge.net/project/showfiles.php?group_id=203619 Download))\n 2. Docs\n - ((http://dl-learner.org/files/dl-learner-manual.pdf Manual))\n - <# List of Components and Config Options #>\n - <# Basic Installation #>\n - <# Reasoner Installation #>\n - <# Web Service Installation #> \n - <# First Steps #> \n - <# Javadoc #> \n 3. Development\n - <# Architecture #>\n - <# Maven #>\n - <# ChangeLog #>\n - <# Eclipse & DL-Learner #>\n - <# Code Style #>\n - <# Writing Clients #>\n - <# Contact Developers #>\n - <# Topics for Theses #>\n 4. Community\n - ((http://sourceforge.net/projects/dl-learner/ SF.net Project Page))\n - ((http://sourceforge.net/mail/?group_id=203619 Mailing Lists))\n - <# Carcinogenesis #>\n - <# OntoWiki Plugin #> \n - <# Protégé Plugin #>\n - <# ORE Tool #> \n - <# Learning Examples #>\n - <# Publications #>\n - <# Related Work #>\n\n%%(comments)\nStartseite: Navigation, Screenshot, Kurzbeschreibung, News\n%%\n\n" . . . . "2009-04-15T17:21:53"^^ . "{{Include page=\"/Projects/DLLearner/Menu\" divclass=\"floatbox\" nomark=\"1\"}}\n==Contact Developers==\n\n===Developers===\n * ((http://jens-lehmann.org Jens Lehmann))\n * ((http://bis.informatik.uni-leipzig.de/SebastianHellmann Sebastian Hellmann)) (SPARQL component)\n * Sebastian Knappe (DBpedia Navigator)\n * Tilo Hielscher (DL-Learner GUI)\n * Lorenz Bühmann (Ontology Repair and Enrichment Tool)\n * Maria Moritz, Vu Duc Minh (~OntoWiki plugin)\n * Christian Kötteritzsch (Protégé 4 plugin)\n\n===Contributors===\n * Christoph Haase (joint development of ideal refinement operator for EL)\n * Sebastian Bader (Prolog Parser)\n\n===Contact===\nIn general, please use the discussion ((http://sourceforge.net/mail/?group_id=203619 mailing list)) (low traffic) for asking questions about DL-Learner. The developers are subscribed to this list and will answer your mails as soon as possible.\n\nIf the public mailing list is not appropriate, you can contact ((http://jens-lehmann.org Jens Lehmann)) (project admin) directly.\n" . . . . "2011-06-07T13:00:46"^^ . "{{Include page=\"/Projects/DLLearner/Menu\" divclass=\"floatbox\" nomark=\"1\"}}\n==Web Service Installation==\n\n===Latest Stable Release===\nPlease make sure you have completed the ((Installation basic installation)).\n\nTo run the DL-Learner web service you can use the files \"ws\" and \"ws.bat\". They create a local server, which clients can connect to.\n\nFor writing your own clients, please have a look at the wiki page on ((WritingClients writing clients)).\n\n===Subversion===\nIf you want to develop DL-Learner, please follow the instructions for running DL-Learner in your IDE as described ((http://dl-learner.org/Projects/DLLearner/Eclipse here)) for Eclipse. Use org.dllearner.server.DLLearnerWSStart as start class for the DL-Learner web service (Maven command line: mvn exec:java -Dexec.mainClass=\"org.dllearner.server.DLLearnerWSStart\").\n\n%%(comments)\nIf you do not want to develop DL-Learner, but use the Web Service Interface, you can do the following:\n * create a temporary directory and change to it\n * checkout DL-Learner: ##svn co ~http://dl-learner.svn.sourceforge.net/svnroot/dl-learner/trunk/ .##\n * ##ant## (((http://ant.apache.org/ Apache Ant)) required) - this builds DL-Learner release files, which you can use in the same way as the stable release, i.e. extract the file and run ws or ws.bat (using ##ant local## will be sufficient for compiling the Web Service, don't forget to make the script executable by using ##chmod +x local/ws##)\n%%\n" . . . . "2009-04-20T10:13:49"^^ . "{{Include page=\"/Projects/DLLearner/Menu\" divclass=\"floatbox\" nomark=\"1\"}}\n==Learning Examples==\nHere is a preview of some of the simpler test learning examples, which are included in DL-Learner:\n\n**Trains** \n\nAn example by Michalski (see ((http://www.mli.gmu.edu/papers/79-80/80-05.pdf paper))).\n\nhttp://dl-learner.org/Projects/DLLearner/LearningExamples/files?get=trains.png\n\n**Arches** \n\nClassical example in the ML literature (rewritten, originally published in //Winston, P.H. (1975). Learning structural descriptions from examples. In P.H. Winstons (Ed.), The psychology of computer vision. New York: McGraw-Hill.//).\nhttp://dl-learner.org/Projects/DLLearner/LearningExamples/files?get=arch_neu.png\n\n**Moral Reasoner**\n\nA Prolog program which we rewrote to OWL and learned concepts in it (see ((http://mlearn.ics.uci.edu/databases/moral-reasoner/))).\n\n<# #>\n\n\n**Poker**\nFinding the definition of decks in Texas Hold'em for randomly created sets of 5 cards.\n\nhttp://dl-learner.org/Projects/DLLearner/LearningExamples/files?get=21.png http://dl-learner.org/Projects/DLLearner/LearningExamples/files?get=19.png http://dl-learner.org/Projects/DLLearner/LearningExamples/files?get=13.png http://dl-learner.org/Projects/DLLearner/LearningExamples/files?get=10.png http://dl-learner.org/Projects/DLLearner/LearningExamples/files?get=8.png\n\n%%(comments)\n#|\n|| **Trains** \n\nAn example by Michalski (see ((http://www.mli.gmu.edu/papers/79-80/80-05.pdf paper))).\n| http://dl-learner.org/Projects/DLLearner/LearningExamples/files?get=trains.png||\n|| **Arches** \n\nClassical example in the ML literature (rewritten, originally published in //Winston, P.H. (1975). Learning structural descriptions from examples. In P.H. Winstons (Ed.), The psychology of computer vision. New York: McGraw-Hill.//).\n| http://dl-learner.org/Projects/DLLearner/LearningExamples/files?get=arch_neu.png ||\n|| **Moral Reasoner** \n\nA Prolog program which we rewrote to OWL and learned concepts in it (see ((http://mlearn.ics.uci.edu/databases/moral-reasoner/))).\n| <# #>||\n|#\n%%\n" . . . . "2011-07-11T10:37:37"^^ . "<#\n
\n

xOperator

\n\n\n

combines advantages of social network websites with instant messaging.

\n

A semantic agent for xmpp / jabber network which finds and shares content about resources (using RDF/SPARQL) for you and your jabber friends.

\n

Download xOperator

\n
\n
\n{{Include page=\"/Projects/xOperator/Menu\" nomark=\"1\"}}\n
\n
#>\n{{a name=\"updates\"}}{{feed divclass=\"floatbox\" title=\"Project Updates\" url=\"http://code.google.com/feeds/p/xoperator/updates/basic\" max=\"5\"}}\n{{a name=\"News\"}}{{feed divclass=\"box\" title=\"News\" url=\"http://blog.aksw.org/category/projects/xoperator/feed/\" max=\"2\"}}{{a name=\"Overview\"}}\n==Introduction==\nInstant Messaging is in addition to Web and Email the most popular service on the Internet. With xOperator we present a strategy and implementation which deeply integrates Instant Messaging networks with the Semantic Web. The xOperator concept is based on the idea of creating an overlay network of collaborative information agents on top of social IM networks. It can be queried using a controlled and easily extensible language based on AIML templates. Such a deep integration of semantic technologies and Instant Messaging bears a number of advantages and benefits for users when compared to the separated use of Semantic Web technologies and IM, the most important ones being context awareness as well as provenance and trust.\n\n==Idea==\nInspired by Tim Berners-Lee's Semantic Agent the xOperator lifts personal knowledge exchange to a new level. Imagine sharing exactly the information you want with the people you trust. Need a phone number? Want to know the birthday of your best friends girlfriend (and in a second step where to buy her a present in a store near you)? Do you get tired to tell everybody that you have a new cellphone number? xOperator enables users to share all that knowledge in a trusted network. Built upon the already existing jabber network (secure connections, widely available) an agent running on your pc allows other users to query your RDF-database returning the favor to you.\n\nMillions of people already share their information on Social Network Sites, only for designated friends to see of course. The great drawback is though that actually, they are helping to maintain a great database for the companies offering these services. Once the Semantic Web will be fully implemented it might also enable the possibility to unify personal information about an individual from different sources. xOperator keeps all data on your computer, giving you the choice what to share with whom and best of all it can't take away that choice by changing the terms and conditions.\n\nDespite all this ideology, xOperator will be, surely, once it exists, a very cool thing to use, which is to say, we are very exited ourselves, what uses it can be put to.\n\n==Vision==\nxOperator tries to create a decentralized network of trust. Information is shared in the form of resources, which can be anything (even the information that you are selling your old washing machine). In a later stage it enables you to find friends of friends like centralized services, can already. At the end of the road, xOperator might even be able to find the best product for you without the normally necessary tedious internet research. Companies will be able to offer semantic annotated information about their products, giving the customer a new way of yet unknown price transparency.\n" . . . . "2009-05-08T18:11:01"^^ . " ATTENTION: THIS PAGE IS OUTDATED - FOR A CURRENT VERSION, HAVE A LOOK AT http://code.google.com/p/ontowiki/wiki/InterfaceImplementation\n{{Include page=\"/Projects/OntoWiki/Menu\" divclass=\"floatbox\" nomark=\"1\"}}\n==Default Theme Styles==\n\nWith OntoWiki !!0.8!! we change the default theme. Using generic classes it should be easier to enhance OntoWiki by new functionality.\n\nGenerally we have two sections, one for the main content like views on information in the knowledge bases, one for side content like lists of knowledge bases or class overviews.\n\n%%(html)\n
\n \n
\n
\n \n
\n%%\n\n{{toc}}\n\n===Windows===\n\nWe are using window boxes for all content. Windows can be added to ##section-mainwindows## as well as to ##section-sidewindows##. Each window must have a title and content. It can be extended by a window specific context menu, a drop down menu, tabs for different contents and content specific windows laying inside other windows.\n\nA basic window is done by:\n\n%%(html)\n
\n

Window Title

\n
\n \n
\n
\n%%\n\n====Drop down menu and Context menu====\n\nYou can add menus by adding them after the content:\n\n%%(html)\n
\n

Window Title

\n
\n \n
\n\n \n\n
\n \n \n
\n
\n%%\n\nWithout Javascrip both menus are displayed under the content in the order you placed them. With Javascript you will get a real drop down menu and and context menu (under the left symbol at the title) like you know it from desktop applications.\n\n====Tabbed content====\n\nSometimes it is helpful to have different tabs and tab related content, for example for different views on same information or collateral content (like the tabs in your browser).\n\n%%(html)\n
\n

Window Title

\n \n\n
\n

Tab title One

\n \n
\n
\n

Tab title One

\n \n
\n
\n

Tab title One

\n \n
\n\n \n
\n%%\n\nWithout javascript it is displayed as linear content with upper navigation links, with javascript only the active content is displayed and the tabs can be used to switch between the different contents. !!You have to declare at the tab section which content is displayed on initiation (use li.active).!!\n\n====Inside windows====\n\nIt may be helpful to have windows laying inside other windows, for example to pick different tools to work on displayed content. You only need to part your content from the section for inside windows:\n\n%%(html)\n
\n

Window Title

\n
\n
\n \n \n
\n

Window Title

\n \n
\n \n
\n
\n \n
\n\n \n
\n
\n%%\n\n!!Please take care about your document structure.!! When you have tabbed content -- where you use level 2 headlines for each content -- you should use level 3 headlines for titles of inside windows. Like in normal windows you can use drop down menu and context menu for inside windows.\n\n====Window buttons====\n\nButtons for the context menu, minimize/restore window and close window will be automatically generated by javascript. The Button for the context menu is inserted if you added a context menu to the window. Buttons for minimize/restore and close window will be inserted in every window. You can change this behaviour by adding some class values to the ##div.window##: ##
##. Possible values are:\n\n * ##is-minimized##: window is minimized when rendered first\n * ##dont-resize##: window cannot be minimized/restored or vertically resized (!!not implemented yet!!)\n * ##dont-close##: window cannot be closed (!!not implemented yet!!)\n\n===List elements===\n\nWe are using generic class values for layouting ordered and unordered lists:\n\n * ##bullets-none##: list without bullets or counting numbers\n * ##bullets-disc##: use a disc (filled circle) as bullet for list items\n * ##bullets-square##: use a filled square as bullet for list item\n * ##bullets-decimals##: use counting numbers for list items (makes only sense with ordered lists)\n\nWe have two class values for vertical and horizontal separations between list items (our standard style sheet uses a dotted light gray line):\n\n * ##separated-vertical##: list items will be displayed one below the other and they are separated by a horizontal line\n * ##separated-horizontal##: list items will be displayed like inline elements (like text) in a row, separated by small vertical lines\n\nYou can combine those class values, e.g.: ##
    ##.\n\n===Tables===\n\nYou can style tables by using following generic class values:\n\n * ##.separated-vertical##: table rows are displayed separated by a dotted line, if you use several table bodies (#### elements) then rows from different table bodies are separated bei a solid line\n * ##.separated-horizontal##: table columns are displayed separated by a dotted line\n * ##.backgrounded##: table cells have a grey background color, if you only want a darker background for the table header then please directly use ##thead.backgrounded##\n * ##.spaced-vertical##: table rows have a small space between each other\n * ##.spaced-horizontal##: table columns have a small space between each other\n\nYou can combine those class values !!except for vertical spacing combined with vertical separation and horizontal spacing combined with horizontal separation!! (due functional lack in MSIE, they don't suppert cell spacing). You can alter table row background colors by using ##tr.odd##.\n\n===Forms===\n\n====Buttons====\n\n Please do not use #### for buttons because all style declarations will fail in our beloved browser MS Internet Explorer 6.\n\n * Buttons in forms: ####\n * links styled like buttons: ##Button Text##\n\n====Input elements====\n\n Because of compatibility to MS Internet Explorer 6 we recommend to repeat input type values as class values.\n\n * Text input: ####\n * Checkboxes: ####\n * Radio buttons: ####\n * Text area: ####\n\nOf course you may use other attributes like ##name##, ##id##, ##value## or other html standard attributes for input fields. On select fields we also recommend an exact class value (it works without but it looks nicer with):\n\n * #### for spanned selects\n * ####\n\n====Grouping form elements====\n\nWe recommend the use of ##
    ## and #### elements to group and structure your forms. Also nested fieldsets are appreciated. Additionally we provide some generic layout elements to improve usability on forms (not to forget that it looks nicer). You can group a label and an input field by ##
    ##, for example:\n\n%%(html)\n
    \n
    Register now\n
    \n \n
    \n
    \n \n
    \n \n
    \n
    \n%%\n\nUsing ##row-input## brings effort like highlighting that rows on mouse over (through CSS) and marking that rows while nested input elements are focused through javascript (!!not implemented yet!!). You can justify labels and input elements (looks a little bit like used design tables) by using class value ##input-justify-left##, that means label first and input field second (the opposite on checkboxes and radio buttons). You als can combine those classes:\n\n%%(html)\n
    \n
    Register now\n
    \n \n
    \n
    \n
    \n \n
    \n
    \n
    \n \n
    \n
    \n
    \n%%\n\n##div.actionbuttons## is used to set the button at one axial alignement with the input fields. Please take aware of the use ##
    ## at last element in justified rows because we have to clear the floats. You also can use the same class values at the ##form## element:\n\n%%(html)\n
    \n
    Register now\n
    \n \n
    \n
    \n
    \n \n
    \n
    \n
    \n \n
    \n
    \n
    \n%%\n\nYou can use other generic design elements to layout nice but good structured forms.\n\n===Layout helper===\n\n====Design helper====\n\nWe provide some simple support to design your content elements. Basically we implemented some classes for sizes and floats:\n\n * for elements by a width of 25%, 33%, 50%, 67%, 75% use ##.width25##, ##.width33##, ##.width50##, ##.width67## and ##.width75##\n * float elements by using ##.float-left## and ##.float-right##, !!please don't forget to use a ##
    ## to clear floats!!\n * you can combine those classes, for example display your content in two columns: %%(html)\n
    \n \n
    \n
    \n \n
    \n
    \n%%\n\nYou also can use it together with grouping elements for forms:\n\n%%(html)\n
    Registration\n
    \n \n \n
    \n
    \n
    \n \n \n
    \n
    \n
    \n\n
    \n \n \n
    \n
    \n
    \n \n \n
    \n
    \n
    \n\n
    \n \n
    \n
    \n
    \n \n \n
    \n
    \n
    \n \n
    \n \n
    \n
    \n%%\n\n====Message boxes====\n\nYou can simple display a message box by using the ##.messagebox## class, and it is possible to specify it by combination with ##.info##, ##.error##, ##.warning## and ##.success##.\n\n%%(html)\n

    This is a info box, please read. The answer is 42.

    \n\n
    \n

    Attention, this is a warning message.

    \n

    You better read it! You forget your towel.

    \n
    \n\n
    \n
      \n
    • Error message One!
      • \n
    • Error message Two!
      • \n
    • Error message Three!
      • \n
    \n

    Please remember: Don't panic!

    \n
    \n%%" . . . . "2010-07-05T14:40:39"^^ . " ATTENTION: THIS PAGE IS OUTDATED - FOR A CURRENT VERSION, HAVE A LOOK AT http://code.google.com/p/ontowiki/wiki/ExtensionDeveloperStart\n{{Include page=\"/Projects/OntoWiki/EventPluginArchitectureMenu\" divclass=\"floatbox\" nomark=\"1\"}}\n==Events and plugin architecture==\n\nWith **~OntoWiki 0.8.5** we add a plugin architecture which can be used to integrate your own functionality to ~OntoWiki and Erfurt through plugins. Those plugins can be deployed by providing classes and methods as event handlers to ~OntoWiki and Erfurt events. An event dispatcher is used to publish those events.\n\n{{toc}}\n\n===Plugins===\n\n====Installation====\n\nPlugin integration to ~OntoWiki is easy: copy all files of a plugin package and the associated configuration file (##config.ini##) into one own folder in ~OntoWiki's plugin directory and switch the plugin on (for now in ##config.ini##). You can specify ~OntoWiki's plugin directory in ~OntoWiki's ##config.ini##:\n\n%%(ini)\n;---------------------------------------;\n; The path to OntoWiki plugin folder ;\n;---------------------------------------;\n\nplugins.ontowiki = plugins/ ; relative path to OntoWiki root directory\n%%\n\nAdd more different folders (!!this feature is planned, it's not working yet!!):\n\n%%(ini)\nplugins.name1 = pluginfolder2/\nplugins.name2 = ../../plugins/outside/ontowiki/app/\n%%\n\nChoose your own alphanumerical names but !!please do not use ##plugins.erfurt##!! in ##config.ini##. All added paths are crawled for plugins' for the ##config.ini## configuration file.\n\n====Plugin development====\n\nPlugins can be used to add new functionality to ~OntoWiki or its user interface without the necessary to hack the ~OntoWiki core code. Additionally you can provide new libraries and their interfaces through plugins. To integrate plugins automatically we provide events which can be subscribed by your plugin's methods as event handlers. Please read further:\n\n * ((/Projects/OntoWiki/EventPluginArchitecture/PluginDevelopment How to develop an OntoWiki plugin))\n * ((/Projects/OntoWiki/PluginCookbook Plugin Cookbook)) (work in process)\n\n===Events===\n\nThe event dispatcher has been built in with ~OntoWiki 0.8.5 and it can be used to publish events (trigger events) and to subscribe event handlers (announcing mthods from plugin classes as event handlers) to those events. We distinguish between three groups of events:\n\n * **Zend events**: those events are triggered automatically based on Zend event methods\n * **Core events**: contains events which are triggered in the core code on decision by ~OntoWiki / Erfurt developers\n * **Third party events**: events triggered by plugins\n\nTechnically there are no differences between the events of each group.\n\n====Zend events====\n\nIn ~OntoWiki we trigger ((http://framework.zend.com/manual/en/zend.controller.plugins.html Zend event methods)) automatically, names are:\n\n * ~ZendRouteStartup\n * ~ZendRouteShutdown\n * ~ZendDispatchLoopStartup\n * ~ZendPreDispatch\n * ~ZendPostDispatch\n * ~ZendDispatchLoopShutdown\n\nAdditionally we have those events prefixed by the current route request. The prefix is composed of the module name, controller name and the action name (all parts in lowercase letters) of the requested route. ~OntoWiki has only one default module, so the prefix is ending up in ##default_controllername_actionname_##. For example while the request of http://demo.ontowiki.net/wiki/registerNew/ the event ##default_wiki_registernew_ZendPostDispatch## is published beside the ##~ZendPostDispatch## event. The prefixed Zend event are triggered right after the usual Zend event has been published.\n\n====Core events====\n\nCore events are added to the core code of ~OntoWiki and Erfurt. We will develop a convention for trigger names which will be documented here together with the attribute passed to the plugin's method.\n\n * ~RDFSModel_add_pre with data: associative array with key statement\n * ~RDFSModel_add_post with data: associative array with keys statement, success\n * ~RDFSModel_remove_pre with data: associative array with key statement\n * ~RDFSModel_remove_post with data: associative array with keys statement, success\n\n====Third party events====\n\nAlso plugins and other third party code can trigger events. Please use the private ##$_erfurtApp## object in your methods:\n\n%%(php)\n$eventDispatcher = $this->_erfurtApp->getEventDispatcher();\n$bool = $eventDispatcher->trigger('name_of_event',&$passed_var);\n%%\n\nPlease pass references to the trigger (objects are references!)." . . . . "2010-08-08T10:55:10"^^ . "{{Include page=\"/Projects/DLLearner/Menu\" divclass=\"floatbox\" nomark=\"1\"}}\n==~ChangeLog==\n=== Build 2010-08-07 ===\n * support for OWL API 3\n * <# ORE tool #> based on DL-Learner algorithms (soon to be migrated to an own project)\n * implemented several new heuristics, e.g. generalised F-Measure\n * stochastic approximation of computing F-Measure\n * learning algorithms for the EL description logic\n * support for hasValue construct in combination with string datatype\n * support for refining existing definitions (instead of learning from scratch) for CELOE ontology engineering algorithm\n * increased number of unit tests (now 40)\n * support for direct Pellet 2 integration and reasoners connected via OWLLink\n * 24 bugs fixed and 12 feature requests implemented at sourceforge.net bug tracker\n%%(comments)\n * <# 24 bugs fixed #> and <# 3 feature requests #> at sourceforge.net trackers (TODO: actually more feature requests have been resolved; sf.net search function does not seem to work)\n%%\n=== Build 2009-05-06 ===\n * new algorithm: CELOE (class expression learning for ontology engineering)\n * <# Protégé Plugin #> based on CELOE\n * wrote a ((http://dl-learner.org/files/dl-learner-manual.pdf manual)) for DL-Learner\n * an efficient refinement operator for the EL description logic\n * fast stochastic class expression coverage estimation included\n * reasoner component design and learning problem structure improved\n * more learning examples provided and unit tests for ensuring code quality extended\n * 6 bugs and feature requests reported at the sourceforge.net tracker fixed\n\n=== Build 2008-10-13 ===\n * improved refinement operator based learning approach taking domain/range of properties, property hierarchies, disjoint classes into account to structure search space more efficiently \n * DL-Learner GUI for loading, saving, and modifying configuration files\n * fast instance checking algorithm reduces the time to test example coverage of class descriptions significantly\n * ((http://dl-learner.org/wiki/Carcinogenesis Carcinogenesis Benchmark))\n * extraction component: more flexible structure, SPARQL results are converted to OWL on the fly, correct blank node handling ((http://jenslehmann.org/files/2008_kb_extraction.pdf Poster Abstract))\n * more learning examples provided in release\n * 12 bugs and 10 feature requests reported at the sourceforge.net tracker fixed\n\n=== Build 2008-02-18 ===\n * Flexible new component based structure:\n * 4 types of components: knowledge sources, reasoners, learning problems, learning algorithms\n * easily extensible: to implement a new component of one of the above types you only have to extend the corresponding class in org.dllearner.core and add the name of your class to the components.ini file\n * each component can maintain and easily extend its own configuration options\n * Support for using SPARQL endpoints as background knowledge, including mechanisms for knowledge fragment selection. This feature enables DL-Learner to use ((http://dbpedia.org DBpedia)) as background knowledge.\n * Preliminary support for learning from only positive examples and learning of inclusion axioms instead of definitions.\n * Support for N-Triple files.\n * Support for using role hierarchies in the refinement operator based algorithm.\n * Much more powerful web service interface allowing to access and modify all DL-Learner components.\n * Reasoners:\n * preliminary OWL API reasoner interface support: Pellet, ~FaCT++ \n * KAON2 dropped, such that DL-Learner now depends solely on open source libraries\n * A Prolog parser, which can help in converting Prolog files to OWL (thereby transfering ILP problems into OWL learning problems).\n * More examples added: \n * complete Moral Reasoner Benchmarks\n * more SPARQL benchmarks\n * all examples now also available in OWL\n\n=== Build 2007-08-31 ===\n\nInitial release." . . . . "2007-09-19T21:13:12"^^ . "==Knowledge Bases==\nEvery Knowledge Base is an RDF Model, which is a set of RDF statements of subject, predicate and object.\n{{toc}}\n\n\n===Knowledge Base Window===\nThe main function of the Knowledge Base Window is to do actions on model scope. This window lists all models where you have at leat read access.\n\nhttp://ontowiki.net/Projects/OntoWiki/Help/Models/files?get=models.png\n\nBy using the context menu of a model, you can choose from one of these actions.\n\n====Select a Knowledge Base====\nThis is the default action. If you select a Model, every action in the current session uses this model. This means, if you select the SPARQL shell afterwards and query the model, your query will be evaluated in that model.\n\n====Delete the Knowledge Base====\nIf you have access for the action \"Model Management\" and write access to that model, you can delete that model. If you delete a model, all statement, the popularity, the ratings and the cache of that model will be deleted. \n\n====Export the Knowledge Base as RDF/XML====\nThis is a link to the RDF/XML representation of that model. You can download the XML file or put the link to another Semantic Web application.\n\nAdditional to these model specific actions, you can choose these actions from the context menu of the Knowledge Base Box (the white circle):\n\n====Show / Hide Hidden Knowledge Bases====\nThis Feature is not implemented yet. You can hide a model by setting the attribute SysOnt:hidden to ##true##. By default, hidden models are not displayed in the Knowledge Bases Window. You can choose \"Show Hidden Knowledge Bases\" in the window context menu to show all hidden models.\n\n====Create a new Knowledge Base====\nIf you have access for the action \"Model Management\", you can create a new Knowledge Base here.\nYou can choose from these options:\n * Create an empty Knowledge Base\n * Import an RDF document from the Web\n * Import a local RDF document by uploading it\n * Paste RDF/XML source code to a text box\n\nYou have to provide a resource identifier (URI) for your new model. The name of the model, which is displayed in the Knowledge Bases Window, is taken from the model itself (e.g. an rdf:label).\n\n{{tree from=\"/Projects/OntoWiki/Help\" divclass=\"floatbox\"}}\n" . . . . "2007-09-20T11:48:50"^^ . "{{Include page=\"/Projects/OntoWiki/Menu\" divclass=\"floatbox\" nomark=\"1\"}}\n==OntoWiki User Documentation==\nThese pages should help OntoWiki users if they click on one of the help buttons or help menu entries which are scattered over the application.\n{{tree}}" . . . . "2007-09-19T20:52:03"^^ . "==Classes==\n{{toc}}\n===Classes Window===\nBy using the classes box context menu (the white circle), you can\n * Create a new Class\n * Show / Hide empty, hidden or system classes\n\nBy using the context menu of a class:\n * List Instances\n * Create a new instance\n * View class description\n * Edit class descripion\n * Delete class description\n\nhttp://ontowiki.net/Projects/OntoWiki/Help/Classes/files?get=classes.png\n\n===OntoWiki Class Types===\nOntoWiki distinguish between these types of classes.\n Note, that this is not the same like rdf:Class or owl:Class (which are types of classes too but which is not meant here)\n\n====Hidden Class====\nYou can hide a class by setting the attribute SysOnt:hidden to ##true##. By default, hidden classes are not displayed in the Classes Window. You can choose \"Show Hidden Classes\" in the window context menu to show all hidden classes.\n====System Class====\nA system class is defined as a class from the RDF, RDF Schema and OWL namespace. By default, system classes are not displayed in the Classes Window. You can choose \"Show System Classes\" in the window context menu to show all system classes.\n====Empty Class====\nAn empty class has no instances. This means there is no statement ##?resource rdf:type ?EmptyClass## but a class description of that class. By default, empty classes are not displayed in the Classes Window. You can choose \"Show Empty Classes\" in the window context menu to show all empty classes.\n====Implicit Class====\nAn implicit class has at least one instance but there is no class description defined in the model. This means, you should select \"Edit Class Description\" from that class context menu and add at least a label for that class.\n\n{{tree from=\"/Projects/OntoWiki/Help\" divclass=\"floatbox\"}}\n" . . . . "2009-05-08T17:50:49"^^ . " ATTENTION: THIS PAGE IS OUTDATED - FOR A CURRENT VERSION, HAVE A LOOK AT http://code.google.com/p/ontowiki/wiki/BrowserCompatibility\n {{Include page=\"/Projects/OntoWiki/Menu\" divclass=\"floatbox\" nomark=\"1\"}}\n==Browser Compatibility==\nThis document describes what you can expect from OntoWiki if you use a certain browser.\n{{toc}}\n\n===Firefox===\nFirefox is one of our development browser. CSS and JavaScript is implemented for the current Firefox Version first. Older versions of Firefox are not supported.\n\n===Safari===\nThis is our second development browser because some core developer are mac evangelists.\n\n===Internet Explorer===\nSince nobody of the core developer is using Windows, this browser is not as well supported as the other ones. We use VirtualBox for our testing sessions but this is not the same. If you are interested in coding MSIE hacks, you are welcome. Nevertheless, we want full support for the current version of MSIE (IE7) both in functionality and display.\n\nIE6 is supported only in functionality. Older versions (<= IE5.5) are not supported.\n\nMSIE does not support alpha layers in PNG images, so we have disabled PNG background images for MSIE." . . . . "2009-08-02T04:37:29"^^ . "{{Include page=\"/Projects/OntoWiki/Menu\" divclass=\"floatbox\" nomark=\"1\"}}\n WebDAV is only supported in 0.86 and needs to be re-released for OntoWiki > 0.9\n==OntoWiki ~WebDAV Service==\nOntoWiki now supports ~WebDAV for browsing and exporting Ontology resources and classes, adding data to models, further functionality could be added later.\n\n==== Browser-support ==\n\nFor a short test if ~WebDAV works on your OntoWiki installation you could browse the ~WebDAV Filesystem with any webbrowser just open %%(ini) http://yourdomain.tld/ontowiki-installation/service/webdav/%% this will give you the ability to browse and download from your models. It's good for exploring and understanding hierarchy of the filesystem. This version needs no login, it will use the current OntoWiki session active in your browser.\n\n==== Filesystem-tree ==\n<##>\n(Click image for a high resolution version ...)\n\n==== supported (tested) Clients ==\n\n * Windows Explorer (via add Networkresource)\n * SkunkDAV\n * DAVExplorer\n * mount (fstype davfs) (untested)\n" . . . . "2007-10-06T04:10:42"^^ . "==Running ~OntoWiki on Virtuoso==\n{{toc}}\n===Using Virtuoso as Webserver===\n\nDownload the open-source version from http://virtuoso.openlinksw.com/wiki/main/\n\nA guide for installing Virtuoso on Windows can be found at: http://virtuoso.openlinksw.com/wiki/main/Main/VOSUsageWindows\nViruoso will use your existing PHP installation as long as the install directory is contained in the %PATH% variable.\n\nInstall ~OntoWiki as usually in the directory %virtuosodir%\\var\\lib\\virtuoso\\vsp.\n\nSince, ~OntoWiki requires all HTTP accesses to go to boot.php and Virtuoso has no support for the RewriteRules in .htaccess you have to configure the ontowiki directory using the Virtuoso conductor (http://localhost:8889/conductor):\n\n * Go to the tab \"WebDAV & HTTP\" / \"HTTP Hosts & Directories\",\n * select \"New Directory\" at \"{Default Web Site}\",\n * choose \"Filesystem\" as type\n * in the next form fill in \"/ontowiki/\" for \"Path\" as well as \"Physical path\" and use \"boot.php\" as \"Default page\"\n\nIf you have setup ~MySQL in parallel and configured ~OntoWiki to use ~MySQL, ~OntoWiki should run now using Virtuoso at least as Webserver.\n\n===Using Virtuoso as database backend for ~OntoWiki===\n\nThere are two options for running OntoWiki with Virtuoso as a storage backend:\n 1. using Virtuoso's triple store functionality directly. This should be the preferred method on the long run.\n 2. using Virtuoso with ~OntoWiki's SQL triple storage layout. This should be possible without (hopefully) changing much of ~OntoWiki.\n\nFor both options it is essential to setup the PHP to Virtuoso connection. Virtuoso can be accessed by ODBC. Using PHP's native functions this can be done via:\n\n%%$db=odbc_connect('virtuoso','dba','dba');%%\n\nUsing ADODB you would use:\n\n%%$conn = &ADONewConnection('odbc');\n$conn->PConnect('virtuoso','dba','dba');%%\n\nIn order to use Virtuoso from ~OntoWiki, we now have either to\n * test and debug all ~OntoWiki/Erfurt functions interacting with the database, or\n * to change ~OntoWiki/Erfurt so it solely uses SPARQL and SPARUL\n\n===Differences between Virtuoso's SQL and ~MySQL===\n\n====Quotation====\n\n#|\n|| | MySQL | Virtuoso ||\n|| Identifiers (table, column names etc.) | ` (backtick) | \" (double quotes) ||\n|| Data values | \" / ' (double or single quotes) | ' (single quotes) ||\n|#\n\n====ENUM/SET datatype====\n\n~MySQL allows to define a table column to be an enumeration or set of a number of elements, e.g.:\n\n%%(sql)CREATE TABLE person (\n name VARCHAR,\n sex ENUM('male', 'female')\n)%%\n\nor:\n\n%%(sql)CREATE TABLE person (\n name VARCHAR,\n likes_fruits SET('apple', 'pear','orange')\n)%%\n\nVirtuoso does not offer ENUM or SET datatypes but constraints on the allowed column values can be checked e.g.:\n\n%%(sql)CREATE TABLE person (\n name VARCHAR,\n likes_fruits VARCHAR CHECK ( likes_fruits in ('apple','pear','orange'))\n);%%\n\n====LIMIT vs. TOP====\n\nVirtuoso uses the TOP syntax, ~MySQL LIMIT:\n\n%%(sql)SELECT * FROM mysql.users LIMIT 3 %%\n\nis written in Virtuoso:\n\n%%(sql)SELECT TOP 3 * FROM DB.DBA.SYS_USERS %%\n\n====Index Creation====\n\n~MySQL allows to create indexes inside the table definition:\n\n%%(sql)CREATE TABLE person (\n name VARCHAR(255),\n KEY (name)\n);%%\n\nIn Virtuoso keys have to be created separately:\n\n%%(sql)CREATE INDEX name ON person (name)%%\n\nAdditionally, ~MySQL allows to create indexes just up to a specified length of the data values:\n%%(sql)CREATE INDEX name ON person (name(10))%%\nSimilar functionality does not seem to be available for Virtuoso.\n\n====IF EXISTS====\n\nVery handy shortcut are \"IF EXISTS\" and \"IF NOT EXISTS\" keywords:\n\n%%(sql)DROP [TEMPORARY] TABLE [IF EXISTS]\n tbl_name [, tbl_name] ...\n\nCREATE [TEMPORARY] TABLE [IF NOT EXISTS] tbl_name\n [(create_definition,...)]%%\n\n====LOAD DATA INFILE====\n\n~MySQL has a very handy feature to rapidly load large amounts of (CSV) data into tables:\n\nhttp://dev.mysql.com/doc/refman/5.1/en/load-data.html" . . . . "2009-04-03T10:10:34"^^ . "{{Include page=\"/Projects/DLLearner/Menu\" divclass=\"floatbox\" nomark=\"1\"}}\n==Topics for Theses==\nCurrent topics for theses include:\n * combinations of ((http://dbpedia.org DBpedia)) and DL-Learner (Master or Bachelor)\n * navigation in DBpedia\n * improving the Wikipedia category system\n * developing applications of DL-Learner in the area of life sciences (Master or Bachelor)\n * integration of DL-Learner in ((http://ontowiki-net OntoWiki)) (Master or Bachelor)\n * developing a music recommendation system (Master or Bachelor)\n * --writing a Java GUI as DL-Learner interface (Bachelor)--\n * --writing a ((http://protege.stanford.edu/ Protégé)) DL-Learner plugin (Bachelor)--\n * converting ILP benchmarks to OWL and benchmarking against state-of-the-art ILP tools\nRelated or own ideas are also welcome. Students of the University of Leipzig and others (if their study regulations allow it) can apply for those topics.\n<##>\nFor a list of DL-Learner related tasks, you can also have a look at ((http://cofundos.org Cofundos)), the platform for community innovation and funding.\n((http://www.cofundos.org/projects.php?tag=DL-Learner List of DL-Learner related projects at Cofundos))\n\nA more detailed description of available theses topics is available in German:\nhttp://bis.informatik.uni-leipzig.de/de/Abschlussarbeiten/neu/JensLehmann" . . . . "2010-07-05T14:46:21"^^ . "{{Include page=\"/Projects/OntoWiki/Menu\" divclass=\"floatbox\" nomark=\"1\"}}\n ATTENTION: THIS PAGE IS OUTDATED - FOR A CURRENT VERSION, HAVE A LOOK AT http://code.google.com/p/ontowiki/wiki/WebServices\n==~OntoWiki Web Services==\n{{toc}}\nWeb services are handled by ~OntoWiki's ~ServiceController. \n\n===Authentication (/service/auth)===\n====Authentication Request====\nYou can authenticate using via web service with an ~OntoWiki installation under the URI /service/auth.\n\nAuthentication parameters can be supplied using POST or GET. However, GET is disabled by default and we don't recommend using it as passwords will be visible in the URI sent to the server. If you want to enable GET authentication set ~OntoWiki's config parameter rest.allowGetAuth to true. \n\nThe authentication supports the following parameters:\n * u -- the username to authenticate with (required parameter if logout is not supplied or false)\n * p -- the password to authenticate with (can be omitted; defaults to \"\")\n * logout -- supply this parameter with the value \"true\" to remove the current authentication (required for logout).\n\n====Authentication Response====\nThe REST Server responds with one of the following HTTP responses:\n * 200 OK -- The authentication was successfull. You now can request ~OntoWiki URIs that require authentication.\n * 401 Unauthorized -- The authentication did not succeed. In most cases you supplied invalid user name, password or both.\n * 405 Method Not Allowed -- You tried to authenticate via GET, although this is disabled in ~OntoWiki config.\n * 400 Bad Request -- You didn't supply the parameters needed to fullfill the request.\n\n===SPARQL Query (/service/sparql)===\nOntoWiki's web service accepts SPARQL queries according to the [[http://www.w3.org/TR/rdf-sparql-protocol/|SPARQL protocol]]. The service is reachable under the URI /service/sparql.\n====Installation====\nYou should go to Erfurt-directory and enable it in erfurt.ini by setting the value of endpoint.http to 'true'.\n====Usage====\nvalues submitted by HTTP GET/POST Variables:\n * query: OBLIGATORY must contain the SPARQL-query to be executed on the Database\n * default-graph-uri: OPTIONAL can contain an URI of a model to query on\nError Message is given if any problem occured. (See Authentication Response for Error-Codes; they are applying on SPARQL Endpoint too)\n====Example==== \n/service/sparql?query=SELECT * WHERE {?s ?p ?o}&default-graph-uri=~http://mymodel.org/ will give you all triples from ~http://mymodel.org. The result of the query is delivered as xml like specified from: http://www.w3.org/TR/rdf-sparql-XMLres/.\n\n===Model Update (/service/update)===\n~OntoWiki supports updating models via its web service. As of version 0.9 we support a ((http://n2.talis.com/wiki/RDF_JSON_Specification JSON format)) but more formats are planned. To update a model, three parameters must be supplied:\n * model -- the graph URI to be updated\n * old -- the old model as it was before the update process \n * new -- the updated model.\n\nThe difference between old and new determines the statements that will be added to the model.\n" . . . . "2008-06-16T02:35:43"^^ . "==IT-Risk Ontology==\n\n Author: Jan Hellich\n Ontology: ((http://aksw.org/Projects/Ontology/itrisk/files?get=itriskontology.xml http://ns.softwiki.de/it-risk/))\n Example Data:\n Diploma Thesis: ((http://aksw.org/Projects/Ontology/itrisk/files?get=diplomarbeit_itrisikoontologie.pdf Entwicklung der IT-Risiko-Ontologie im Rahmen einer IT-Risikoanalyse fur die Carl Zeiss Jena GmbH))\n\n\n===Abstract===\nDie IT-Risikoanalyse in Unternehmen ist ein Prozess der von verschiedenen internen (Unternehmensstruktur, Verantwortliche, Systeme) und externen Bedingungen (Gesetze, Richtlinien und Standards) abhangig ist. Als erstes Ergebnis dieser Arbeit wurde eine Standardmethode zur Durchführung einer IT-Risikoanalyse für die Carl Zeiss Jena Gmb H ausgewählt. Diese Methode wurde an die speziellen Anforderungen der Carl Zeiss Jena Gmb H angepasst und durchgeführt. Die bei der Analyse entstandenen Ergebnisse wurde mit dem methodeneigenen Werkzeug GSTOOL aufgenommen und stehen als Datenbasis für das IT-Risikomanagement zur Verfügung. Die in dieser Arbeit entwickelte Vorgehensweise für die Durchführung einer IT-Risikoanalyse auf Basis von IT-Grundschutz, kann in dieser Form auch in anderen Tochterunternehmen der Carl Zeiss AG oder in externen Unternehmen durchgeführt werden. Eine Betrachtung der IT-Risikoanalyse unter dem Aspekt des Wissensmanagements zeigte, dass es bei dem eingesetzten Tool zur IT-Risikoanalyse, Defizite bei der Erstellung von komplexen Anfragen auf den Datenbestand und bei der Möglichkeit der gemeinschaftlichen Arbeit mit dem enthaltenen Wissen gibt. Deshalb war es das Ziel, durch Methoden und Werkzeuge des Wissensmanagements, Lösungen für diese beiden Anforderungen zu finden. Dieses Thema wurde im zweiten Teil dieser Arbeit betrachtet...\n\nmehr ((!/Abstract Zusammenfassung und Literatur))" . . . . "2008-02-27T10:07:04"^^ . "{{Include page=\"/Projects/xOperator/Menu\" divclass=\"floatbox\" nomark=\"1\"}}\n==Demo / Public Agents==\n{{toc}}\n===Demo Agent===\nYou can test an xOperator demo agent in a group agent like setup. The agent has access to ((http://dbpedia.org DBpedia)) and the ((http://ontowiki.net OntoWiki)) installation @ http://demo.ontowiki.net/.\n\nIn order to use the agent, you have to add it to your jabber roster (JabberID: ##<#xoperator-demo@aksw.org#>##). The agent will accept the authorization request immediately, so that you can send him commands and questions after that.\n\nYou have full access to the agent (change datastores, namespaces, queries) but the agent will be purged every day.\n\nFor more information on how to use the agent, have a look at our ((FirstSteps first steps document)).\n\nExample queries which are already configured:\n * ##tell me (the) * of *## e.g. the phone of seebi\n * ##where is * now## e.g. where is seebi now\n\n===Public Agents===\n * ##\"\"jamendo@jabber.org\"\"## is a public agent from ((http://blog.dbtune.org/post/2008/02/25/Playing-with-SPARQL-and-XMPP Yves Raimond)) which which provides SPARQL/XMPP on top of the ((http://dbtune.org/jamendo/ Jamendo SPARQL end-point)).\n * tbc :-)\n" . . . . "2010-07-05T17:03:38"^^ . " ATTENTION: THIS PAGE IS OUTDATED\n{{Include page=\"/Projects/OntoWiki/EventPluginArchitectureMenu\" divclass=\"floatbox\" nomark=\"1\"}}\n==Plugin Cookbook==\n{{toc}}\n\n===General Plugin Architecture===\n====Erfurt or OntoWiki Plugin?====\n====Plugin Configuration====\n====Overwrite OntoWiki Strings / Add Plugin Strings====\nSimply put a ##strings.ini## file in your plugin directory. The plugin manager will include that to the main strings data.\n\nThis is a sample ##strings.ini##:\n%%(ini)\n[english]\n; this overwrites the title of the login box\nauth.login.login = My own Login String\n; this adds a new string to the strings object\nmyspecialplugin.info = This is my special plugin ...\n\n[german : english]\nauth.login.login = My eigener Login String\nmyspecialplugin.info = Dies ist mein spezielles Plugin ...\n\n[default : english]\n%%\n\n\n\n====Simple Plugin Class====\n\n===Access to Session Interna / Request Data / ...===\nall\n====Access to the Plugin Root Dir (Filesystem)====\n%%(php)\n// e.g. /var/www/ontowiki/plugins/ExamplePlugin (without last slash)\n$this->_getPluginRootDir();\n%%\n====Access to the Plugin Base URI====\n%%(php)\n// e.g. http://localhost/ontowiki/plugins/ExamplePlugin\n$this->_getPluginBaseUri();\n%%\n====Access to the OntoWiki Base URI====\n%%(php)\n// e.g. http://localhost/ontowiki\n$this->_getOntoWikiBaseUri();\n%%\n\n====Access to the active resource / resource list====\n\n===Addtional CSS / JavaScripts===\n\n===Sidebar===\n====Adding a special main window to the sidebar====\nPKM\n====Hiding an existing main window====\nOntobuilder\n====Creating a completely new sidebar====\n\n\nSoftwiki\n===Different Forms / Views===\n====Adding my own Edit-Form for a specific resource-type====\nSoftwiki, Ontobuilder\n====Adding my own Create-Form for a specific resource-type====\nOntobuilder\n%%\nannounce.3.event = \"default_resource_create_ZendPostDispatch\"\nannounce.3.class = \"SemPKM\"\nannounce.3.method = \"niceForms\"\n%%\n%%(php)\npublic function niceForms (&$a) {\n if (isset($this->_view->properties['rdf:type']) && $this->_view->properties['rdf:type'] == 'http://purl.net/net/sempkm/Note') {\n #$this->_view->properties['dc:relation']='';\n $vr = Zend_Controller_Action_HelperBroker::getStaticHelper('viewRenderer');\n $this->_view->addScriptPath($this->_getPluginRootDir().'/templates/');\n $vr->setScriptAction('edit-notes');\n }\n return;\n }\n%%\n%%(php)\nplaceholder('tabs')->set($this->tabs) ?>\nplaceholder('title')->set($this->title) ?>\nplaceholder('menu')->set($this->menu) ?>\nplaceholder('statusTools')->set($this->statusTools) ?>\n\n
    actionUrl ?>\" class=\"no-min-width\">\n \n
    Querverbindungen\n
    \n
    \n type, 'dc:relation') ?>\n
    \n
    \n
    \n\n%%\n====Adding my own List-View for a specific resource-type====\nSoftwiki, Ontobuilder\n\n===Tabs===\n====Hiding an existing Tab (e.g. Map/Calendar)====\nOntobuilder (modified: resourcecontroller.php/getTabNavigation)\n====Adding a new Tab====\n%%\nannounce.3.event = \"template_window_create_tabs\"\nannounce.3.class = \"Example\"\nannounce.3.method = \"changeTabs\"\n%%\n%%(php)\npublic function changeTabs(&$tabs) {\n $action = 'ttt'; // define your action here\n $baseURI = \n \n $tabs['tabs][$baseUri . 'exampleController/tttAction'] = 'New Tab Label'; \n\n}\n%%\nFlashviz\n===Inner Windows===\n====Creating my own inner window in a given view===\nPKM, Socializr\n\n===Menus===\n====Adding an item to windows main menu (e.g. Extras)====\nDL-Learner, Socializr\n====Adding an item to a windows context menu====\n====Adding an item to a class context menu====\n\n===Controller===\n====Adding a new controller====\n%%\nannounce.2.event = \"ZendPreDispatch\"\nannounce.2.class = \"ExamplePlugin\"\nannounce.2.method = \"addNewController\"\n%%\n%%(php)\npublic function addNewController() {\n\n // get front controller\n $frontController = Zend_Controller_Front::getInstance();\n\n // get request object \n $request = $frontController->getRequest();\n\n // add the plug-in dir as a controller dir\n $frontController->addControllerDirectory($this->_getPluginRootDir());\n\n // set dispatched to false so that default OntoWiki action will not be dispatched\n $request->setDispatched(false);\n\n // set the controller to softwiki\n $request->setControllerName('example');\n\n // set the action to view\n $request->setActionName('view');\n}\n%%\n%%(php)\nclass ExampleController extends OntoWiki_Controller_Action {\n\n /**\n * SoftWiki view action.\n * Overwrites the default OntoWiki view action and renders its own templates.\n */\n public function viewAction() {\n // set window title\n $this->view->placeholder('title')->set('Example Main Window');\n\n // ...\n }\n}\n%%\n\nDL-Learner, Flashviz?\n====Replacing a existing controller====\n====Adding a new action to existing controller====\nFlashviz\n\n===Data Manipulation===\n====How to create a new knowledge base template====\nOntoBuilder (modified: modelcontroller.php/createaction, templates/model/create.php (new file))\n\n====Write Erfurt Plugins====\nIt is also possible to write plugins for the Erfurt Semantic Web Framework. A Erfurt plugin is useful in case your Erfurt based application needs to do some additional things when data is manipulated through Erfurt. A good example for a usecase of such a plugin is cache invalidating when adding or removing statements or logging of the same.\n\nThe following example will give you a brief overview of the steps you will have to through in order to build such a plugin.\n\n 1. First of all you have to decide, which events your plugin should handle. Have a look at the Event section of the [[EventPluginArchitecture]] page in order to get a up-to-date list of triggered events. Our example plugin will announce to the ##RDFSModel_add_pre## and ##RDFSModel_add_post## events. These Erfurt core events are triggered in the ##add##-method of the ##RDFSModel##-class. The first one is triggered before a statement is added and the second one after the addition of a statements to the model. When a plugin announces to one of these events, it gets a reference to the data, which actually is an array containing a key //statement// with the statement as payload. The ##RDFSModel_add_post## event has a additional key //success//, which indicates whether the addition was successful or failed.\n 2. Open the ##plugins/## folder, which is located under your ##Erfurt/## directory (Have a look at the [[PluginCookbook#h???]] section to learn about setting up custom plugin directories.).\n 3. Create a new folder with the name of your plugin. In our case this will be ##ErfurtExamplePlugin##.\n 4. Create a new file called ##ErfurtExamplePlugin.ini-dist##. This file will contain the followin lines: %%(ini)\n[general]\n\nname = \"Erfurt Example Plugin\"\ndescription = \"This is a example Erfurt plugin. It will do some example stuff when a statements is added.\"\nauthor = \"Philipp Frischmuth\"\nurl = \"http://ontowiki.net\"\n\nswitch = \"on\" ; is plugin active? on|off\n\nfolder.0 = \".\"\n\nannounce.0.event = \"RDFSModel_add_pre\"\nannounce.0.class = \"ErfurtExamplePlugin\"\nannounce.0.method = \"preAddAction\"\n\nannounce.1.event = \"RDFSModel_add_post\"\nannounce.1.class = \"ErfurtExamplePlugin\"\nannounce.1.method = \"postAddAction\"\n%%\n * The first section contains some metadata about the plugin, like author and description.\n * The ##switch## directive is very important. It tells the plugin manager, whether the plugin is active or not\n * The ##folder## directive announces the folders, which are needed by the plugin. This is in our case only the root of the plugin dir\n * The last section is very important, too. Here you announce your plugin to one or more events and tell the plugin manager, which class(es) and method(s) to use.\n 5. Now we have to implement the plugin. Therefor we need to create a file called ##ErfurtExamplePlugin.php##, which contains our ##preAddAction## and ##postAddAction## methods, that we defined in the configuration file. %%(php)\n do nothing\n // 2b: true -> check whether object has a language\n // 3a: true -> do nothing\n // 3b: false -> add a standard language tag... e.g. 'de'\n \n $stm = $data['statement'];\n if ($stm->getPredicate()->getURI() === EF_RDFS_LABEL) {\n $obj = $stm->getObject();\n \n if ($obj->getLanguage() === null) {\n $obj->setLanguage('de');\n }\n }\n \n return;\n }\n \n public function postAddAction(&$data) {\n \n // do some stuff after adding a statement\n \n // e.g. log statement serialization and success status\n $stm = $data['statement'];\n $success = $data['success'];\n \n $logger = Zend_Registry::get('erfurtLog')->info('ErfurtExamplePlugin - Statement added (' . \n date('d.m.Y H:i:s') . '): ' . $stm->toString() . \n ($success ? ' successfully added' : ' addition failed'));\n }\n}\n?>\n%%\n 6. We are done. If we want to use our plugin, we need to copy the ##ErfurtExamplePlugin.ini-dist## file to ##ErfurtExamplePlugin.ini##. That's all, no our plugin should work as we expect.\n\n===Integration of new API components===\n%%\nfolder.0 = \"./lib\"\nadd.0.class = \"ClassName0\"\nadd.1.class = \"ClassName1\"\nadd.2.class = \"ClassName2\"\n%%\nSocializr, Flashviz" . . . . "2008-02-04T12:56:57"^^ . "==Lecture Tagger==\n\n===Publikationen===\n\n\n===Einsatz===\nVorlesung Betriebliche Informationssysteme\nhttp://lt.aksw.org\n\n\n===Source Code===\n\n\n===Jan Fienhold===\n\nJan Fienhold entwicklete den Lecture Tagger im Rahmen seiner Diplomarbeit.\n\nhomepage: \n" . . . . "2007-11-26T21:28:16"^^ . "{{Redirect page=\"/Projects/OntoWiki/WebServices\"}}" . . . . "2007-11-29T04:43:25"^^ . "==Towards Bottom-Up, Stakeholder-Driven Research Funding==\n\nThere is an ongoing trend of increasingly incorporating prospective societal impacts into the decisions about funding of research projects/proposals. Societal impacts include the creation of jobs, the commercialization of research results, supporting knowledge transfer between geographical regions, organizations or groups of people, strengthening the competitiveness of enterprises and the like. Such objectives appear reasonable with regard to the fact that research is often ultimately funded by tax payers and consequently scientific communities should be accountable on how they contribute to the societal advancement.\n\nWhen analyzing the practices of funding agencies (such as the European Union, national or federal ministries or private foundations), however, we gain the impression that the measures used to trigger societal impacts are not always very efficient: Funded research projects tend to be large since funding agencies believe a big impact requires big investments. Large science projects are due to the uncertain nature of scientific progress very hard to plan a priori. Scientists tend to write proposals in such ways they think maximize their chances to get funded - but a pretty proposal does not guarantee excellent results. The few evaluators and reviewers of a specific proposal or project might often be experts in the area but are usually not direct stakeholders of that project and thus their valuation of the potential impact or success of a project is a rather rough estimate. Collaboration and interdisciplinary were identified as success factors for innovation, but each additional partners also potentiates communication and management overhead.\n\nIn order to overcome the mentioned obstacles we argue that new ways of research funding should be sought, which are stakeholder-driven, spur bottom-up innovations and complement thus existing funding instruments. We envision a funding model, which is based on a platform for the discussion of research ideas and their prospective outcomes. The actual funding decision should be based on the number of votes from stakeholders, i.e. users/applicants of the research result or companies interested in their commercialization. In order to not disadvantage research projects, with a small but strong number of stakeholders, participants could be equipped with a number of votes, which can be either spread across several project ideas or awarded bundled to one.\n\nSuch a system would have a number of advantages: it will precisely reveal the stakeholders of certain research results; it will make the interfaces between research results clearer; researchers are better accountable for really achieving the initially defined requirements; the model would have a very low overhead, since communities of researchers, stakeholders could organize themselves, given a Web platform which facilitates the description, browsing, searching of projects and automates the voting processes.\nIn order to showcase the practicability of such a model we implemented such a platform and in order to test their feasibility we adopted the platform firstly for the development of open-source software. The platform works as outlined, but participants are users and developers of open-source software and the funding of projects is provided by pooling donations from stakeholders. The platform is online at http://Cofundos.org and is actively used.\n" . . . . "2008-02-25T13:43:27"^^ . "{{Include page=\"/Projects/xOperator/Menu\" divclass=\"floatbox\" nomark=\"1\"}}\n==Install a bleeding edge ~xOperator Agent from Subversion==\nThis wiki page documents the installation on a ubuntu linux box. You have to adapt it for other distributions or operating systems.\n{{toc divclass=\"box\" notitle=true}}\n\n===Requirements===\nIn order to install and use xOperator you need:\n * Java\n * ant\n\n===Download===\nAn ~xOperator installation can be downloaded by only one checkout:\n##svn checkout \"\"http://xoperator.googlecode.com/svn/trunk/\"\" /path/to/xOperator##\n\n===Build===\n\nGo to your xOperator directory (##/path/tp/xOperator##) and type run ##ant## in this directory. After that, the directory ##dist## is created.\n\nAfter the build, you probably want to read the ((FirstSteps First Steps)) documentation.\n\n===TroubleShooting===\nIf you have any question, you can write an email to the ((http://groups.google.com/group/xoperator xOperator mailing list)).\n" . . . . "2008-02-25T13:44:09"^^ . "{{Include page=\"/Projects/xOperator/Menu\" divclass=\"floatbox\" nomark=\"1\"}}\n==Changelog / Roadmap==\n{{toc divclass=\"box\" notitle=true}}\n\n{{a name=\"roadmap\"}}\n===Roadmap===\nThese points are not implemented yet but are planned for implementation. You can write feature requests at our ((http://code.google.com/p/xoperator/ Google Code project site)).\n * Distinguish between documents and endpoints (integrate jena)\n * Provide a dynamically generated RDF model from the Jabber Roster\n * Provide better query scripting support\n * Use webservices in query scripts\n * Basic Access Control\n * Multi user installation\n * Scriptable events\n\n{{a name=\"trunk\"}}\n===SVN Trunk===\nThe trunk is the newest bleeding edge version from the SVN source repository (((InstallFromSubversion Installation Notes))). The following changes are only present in the trunk and not released yet:\n * autodiscovery of neighbouring agents\n * buggy: SPARQL over XMPP (and results back)\n\n{{a name=\"0.1\"}}\n===~xOperator 0.1===\nRelease Notes: http://blog.aksw.org/2008/xoperator-01-released/\nThis is the first public release of xOperator. It includes the following features:\n * basic account management\n * add/remove/list of templates, datastores and namespaces\n * simple query templates\n * query scripts\n" . . . . "2008-02-20T17:05:04"^^ . "{{Include page=\"/Projects/xOperator/Menu\" divclass=\"floatbox\" nomark=\"1\"}}\n==First Steps==\n{{toc divclass=\"box\" notitle=true}}\n===Configuration===\nThe most important configuration step is the account credential configuration.\nYou have to change the property file ##xoperator.properties## according to your account credentials. \n\nCopy the file ##xoperator.properties-dist## to ##xoperator.properties## and open it in your favourite text editor. Follow the comments in the property file and change the values according to your setup.\n\nThe agent logs into your jabber account. Therefore the username, which is the full Jabber ID (JID), like ##user@example.com## and the users password have to be given as parameters to the application (in the property file). Should the server to which the agent connects differ from the domain part of the JID, then the optional ##main_server## parameter needs to be set. This is for example the case, when using a Google Talk account, where a JID would be ##someuser@googlemail.com## and the main_server parameter is set to ##talk.google.com##.\n\nFor creating a personal agent you need an additional jabber account. This account is neccesary for convenient communication with the agent. The proxy account does not have to be on the same server as the main account. The account does not need to have any contacts, the agent will automatically connect the accounts, therefore a brand new account on a server like http://jabber.chaotic.de will do the trick.\n\nNow you can start the agent with ##./start.sh## (or ##start.bat## on Windows). After that, the agent is ready. Now you have to add the proxy JID to your roster. If you see the agent in your roster, start a chat and enter ##help##.\n\nThe ##help## command list all possible commands and explain how to use them:\n%%\n[18:26:21] Seebi: help\n[18:13:20] xOperator: The agent understands the following commands: query executes a simple query. for example: 'query select distinct....' \nhelp lists information about ...\n[...]\n%%\n\n===Managing Datastores===\nYou can manage your trusted datastores with the following commands. Each source is locally identified by a name which is associated to an URI.\n * ##list ds## - lists all configured datastores\n * ##add ds {name} {uri}## - add a datastore to the agent\n * ##del ds {name}## - remove a datastore\n\nExample:\n * The following command adds the dbpedia sparql endpoint as an agent datastore: ##\"\"add ds dbpedia http://dbpedia.org/sparql?format=XML&default-graph-uri=http%3A%2F%2Fdbpedia.org\"\"##\n\n\n===First Query / Managing Namespaces===\nThe ##query## command is used to send on-the-fly SPARQL queries to the xOperator. The query will be evaluated on every datastore and routed to every agent in the neighbourhood (not in group agent mode). The query results will be rendered by a default renderer.\n\nThe syntax of the command is: ##query {sparql query}##\n\nBefore you send your first SPARQL query, you have to define some namespaces, which you can use in the query (you can also define it in the query). The ##add ns## command can do that for you (type ##help## for more namespace commands).\n\nNamespace Example:\n * ##\"\"add ns foaf http://xmlns.com/foaf/0.1/\"\"##\n * ##\"\"add ns dbpedia2 http://dbpedia.org/property/\"\"##\n\nAfter that, you can send your first query.\n\nQuery Example:\n * The following query asks dbpedia for people which are born in Berlin in the year 1900: ##\"\"query SELECT ?name ?birth ?death WHERE { ?person dbpedia2:birthPlace . ?person dbpedia2:birth ?birth . ?person foaf:name ?name . ?person dbpedia2:death ?death. FILTER (?birth < \"1901-01-01\"^^xsd:date) . FILTER (?birth > \"1899-12-31\"^^xsd:date) . } ORDER BY ?name LIMIT 20\"\"##\n\n===Using Templates===\n\nA template is a customizable SPARQL query which is executed by a given sentence. Instead of writing the whole query again and again, you can create it as a template, where\nTo add a template, type ##add template {pattern} {query}##.\n\nTemplate Example:\n * The following command creates a template from the query example above: ##\"\"add template \"Who was born in berlin between * and *\" \"SELECT ?name ?birth ?death WHERE { ?person dbpedia2:birthPlace . ?person dbpedia2:birth ?birth . ?person foaf:name ?name . ?person dbpedia2:death ?death. FILTER (?birth < '%%2%%'^^xsd:date) . FILTER (?birth > '%%1%%'^^xsd:date) . } ORDER BY ?name LIMIT 20\"\"\"## - After creating the template, try ##Who was born in Berlin between 1899-12-31 and 1901-01-01##.\n\n\n===Writing Query Scripts===\nQuery scripts basically are small pieces of software, which run in a special environment where they have access to all relevant subsystems. They are given access to the list of known data sources and neighbouring agents. xOperator, allows the execution of query scripts in the ((http://groovy.codehaus.org/ Groovy scripting language)) for Java.\n\nTo write query script, you need access to the xOperator installation. This advanced topic is described in more detail on our ((QueryScripts query scripts page))." . . . . "2008-02-27T10:08:22"^^ . " 1. About\n - ((/Projects/xOperator#Overview Introduction))\n - ((/Projects/xOperator#News News))\n - ((/Projects/xOperator/CommunicationScenarios Scenarios))\n - ((/Projects/xOperator/Screenshots Screenshots))\n 2. Get started\n - ((/Projects/xOperator/Demo Demo / Public Agents))\n - ((/Projects/Downloads#xOperator Download))\n - ((/Projects/xOperator/FirstSteps First Steps))\n 3. Developing\n - ((/Projects/xOperator/InstallFromSubversion Install from SubVersion))\n - ((/Projects/xOperator/ChangeLog Changelog / Roadmap))\n - ((/Projects/xOperator/QueryScripts Query Scripts))\n - ((http://code.google.com/p/xoperator/issues/list Issues))\n 4. Community\n - ((http://code.google.com/p/xoperator/ Google Code Page))\n - ((http://groups.google.com/group/xoperator Mailinglist))\n - ((/Projects/xOperator/RelatedWork Related Work))\n" . . . . "2007-12-21T11:20:18"^^ . "{{Include page=\"/Projects/xOperator/Menu\" divclass=\"floatbox\" nomark=\"1\"}}\n==Communication Scenarios==\n{{toc divclass=\"box\" notitle=true}}\nhttp://aksw.org/Projects/xOperator/files?get=usagescenarios.png\n\n===Personal Agent (A)===\nThis scenario is the most important one and also builds the foundation for the other two communication scenarios. A user of an Instant Messaging network installs his own personal agent and configures information sources he owns or trusts. Information sources can be for example a FOAF profile of the user containing personal information about the user and about relationships to other people he knows and where to find further information about these. This information is represented in FOAF using the properties ##foaf:knows## and ##rdfs:seeAlso##.\nThe following listing shows an excerpt from a FOAF profile.\n%%\n:me a foaf:Person ;\n foaf:knows [\n a foaf:Person ;\n rdfs:seeAlso ;\n foaf:name \"Michael Haschke\" ;\n foaf:nick \"Haschek\" ] .\n%%\nAdditionally this FOAF profile can link to other RDF documents which contain more information about the user and his activities. The RDF version of his calendar, for example, could be linked as follows:\n%%\n:me rdfs:seeAlso .\n a ical:Vcalendar;\n rdfs:label \"Haschek's Calendar\" .\n%%\nSuch links span a network of information sources as depicted in theFigure above. Each user maintains his own information and links to information sources of his acquaintances. Depending on the query, the agent will access the respective resources.\n\n===Group Agent (B)===\nThis communication scenario differs from the Personal Agent scenario in that multiple users get access the same agent. The agent should be able to communicate with multiple persons at the same time and to answer queries in parallel. As is also depicted in the above Figure the agent furthermore does not only access remote documents but can also use a triple store for answering queries.\nWhen used within a corporate setting this triple store can for example contain a directory with information about employees or customers. The triple store can be also used to cache information obtained from other sources and thus facilitates faster query answering.\nFor agents themselves, however, the distinction between RDF sources on the Web and information contained in a local triple store is not relevant.\n\n===Agent Network (C)===\nThis scenario extends the two previous ones by allowing communication and interaction between agents.\nThe rationale is to exploit the trust and provenance characteristics of the Instant Messaging network: Questions about or related to acquaintances in my network of trust can best answered by their respective agents. Hence, agents should be able to talk to other agents on the IM network. First of all, it is crucial that agents on the IM network recognize each other. A personal agent can use the IM account of its respective owner and can access the contact list (also called roster) and thus a part of its owner's social network. The agent should be able to recognise other personal agents of acquaintances in this contact list (auto discovery) and it should be possible for agents to communicate without interfering with the communication of their owners. After other agents are identified it should be possible to forward SPARQL queries (originating from a user question) to these agents, collect their answers and present them to the user.\n" . . . . "2007-12-21T11:55:35"^^ . "{{Include page=\"/Projects/xOperator/Menu\" divclass=\"floatbox\" nomark=\"1\"}}\n==Related Work==\n\nAgent software is a rapidly developing area of research. According to the ((http://agents.umbc.edu/introduction/ao/ typology of Hyacinth S. Nwana)) xOperator is an interface agent for the Semantic Web.\n\nProposals and first prototypes which are closely related to xOperator and inspired its development are\n * Dan Brickley's ((http://svn.foaf-project.org/foaftown/jqbus/intro.html JQbus)) and\n * Chris Schmidt's ((http://crschmidt.net/semweb/sparqlxmpp/ SPARQL over XMPP)).\nHowever, both works are limited to the pure transportation of SPARQL queries over XMPP.\n\nQuite different but the xOperator approach nicely complementing are works regarding the semantic annotation of IM messages.\n * ((http://nabu.opendfki.de/ Nabu)) for example is a semantic archive for XMPP instant messaging which facilitates search in IM message archives.\n * ((https://www.uni-koblenz.de/FB4/Institutes/IFI/AGStaab/Research/sam SAM)) suggests ways to make IM more semantics aware by facilitating the classification of IM messages, the exploitation of semantically represented context information and adding of semantic meta-data to messages.\n" . . . . "2007-12-21T11:10:16"^^ . "{{Include page=\"/Projects/xOperator/Menu\" divclass=\"floatbox\" nomark=\"1\"}}\n==Screenshots==\n((http://www.flickr.com/photos/seebi/2125943357/ http://farm3.static.flickr.com/2095/2125943357_1658a49bd9.jpg))\nUsing xOperator in Gajim for some queries\n\n((http://www.flickr.com/photos/seebi/2017354917/ http://farm3.static.flickr.com/2029/2017354917_f2392a3373.jpg))\nFirst Contact - showing some admin commands using the Psi Client" . . . . "2008-02-27T09:56:14"^^ . "{{Include page=\"/Projects/xOperator/Menu\" divclass=\"floatbox\" nomark=\"1\"}}\n==Query Scripts==\nExperiences during the evaluation have led to the following rules for creating patterns and queries in xOperator.\n\n{{toc divclass=\"box\" notitle=true}}\n\n===Script Setup===\n\n===Query formulation===\n====Query as fuzzy as possible====\nInstant Messaging is a very quick means of communication. Users usually do not capitalize words and use many abbreviations. This should be considered, when designing suitable AIML patterns. If information about the person `Sören Auer' should be retrieved, this can be achieved using the following graph pattern:\n##?subject foaf:name \"Auer\".##\n\nHowever, information can be represented in multiple ways and often we have to deal with minor misrepresentations (such as trailing whitespace or wrong capitalizations), which would result for the above query to fail. Hence, less strict query clauses should be used instead. When searching for information regarding `Sören Auer' the following relaxed SPARQL clause, which matches also substrings and is case insensitive, could be used:\n%%\n?subject foaf:name ?name.\nFILTER regex(?name, '.*Auer.*', 'i')\n%%\n\n====Use patterns instead of qualified identifiers for properties====\nSimilar, as for the identification of objects, properties should be matched flexible. When searching for the ##homepage## of `Sören Auer' we can add an additional property matching clause to the SPARQL query instead of directly using, for example, the property identifier ##foaf:homepage##:\n%%\n?subject ?slabel ?spattern.\n?subject ?property ?value.\n?property ?plabel ?ppattern.\nFILTER regex(?spattern, '.*Auer.*', 'i')\nFILTER regex(?ppattern, '.*homepage.*', 'i')\n%%\n\nThis also enables multilingual querying if the vocabulary contains the respective multilingual descriptions.\nCreating fuzzy queries, of course, significantly increases the complexity of queries and will result in slower query answering by the respective SPARQL endpoint. However, since we deal with a distributed network of endpoints, where each one only stores relatively small documents this effect is often negligible.\n\n====Use subqueries for additional documents====\nIn order to avoid situations where multiple agents retrieve the same documents (which is very probable in a small worlds scenario with a high degree of interconnectedness) it is reasonable to create query scripts, which only distribute certain tasks to the agent network (such as the retrieval of prospective information sources or document locations), but perform the actual querying just once locally.\n" . . . . "2008-03-03T17:22:15"^^ . "==IT-Risiko-Ontologie: Zusammenfassung==\nDie IT-Risikoanalyse in Unternehmen ist ein Prozess der von verschiedenen internen (Unternehmensstruktur, Verantwortliche, Systeme) und externen Bedingungen (Gesetze, Richtlinien und Standards) abhangig ist. Als erstes Ergebnis dieser Arbeit wurde eine Standardmethode zur Durchführung einer IT-Risikoanalyse für die Carl Zeiss Jena Gmb H ausgewählt. Diese Methode wurde an die speziellen Anforderungen der Carl Zeiss Jena Gmb H angepasst und durchgeführt. Die bei der Analyse entstandenen Ergebnisse wurde mit dem methodeneigenen Werkzeug GSTOOL aufgenommen und stehen als Datenbasis für das IT-Risikomanagement zur Verfügung. Die in dieser Arbeit entwickelte Vorgehensweise für die Durchführung einer IT-Risikoanalyse auf Basis von IT-Grundschutz, kann in dieser Form auch in anderen Tochterunternehmen der Carl Zeiss AG oder in externen Unternehmen durchgeführt werden. Eine Betrachtung der IT-Risikoanalyse unter dem Aspekt des Wissensmanagements zeigte, dass es bei dem eingesetzten Tool zur IT-Risikoanalyse, Defizite bei der Erstellung von komplexen Anfragen auf den Datenbestand und bei der Möglichkeit der gemeinschaftlichen Arbeit mit dem enthaltenen Wissen gibt. Deshalb war es das Ziel, durch Methoden und Werkzeuge des Wissensmanagements, Lösungen für diese beiden Anforderungen zu finden. Dieses Thema wurde im zweiten Teil dieser Arbeit betrachtet.\nAls Grundlage für das IT-Risiko spezifische Wissen, wurde auf Basis der Erfahrungen aus Phase eins, die IT-Risiko-Ontologie erstellt. Diese Ontologie kann als Grundlage für zukünftige Ontologien in diesem Bereich angesehen werden oder durch die beschriebene Vorgehensweise bei der Entwicklung anderer Ontologien hilfreich sein.\nAls Lösung für die beiden Probleme, der komplexen Suche und der fehlenden gemeinschaftlichen Interaktionsmöglichkeiten bei klassischen Tools der IT-Risikoanalyse,konnten die folgenden Erkentnisse ermittelt werden.\nBei der Untersuchung der IT-Risiko-Ontologie im Einsatz mit OntoWiki wurde herausgefunden, dass die Möglichkeit zur komplexen Suche in Ontologien mit SPARQL großes Potential gerade im Bereich IT-Risikoanalyse hat. Es wurde gezeigt, wie schnell Wissen welches in der Ontologie enthalten ist, mit einer SPARQL-Anfrage analysiert werden kann. Die Wiki-Funktionalitäten von OntoWiki im Bereich Wissensmanagement wurden als Ansatz erkannt, wie Wissensmanagement auch in Unternehmen eingesetzt werden kann.\n\nDie gesamte Vorgehensweise der Arbeit kann zukünftig als Orientierung für andere Projekte im Bereich der IT-Risiko-Ontologien dienen. Die IT-Risiko-Ontologie selbst, kann in späteren Projekten als Ergänzung zu klassischen Risikoanalysemethoden eingesetzt werden, um die Arbeit mit dem vorhandenen Wissen zu unterstützen. Die IT-Risiko-Ontologie wird zukünftig im Internet zur Verfügung stehen, um die Ontologie auch in anderen Projekte einsetzen zu können oder auf deren Basis eine Weiterentwicklung durchzuführen. Eine Weiterentwicklung der Ontologie oder die Entwicklung von Plugins für OntoWiki, in Zusammenarbeit mit Unternehmen, können dabei wie diese Arbeit für beide Seiten produktive Ergebnisse liefern. Ein letzter Punkt sind aber ebenfalls die gewonnen Erfahrungen, die bei der Erstellung der Ontologie entstanden sind und durch diese Arbeit an die Entwicklungscommunity weitergegeben werden.\nDa Informationen in Unternehmen, um auf das Leitzitat der Arbeit zurückzukommen, in Zukunft immer starker an Bedeutung gewinnen werden, wird Wissensmanagement in Unternehmen, mit generischen Tools wie OntoWiki oder Ontologien wie der IT-Risiko-Ontologie, eine noch wesentlich wichtigere Bedeutung zukommen.\n\n===Literatur===\n\n[AG 2006] AG, Zeiss (2006). Geschäftsbericht Carl Zeiss Gruppe 2005/06. Carl Zeiss Gruppe.\n[Andreas Ekelhart 2007] Andreas Ekelhart, Stefan Fenz, Markus Klemen (2007). Security Ontologies: Improving Quantitative Risk Analysis. Proceeding, Vienna University of Technology.\n[BIS 2004] BIS (2004). Internationale Konvergenz der Eigenkapitalmessung und der Eigenkapitalanforderungen ISBN 92-9197-322-X. Rahmenvereinbahrung, BIS.\n[Bontas 2005] Bontas, Elena Paslaru (2005). Practical Experiences in Building Ontology-based Retrieval Systems. Proceeding, Freie Universitat Berlin.\n[BSI 2005] BSI, Hrsg. (2005). BSI Standard 1002IT-Grundschutz-Vorgehensweise.\n[BSI 2006] BSI (2006). BSI Grundschutzkataloge. Verlag.\n[BSI 2007] BSI (2007). Lage der IT-Sicherheit in Deutschland 2007. Report, BSI.\n[BSI100-1 2006] BSI100-1 (2006). BSI-Standard 100-1 Management fur Informationssicherheit. Verlag.\n[BSI100-2 2006] BSI100-2 (2006). BSI-Standard 100-2 IT-Grundschutz-Vorgehensweise. Verlag.\n[BSI100-3 2006] BSI100-3 (2006). BSI-Standard 100-3 Risikoanalyse auf Basis von IT-Grundschutz. Verlag.\n[Bundestag 1998] Bundestag, Der Deutsche (1998). Kontroll und Transparenz Gesetz. Gesetz, Deutsche Bundestag.\n[Bundestag 2006] Bundestag, Der Deutsche (2006). Bundesdatenschutzgesetz. Gesetz, Deutscher Bundestag.\n[(Datenschutzbeauftragter) 2002] (Datenschutzbeauftragter), Wolfgang Schüler , Hrsg. (2002). CQP0029 Risikomanagement.\n[Eberlein 2007] Eberlein, Rüdiger (2007). Studie IT-Trends 2007. Report, Capgemini.\n[Eric Prud’hommeaux 2008] Eric Prud’hommeaux, Andy Seaborne (2008). W3C Recommendation 15 January 2008. Recommendation 15 January 2008, W3C.\n[EU 2004] EU (2004). VERORDNUNG (EG) Nr. 460/2004 DES EUROPÄISCHEN PARLAMENTS UND DES RATES vom 10. Marz 2004 zur Errichtung der Europäischen Agentur fur Netz- und Informationssicherheit. Amtsblatt der europäischen Union, EU.\n[Fensel 2001] Fensel, Dieter (2001). Ontologies: A Silver Bullet for Knowledge Management and Electronic Commerce. Report, Digital Enterprise Research Institute.\n[Fernandez Lopez 1999] Fernandez Lopez, M. (1999). Overview Of Methodologies For Building Ontologies. Proceeding, Universidad Politecnica de Madrid.\n[Floris Ampe 2004] Floris Ampe, Dirk Steuperaert (2004). IT Governance Global Status Report. Report, IT Governance Institute.\n[Landwehr 2004] Landwehr, Avizienis, Laprie (2004). Basic concepts and taxonomy of dependable and secure computing. Proceeding, University of Maryland.\n[Luckhardt 2006] Luckhardt, Norbert (2006). Lagebericht zur Informationssicherheit. Report, Microsoft Deutschland GmbH.\n[Mansoor Ahmed und Tjoa 2007] Mansoor Ahmed, Amin Anjomshoaa, Tho Manh Nguyen und\nA. M. Tjoa (2007). Towards an Ontology-based Organizational Risk Assessment in Collaborative Environments Using the SemanticLIFE. Proceeding, Vienna University of Technology.\n[Michael K. Smith 2004] Michael K. Smith, Chris Welty, Deborah L. McGuinness (2004). OWL Web Ontology Language Guide. Recommendation, W3C.\n[Nenad Stojanovic 2002] Nenad Stojanovic, Ljiljana Stojanovic, Siegfried Handschuh (2002).\nEVOLUTION IN THE ONTOLOGY-BASED KNOWLEDGE MANAGEMENT SYSTEMS. Proceeding, University of Karlsruhe.\n[Noy und McGuinness 2000] Noy, Natalya F. und D. L. McGuinness (2000). Ontology Development 101: Proceeding, Stanford University. \n[Organization 2005] Organization, Inernational Standard (2005). International Standard ISO/IEC 27001. Standard, Inernational Standard Organization.\n[Philip L. Campbell 2004] Philip L. Campbell, Jason E. Stamp (2004). A Classification Scheme for Risk Assessment Methods. Recommendation, Sandia National Laboratories.\n[Sören Auer 2007] Sören Auer, Sebastian Dietzold und Thomas Riechert (2007). OntoWiki - A Tool for Social, Semantic Collaboration. Proceeding, University of Pennsylvenia, Universität Leipzig.\n[Victor Raskin 2001] Victor Raskin, Hempelmann, Triezenberg (2001). Ontology in Information Security: A Useful Theoretical Foundation and Methodological Tool. Proceeding, CERIAS, Purdue University,Computing Research Laboratory, New Mexico State.\n[ad hock Working Group 2006] Working Group, ENISA ad hock (2006). ENISA RM Deliverable1 Final version v1.0. Deliverable, ENISA.\n\n" . . . . "2010-07-05T14:40:00"^^ . "{{Include page=\"/Projects/OntoWiki/EventPluginArchitectureMenu\" divclass=\"floatbox\" nomark=\"1\"}}\n ATTENTION: THIS PAGE IS OUTDATED - FOR A CURRENT VERSION, HAVE A LOOK AT http://code.google.com/p/ontowiki/wiki/ExtensionDeveloperStart\n==How to develop an ~OntoWiki Plugin==\n\n{{toc}}\n\nThis wiki page introduces how to develop plugins for ~OntoWiki. Developing Erfurt plugins is basically the same but you don't have Zend events, views and action controllers.\n\n===Folder structure for plugins===\n\nDeclare the plugin folder (relative to application's root dir) in ~OntoWiki's ##config.ini##:\n\n%%(ini)\nplugins.ontowiki = ./plugins/\n%%\n\nCurrently only one folder can be declared, in future versions of ~OntoWiki different folders may be possible. In the same way you may declare the folder for Erfurt plugins in Erfurt's ##config.ini##: ##plugins.erfurt = ./erfurtplugins/## (relative to Erfurt folder).\n\nThere every plugin has its own folder. A plugin folder can include several other plugin folders but it is not possible to have two different plugins packages parallel in one folder. Every plugin package can include different plugin classes and libraries, and it haves its own ##config.ini## which must be located in the root folder of the plugin package. For example:\n\n%%(email)\n|-ontowiki/\n |-plugins/\n |-plugin-one/\n | |-config.ini\n | |-Plugin-one.php\n | |-templates/\n | |-controllers/\n | |-library/\n | |-plugin-two/\n | |-config.ini\n | |-Plugin-two.php\n |-plugin-three/\n |-config.ini\n |-Plugin-three-A.php\n |-another-folder/\n | |-Plugin-three-B.php\n |-api/\n%%\n\nThe class file have to be named like the inluded plugin class extended by ##.php##, e.g. if you have a plugin class called **Myplugin** then you have to store it in **Myplugin.php**.\n\n===The plugin class===\n\nLike we said before one plugin can be composed of different plugin classes. Each of those plugin classes can provide methods for API functions or -- most important for plugin developement -- event handlers for ~OntoWiki/Erfurt events. A plugin class may extend the general plugin classes of ~OntoWiki or Erfurt. This is not is not necessary but it prevents a lot of problems and it provides a better interface to ~OntoWiki/Erfurt.\n\n%%(php)\nclass YourPluginClass extends OntoWiki_Plugin {\n\n public function yourEventHandler() {\n\n // your event handler without event data\n\n }\n\n public function yourOtherEventHandler(&$data) {\n\n // your event handler with data passed\n // now you can do something with $data (but do not overwrite it accidently)\n\n }\n\n // your other stuff for the plugin class\n\n}\n%%\n\n!!Your event handlers cannot be private because the event dispatcher must be able to call them.!! If you want to write plugins only for Erfurt you may extend ##Erfurt_Plugin##. You have to name the file like the plugin class extended by ##.php##, in our example above it is ##~YourPluginClass.php##.\n\nIf you write event handler methods for events passing data, you must use references (##**&**$var##).\n\n===What to do===\n\nWriting plugins for ~OntoWiki is based on using events, writing event handlers, and using functionality provided by ~OntoWiki or Erfurt or by Zend helper classes (eg. the view helpers for ~OntoWiki to manipulate/extend the output). You can change templates/views, replace or insert action controllers, and doing smaller tasks like adding tabulators or menu options to windows and so on.\n\n====Using the interface, methods and objects====\n\nThe parent plugin classes from ~OntoWiki and Erfurt provide some methods and objects as an interface for plugins to core functionality. Currently provided interface objects are:\n\n * ##$_erfurtApp##: Erfurt object to use the ((http://docs.ontowiki.net/erfurt/doc/ Erfurt API))\n * ##$_eventDispatcher##: the ((http://docs.ontowiki.net/erfurt/doc/plugin/Erfurt_EventDispatcher.html event dispatcher)) object\n * ##$_pluginManager##: the ((http://docs.ontowiki.net/erfurt/doc/plugin/Erfurt_PluginManager.html plugin manager)) object\n * ##$_action##: object of currently used action controller (if available)\n * ##$_view##: view object (instance of ((http://framework.zend.com/manual/en/zend.view.html Zend_View))) provided by current action controller or the viewRenderer helper\n * ##$_viewRenderer##: object of currently used ((http://framework.zend.com/manual/en/zend.controller.actionhelpers.html#zend.controller.actionhelpers.viewrenderer viewRenderer helper)) (if available)\n\nPlease have a look at the referenced documents how to use the methods of these objects. Some of those methods we use in our examples but generally you can do more. Methods provided by the parent plugin classes currently are:\n\n * ##_setEnvironment()##: this method tries to allocate the ##$_action## and ##$_view$## objects, because they could change between application states when event handlers are called\n * ##_getPluginRootDir()##: returns the server dir where the plugin is located (as string)\n * ##_getPluginBaseUri()##: returns the URL of the plugin folder, needfull when a plugin tries to add own javascript or stylesheet files to the theme\n * ##_getOntoWikiBaseUri()##: returns the URL of the ~OntoWiki installation\n * ##_getActiveModel()##: returns the URI of the currently choosen knowledge base\n\nMaybe there will be new methods in future. If you have any requests for new simplyfied interfaces to ~OntoWiki/Erfurt/Zend functionality, please add your request to our ((http://code.google.com/p/ontowiki/issues/list issue tracker)).\n\n====Replace a template====\n\n~OntoWiki provides standard templates for all actions but sometimes it makes sense to replace them by your own, for example if you want to add event triggers or other new stuff to the template. This will become important for delivering plugins when you write event handlers for your own template triggers. Another case is a new template needed by a new controller action added by a plugin.\n\nTo replace a template you need at least the ((http://framework.zend.com/manual/en/zend.view.controllers.html#zend.view.controllers.script-paths addScriptPath method from Zend_View)) (##_view## object) and the ((http://framework.zend.com/manual/en/zend.controller.actionhelpers.html#zend.controller.actionhelper.viewrenderer.api setScriptAction method of the viewRenderer helper)) (##_viewRenderer##).\n\n%%(php)\nfunction replaceTemplate() {\n\n // 1. Test for _view and _viewRenderer\n $this->_setEnvironment(); // getting the right objects for _view and _viewRenderer\n \n // 2. add the template folder within the plugin folder (use _view object)\n $this->_view->addScriptPath($this->_getPluginRootDir().'/templates/');\n \n // 3. exchange the template script (use _viewRenderer helper)\n // within your new template folder, the script must be in a folder called like controller (lowercase!)\n $this->_viewRenderer->setScriptAction('replace-template'); // set name (NAME.php) of template\n\n // alltogether the template is now PLUGINFOLDER/templates/resource/replace-template.php\n\n}\n%%\n\nOf course the example is simplyfied, usually it is better to check the obejects before, have a look a the ((http://powl.svn.sourceforge.net/viewvc/powl/trunk/ontowiki/plugins/Example/Example.php?view=markup#l_75 similar event handler from our Example plugin)).\n\nNow you have to announce your event handler ##replaceTemplate## to the ##~ZendPostDispatch## event (may also work with ZendPreDispatch event). If you only want to replace a template for a special action in one controller then you can add their names as prefix, dont forget ##default## as prefix for the module. Like in the Example plugin we only replace the template for the ##view## action of the ##resource## controller, we will get ##~default_resource_view_ZendPostDispatch## as the name of the event the event handler has to be announced to. You can specify those announcements in the plugin's configuration file:\n\n%%(ini)\nannounce.0.event = \"default_resource_view_ZendPostDispatch\"\nannounce.0.class = \"YourPluginClass\"\nannounce.0.method = \"replaceTemplate\"\n%%\n\nSee the corresponding announcement from our ((http://powl.svn.sourceforge.net/viewvc/powl/trunk/ontowiki/plugins/Example/config.ini-dist?view=markup#l_49 Example plugin's config.ini)).\n\n====Add/Replace an action controller====\n\nYou will need methods from Zend's ((http://framework.zend.com/manual/en/zend.controller.front.html Front Controller)) and the ((http://framework.zend.com/manual/en/zend.controller.request.html Request object)) to add or replace a controller or only one action:\n\n%%(php)\nfunction addYourController()\n{\n // 1. get front controller\n $frontController = Zend_Controller_Front::getInstance();\n\n // 2. get request object\n $request = $frontController->getRequest();\n\n // 3a. save controller name\n $controller = $request->getControllerName();\n\n // 3b. you can also save the action's name if you want to replace only the controller when a special action is called\n $action = $request->getActionName(); // not needed in this example\n \n // 4. check for controller [/action] name (your new controller)\n if ($controller == 'yourcontroller') {\n // add the directory from your plugin folder where controllers are located in\n $frontController->addControllerDirectory($this->_getPluginRootDir().'/controller/');\n\n // alltogether the controller is now PLUGINFOLDER/controller/YourcontrollerController.php\n }\n}\n%%\n\nNow announce this event handler in your plugin's configuration file. Use ##~ZendRouteShutdown## for new controllers, ##~ZendPreDispatch## is for replacing controllers.\n\n===Plugin configuration===\n\nEvery plugin package has its own ##config.ini## -- stored in the root folder of the plugin package -- to make declarations about plugin's folder structure, event handlers or translation files. Currently their are four main parts: meta information about the plugin, local folder structure, announcements for event handlers and announcing additional classes (e.g. for simple integration of APIs or other libraries). It also keeps information about the plugin's state (enabled or disabled). The ((http://code.google.com/p/ontowiki/source/browse/trunk/ontowiki/plugins/Example/config.ini-dist?r=2321 configuration file of the Example plugin)) can be found in the SVN. Every plugin configuration has to start with ##[general]##.\n\n====Meta information about the plugin====\n\nRight now meta information are not necessary but OntoWiki may get an overview or manager of running plugins later (or you could write a plugin for that issue ;) ). But providing meta information may be helpfully at all.\n\n%%(ini)\n[general]\n\n;------------------------------------------------------------------------------;\n; Information about Plugin ;\n;------------------------------------------------------------------------------;\n\nname = \"Example Plugin\"\ndescription = \"This is an example for an OntoWiki/Erfurt plugin.\"\nauthor = \"Michael Haschke\"\nurl = \"http://ontowiki.net/\"\nversion = \"$Id:$\"\n\nswitch = \"off\" ;is plugin active? on|off\n%%\n\n====Describe folder structure====\n\nIt may be necessary to split a plugin into different classes in several sub folders (e.g. see 'plugin-three' in our directory example above). If you add those folders to the configuration file they will be managed automatically by the plugin manager. Declare folders relative to the plugin's root folder (the folder where the configuration file is located):\n\n%%(ini)\n;------------------------------------------------------------------------------;\n; Which folders are needed ;\n;------------------------------------------------------------------------------;\n\nfolder.0 = \"./\" ; its not necessary to declare './' (plugin root itself)\nfolder.1 = \"./another-folder\"\nfolder.2 = \"./api\"\n%%\n\nIt's important to declare all folders you want use plugin classes from.\n\n====Announcing event handlers====\n\nYou can announce methods from a plugin class as event handlers, you have to declare the event name, name of the plugin class and name of the method from that class:\n\n%%(ini)\n;------------------------------------------------------------------------------;\n; Announcements of event handlers ;\n;------------------------------------------------------------------------------;\n\nannounce.0.event = \"ZendPostDispatch\" ; name of event\nannounce.0.class = \"Plugin-three-A\" ; name of plugin class\nannounce.0.method = \"changeTitleAtPostDispatch\" ; name of method from plugin class\n\nannounce.1.event = \"default_resource_view_ZendPostDispatch\"\nannounce.1.class = \"Plugin-three-B\"\nannounce.1.method = \"changeViewTemplate\"\n%%\n\n====Additional class registrations====\n\nYou can declare additional plugin classes which do not provide event handlers (e.g. providing an API or library for other plugins) because access to those classes will be easier through the plugin manager.\n\n%%(ini)\n;------------------------------------------------------------------------------;\n; Announce additional Classes ;\n;------------------------------------------------------------------------------;\n\nadd.0.class = \"ClassName\"\n%%\n\n====Private configuration sections====\n\nIn case your plugin needs some configuration internally, we encourage you to use one or more sections in your ##config.ini## file, e.g. ##[private]##. You also can use another name for the section or define more than one section, but in most cases a ##[private]## section should fullfill your needs.\nYou can access the config in your plugin class by calling the protected ##_getPluginConfig()## method. This method will return an instance of ##Zend_Config##. In case your section is called ##[private]## you would access your configuration the following way: ##$this->_getPluginConfig()->private->foo->bar##.\n\n====Language configuration files====\nYour plugin can have it's own language configuration file in order to support multiple languages or change the default behaviour of OntoWiki. You just have to create a file called ##string.ini## in your plugin root folder and add at least two sections: ##[english]## and ##[default : english]##. So your file could look like this:\n\n%%(ini)\n[english]\nfoo = \"Bar\"\n\n[default : english] \n%%\n\n====Code definitions====\n\n//Is coming later ...//\n\n" . . . . "2008-10-23T13:40:10"^^ . "<##>\n\n==International Workshop on Interacting with Multimedia Content in the Social Semantic Web (IMC-SSW 2008)==\n**Collocated with the ((http://samt2008.uni-koblenz.de/index.php?page=home 3rd International Conference on Semantic and Digital Media Technologies (SAMT 2008) )), Koblenz, Germany, Dez 03 2008**\n\n Resources: ((http://blog.aksw.org/feed/atom/?tag=imcssw RSS Feed)), ((http://www.google.com/calendar/ical/l0m29bt3mp79jhobmf3u8ufu88%40group.calendar.google.com/public/basic.ics iCal Calendar)), ((http://demo.ontowiki.net/resource/export/?r=http%3A%2F%2F3ba.se%2Fconferences%2FIMCSSW2008&m=http%3A%2F%2F3ba.se%2Fconferences%2F&output=xml&file=imc-ssw-2008.rdf RDF)) [((http://demo.ontowiki.net/resource/view/IMCSSW2008?m=http%3A%2F%2F3ba.se%2Fconferences%2F OntoWiki view))], ((http://aksw.org/Events/2008/IMCSSW/files?get=agreement.pdf Copyright Agreement))\n\n{{toc divclass=\"floatbox\"}}\n===News===\n{{feed url=\"http://blog.aksw.org/feed/?tag=imc-ssw\" max=\"1\"}}\n\n===Motivation===\nMedia sharing and social networking websites have attracted many millions of users resulting in vast collections of user generated content. The contents are typically poorly structured and spread over several platforms, each supporting specific media types. With the increasing growth and diversity of these websites, new ways to access and manage the contents are required – both within and across web platforms.\n\n===Topics of Interest===\nThis workshop focuses on the interaction with these multimedia contents. We are particularly interested in contributions that follow Web 2.0 principles of simplicity and/or social navigation in combination with the representation, annotation, and linking power of the Semantic Web. Topics of interest include, but are not limited to:\n\n * Navigating and visualizing semantically annotated multimedia content\n * Social semantic tagging of multimedia content\n * Social semantic recommendation and search of multimedia content\n * Semantic mashups of multimedia content across websites\n * Semantic annotation of multimedia content in Wikis and Weblogs\n * Interaction with multimedia content on the semantic desktop\n * Semantic user interfaces for media sharing and social networking websites\n * Experiences and use cases regarding the interaction with multimedia content on the Social Semantic Web\n\n===Programm===\nThe workshop programm is also available as an ((http://www.google.com/calendar/ical/l0m29bt3mp79jhobmf3u8ufu88%40group.calendar.google.com/public/basic.ics iCal Calendar)).\n====Workshop Programm====\n**03.12.2008 - 09:00 Start of IMC-SSW**\n**09:00 - 10:30 Session 1**\n * Towards Increased Reuse: Exploiting Social and Content Related Features of Multimedia Content on the Semantic Web (Buerger, Tobias)\n * Mining User Profiles to Support Structure and Explanation in Open Social Networking (Stewart, Avare; Diaz-Aviles, Ernesto; Nejdl, Wolfgang)\n * Interlinking Multimedia - Principles and Requirements (Buerger, Tobias; Hausenblas, Michael) - position paper\n**10:30 - 11:00 Coffee break**\n**11:00 - 12:30 Session 2**\n * ImageNotion as a mashup service for a semantic image web? (Walter, Andreas; Gabor, Nagypal)\n * gFacet: A Browser for the Web of Data (Heim, Philipp; Ziegler, Jürgen)\n * select * where { :I :trust :you } (Halb, Wolfgang; Hausenblas, Michael) - position paper\n**12:30 - 13:00 Summary & Discussion**\n**13:00 End of IMC-SSW**\n**13:00 - 14:00 Lunch**\n====Afternoon Programm of SAMT conference===\n**14:00 - 17:30 Excursion**\n**18:00 - 20:00 Poster Cocktail**\n\n===Target Audience===\n * Researchers of the Semantic Web and Knowledge Representation communities interested in interaction aspects\n * Researchers of the Multimedia and Human-Computer-Interaction communities interested in semantic aspects\n * Developers of web applications, interaction designers, and information architects\n\n===Submission Types===\n * Full papers (8-12 Pages)\n * Position papers (4-8 Pages)\n * Poster and Demo papers (3-4 Pages)\nSubmissions should be formatted according to ((http://www.springer.com/computer/lncs?SGWID=0-164-7-72376-0 LNCS style)) and submitted in PDF format.\nPlease use the ((https://www.conftool.net/samt2008/ SAMT Conference Tool)) for your submission. \nThe workshop proceedings will be published as a volume at ((http://ftp.informatik.rwth-aachen.de/Publications/CEUR-WS/ CEUR Workshop Proceedings)).\n\n===Important Dates===\n * **--14th-- 19th September**: Submission Deadline \n * **--5th-- 13th October**: Author's Notification \n * **--26th-- 31th October**: Camera ready\n\n * 3rd Dezember: Workshop\n\nAll important dates are included in this ((http://www.google.com/calendar/ical/l0m29bt3mp79jhobmf3u8ufu88%40group.calendar.google.com/public/basic.ics iCal calendar)).\n\n===Committees===\n**Organizers**\n((http://www.informatik.uni-leipzig.de/~auer/ Sören Auer)), University of Leipzig, Germany\n((http://bis.informatik.uni-leipzig.de/SebastianDietzold Sebastian Dietzold)), University of Leipzig, Germany\n((http://www.interactivesystems.info/Mitarbeiter/Personen/Lohmann Steffen Lohmann)), University of Duisburg, Germany\n((http://www.interactivesystems.info/Mitarbeiter/Personen/Ziegler Jürgen Ziegler)), University of Duisburg, Germany\n\n**Program Comittee**\n((http://www.cs.usask.ca/~ssb609/ Scott Bateman)), University of Saskatchewan, Canada\n((http://www.fzi.de/ipe/mitarbeiter.php?id=437 Simone Braun)), Research Center for Information Technology, Germany\n((http://davide.eynard.it/ Davide Eynard)), Politecnico di Milano, Italy\n((http://sw-app.org/ Michael Hausenblas)), Johanneum Research, Austria\n((http://www.andreas-hess.info/ Andreas Heß)), Lycos Europe GmbH, Germany\n((http://www.deri.ie/about/team/member/knud_m%F6ller/ Knud Möller)), DERI Galway, Ireland\n((http://www.ifi.uzh.ch/im/people/dr_jasminko_novak/ Jasminko Novak)), University of Zurich, Switzerland\n((http://apassant.net/ Alexandre Passant)), Université Paris-Sorbonne, France\n((http://www.elec.qmul.ac.uk/department/staff/research/yvesr.htm Yves Raimond)), Queen Mary University of London, UK\n((http://www.minet.uni-jena.de/~sack/ Harald Sack)), University of Potsdam, Germany\n((http://www.schaffert.eu/ Sebastian Schaffert)), Salzburg Research, Austria\n((http://www.fzi.de/ipe/mitarbeiter.php?id=128 Andreas Schmidt)), Research Center for Information Technology, Germany\n\n===Related Events===\n((http://aksw.org/SocialSemanticWebConference 1st Conference on Social Semantic Web (CSSW 2007), 26–28th September, Leipzig, Germany))\n((http://triple-i.tugraz.at/i_semantics 4th International Conference on Semantic Systems (I-SEMANTICS'08), 3-5th September 2008, Graz, Austria))\n\n%%(wacko wrapper=text wrapper_align=center) \nhttp://www.interactivesystems.info/assets/images/Events/SAMTbanner.jpg\n%%" . . . . "2008-03-25T16:30:06"^^ . "{{Redirect page=\"/Projects/DL-Learner/Carcinogenesis\"}}" . . . . "2008-07-25T15:11:55"^^ . "==Market potential of the Semantic Web Technologies==" . . . . "2008-04-15T12:20:02"^^ . "== Carcinogenesis Predictions using DL-Learner ==\n//\"Obtaining accurate structural alerts for the causes of chemical cancers is a problem of great scientific and humanitarian value.\" (A. Srinivasan, R.D. King, S.H. Muggleton, M.J.E. Sternberg in [5])//\n\n{{toc}}\n\n=== About Carcinogenesis Prediction ===\nCarcinogenesis (meaning literally, the creation of cancer) is the process by which normal cells are transformed into cancer cells. Cell division is a normal physiological process. However, mutations in DNA that lead to cancer can disrupt the balance between proliferation and programmed cell death. This results in uncontrolled cell division and tumor formation. \n\nPrevention of environmentally-induced cancers is a health issue of unquestionable importance. Almost every sphere of human activity in an industrialised society faces potential chemical hazards of some form. It is estimated that nearly 100,000 chemicals are in use in large amounts every day. A further 500-1000 are added every year. Only a small fraction of these chemicals have been evaluated for toxic effects like carcinogenicity (paragraph taken from [3]).\n<# #>\nThere have been several approaches by both - human and machines - to predict carcinogenicity. It has been shown in [6] that the performance of machine derived models for carcinogenicity can be equal to human experts. Classifying chemicals is a massive challenge, due to the high number and diversity of elements, structures, and tests involved in the problem. As outlined in several journal articles in the area of bioinformatics [1,3,7], reliable carcinogenesis prediction has not been achieved yet, but Artificial Intelligence approaches were able to learn new or confirm existing toxicological knowledge. The use of carcinogenicity models, which can be derived by humans and AI approaches, for setting priorities in the experiments of the ((http://ntp-server.niehs.nih.gov/ The U.S. National Toxicology Program)) (NTP) has been succesful [1].\n\n=== Modelling Carcinogenesis Data in OWL ===\nThe NTP makes a set of more than 300 tested compounds available for training by Machine Learning tools. Carcinogenicity of these compounds has been predicted using standardised chemical bioassays (exposure of rodents to chemicals). However, obtaining empirical evidence from such bioassays is expensive and usually too slow to cope with the number of chemicals that can result in adverse effects on human exposure. This has resulted in a need for models for carcinogenesis and lead to the decision of the NTP to make the data available in a suitable form.\n<# #>\n\nFor each compound, the chemical structure, structural indicators, and the results of short-term assays were made available. They can be downloaded at the website of the ((http://web2.comlab.ox.ac.uk/oucl/research/areas/machlearn/cancer.html Oxford University Machine Learning Group)). The data was made available in ((http://en.wikipedia.org/wiki/Prolog Prolog)) format. It is well known that not every logic program can be converted to an ((http://www.w3.org/2004/OWL/ OWL)) knowledge base and vice versa. However, for the carcinogenesis problem, such a mapping is possible. DL-Learner contains a Prolog parser, which was used to read in the data. Using a set of mapping rules, the Prolog files were converted into an OWL ontology, which can be downloaded ((http://dl-learner.svn.sourceforge.net/viewvc/*checkout*/dl-learner/trunk/examples/carcinogenesis/carcinogenesis.owl here)) and viewed using e.g. ((http://protege.stanford.edu/ Protegé)) or ((http://ontowiki.net OntoWiki)). During the transformation process almost no knowledge was lost or added. The resulting ontology contains 142 classes, 19 properties, 22373 instances, and 74567 triples.\n\n=== DL-Learner Prediction Results ===\nWe used DL-Learner to learn general models for substances causing cancer. The most sensible parameter of DL-Learner in this case is noise (bounding the minimum acceptable training set accuracy of the learned definition). We varied the noise parameter starting from 35% downwards in one percent steps and finally determined 32% as the setting, which minimizes the 10 fold cross validation error. The following table summarizes the accuracy of the learned definitions in comparison with other approaches using the same background knowledge (many of those use ((http://web2.comlab.ox.ac.uk/oucl/research/areas/machlearn/Aleph/ Aleph)) - a state of the art Inductive Logic Programming system - as their basis):\n\n<# #>\n#|\n|| **approach/tool** | **accuracy (standard deviation)** | **reference** ||\n|| DL-Learner | 67.4% (+- 7.9%) | ||\n|| Aleph with Ensembles | 59.0% to 64.5% | [2] ||\n|| Boosted Weak ILP | 61.1% | [4] ||\n|| Weak ILP | 58.7% | [4] ||\n|| Aleph Deterministic Top-Down 0.7 | 57.9% (+- 9.8%) | [8] ||\n|| Aleph Randomized Rapid Restarts 0.9 | 57.6% (+- 6.4%) | [8] ||\n|| Aleph Deterministic Top-Down 0.9 | 56.2% (+- 9.0%) | [8] ||\n|| Aleph Randomized Rapid Restarts 0.7 | 54.8% (+- 9.0%) | [8] ||\n|#\n\nAs evident from the table, DL-Learner has the highest cross validation accuracy of the listed approaches. For all approaches, where the standard deviation was given in the articles, we calculated whether the difference in accuracy is statistically significant using a t-test with a confidence interval of 95%. Indeed, in all those cases the difference turned out to be statistically significant. Note, that the second and third table entry combine different learned rules to obtain a classifier, which increases accuracy but reduces readability of the result. The average runtime of DL-Learner for each of the ten folds was 178 seconds on a 2.2Ghz Dual core machine with 2GB RAM. Additional 36 seconds were needed to read in the ontology (using the ((http://owlapi.sourceforge.net/ OWL API))) and prepare it for the approximate reasoner built into DL-Learner. Overall, DL-Learner reaches a similar accuracy as those approaches involving (possible task-specific) additional preprocessing steps.\n\nDL-Learner classifies slightly more than 2 out of 3 chemical compounds correctly, which is remarkable considering the difficulty of the considered problem. However, it is just one step towards more reliable carcinogenicity predictions and could be improved further for instance through a) more classified compounds in the background knowledge, b) more complete short-term assays for each compound, c) a proper selection of structural indicators by experts or feature selection AI approaches (which was not yet available for experiments here), d) the inclusion of more scientific principles (\"chemical reasoning\") developed within chemistry over the last decades, and e) improvements in DL-Learner and other Machine Learning approaches.\n\nAs an example, the following definition was obtained when using DL-Learner over the full training set (72% accuracy, for easier readability negation symbols are moved further out if possible):\n\n<# #>\n\nThis can be phrased in natural language as:\n\nA chemical compound is carcinogenic iff ...\n... it does not contain a Nitrogen-35, Phosphorus-60, Phosphorus-61, or Titanium-134 atom\n... and it has at least three Halide - excluding ~Halide10 - structures\n       or the ames test of the compound is positive and there are at least five atom bonds which are not of bond type 7.\n\nOver various runs, the DL-Learner has identified the ames test and multiple occurences of halide groups (in particular Ar-Halide) as indicators for carcinogenicity.\n\n=== References ===\n[1] R. Benigni and A. Giuliani, Putting the Predictive Toxicology Challenge Into Perspective: Reflections on the Results, Bioinformatics, 19(10), pp. 1194-1200, 2003.\n[2] I. Dutra, D. Page, V. S. Costa, and J. Shavlik, An Empirical Evaluation of Bagging in Inductive Logic Programming, Proceedings of the 12th International Conference on Inductive Logic Programming, Lecture Notes in Artificial Intelligence, Vol. 2583, pp. 48-65, Springer-Verlag, 2003.\n[3] C. Helma, R. D. King, S. Kramer, and A. Srinivasan, The Predictive Toxicology Challenge 2000-2001, Bioinformatics, 17(1), pp. 107-108, 2001.\n[4] N. Jiang and S. Colton, Boosting Descriptive ILP for Predictive Learning in Bioinformatics, Proceedings of ILP 2006, Lecture Notes in Computer Science, Vol. 4455, pp. 275-289, Springer, 2006.\n[5] A. Srinivasan, R. D. King, S. Muggleton, and M. J. E. Sternberg, Carcinogenesis Predictions Using ILP, Proceedings of the 7th International Workshop on Inductive Logic Programming, Lecture Notes in Artificial Intelligence, Vol. 1297, pp. 273-287, Springer-Verlag, 1997.\n[6] A. Srinivasan, R. D. King, and D. W. Bristol, An assessment of submissions made to the Predictive Toxicology Evaluation Challenge, Proceedings of the 16th International Joint Conference on Artificial Intelligence (IJCAI-99-Vol1), pp. 270-275, Morgan Kaufmann Publishers, July 31- August 6 1999.\n[7] H. Toivonen, A. Srinivasan, R. D. King, S. Kramer, and C. Helma, Statistical Evaluation of the Predictive Toxicology Challenge 2000-2001, Bioinformatics, 19(10), pp. 1183-1193, 2003.\n[8] F. Zelezný, A. Srinivasan, and D. Page, Lattice-Search Runtime Distributions May Be Heavy-Tailed, Proceedings of the 12th International Conference on Inductive Logic Programming, Lecture Notes in Artificial Intelligence, Vol. 2583, pp. 333-345, Springer-Verlag, 2003.\n" . . . . "2009-11-04T16:22:16"^^ . "==AKSW Partner==\n\nAKSW works with a wide range of international academic and industrial partners.\n\nThere exist in particular close collaborations with the following departments at Universität Leipzig:\n * ((http://www.asv.informatik.uni-leipzig.de Automatic Language Processing)) (ASV, Prof. Heyer)\n * ((http://dbs.uni-leipzig.de Databases)) (DBS, Prof. Rahm)\n\nSome examples of related research groups include:\n * Max Planck Institute for Evolutionary Anthropology (MPI Eva), with its ((http://www.eva.mpg.de/genetics/files/bio_informatic.html bioinformatics group)) focusing on applications of ontologies and knowledge representation in biology and medicine.\n * Institute for Medical Informatics, Statistics and Epidemiology (IMISE) with its research group ((http://www.onto-med.de Onto-Med (Ontologies in Medicine))).\n * ((http://infai.org Institute for Applied Informatics (InfAI) e.V. at Universität Leipzig)), which is a cooperation of eight departments from the computer science and business informatics as well as industrial sponsors, aiming to promote research and knowledge transfer.\n * ((http://liv.uni-leipzig.de Leipziger Informatik Verbund (LIV))), a network of academic and industrial members working in computer science with corporate members such as Perdata and Sun Microsystems \n * ((http://ontos.com Ontos AG)), a company and close cooperation partner of AKSW, which internationally markets ontology- and semantics-based products, in particular in the area of text mining and unstructured information integration.\n\nInternational partners include:\n\n<#

     

    #>\n\nhttp://www.isa-tools.de/images/Logo_kurz_blau_72.gif        http://www.uni-due.de/style_15/i/logo.gif        http://www4.wiwiss.fu-berlin.de/dbpedia-docs/fu-logo.gif        \n\n<#

     

    #>\n\nhttp://www.qa-systems.de/images/logo.gif        http://www.deri.ie/fileadmin/images/elements/deri_ie_head.gif        http://prodv.de/pdvweb/cms/downloads/3212/PRODV-logo.gif         \n\n<#

     

    #>\n\nhttp://www.lecos-gmbh.de/img/slice_03.gif        http://db.cis.upenn.edu/img/penn_logo.gif        http://www4.wiwiss.fu-berlin.de/dbpedia-docs/openlink150.gif    \n\n<#

     

    #>\n\nhttp://www.punkt.at/images/punktlogo.gif        http://bi-web.de/images/layout_bi_logo.jpg\n" . . . . "2008-06-16T02:50:17"^^ . "==E-Learning Ontologies==" . . . . "2008-06-16T03:07:15"^^ . "==E-Lerning Ontology for Lecture Slides==\n\n Author: Thomas Riechert\n Ontology: ((http://vorlesungen.ontowiki.net/model/export/?m=http://ns.aksw.org/e-learning/lectures/ http://ns.aksw.org/e-learning/lectures/))\n Example Data: ((http://vorlesungen.ontowiki.net))\n" . . . . "2008-06-13T17:45:14"^^ . "==IT-Infrastruktur Ontologie==" . . . . "2008-05-30T22:32:09"^^ . "<#\n
    \n

    RDFAPI-JS

    \n\n\n

    Use JavaScript RDFa Widgets for Model/View Separation inside Read/Write Websites

    \n

    SVN Repository

    \n
    \n
    #>\n{{a name=\"News\"}}{{feed divclass=\"floatbox\" title=\"News\" url=\"http://blog.aksw.org/feed/?tag=rdfapi-js\" max=\"2\"}}{{a name=\"Overview\"}}\n\n==Introduction==\nAs more and more websites start to embed RDFa content in their web application view, the need arises to provide a more extensive way for viewing and editing this semantic content independently from the remainder of the application. We present a JavaScript API that allows the independent creation of editing widgets for embedded RDFa, which adds a new edge to Web development in the context of the Semantic Web. As an addition, the API also provides sound update methods that allow on-the-spot model synchronization between client and server.\n\n==Publications=={{a name=\"Publications\"}}\n**Dietzold, S.; Hellmann, S., Peklo, M.:**\n((http://www.semanticscripting.org/SFSW2008/papers/15.pdf Using JavaScript RDFa Widgets for Model/View Separation inside Read/Write Websites)). Proceedings of the SFSW 08 Workshop on Scripting for the Semantic Web, Tenerife, Spain, June 2, 2008.\n" . . . . "2011-06-08T16:41:10"^^ . "==Press==\n\nFeel free to ((http://aksw.org/Team contact us)) if you plan to publish an article about the (Social) Semantic Web and/or need further information about AKSW technology and developments.\n\nTo stay tuned about all AKSW developments, please visit the ((http://blog.aksw.org/ AKSW blog)) regularly or subscribe to our ((feed://http//blog.aksw.org/feed/ RSS feed)).\n<#
    #>\n\n===Articles about AKSW===\n\nAKSW projects and its results are frequently featured in online and print media. \n\n====2011====\n * Another interesting article on AKSW's activities has been published about the Leipzig Semantic Web Day 2011. Many of the talks and discussions are summarised in here, thus giving a nice overview on current developments in the Semantic Web field in general and on the event's main theme \"Linked Data for the Masses\" in particular. The article can be found ((http://www.unternehmen-region.de/de/5785.php here)).\n\n * The magazine of the University of Leipzig has published an article on a new regional project between AKSW and the Kunert Business Software company based in Leipzig. Sponsored by Leipzig's Chamber of Industry and Commerce, this project is about developing another open-source tool for the interlinking of enterprise data. The article written in German can be found ((http://aksw.org/Press/files?get=1102ul_journal.pdf here)).\n\n * In the quarterly magazine //Transferbrief Leipzig// the University of Leipzig takes the opportunity to report on latest research results and concrete interaction projects between academia and the business community. This year's first issue covers a one-page introduction to AKSW's newest projects. The article can be found in the ((http://aksw.org/Press/files?get=tb_12011.pdf print issue 1/2011)) on page 11. \n\n<##>\n====2010====\n * On December 18, the //Leipziger Volkszeitung// wrote about the Professors Catalog of the University of Leipzig, which is based on the AKSW software OntoWiki and has been developed and managed in cooperation with historians from the university. The article describes the award-winning and so far unique online catalog through nice examples and especially praises its easy-to-use character. \n\n * With a long and amiable article on the Semantic Web in its March issue (03/2010), Leipzig's city events guide and social magazine //Kreuzer// notably featured AKSW and its projects. A PDF of the print version can be accessed ((http://aksw.org/files/201003kreuzer.pdf here)). A shorter ((http://www.kreuzer-leipzig.de/magazin/1218 online version)) is also available. \n<#
    #>\n\n====2009====\n * Austrian newspaper //Die Presse// published a long article about the Semantic Web and prominently references AKSW technologies such as Triplify. A PDF of the original article can be accessed ((http://aksw.org/files/semanticpressestory2.pdf here)), a shorter ((http://diepresse.com/home/techscience/internet/index.do online version is also available)).\n \n====2008====\n * The popular Web technology blog ((http://www.readwriteweb.com/archives/semantify_your_web_apps_with_triplify.php ReadWriteWeb)) featured AKSW's light-weight information integration tool ((http://Triplify.org Triplify)).\n * ((http://www.semantic-web.at/ Semantic Web School)) published an interview with ((http://www.informatik.uni-leipzig.de/~auer/ Sören Auer)) on ((http://Cofundos.org Cofundos)) and the vision of participatory R&D. Read the interview ((http://www.semantic-web.at/1.36.resource.215.s-ren-auer-x22-cofundos-is-based-on-the-vision-that-the-combination-of-multiple-contributi.htm here)).\n * AKSW's participatory R&D platform ((http://Cofundos.org Cofundos.org)) was mentioned in popular news channels and Weblogs (e.g. ((http://www.heise.de/newsticker/meldung/97846 Heise)), ((http://www.golem.de/0710/55592.html Golem)), ((http://www.linux.com/feed/119980 linux.com)) and ((http://technorati.com/search/cofundos?authority=n&language=n many others))).\n<#
    #>\n\n===Press Releases===\n" . . . . "2008-05-22T12:11:36"^^ . "{{Include page=\"/Projects/DLLearner/Menu\" divclass=\"floatbox\" nomark=\"1\"}}\n==DL-Learner Architecture==\n\nDL-Learner consists of core functionality, which provides Machine Learning algorithms for solving the learning problem, support for different knowledge base formats, an OWL library, and reasoner interfaces. There are several interfaces for accessing this functionality, a couple of tools which use the DL-Learner algorithms, and a set of convenience scripts. The general structure is illustrated in the following figure:\n\nhttp://dl-learner.org/Projects/DLLearner/Architecture/files?get=structure.png\n\nTo be flexible in integrating new learning algorithms, new kinds of learning problems, new knowledge bases, and new reasoner implementations, DL-Learner uses a component based model. Adding a component is as easy as subclassing the appropriate class and adding the name of the new class to the \"components.ini\" file.\n\nIn DL-Learner, there are four types of components (knowledge source, reasoning service, learning problem, learning algorithm). There are several components of each type and each component can have its own configuration options as illustrated below:\n\nhttp://dl-learner.org/Projects/DLLearner/Architecture/files?get=components.png\n\nEach component can specify its own configuration options. Currently, the following configuration option types exist (new ones can be implemented if necessary):\n * boolean\n * string (a set of allowed strings can be specified)\n * int (min and max value can be specifified)\n * double (min and max value can be specifified)\n * set of strings\n * list of string tuples\nAlthough, we loose the ability to use arbitrary argument types in components, this gives us the possibility to build very flexible user interfaces. Whenever, a new component or a new configuration option for a component is added, the current user interfaces (GUI, web service, commandline) will automatically support it without any need for code changes.\n" . . . . "2008-05-20T16:06:07"^^ . "==Diplomarbeit: Integration der Softwiki-Methode in die Open-Source-Founding Plattform COfundOS.org auf Basis des Ressource Description Frameworks (RDF)==\n\nBearbeiter: Herr Zhang\nBetreuer: Thomas Riechert\n\n((!/intern))" . . . . "2010-07-05T17:02:27"^^ . " ATTENTION: THIS PAGE IS OUTDATED\n{{Include page=\"/Projects/OntoWiki/Menu\" divclass=\"floatbox\" nomark=\"1\"}}\n\n==Map Plugin==\n\nThe OntoWiki MapPlugin was developed during the software engeneering practical training at the university of Leipzig by a group of nine students. Our intention was to produce a plugin which makes instances from ontologies viewable. We are proud to present you the result:\n\n...the OntoWiki MapPlugin!\n\n((http://pcai042.informatik.uni-leipzig.de/~swp08-5/ Project Homepage))\n((http://ontowiki.net/Projects/OntoWiki/MapPlugin/files?get=mapplugin.tar.gz Download the Plugin))\n\n{{toc}}\n\n\n===Installing the MapPlugin===\n\n====Requirements====\nA running OntoWiki installation and an internet connection is all you need to install and use the MapPlugin.\n\n====Four easy steps to your working MapPlugin====\n * download the MapPlugin.zip from LINK \n * unzip the MapPlugin.zip to !!\"...YOUR_ONTOWIKI_DIRECTORY/Plugins/\"!!\n * rename the !!config.ini-dist!! into !!config.ini!! in the !!\"...YOUR_ONTOWIKI_DIRECTORY/Plugins/MapPlugin\"!! folder.\n * login as admin and click on any knowledge base in your OntoWiki and then click on the map tabulator to auto-import the MapPlugin ontology (default settings) and activate the MapPlugin. Maybe you need to refresh your browser to see the MapPlugin ontology.\n\n====Validate the installation====\nYou can test the installation by choosing the MapPlugin knowledge base and clicking on the \"Check-Install\" class. When you click the map tabulator you see a marker with a checkmark-icon labeled \"installation succesful!\". This test could be helpful if your existing ontologies do not have geo coordinates (and no attributes which could be used for geocoding), and you will check the MapPlugins functionality for future uses.\n\n\n===Using the MapView===\n====What is shown?====\nEverytime you click on the map tabulator the current selection will be represented in the mapview.\nInstances which possesses latitude and longitude values will be represented directly by these attributes. For instances without geo coordinates the MapPlugin tries to ascertain longitude and latitude by geocoding. There are three different marker types per default. One for a single instance, one for clustered instances (for more informations about clustering, look at //\"Customize your MapPlugin\"//) and in another way representation of the instance by an existing depiction icon.\n\nWhat ever you want to locate on the map, if it is educible the MapPlugin makes it visible.\n\n====How to navigate?====\nThe mapview-layout is adopted from OpenLayers. To navigate through the map you can easily use the control buttons given by OpenLayers (at the left side in the mapwindow) or alternatively you can drag the map with the mouse and zoom in and out with your mousewheel. \n\nExtending the windowsize vertical is possible by using the arrowbuttons at the right bottom. Horizontal you can adjust the frame by using your mouse.\n\n====Save a mapview====\nTo save or share the current mapview, click on !!\"Permalink\"!! at the right bottom of the map. The URI will be extended by latitude, longitude, zoomlevel and the used layer. Now you can save the link in your bookmarks or share it with someone.\n\n((http://pcai042.informatik.uni-leipzig.de/~swp08-5/screenshots/open_layer_use.png))\n\n===Customize your MapPlugin===\n====Different map provider====\nChanging the map provider is offered by the !!\"+\"!! symbol at the right border (in the mapwindow), if you click it a menu will appear, where you can choose another map provider.\n\n====Customize your icons====\nYou can customize the icons used to represent a class.\nTo set an icon follow these few steps:\n * make sure you are logged in as admin\n * choose the MapPlugin knowledge base\n * choose \"Create Instance\" from the drop down menu at the \"default\" class \n * enter the name of the class which should be customized as label\n * type the URI of the class into the \"Identifier (URI)\" field (you can get the URI from the class by checking the edit options at the specific class, if the URI is unknown to you)\n * add a new property named logo and select ressource\n * specify the logo by the URL to the icon of your choice\n * finish your customization by clicking \"Submit Values\"\n * enjoy the new icon\n\n((http://pcai042.informatik.uni-leipzig.de/~swp08-5/screenshots/config_icons.png))\n\n((http://pcai042.informatik.uni-leipzig.de/~swp08-5/screencast/custom%20icon/custom_icon.htm Check out our screencast.))\n\n====Define the clustering====\nAfter clicking on the \"more options\" button on the right bottom of the mapwindow, the cluster settings appear below the mapwindow. Here you can enable or disable the clustering with the checkbox. For a finer control you can assign the grid count and the maximum amount of allowed markers per grid element. The grid count devides the map into serveral pieces (for example: grid count = 3 means 3 * 3 = 9 pieces). If there are more markers within one grid piece than the maximum markers, clustering will coalesce the markers for a clearly arrangement.\n\n\n===Team===\nNatanael Arndt\nNaranbaatar Avir\nRobert Frohl\nClaudius Henrichs\nEdgar Lensing\nSebastian Kiunke\nMarkus Nentwig\nNorman Radtke\nMatthias Schreiter\n" . . . . "2008-07-14T18:27:40"^^ . "==AKSW Schema Documentation==\nAKSW is maintaining a couple of RDF schema / OWL ontologies. This is the documentation part of these projects. All namespaces accept content negotiation for delivering RDF/XML documents. The default content type is (X)HTML.\n\n\n#|\n||http://ns.softwiki.de/req/|**S**oft**W**iki **O**ntology for **R**equirements **E**ngineering (SWORE)||\n||http://ns.ontowiki.net/SysOnt/|OntoWiki **Sys**tem **Ont**ology||\n||http://ns.aksw.org/e-learning/lectures/|**Lecture** **S**lides Ontology for Personal Knowledge Management||\n|#\n\nNote: To test correct delivery, try ##wget --header=\"Accept: application/rdf+xml\" namespace-uri##.\n\n{{tree}}\n" . . . . "2009-03-05T23:48:47"^^ . "==~SoftWiki Ontology for Requirements Engineering (SWORE)==\nNamespace: http://ns.softwiki.de/req/\n\n<#\n\n\n\n\n\n
    \nDownload SWORE (Version 1.02)\nDownload SWORE (Version 0.08)\n
    \n#>\n <# About the two Versions #>\n \n ((!/008 Version 0.8)) - published in [6], [7] and used in SoftWiki Prototype 1\n ((!/102 Version 1.02)) (current work) - extention for SoftWiki Prototype 2\n http://ns.softwiki.de/req/ provides this version\n\nThe following partners participated in the development: Dirk Fritsch, Jens Lehmann, Kim Lauenroth, Steffen Lohmann, Thomas Riechert and Sebastian Dietzold\n\nThe figure visualises the core of the RE ontology, which we developed in accordance with [2,3,4,5]. Central to our approach are the classes Stakeholder and Abstract Requirement as well as the properties details and defines. Abstract requirements have the subclasses Goal, Scenario, and Requirement, each of which are defined by stakeholders and can be detailed by other abstract requirements. This enables the specification of abstract requirements at different levels of granularity. We emphasise the collaborative aspects of requirements engineering by integrating discussions amongst the stakeholders and voting (with the criteria of agreement and importance) in the model. In the RE process this documentation is often relevant for future decisions.\n\nhttp://powl.svn.sourceforge.net/viewvc/powl/trunk/models/SWORE/swore800.png\n\n===References===\n\n[1] Sören Auer, Klaus-Peter Fähnrich, and Thomas Riechert. ((http://softwiki.de/HomePage SoftWiki)) – Agiles Requirements-Engineering fur Softwareprojekte mit einer großen Anzahl verteilter Stakeholder. In ((http://softwiki.de/RequirementsOntology/files GeNeMe’ 06)) – Gemeinschaft in neuen Medien, 2006.\n\n[2] Peter Haumer, Klaus Pohl, and Klaus Weidenhaupt. Requirements elicitation and validation with real world scenes. IEEE Transactions on Software Engineering, 24(12):1036–1054, December 1998.\n\n[3] Klaus Pohl. Process-centered requirements engineering. Research Studies Press, Advanced Software Development, 1996.\n\n[4] Klaus Pohl: ((http://www.bibsonomy.org/bibtex/23d3fe69cfc985a731293a2051f688458/tausendeins Requirements Engineering)). Grundlagen, Prinzipien, Techniken. Dpunkt Verlag,2007.5. Axel van Lamsweerde. \n\n[5] Goal-oriented requirements engineering: A guided tour. In Fifth IEEE International Symposium on Requirements Engineering (RE’01), pages 249–263. IEEE Computer Society Press, August 2001\n\n[6] Riechert, T.; Lauenroth, K.; Lehmann, J.: SWORE - SoftWiki Ontology for Requirements Engineering. In: Auer, S.; Bizer, C.; Müller, C.; Zhdanova, A (Hrsg.) Proceedings of the First Conference on Social Semantic Web (CSSW 2007), SABRE. LNCS, 2007.\n\n[7] Riechert, T.; Lauenroth, K.; Lehmann, J.; Auer, S.: Towards Semantic based Requirements Engineering. In: Proceedings of the 7th Intl. Conference on Knowledge Management, I-KNOW’07, 5–7 September, Graz, Austria, 2007.\n" . . . . "2008-07-04T17:40:22"^^ . "==Events==\n{{tree}}" . . . . "2008-07-11T17:33:23"^^ . "==Lecture Slides Ontology for Personal Knowledge Management==\nNamespace: http://ns.aksw.org/e-learning/lectures/\n\n<#Download Ontology#>\n\n((http://powl.svn.sourceforge.net/svnroot/powl/trunk/models/e-learning/lectures.rdf lectures))\n\n===Use Case===\n((http://vorlesungen.ontowiki.net/ Lecture Slides (University Leipzig) )) (german)\n\n===Example Queries for RDF===\nhttp://ns.aksw.org/e-learning/lectures -> RDF of the ontology, HTML with ontology description\nhttp://ns.aksw.org/e-learning/lectures/ClassName -> RDF of the ontology, HTML class description\n\nhttp://aksw.org/schema/lectures/files?get=lectures_schema.gif\n\n{{a name=\"Slide\"}}\n===Calendar===\nThis is a docu section to a specific Class\nhttp://ns.aksw.org/e-learning/lectures/Calendar\n\n{{a name=\"Lecture\"}}\n===Lecture===\nThis is a docu section to a specific Class\nhttp://ns.aksw.org/e-learning/lectures/Lecture\n\n{{a name=\"Slide\"}}\n===Slide===\nThis is a docu section to a specific Class\nhttp://ns.aksw.org/e-learning/lectures/Slide\n\n{{a name=\"Tag\"}}\n===Tag===\nThis is a docu section to a specific Class\nhttp://ns.aksw.org/e-learning/lectures/Tag" . . . . "2010-07-05T17:04:19"^^ . " ATTENTION: THIS PAGE IS OUTDATED\n{{Include page=\"/Projects/OntoWiki/Menu\" divclass=\"floatbox\" nomark=\"1\"}}\n==Syn PKM Plugin==\n\nThe OntoWiki Syn PKM Plugin was developed during the software engeneering practical training at the university of Leipzig by a group of 8 students. Our intention was to produce a plugin for easy access to personal ontologies. \n\n((http://pcai042.informatik.uni-leipzig.de/~swp08-4/ Project Homepage))\n\n((http://ontowiki.net/Projects/OntoWiki/Plugins/synPKM/files?get=synpkmfinal.rar Download the Plugin))\n\n===Releated Ontology Schema===\n\n((http://ontowiki.net/Projects/OntoWiki/Plugins/synPKM/files?get=synpkm.rdf http://ns.aksw.org/pkm/))\n((http://ontowiki.net/Projects/OntoWiki/Plugins/synPKM/files?get=config.rdf http://ns.aksw.org/pkm/config/))\n((http://ontowiki.net/Projects/OntoWiki/Plugins/synPKM/files?get=contact.rdf http://ns.aksw.org/pkm/contact/))\n((http://ontowiki.net/Projects/OntoWiki/Plugins/synPKM/files?get=calendar.rdf http://ns.aksw.org/pkm/calendar/))\n((http://ontowiki.net/Projects/OntoWiki/Plugins/synPKM/files?get=annotation.rdf http://ns.aksw.org/pkm/annotation/))\n\n\n===Installing the MapPlugin===\n\n((!/Installation)) (german)\n((!/Ontologien)) (german)\n===Team===\nAndreas Weise\nChristian Petzold\nJan Engelhardt\nRobert Wieczoreck\nRick Hegewald\nAnthony Volkmann\nAntonia Siegert\nDavid Pansch\n" . . . . "2010-07-05T17:04:36"^^ . " ATTENTION: THIS PAGE IS OUTDATED\n\n\n!! Ein Kreuz hinter einer Klasse oder Property bedeutet, daß diese Bestandteile möglichst zuerst implementiert werden sollen. Kein Kreuz bedeutet nicht, daß dies bei den jeweiligen Klassen/Properties nie geschieht, sondern nur, daß es wahrscheinlich später gemacht werden soll. Die Ontologie in rdf-Form unterscheidet sich von den hier angegebenen Komponenten insofern, daß in den Wissensbasen jeweils noch Klassen und Properties drin sind, die nur auf Wunsch unserer allseits geehrten spirituellen Führer und Lenker Darth Riechert und seinem Sith-Apprentice Haschek in der Ontologie enthalten sind, jedoch nach derzeitigem Stand NICHT (nie) implementiert bzw. gespeichert werden. !!\n\n Setup der Ontologien: \n\n1. Alle bisher vorhandenen SynPKM-Teil-und-Hauptontologien aus Ontowiki löschen.\n2. Über \"Create Knowledge Base\" Annotation, Calendar und Contact importieren, d.h. \"Upload from File\" und dann als Model URI \"http://ns.aksw.org/pkm/Annotation/\", \"http://ns.aksw.org/pkm/Calendar/\" und \"http://ns.aksw.org/pkm/Contact/\" eingeben.\n3. Dasselbe mit SynPKM-Ontologie machen. Model URI: \"http://ns.aksw.org/pkm/\".\n\nWichtig: Entgegen der vorherigen Version gibt es zwar noch die Teilontologien in rdf-Form (annotation.rdf...), jedoch haben diese bei in ihnen neu erstellten OWL-Klassen (wie z.B. \"Note\") keine eigenen URI mehr (d.h. nicht mehr http://ns.aksw.org/pkm/Annotation/Note, sondern nur noch http://ns.aksw.org/pkm/Note). Deswegen wurde unten jeweils aus &anno;Note u.ä. &synpkm;Note. \n\n\nEntities\n\n RDF\n OWL\n RDF-Schema\n XML-Schema\n Dublin Core\n\n Annotea Bookmark\n Redwood Tag Ontology\n RDF Calendar\n FOAF\n Geo\n VCard\n\n SynPKM Ontology\n SynPKM Annotation, Bookmarks, Tags\n SynPKM Calendar, Appointments\n SynPKM Contact, Address\n\n\n\nANNOTATION\n\n Klassen\n\n &synpkm;Note x\n &b;Bookmark x\n &rw;Tag x\n\n Properties\n\n &synpkm;annotates x \n &synpkm;notebody x\n &b;recalls x --> URL des Bookmarks\n &dc;title x --> Titel des Bookmarks \n &rw;name x\n &rw;isTagOf x\n &rw;taggedWithTag \n\nCALENDAR\n\n Klassen\n\n &synpkm;VCalendar x --> Kalenderklasse (da mehrere Kalender möglich sein sollen)\n &ical;Vevent x --> Termin\n &ical;Vtodo x --> Task\n\n Properties\n\n &dc;title x --> Name des Kalenders\n &synpkm;eventInCal x --> Event ist in angegebenem Kalender gespeichert\n &ical;dtstart x --> Terminstart\n &ical;dtend x --> Terminende\n &ical;description x --> Beschreibung des Termins\n &ical;summary x --> im Prinzip Betitelung des Termins (z.B. \"Ontowikisux Conference 08\")\n &ical;due x --> Deadline\n &ical;priority x\n\nCONTACT\n\n Klassen\n\n &foaf;Person x\n &foaf;Organization\n &foaf;Image\n &vcard;VCard x\n &vcard;Name x\n &vcard;Organization\n &vcard;Address x\n &vcard;Location\n &geo;SpatialThing --> generell: gegenständliches Objekt\n &geo;Point\n\n Properties\n \n &foaf;depiction --> Bild der Person\n &foaf;birthday x\n &foaf;mbox x --> eMail\n &foaf;jabberID\n &foaf;icqID\n &foaf;aimChatID\n &foaf;yahooChatID\n &foaf;msnChatID\n &foaf;phone x\n &foaf;weblog\n &foaf;familyName x\n &foaf;firstName x\n &foaf;nickname \n &foaf;based_near --> Ort (Heimat, Arbeit ..., je nachdem)\n &foaf;workInfoHomepage --> Homepage, die seine genaue Stellung auf Arbeit beschreibt, nicht die Firma an sich (eigene property vorhanden)\n &foaf;gender --> Geschlecht\n &foaf;depicts --> Image zugewiesen, wen (oder was) zeigt das Bild?\n &geo;alt --> Altitude (Höhe)\n &geo;lat --> Latitude (Breitengrad)\n &geo;long --> Longitude (Längengrad)\n &vcard;fn x --> formatted Name (z.B. \"Thomas Haschke\" oder \"Riechert, Michael\")\n &vcard;nickname\n &vcard;email x\n &vcard;workEmail \n &vcard;tel \n &vcard;workTel \n &vcard;homeTel x\n &vcard;mobileTel \n &vcard;fax\n &vcard;adr\n &vcard;homeAdr x\n &vcard;workAdr \n &vcard;org\n &vcard;n x --> Name (Vor- bzw. Nachname, beides möglich)\n &vcard;geo --> siehe based_near\n &vcard;photo\n &vcard;organization-name\n &vcard;country-name x\n &vcard;label --> formattierte Adresse, d.h. wie sieht die Adresse aus, wenn ich sie ausdrucke (die gesamte)\n &vcard;locality x --> Ort\n &vcard;postal-code x\n &vcard;region\n &vcard;street-address x\n &vcard;bday x\n &synpkm;associatedVCard --> semantische Verbindung von foaf-Person zur zugehörigen VCard" . . . . "2010-07-05T17:04:48"^^ . " ATTENTION: THIS PAGE IS OUTDATED\n\n\nUm das Plugin nutzen zu können, müssen vier Teilontologien in OntoWiki importiert \nund eine Gesamtontolologie erstellt werden (dafür sind Administrator-Rechte in OntoWiki nötig).\n\ni) Teilontologien importieren\n Die Teilontologien befinden sich in einzelnen Dateien im Unterordner 'Setup': 'annotation.rdf', 'calendar.rdf' und 'contact.rdf'.\n Für jede dieser Dateien sind folgende Schritte durchzuführen:\n Öffnen Sie das Menü zur Erstellung neuer Knowledge Bases, wählen Sie 'Upload From File'.\n Geben Sie 'http://ns.aksw.org/pkm/Annotation/' für annotation.rdf \n bzw. 'http://ns.aksw.org/pkm/Calendar/' für calendar.rdf \n bzw. 'http://ns.aksw.org/pkm/Contact/' für contact.rdf\n bzw. 'http://ns.aksw.org/pkm/Config/' für config.rdf\n als ModelUri an. \n Klicken Sie auf 'Durchsuchen' und wählen Sie die jeweils passende Datei.\n Schließen Sie die Erstellung durch einen Klick auf den Button 'Create Knowledge Base' ab.\n\n Alternativ können die rdf-Files über 'Import From the Web' auch direkt aus dem Web importiert werden. Die zugehörigen URL ist:\n 'http://pcai042.informatik.uni-leipzig.de/~swp08-4/kb/annotation.rdf', für die Ontologie Annotation, die ModelUri ist wie oben. Für die anderen Ontologien kann dies analog angewendet werden. \n \n\nii) Gesamtontologie erstellen\n Im Setup-Ordner befindet sich neben den Teilontologien auch die Datei 'synpkm.rdf'.\n In dieser wird eine Ontologie definiert, die die Teilontologien importiert.\n Dies ist die Ontologie, in der letzten Endes Ihre Daten gespeichert werden sollen.\n Erstellt wird sie analog zu den Teilontologien. Dabei ist standardmäßig die URI 'http://ns.aksw.org/pkm/' zu verwenden.\n Wenn Sie eine andere URI nutzen möchten, ist eine Anpassung innerhalb der Datei nötig: Die XML-Base und die URI der Ontologie müssen verändert werden.\n Außerdem muss in diesem Fall beim Import in OntoWiki die veränderte URI der Ontologie als ModelUri angegeben werden.\n Beispielhaft ist dies in der Datei 'synpkm2.rdf' zu sehen.\n \n Diese Ontologie kann wie unter Teilontologien bereits beschrieben ebenfalls über ' Import From the Web' eingebunden werden.\n\nNach korrekter Erstellung der Wissensbasen in OntoWiki kann das Plugin in der config.ini auf 'on' gestellt werden.\nDie Gesamtontologie kann nun mittels 'Set Knowledge Base' ausgewählt werden.\n\n" . . . . "2008-07-24T10:44:53"^^ . "==SWORE Version 0.8==\n\n ((.. SoftWiki Ontology for Requirements Engineering - SWORE))\n \n<#\nDownload SWORE (Version 0.08)\n#>\n\nThe following partners participated in the development: Dirk Fritsch, Jens Lehmann, Kim Lauenroth, Steffen Lohmann, Thomas Riechert and Sebastian Dietzold\n\nThe figure visualises the core of the RE ontology, which we developed in accordance with [2,3,4,5]. Central to our approach are the classes Stakeholder and Abstract Requirement as well as the properties details and defines. Abstract requirements have the subclasses Goal, Scenario, and Requirement, each of which are defined by stakeholders and can be detailed by other abstract requirements. This enables the specification of abstract requirements at different levels of granularity. We emphasise the collaborative aspects of requirements engineering by integrating discussions amongst the stakeholders and voting (with the criteria of agreement and importance) in the model. In the RE process this documentation is often relevant for future decisions.\n\nhttp://aksw.org/schema/SWORE/008/files?get=swore0.08.gif \n\n===References===\n\n[1] Sören Auer, Klaus-Peter Fähnrich, and Thomas Riechert. ((http://softwiki.de/HomePage SoftWiki)) – Agiles Requirements-Engineering fur Softwareprojekte mit einer großen Anzahl verteilter Stakeholder. In ((http://softwiki.de/RequirementsOntology/files GeNeMe’ 06)) – Gemeinschaft in neuen Medien, 2006.\n\n[2] Peter Haumer, Klaus Pohl, and Klaus Weidenhaupt. Requirements elicitation and validation with real world scenes. IEEE Transactions on Software Engineering, 24(12):1036–1054, December 1998.\n\n[3] Klaus Pohl. Process-centered requirements engineering. Research Studies Press, Advanced Software Development, 1996.\n\n[4] Klaus Pohl: ((http://www.bibsonomy.org/bibtex/23d3fe69cfc985a731293a2051f688458/tausendeins Requirements Engineering)). Grundlagen, Prinzipien, Techniken. Dpunkt Verlag,2007.5. Axel van Lamsweerde. \n\n[5] Goal-oriented requirements engineering: A guided tour. In Fifth IEEE International Symposium on Requirements Engineering (RE’01), pages 249–263. IEEE Computer Society Press, August 2001\n" . . . . "2008-07-24T08:51:22"^^ . "This is an alternative approach:\n\n 1. Make sure you have Java 6 and Eclipse installed. \n 2. Install the ((http://subclipse.tigris.org/ Subclipse Plugin)) for Subversion support.\n 3. Checkout the project manually via commandline interface or an SVN GUI tool into an Eclipse workspace folder (e.g. workspace/DL-Learner-SVN)\n 4. Repository Location: http://dl-learner.svn.sourceforge.net/svnroot/dl-learner/trunk\n 5. for developers use https://dl-learner.svn.sourceforge.net/svnroot/dl-learner/trunk\n 6. Create a new java project in eclipse and name the project like the folder above, e.g. \"DL-Learner-SVN\"\n 7. Eclipse will try automatically to determine the setup correctly, which will hopefully succeed.\n 8. right-click on the Project, then \"Team\", the \"share Project\"\n 9. Go to \"Project\" >> \"Properties\" >> \"Java Compiler\" >> \"Compiler Compliance Level\" and set it to 6.0. (Previous compiler levels will report errors.)" . . . . "2008-08-13T10:30:38"^^ . "{{Include page=\"/Projects/DLLearner/Menu\" divclass=\"floatbox\" nomark=\"1\"}}\n==DL-Learner Code Style==\n\nCurrently, we use checkstyle and PMD to test our code style. Here is a quick tutorial to **use checkstyle on DL-Learner in Eclipse**:\n * ((http://dl-learner.org/wiki/Eclipse checkout DL-Learner in Eclipse))\n * ((http://eclipse-cs.sourceforge.net/ install the Eclipse checkstyle plugin)) - see the update below\n * go to \"window\" >> \"preferences\" >> \"checkstyle\" (or \"project\" >> \"properties\" >> checkstyle\") and specify doc/checkstyle.xml in your DL-Learner directory as external configuration file for checkstyle (this file contains the rules we consider useful for DL-Learner)\n * in Eclipse package explorer right click, go to checkstyle and let you show checkstyle warnings\n * go to package org.dllearner.parser and disable checkstyle warnings there (the parser is automatically generated, i.e. we cannot change its code style)\n\nIf you violate any of the checkstyle rules, this will be shown as Eclipse warning. You can also run checkstype on single packages or classes.\n\nSome of the **enabled rules** are:\n * missing Javadoc for public/protected methods shown\n * incomplete Javadoc reported\n * checks whether licence header is present\n * parameters separated by comma and space\n * curly brackets on same line\n\n**Open issues / Best Practice**:\n * @Override: checkstyle claims that Javadoc is missing, but in fact such methods do not need to be documented (the documentation is copied over from the interface or super class); workaround: add an additional /** {@inheritDoc} */ to such methods -- Javadoc should never be duplicated\n * Delegate methods: Unfortunately, there seems to be no nice way to document delegate methods. The best thing to do at the moment seems to include a shortened version of the method we delegate to.\n * Convenience methods with incomplete parameters: Often, you have several convenience methods, e.g. method(int) may call method(int,String,int) by just using defaults for the last two parameters. There seems to be no nice way to document this. As best practice, the most complex method (including the actual implementation) should be documented in detail, whereas the other methods should include a copied or shortened version of the Javadoc.\n\nLet us know if there are further issues.\n\n**Update:** Checkstyle 5.0beta solves the @Override problem (and possibly others specific Java 5 or higher). It is recommended to install it, instead of the previous version. To to this, go to https://sourceforge.net/project/showfiles.php?group_id=80344, download it and extract it in your source folder. (If you have a previous version of checkstyle, make sure you uninstalled it first.) \n\n**Differences between Checkstyle 4 and 5:** In doc/checkstyle.xml you need to rename ~JavadocPackage to ~PackageHtml if you use Checkstyle 4." . . . . "2008-10-06T21:22:40"^^ . "{{toc divclass=\"floatbox\"}}\n===xOperator SWC 2008 instructions===\n\n((http://aksw.org/Projects/xOperator?v=wzs xOperator)) participates at the ISWC ((http://challenge.semanticweb.org/ Semantic Web Challenge 2008)).\nThere are two ways how to use or test the current release of the xOperator:\n 1. Demonstration with the Test Account on Meebo.com \n 2. Installing the xOperator on your local machine\n\n====Demonstration with the Test Account====\n<#
    #>{{Include page=\"/Projects/xOperator/SWC2008/Screenshots\" nomark=1}} <#
    #>\nAs the xOperator uses Instant Messaging for communication with the user, it is necessary to connect via XMPP (Jabber) to xmpp:joerg.tester@aksw.org.\nThis connection can be established with the online web interface from Meebo:\n 1. Log into the jabber account **joerg.tester@aksw.org** and password **test123**.\n 2. Using the ((http://meebo.com meebo.com)) account **joerg.tester** with password **test123**. You find a predefined jabber connection there.\n\nBoth possibilities can be seen in figure 1. You can also use your favorite Jabber client. (Please use the userdata defined in the first Meebo possibility) \n\nWhen the connection is established you can interact with the agent by chatting with the contact \"My Agent\" (See figure 2 for example).\n\nFor a start you can say \"Hello\" to the xOperator and ask for \"Help\", or simply try the examples found in the paper on the one hand. On the other hand you can use the templates described below.\n\n====Querying with Templates====\nThe xOperator will list existing templates by typing \"templates\", alternatively you can try the ((Templates template list)).\n\n====Installation====\nThe second possibility to bring the xOperator to life is by downloading and installing it. Informations about downloading xOperator can be found here: ((http://aksw.org/Projects/Downloads?v=y4d#xOperator Download)). To get this tool installed please have a look at the ((http://aksw.org/Projects/xOperator/FirstSteps?v=fns First Steps Site))\n\n Note: As we hand out the credentials for the meebo account we hope nobody will vandalize it (for example deleting the xOperator ressource). We will check on the regular bases. You can also contact us by mail: ((mailto:unbehauen@informatik.uni-leipzig.de unbehauen@informatik.uni-leipzig.de))" . . . . "2010-07-08T11:14:47"^^ . "<#\n
    \n
    \n
    \n

    aLiDa : autosuggested Linked Data

    \n

    \n

    \nThe aim of the aLiDa project is to provide a quick and easy way to search for ressources \nin RDF graphs. A special feature is the facet based navigation through the result set, which enables extensive searches. aLiDa is mainly developed for OntoWiki.

    \n

    \n

    \n\n\n

    \n

    \n
    \n
    \n
    \n
    \n#>" . . . . "2008-10-10T16:35:40"^^ . "===xOperator templates===\n\nThis is the template overview section. Here is a list of templates with their patterns grouped by their usage scenario. For each template we will give some examples and screenshots.\n\nPlease click on images to enlarge.\n\nThe following technical usage scenario was deployed:\n<# #>\n\n====Scenario: Personal information management (iCal/FOAF/etc.)====\n\nPersonal information management appears to be a natural application for xOperator. People in our IM contact lists are usually those whose contact and calendar information we frequently need. Consequently, when people in our contact lists attach their iCAL calendars and FOAF profiles to xOperator we are easily able to query these:\n\n%%\nPattern: WHAT IS THE * OF *\nDescription: This pattern searches a attribute of the FOAF space and finds foaf:Person(s) related to it. (P2P querying, FOAF schema)\n\nExample: WHAT IS THE phone OF Sören\nExample: WHAT IS THE birthday OF Jörg\n%%\n\n\n====Scenario: DBpedia querying====\n{{a name=\"dbpedia\"}}\nA semantic search is available for DBpedia. It consists of two templates, which normally should be called consecutively.\nThe first question asked is of the form ''What is a *'', which provides answers for available categories for the search term. The second question is ''Tell me more about * the * '', which provides a precise answer for a typed search term. Note that in spite of the simplicity of these templates, it already provides a more semantic search than mere keyword mappings as Google does. For example, if a user is searching for a certain chinatown festival, he can first ask ''What is a chinatown'' and will be presented the following answer: \n\na/an chinatown might be one of the following: \nenclave, musical, musical comedy, musical theater, film, attraction in Hyōgo Prefecture, chinatown, album, record album, building and structures in Vancouver, station, landmark, film directed by William A. Wellman, flick, motion picture, motion-picture show, movie, moving picture, moving-picture show, pic, picture, picture show, festival in the United States, festival in New York City, festival, pageant, superhero, american, play, neighborhood of Yokohama\nThe user can then ask ''Tell me more about chinatown the festival'' and he will be presented precise answers, not just merely a list with links where he has to pick one for himself.\n\n%%\nPattern: WHAT IS A * \nDescription: Queries DBpedia and searches concepts matching the asterisk.\n\nExample1: What is a chinatown\n%%\n%%\nPattern: TELL ME MORE ABOUT * THE * \nDescription: Queries DBpedia and Searches information for an individual (first asterisk), which belongs to a certain category (second asterisk)\n\nExample2: Tell me more about chinatown the festival\n%%\n=====Screenshots of running this examples for the templates=====\n<# \n\n\n
    \n#>\n\n\n((#dbpedia Click here to read why this search is in some ways better than Googles keyword mappings.))\n" . . . . "2008-10-06T16:10:27"^^ . "===RDF Converters===\nThis page contains a list of RDF Converters. Some of them were used for the xOperator test plattform for the ISWC Semantic Web Challenge\n\n\n====Foaf Converters Generators====\n * Facebook Foaf Generator by Matthew Rowe ((http://ext.dcs.shef.ac.uk/~u0057/FoafGenerator/index.php?auth_token=ff8770c1590e51e30676ffde849b0aed Application Page))\n\n\n==== BibTeX Converters ====\n * ((http://www.cs.vu.nl/~mcaklein/bib2rdf/ Online Translation))" . . . . "2008-10-06T20:53:59"^^ . "<#     #>\n**Fig1. Meebo Login Screen**\n\n\n\n<# #>\n**Fig2. Meboo with messaging to MyAgent**\n" . . . . "2008-10-22T17:50:08"^^ . "{{Include page=\"/Projects/LectureWiki/Teaser\" nomark=\"1\"}}\n\n===Overview=== {{a name=\"Overview\"}}\nLecture Wiki provides lecture slides as RDF data in conjunction with OntoWiki and the SynPKM Plugin. The project aims to provide the possibility for self and collaborated structuring of e-learning resources.\n\n===News==={{a name=\"News\"}}\nThis winter semester (2008/2009) Prof. Fähnrich’s lecture on Software Engineering became the first lecture completely provided. The language of this lecture is German. ((!/BIS (more) ))\n\n\n===Publications==={{a name=\"Publications\"}}\nT.Riechert, T.Berger: Persönliche semantische Strukturierung und Annotierung von Lernmaterialien. In: U. Lucke, M.C. Kindsmüller, S. Fischer, M. Herczeg, S. Seehusen (Hrsg.): Workshop Proceedings der Tagungen Mensch und Computer 2008, DeLFI 2008, und Cognitive Design 2008 in Lübeck, Logos Verlag Berlin 2008, S. 317 - 321, ISBN 978-3-8325-2007-6\n\n((http://thomas-riechert.de/documents/publications/riechert_berger_delfiws_2008.pdf Paper)) ((http://thomas-riechert.de/documents/talks/talk_riechert_berger_delfiws_2008.pdf Talk)) (german)\n\nS. Lohmann, T. Riechert und J. Fienhold: Netzwerkeffekte, Dynamik und Feedback durch die Integration von Social Tagging in E-Learning-Umgebungen. In C. Rensing, G. Rößling (Hrsg.): Proceedings der Pre-Conference Workshops der 5. e-Learning Fachtagung Informatik - DeLFI 2007, S. 27-34, 2007" . . . . "2008-10-22T18:32:20"^^ . "{{Include page=\"/Projects/LectureWiki/Teaser\" nomark=\"1\"}}\n\n===Installation des Lecture Wikis für Vorlesungen der Abteilung Betriebliche Informationssysteme===\n\nDas Wiki ist unter ((http://vorlesungen.ontowiki.net)) installiert.\n\n===Benutzung ohne Einloggen===\nIhnen stehen folgende drei Wissensbasen zur Verfügung:\nhttp://ontowiki.net/Projects/LectureWiki/BIS/files?get=wissensbasen.jpg\n\n * **Modell für Vorlesungsskripte** ((http://vorlesungen.ontowiki.net/model/export/?m=http%3A%2F%2Fns.aksw.org%2Fe-learning%2Flectures%2F&output=xml http://ns.aks.org/e-learning/Lectures/)); ((http://vorlesungen.ontowiki.net/model/info/?m=http%3A%2F%2Fns.aksw.org%2Fe-learning%2Flectures%2F Lecture Wiki)) \n * Diese Modell beschreibt die grundlegende Datenstruktur wie folgt:\n * http://ontowiki.net/Projects/LectureWiki/BIS/files?get=ontologieschema.jpg\n\n * **Ontologie der Vorlesung Software Engineering** ((http://vorlesungen.ontowiki.net/swt/)); ((http://vorlesungen.ontowiki.net/model/info/?m=http%3A%2F%2Fvorlesungen.ontowiki.net%2Fswt%2F Lecture Wiki))\n * Diese Ontologie repräsentiert die Vorlesungsskripte. Sie wird durch die Dozenten und Tutoren der Vorlesung editiert. Der Nutzer des Wikis kann diese lediglich lesen. \n\n * **Wiki der Vorlesung Software Engineering** ((http://vorlesungen.ontowiki.net/all/)); ((http://vorlesungen.ontowiki.net/model/info/?m=http%3A%2F%2Fvorlesungen.ontowiki.net%2Fall%2F Lecture Wiki))\n * Nach ihrer Registrierung können alle Nutzer des Lecture Wiki diese editieren. Sie bildet daher das Wiki.\n\n===User Registrierung===\nhttp://ontowiki.net/Projects/LectureWiki/BIS/files?get=register_new_user.jpg\nDerzeit ist die Applikation so konfiguriert, dass jeder Nutzer sich selbst registrieren kann. \n\n\n===Einloggen===\nhttp://ontowiki.net/Projects/LectureWiki/BIS/files?get=login.jpg\nBeachten Sie beim Einloggen, dass der Benutzername //case-sensitive// ist.\n\n===Auswahl des Wiki's===\nhttp://ontowiki.net/Projects/LectureWiki/BIS/files?get=auswahl_lecture_wiki.jpg\n\n===Auswahl der Vorlesungen als Unterklassen von Folien (slides)===\nhttp://ontowiki.net/Projects/LectureWiki/BIS/files?get=auswahl_subclass_planungsphase.jpg\n\nAnschließend werden im Hauptfenster alle Folien aufgelistet. Sie können zusätzlich noch Attribute, z. B. das Bild der Folie einblenden.\nhttp://ontowiki.net/Projects/LectureWiki/BIS/files?get=eigenschaften_anzeigen.jpg\n\n===Anzeige einer Folie===\nDuch Klicken auf den Titel der Folie wählen Sie die Instanz der Klasse //slide// aus.\nhttp://ontowiki.net/Projects/LectureWiki/BIS/files?get=folie_haus_der_swt.jpg\n\n===Navigieren zwischen den Folien===\nDas Navigieren durch die Folien ist einfach. Sie können durch Klicken auf den Titel zur vorherigen oder folgenden Folie wechseln.\n\n===Editieren===\nZum Editieren muss der Inline-Edit Modus aktiviert werden. \nhttp://ontowiki.net/Projects/LectureWiki/BIS/files?get=enable_inline_editing.jpg Sie können nun Eigenschaften ändern http://ontowiki.net/Projects/LectureWiki/BIS/files?get=bearbeiten.gif und hinzufügen\nhttp://ontowiki.net/Projects/LectureWiki/BIS/files?get=addproperty.jpg.\n\n===Hinzufügen von Eigenschaften===\nSie erhalten Vorschläge bei der EIngabe definerter Eigenschaften und Beziehungen. Es ist aber auch möglich eigene Eigenschaften neu zu definieren. http://ontowiki.net/Projects/LectureWiki/BIS/files?get=tag.jpg\n\n" . . . . "2008-10-22T14:47:38"^^ . "<#\n
    \n

    Lecture Wiki

    \n\"Lecture\n

    Lecture Wiki provides lecture slides as RDF data in conjunction with OntoWiki and the SynPKM Plugin. The project aims to provide the possibility for self and collaborated structuring of e-learning resources.

    \n

    Go to Lecture Wiki installation for the Software Engineering lecture (german)

    \n
    \n
    \n{{Include page=\"/Projects/LectureWiki/Menu\" nomark=\"1\"}}\n
    \n
    \n#>" . . . . "2008-10-22T14:26:25"^^ . "{{Include page=\"/Projects/LectureWiki/Teaser\" nomark=\"1\"}}\n\n\n===Lecture Wiki Screenshots===\n\nhttp://ontowiki.net/Projects/LectureWiki/files?get=screenshot_lecture_wiki.jpg" . . . . "2008-10-22T14:48:16"^^ . " 1. About\n - ((/Projects/LectureWiki#Overview Overview))\n - ((/Projects/LectureWiki#News News))\n - ((/Projects/LectureWiki#Publications Publications))\n 2. Features\n - ((/Projects/LectureWiki/Features Features))\n - ((/Projects/LectureWiki/Screenshots Screenshots))\n 3. Get started\n 4. Installations\n - ((/Projects/LectureWiki/BIS Uni Leipzig )) (german)\n" . . . . "2012-04-29T21:57:08"^^ . "{{Include page=\"/Projects/DLLearner/Menu\" divclass=\"floatbox\" nomark=\"1\"}}\n==Protégé DL-Learner Plugin==\n\nThe Protégé 4 DL-Learner plugin allows to learn equivalence and super class axioms based on the instance data in the ontologies loaded in Protégé. It integrates seamlessly in Protégé. \n\nYou can either ((https://sourceforge.net/projects/dl-learner/files/Protege%20DL-Learner%20Plugin/ download)) the plugin or install directly from Protégé 4 itself: Go to \"File\" => \"Preferences\" => \"Plugins\", click on \"Check for Downloads\" and select the DL-Learner plugin.\n\nThe following screen cast shows how to activate the plugin in Protégé and use it:\n**((http://dl-learner.org/files/screencast/protege/screencast.htm View Screencast))**\n\nThe plugin was created by Lorenz Bühmann, Christian Kötteritzsch and Jens Lehmann. If you have any questions or comments, please contact ((http://jens-lehmann.org me)).\n\n====Features====\n * learns definition and super class axioms based on existing instance data in an ontology\n * seamless integration through use of Protégé 4 plugin mechanism\n * based on DL-Learner Machine Learning framework to generate suggestions\n * use of efficient and sophisticated machine learning algorithms\n * can handle cases where an ontology is already damaged, i.e. adding the desired axiom renders the ontology inconsistent - in this case it displays the instances causing inconsistency\n\n====~ChangeLog====\n * Version 0.7 (April 2012):\n * made plugin Protege 4.2 compliant\n * source code improvements\n * Version 0.6 (March 2010):\n * fixed bug, which caused inconsistency not to be shown (suggestions were sometimes not highlighted in red even if they lead to an inconsistent ontology)\n * allow fine-grained selection of language features to use (negation, quantifiers, cardinality restrictions)\n * display minimum and maximum length of searched expressions (this allows to users to adapt the algorithm runtime to their needs and gives an impression of the complexity of searched expressions within the time limit) \n * Version 0.5.2 (May 2009):\n * fixed bugs #2790483 and #2791135, corrected manifest file, ensured Java 5 compatibility\n * Version 0.5.1 (April 2009):\n * corrected display of suggested class expressions; message when learning algorithm is still running\n * Version 0.5 (April 2009):\n * better integration in Protege (thanks to Nick Drummond for his support)\n * switch from general machine learning algorithm to special purpose algorithm for definitions and super class axioms\n * better performance through stochastic coverage testing procedures in machine learning algorithm\n * visualisation of learned results in Protege to simplify the decision whether to add the axiom for the knowledge engineer \n * Version 0.1 (December 2009): initial release\n\nScreenshot:\nhttp://dl-learner.org/Projects/DLLearner/ProtegePlugin/files?get=protege_plugin.png\n\nSee also the ((http://protegewiki.stanford.edu/index.php/DL-Learner DL-Learner page)) in the Protege wiki.\n" . . . . "2010-12-27T10:32:57"^^ . "==~OntoWiki FP7 - Project Kick-off meeting==\n{{ToC}}\n\n===General Information===\n\nVenue:\n December 2nd and 3rd: ((http://www.mml-leipzig.de/index.php?id=38&L=1 Mediencampus Villa Ida))\n December 4th and 5th: ((http://bis.informatik.uni-leipzig.de Johannisgasse 26))\n \nHotel: ((http://www.hotel-vivaldi.de Vivaldi))\n\n((http://maps.google.com/maps?f=d&saddr=Poetenweg,+Gohlis-S%C3%BCd+04155+Leipzig,+Leipzig,+Saxony,+Germany&daddr=Wittenberger+Stra%C3%9Fe+87,+04129+Leipzig,+Germany&hl=en&geocode=&mra=pe&mrcr=0&sll=51.371686,12.333535&sspn=0.061726,0.204105&ie=UTF8&z=15 Directions))\n\n===Participants===\n\n* **EU**: Iphigenia Pottaki (2.12.-3.12.)\n* **Punkt**: Kurt Moser (2.12.-5.12.), Thomas Schandl (2.12.-05.12.), Andreas Blumauer (2.12.-3.12.)\n* **OpenLink**: Orri Erling (2.12.-4.12.), Yrjänä Rankka (2.12.-4.12.)\n* **B2**: David Rozman (2.12.-3.12.), Tomaz Mlakar (2.12.-5.12.)\n* **BI**: Jürgen Schubert, Tobias Gruß\n* **CUAS**: Danilo Garbi Zutin (2.12.-5.12.), Christian Maier (2.12.-5.12.), Michael Niederstätter (2.12.-5.12.), Michael Auer (2.12.-3.12.)\n* **Uni Leipzig/~InfAI/AKSW**: Klaus-Peter Fähnrich, Sören Auer, Sebastian Dietzold, Jens Lehmann, Michael Martin, Sebastian Hellmann, Jörg Unbehauen, Norman Heino, Philipp Frischmuth (only friday), Julian Jöris, Christoph Riess, Sebastian Schreiter\n\n===Agenda===\n\nTelephone during the workshop contact: +49(1522)6230601 \n\n====TUESDAY, DECEMBER 2nd, 2008====\n * 11:00-12:30 Welcome reception, light lunch buffet\n * 12:30-13:00 **Welcome address and introduction Universität Leipzig** (Klaus-Peter Fähnrich - Chair Business Information Systems)\n * 13:00-13:30 **((http://aksw.org/Events/2009/OntoWikiKickOff/files?get=project_overview.pdf Project Overview))** (Sören Auer - Head AKSW, Universität Leipzig/InFAI)\n * 13:30-15:30 **Partner Introductions**\n * FH Kärnten, Michael Auer (Head Center of Competence Online Labs and Open Learning)\n * ~OpenLink Ltd., Orri Erling (Virtuoso Program Manager) ((http://www.slideshare.net/rumito/virtuoso-universal-server-overview-presentation slides))\n * ((http://ontowiki.net/Events/2009/OntoWikiKickOff/files?get=punkt_gesamt.pdf PUNKT.NetServices)), Andreas Blumauer (CEO)\n * B2 d.o.o., David Rozman (General Manager)\n * Business Intelligence, Tobias Gruß \n * Vakantieland, Ceriel Jacobs (CEO)\n * 15:30-16:00 **Coffee Break**\n * 16:00-17:00 ((http://aksw.org/Events/2009/OntoWikiKickOff/files?get=kickoff_ontowiki_iphigenia_pottaki_.pdf Project monitoring and reporting)) (Iphigenia Pottaki - Project Officer European Commission)\n * 17:00-17:30 **QA**\n * 17:30 Transfer to Hotel Vivaldi\n * 20:00 **Social Event** - Short visit of the Christmas Market\n * 20:30 Uhr Dinner at Coffe Baum, Lehmann-Stube\n\n====WEDNESDAY, DECEMBER 3rd, 2008====\n * 9:00-10:00 **Workplan, Workpackages, Deliverables** (Sören Auer, AKSW/InfAI)\n * 10:00-10:30 **Coffee break**\n * 10:30-12:00 **Base technologies**\n * ((http://aksw.org/files/ontowikiintro.pdf OntoWiki Application Framework)) (Norman Heino, AKSW/InfAI)\n * Virtuoso Universal Server (Orri Erling, OpenLink)\n * 12:00-13:00 **Lunch at Gohliser Schlösschen**\n * 13:00-15:00 **Requirements, OntoWiki application scenarios and use cases**\n * ((http://aksw.org/Events/2009/OntoWikiKickOff/files?get=ontowiki_punkt.ppt Kurt Moser (PUNKT.NetServices)))\n * David Rozman (B2)\n * Tobias Gruß (BI Business Intelligence)\n * Ceriel Jacobs (Vakantieland)\n * 15:00-15:30 **Coffee**\n * 15:30-17:00 **Next steps, workpackage discussions, project infrastructure etc.**\n\n====THURSDAY, DECEMBER 4th, 2008 - Semantic Technologies Workshop====\n//Room 3-36//\n * 09:15 - 09:45 Topic: ((http://aksw.org/Events/2009/OntoWikiKickOff/files?get=shorthistoryandintroductiontothesemanticweb.pdf Short History and Introduction to the Semantic Web)) (Sebastian Dietzold)\n * 09:45 - 10:30 Topic: ((http://aksw.org/Events/2009/OntoWikiKickOff/files?get=resourcedescriptionframework.pdf RDF and its Serializations)) (Sebastian Hellmann)\n * 10:30 - 10:45 Coffee break\n * 10:45 - 11:30 Topic: ((http://aksw.org/Events/2009/OntoWikiKickOff/files?get=rdfs.pdf RDF Schema and Common Vocabularies)) (Jörg Unbehauen)\n * 11:30 - 12:15 Topic: ((http://aksw.org/Events/2009/OntoWikiKickOff/files?get=owl_dls.odp OWL (Web Ontology Language) and DLs (Description Logics))) (Jens Lehmann)\n * 12:15 - 13:15 Lunch\n * 13:15 - 14:00 Topic: ((http://aksw.org/Events/2009/OntoWikiKickOff/files?get=owl_dls.odp Reasoning and Learning in OWL and DLs)) (Jens Lehmann)\n * 14:00 - 14:45 Topic: ((http://aksw.org/Events/2009/OntoWikiKickOff/files?get=linkingandembeddingrdf.pdf Linking and Embedding RDF)) (Sebastian Dietzold)\n * 14:45 - 15:00 Coffee break\n * 15:00 - 15:45 Topic: ((http://aksw.org/Events/2009/OntoWikiKickOff/files?get=sparql.pdf SPARQL)) (Jörg Unbehauen)\n * 15:45 - 16:30 Topic: ((http://aksw.org/Events/2009/OntoWikiKickOff/files?get=toolsofthesemanticweb.pdf Tools for the Semantic Web)) (Michael Martin)\n * 16:30 - 17:00 Final discussion\n\nEvery topic is presented with a 30 min presentation and 15min discussion.\n\n====FRIDAY, DECEMBER 5th, 2008 - ~OntoWiki Application Development Workshop====\n//Room 3-36//\n * 09:00 - 09:30 Semantic ~MediaWiki & ~OpenReasearch (Sören Auer)\n * 09:30 - 10:00 ~OntoWiki Demo and Feature Description (Sebastian Dietzold)\n * 10:00 - 10:30 ((http://aksw.org/files/ontowikiextensiondevelopment.pdf Zend & OntoWiki Application Framework I)) (Norman Heino)\n * 10:30 - 10:45 Coffee break\n * 10:45 - 11:15 Zend & ~OntoWiki Application Framework II (Norman Heino)\n * 11:15 - 12:00 ((http://aksw.org/Events/2009/OntoWikiKickOff/files?get=erfurt_api.pdf The Erfurt API)) (Philipp Frischmuth)\n * 12:00 - 13:00 Lunch\n * 13:00 - 14:00 OntoWiki FP7 - Partner Use-Cases\n * 13:30 - 14:00 ((http://aksw.org/files/test_framework.pdf API and GUI Test Framework (Julian Jöris)))\n * 14:00 - 14:30 Issue Tracker / Subversion / Wiki / **First Installation** (all)\n" . . . . "2009-10-19T11:46:27"^^ . "{{Redirect page=\"/Groups/MOLE\"}}" . . . . "2009-11-16T13:32:37"^^ . "==Open Data @ Fakultät für Mathematik und Informatik der Universität Leipzig==\n==OD@FMI==\n\n===Ziele des Projekts===\n\nIm Rahmen des Projektes werden zukünftig alle verfügbaren Informationen zur den Lehrveranstaltungen (und in späteren Phasen darüber hinaus weiter Informationen) als Linked Opend Data zur Verfügung gestellt. Dies ermöglicht es den Studierenden eigene Applikationen zu entwickeln und zu nutzen, um diese Daten z.B. für Terminplanung etc. nutzen zu können. Die bestehende Informationen werden basierend auf einem semantischen datenbasierten Wiki. gesammelt und aktuell gehalten. An dem damit verbundenen kollaborativen Entwicklungsprozess werden nicht nur die Mitarbeiter der Fakultät sondern auch die Studierenden einbezogen.\n\n===Inhalte des Projektes===\n\nIm Rahmen des Projektes werden derzeit die Basisdaten und die Veranstaltungsplanung des WS 2009/10 und des folgenden Sommersemesters importiert. Es wurde eine ~OntoWiki-Plattform installiert.\n\n===Plattform===\nDie Daten sind innerhalb der Plattform http://od.fmi.uni-leipzig.de verfügbar. \n\n===Verwendete Vokabulare===\nIm Rahmen des des Projektes werden verschiedene Ontologien bearbeitet und veröffentlicht. Es werden zwei Basisvokabulare importiert. Für Informationen, die Semester-übergreifend sind, wurden extra Vokabulare angelegt. \n\n\nDie folgende Vokabulare beschreiben die Struktur der Daten. \n\n \n====Academic Institution Internal Structure Ontology (AIISO)====\n \n\n====Erweiterung des AIISO Vokabulars====\n \n\n===Basisdaten===\n\n====Lehrveranstaltungen der Fakultät====\n \n\n\n====Räume der Universität, die für Lehrveranstaltungen genutzt werden====\n \n\n====Mitarbeiter/innen der Fakultät====\n \n\n===Semesterdaten===\n\n====Wintersemester 2009/10====\n \n \n \n \n \n \n \n\n====Sommersemester 2010====\n \n \n \n \n \n \n \n\n===Meta-Daten===\n\nDie folgende Ontologie liefert Meta-Informationen, News, Blog und Webseiten über das Projekt. ALs Vokabular wird SIOC verwendet.\n\n \n \n \n \n " . . . . "2010-02-01T06:37:26"^^ . "==Workshop am 03.02.2010==\n\n===Teil 1 - Einführung und Grundlagen des Semantic Webs===\n\n * Einleitung und Ausblick\n * XML und URIs\n * Einfuehrung in RDF\n * RDF Schema\n\n===Teil 2 – Vorstellung ausgewählter Anwendungsfälle===\n\n * Professorenkatalog der Universität Leipzig\n * SoftWiki (aus Sicht des Semantic Webs)\n * DBpedia (Nutzung der Datenbasis, z.B. Finden von Beziehungen zwischen Einträgen)\n\n===Weitere Terminvorschläge===\n\nJeweils Mittwochs von 10-15 Uhr\n\n * 24.02.2010\n * 10.03.2010\n * 17.03.2010\n * 31.03.2010\n" . . . . "2010-02-01T16:04:24"^^ . "{{vcard name=\"sn\" value=\"Jänicke\"}}\n" . . . . "2011-06-18T16:14:26"^^ . "==='Fuzzy Trains' fuzzy learning example===\nA fuzzy and OWL-based version of Michalski’s train problem has been designed in order to be used for testing general-purpose fuzzy ILP reasoners.\n\nThe fuzzy trains ontology design starts from defining a crisp ontology to be later ’fuzzified’ (see next Figure). In this ontology, each locomotive (Train) can have several carriages (Car) attached (hasCar). The order of the locomotive and the carriages is also stated (isInFrontOf). Each carriage has a certain length (hasLength) and may have some load (hasLoad). This load can have several shapes. Currently, triangular (Triangle) and square (Square) shapes are con- sidered. Finally, there may exist three types of carriages depending on its length (ShortCar, MediumCar, LongCar).\n\nhttp://dl-learner.org/Projects/DLLearner/fuzzyTrains/files?get=fuzzydlscheme.jpg\n\nA particular test case has been created from previous design:\n\nhttp://dl-learner.org/Projects/DLLearner/fuzzyTrains/files?get=fuzzytrainsexample.jpg\n\nThis ontology can be found ((http://dl-learner.org/Projects/DLLearner/fuzzyTrains/files?get=fuzzytrains_v5.0.owl here)).\n\n===Crisp version===\nCrisp versions of the //fuzzyTrains// ontology were developeded in order to compare the solutions obtained by //(1)// DL-Learner configured to solve a crisp ILP problem and //(2)// DL-Learner configured to solve fuzzy ILP problems:\n 1. ((http://dl-learner.org/Projects/DLLearner/fuzzyTrains/files?get=nofuzzytrains_v1.5.owl noFuzzyTrains_v1.5.owl))\n 2. ((http://dl-learner.org/Projects/DLLearner/fuzzyTrains/files?get=fuzzytrains_v1.5.owl fuzzyTrains_v1.5.owl))\n" . . . . "2011-09-30T15:05:37"^^ . "==Lutherbibliographie==\n\nhttp://lutherbibliographie.theologie.uni-leipzig.de\n\nhttps://bitbucket.org/aksw/luther" . . . . "2011-10-02T21:18:36"^^ . "<#\n
    \n

    Mobile DSSN Client

    \n\n

    Distributed Semantic Social Networking on mobile devices

    \n

    Mobile DSSN Client was developed to address the need for a mobile web application to access the Distributed Semantic Social Network. It allows users to alter their information as well as track what their friends are doing.\n

    \n

    Mobile DSSN on GitHub

    \n

    Mobile DSSN demo

    \n
    \n
    \n#>\n\n{{feed title=\"Project News\" divclass=\"floatbox\" url=\"http://blog.aksw.org/category/projects/dssn/dssn-mobile/feed/\" max=\"5\"}}\n\n===Overview===\nSmartphones, which contain a large number of sensors and integrated devices, are becoming increasingly powerful and fully featured computing platforms in our pockets.\nFor many people they already replace the computer as their window to the Internet, to the Web as well as to social networks.\nHence, the management and presentation of information about contacts, social relationships and associated information is one of the main requirements and features of today's smartphones.\nThe problem is currently solved only for centralized proprietary platforms (such as Google mail, contacts \\& calendar) as well as data-silo-like social networks (e.g. Facebook).\nWithin the Semantic Web initiative standards and best-practices for social, Semantic Web applications such as FOAF emerged.\nHowever, there is no comprehensive strategy, how these technologies can be used efficiently in a mobile environment.\nIn this article we present the architecture as well as the implementation of a mobile Social Semantic Web framework, which weaves a distributed social network based on semantic technologies\n\n===Features===\n * implemented platform independently in HTML5 and JavaScript\n * supports ((http://www.w3.org/2005/Incubator/federatedsocialweb/wiki/SWAT0 SWAT0))\n * uses Sindice for searching for FOAF profiles\n\n===Further Information===\n * Sebastian Tramp, Philipp Frischmuth, Natanael Arndt, Timofey Ermilov and Sören Auer: ((http://svn.aksw.org/papers/2011/ESWC_MobileSocialSemanticWeb/public.pdf Weaving a Distributed, Semantic Social Network for Mobile Users.)) Proceedings of 8th Extended Semantic Web Conference (ESWC2011), Heraklion, Crete, Greece, May 29 - June 02, 2011. \n * Timofey Ermilov, Sebastian Tramp, Sören Auer: ((http://svn.aksw.org/papers/2011/JWS_MobileDSSN/public.pdf A Mobile Client for the Distributed Semantic Social Network,)) submitted to JWS\n\n\n===Contact==={{a name=\"Contact\"}}\n{{vcard name=\"sn\" value=\"Ermilov\"}}\n{{vcard name=\"sn\" value=\"Tramp\"}}\n{{vcard name=\"sn\" value=\"Auer\"}}" . . . . "2010-03-05T05:49:31"^^ . "http://www.bowlinginlubbock.com/Prednisone_Orders.htm prednisone online 8680 http://www.paesine.com/acomplia.html acomplia weight loss drug eank http://www.lilianmahoukou.net/ phentermine without a prescription =-DD http://www.bookami.com/ xanax hek http://www.santiliebana.com/ tramadol for dogs 83290" . . . "2010-04-07T09:32:29"^^ . "===RDB2RDF===\n\n\nis a simple as well as straight forward approach for integrating relational databases into the Linked Data cloud. It offers a high-performance mapping of SPARQL to SQL based upon an easy-to-understand declarative mapping language.\n\n\n====Approach====\nWe rely on a on-the-fly transformation of SPARQL queries into SQL. \n\n\n====Mapping Language===\nOne of our main goals is to provide a easily readable mapping language. A mapping of a relational database table containing data about persons could for example be specified employing the following syntax:\n\n%%(php)\nR2RMap(\n \"select authorid, username, realname, email from serendipity_authors\", \n \"person\", \n \"foaf:Person\",\n \"id\",\n \"foaf:accountName\", \n \"foaf:name\", \n \"foaf:mbox\"\n);\n%%\n\nThe R2RMap element first names a table, view or select query, than a linked data path for the instances, a rdf:type, followed by a mapping from columns to properties.\n\nThis mapping language is explained in detail ((http://www.w3.org/2001/sw/rdb2rdf/wiki/R2RML_SQL_View_Annotation here)).\n\n\n\n====Validation====\n\nWe are testing our approach with ~WordPress, ~WakoWiki and BSBM.\n\n\n====Implementations====\n\nCurrently two different implementations are under development, one in Java and one in PHP. While Java is is well supported in the scientific and business communities, the combination of PHP and MySQL is highly popular in the web and increases the reach of our approach.\n\n**Java Implementation**\n\nThe Java implementation currently features basic graph pattern matching of select statements.\n\nCurrently supported:\n * BGP\n\nNot yet supported:\n * UNION\n * FILTER\n\n**PHP Implementation**\n\nThe PHP implementation currently covers the following parts of the SPARQL specification:\n\n * SELECT (DISTINCT) queries with one Basic Graph Pattern (BGP)\n * PREFIX\n * ORDER BY\n * LIMIT, OFFSET\n * FILTER: bound, regex (mySQL only), sameTerm \n\nNot yet supported are:\n * OPTIONALs\n * Group Graph Pattern \n * remaining FILTER functions\n \n====Releases====\n\ncurrently no software has been released yet, an early preview will be available when at least a large part of the BSBM benchmark is supported.\n\n===Contributions and Support===\nThe following people of AKSW created this project and provide support:\n\n===Contact==={{a name=\"Contact\"}}\n{{vcard name=\"sn\" value=\"Unbehauen\"}}\n{{vcard name=\"sn\" value=\"Frischmuth\"}}\n{{vcard name=\"sn\" value=\"Auer\"}}\n" . . . . "2009-10-19T13:05:05"^^ . "==~OntoWiki FP7 - mid-term project meeting==\n{{ToC}}\n\n===General Information===\n\nVenue:\n October 15th and 16th: ((http://www.mml-leipzig.de/index.php?id=38&L=1 Mediencampus Villa Ida))\n \nHotel: ((http://www.motel-one.com/de/hotels/hotels-leipzig.html Motel One))\n\n((http://maps.google.com/maps?f=d&source=s_d&saddr=Nikolaistra%C3%9Fe+23,+04109+Leipzig&daddr=villa+ida&hl=en&geocode=%3BFTSkDwMd56K8ACH1qvQjrdhtmA&gl=de&mra=ls&dirflg=w&sll=51.34607,12.37003&sspn=0.03608,0.115099&ie=UTF8&z=15 Directions))\n\n===Participants===\n\n * **Punkt**: Kurt Moser, Martin Kaltenböck\n * **OpenLink**: Orri Erling, Yrjänä Rankka\n * **B2**: David Rozman, Tomaz Mlakar\n * **BI**: Tobias Gruß, Ronny Voigt\n * **CUAS**: Danilo Garbi Zutin, Christian Maier, Michael Niederstätter, Sebastian Schreiter\n * **Vakantieland**: Ceriel Jacobs\n * **Uni Leipzig/~InfAI/AKSW**: Sören Auer, Sebastian Dietzold, Jens Lehmann, Michael Martin, Sebastian Hellmann, Jörg Unbehauen, Norman Heino, Philipp Frischmuth\n\n===Agenda===\n\nTelephone during the workshop contact: +49(1522)6230601 \n\n====THURSDAY, OCTOBER 15th, 2009====\n * 11:00-12:30 Welcome reception, light lunch buffet\n * 13:00-13:30 **State of Play** (Sören Auer - Head AKSW, Universität Leipzig/~InfAI)\n * 13:30-15:00 **Workpackage Presentations 1**\n * //WP2: Virtuoso knowledge store developments in the last year//, ~OpenLink Ltd., Orri Erling (Virtuoso Program Manager)\n * //D3.1 ((http://aksw.org/Events/2009/OntoWikiKickMidTerm/files?get=ontowiki_dllearner.pdf Adaptive Ontology Schema Engineering: Integration of OntoWiki and DL-Learner)) //, Jens Lehmann, Sebastian Dietzold (~InfAI)\n * //D3.2 ((http://aksw.org/Events/2009/OntoWikiKickMidTerm/files?get=taggingandfacetbasedbrowsing.pdf OntoWiki support for collaborative tagging, annotation & facet-based browsing))//, Sebastian Dietzold (~InfAI)\n * 15:00-15:30 **Coffee Break**\n\n * 15:30-17:00 **Workpackage Presentations 2**\n * D3.3 //((http://aksw.org/Events/2009/OntoWikiKickMidTerm/files?get=ow_midterm_dbpedialive.pdf Established analyse-improve-release cycle for the DBpedia multi-domain ontology))//, Sebastian Hellmann/Claus Stadler (~InfAI)\n * D4.1 //((http://aksw.org/Events/2009/OntoWikiKickMidTerm/files?get=mid_term_wp4_1.pdf Selection and development of vocabularies for representing enterprise knowledge))//, Jörg Unbehauen (InfAI)\n * D5.1 //Vocabularies for representing E-Learning content//, Michael Niederstädter (CUAS)\n * WP6 // ((http://aksw.org/Events/2009/OntoWikiKickMidTerm/files?get=wp6__presentation.pdf Market Adoption: E-Tourism)) //, Michael Martin (~InfAI) / Ceriel Jacobs (Vakantieland) / Daniel Gerber (Uni Leipzig)\n * 17:00-17:30 **QA**\n * 17:30 Transfer to Motel One\n * 20:00 **((http://maps.google.com/maps?f=q&source=s_q&hl=en&geocode=&q=alte+nikolaischule+leipzig&sll=37.0625,-95.677068&sspn=29.219963,67.236328&ie=UTF8&hq=alte+nikolaischule&hnear=Leipzig,+Germany&ll=51.344151,12.378244&spn=0.011232,0.03283&z=15&iwloc=A Dinner at Alte Nikolaischule))**\n\n====FRIDAY, OCTOBER 16th, 2009====\n * 9:30-10:30 **Partner Presentations**\n * CONX developments, Kurt Moser (Punkt)\n * Trilith developments, Tobias Gruß (BI)\n * Semantic Technologies for E-Learning, David Rozman (B2)\n * 10:30-11:00 **Coffee break**\n * 11:00-12:00\n * **Discussion of the Reporting for first Period**\n * **Next Steps: Workplan, Workpackages, Deliverables** (Sören Auer, AKSW/~InfAI)\n * 12:00-13:00 **Lunch at Gosenschänke \"Ohne Bedenken\"**\n * 13:00-15:00 **Workpackage discussions in small groups**\n * 15:00-15:30 **Coffee**\n * 15:30-17:00 **Workpackage discussions in small groups**\n * 17:00 **Farewell**\n" . . . . "2009-10-06T12:26:25"^^ . "==FP7 Projects==\n\n===Accepted Fp7 ICT Call 4 IPs===\n\nhttp://cordis.europa.eu/fetch?CALLER=FP7_PROJ_EN&ACTION=D&DOC=15&CAT=PROJ&RCN=89449\nhttp://cordis.europa.eu/fetch?CALLER=FP7_PROJ_EN&ACTION=D&DOC=13&CAT=PROJ&RCN=89484\nhttp://cordis.europa.eu/fetch?CALLER=FP7_PROJ_EN&ACTION=D&DOC=11&CAT=PROJ&RCN=89494\nhttp://cordis.europa.eu/fetch?CALLER=FP7_PROJ_EN&ACTION=D&DOC=10&CAT=PROJ&RCN=89482\nhttp://cordis.europa.eu/fetch?CALLER=FP7_PROJ_EN&ACTION=D&DOC=6&CAT=PROJ&RCN=89486\nhttp://cordis.europa.eu/fetch?CALLER=FP7_PROJ_EN&ACTION=D&DOC=4&CAT=PROJ&RCN=89491\nhttp://cordis.europa.eu/fetch?CALLER=FP7_PROJ_EN&ACTION=D&DOC=3&CAT=PROJ&RCN=89256\nhttp://cordis.europa.eu/fetch?CALLER=FP7_PROJ_EN&ACTION=D&DOC=40&CAT=PROJ&RCN=85416\nhttp://cordis.europa.eu/fetch?CALLER=FP7_PROJ_EN&ACTION=D&DOC=39&CAT=PROJ&RCN=85448\nhttp://cordis.europa.eu/fetch?CALLER=FP7_PROJ_EN&ACTION=D&DOC=37&CAT=PROJ&RCN=85468\nhttp://cordis.europa.eu/fetch?CALLER=FP7_PROJ_EN&ACTION=D&DOC=28&CAT=PROJ&RCN=85383\nhttp://cordis.europa.eu/fetch?CALLER=FP7_PROJ_EN&ACTION=D&DOC=25&CAT=PROJ&RCN=89260" . . . . "2011-06-06T16:01:31"^^ . "Achtung beim Upload auf die Plattform Vimeo ist die Lautstärke verändert wurden. wir werden dies noch korrigieren.\n\n{{feed title=\"Videos\" url=\"http://aksw.org/Events/2011/LeipzigerSemanticWebDay/Videos/files?get=videoslswt.rss\" max=\"20\"}}" . . . . "2010-03-18T09:21:20"^^ . "===TIGER Corpus Navigator===\n\nmoved here ((/Projects/NLP2RDF#tigercorpusnavigator))\n\n" . . . . "2010-03-02T06:52:19"^^ . "ocJ7b6 rlywvetrtlin, [url=http://tjqqlcotixdw.com/]tjqqlcotixdw[/url], [link=http://hursjckhuhzg.com/]hursjckhuhzg[/link], http://euwrinhjdtly.com/" . . . "2010-04-08T17:42:20"^^ . "<#\n
    \n

    Vakantieland

    \n\"Screenshots\"\n\n

    In 3 kliks de leukste trips

    \n

    \nDie Web-Applikation vakantieland.nl ist ein ehemals in den Niederlanden entwickeltes und ebenfalls dort veröffentlichtes Tourismusportal. In diesem können Benutzer einen umfassenden Überblick über mögliche touristische Ziele (folgend Point of Interest oder kurz als POI bezeichnet) erhalten. Zudem werden zu jedem einzelnen POI relevante und weitergehende Informationen gehalten und veröffentlicht. Ein Beispiel hierfür wäre ein konkretes Museum in Amsterdam, welches unter anderem durch dessen Namen, Anschrift und Klassifizierung aber auch durch die Öffnungszeiten, Lage in der Stadt und in dessen Umgebung vorhandenen POIs beschrieben sein könnte.\n

    \n
    \n#>\n\n==== Demo Applications ====\n\nDifferent Demo Systems are available via: ((http://staging.vakantieland.nl http://staging.vakantieland.nl))" . . . . "2010-06-20T19:57:28"^^ . "==HBFG 2010==\n\n((/SebastianDietzold SebastianDietzold)) /21.04.2010 19:04/ Fraglich wären noch ordentlich Ergonomische Stühle, welche unsere Rücken schonen ...\n+1 (Norman)\n((/MichaelMartin Michael Martin)) Ich habe mir selbst so einen Stuhl mitgebracht, würde also auch so einen nehmen. Weiterhin wäre ich wir höhenverstellbare Schreibtische, gerade wenn neue Räume zur Verfügung stehen, brauchen wir eh welche.\n\n===Generell===\n * Skype Conference Hardware (=> 500 EU) (z.b. von ((http://www.amazon.com/Polycom-VoiceStation-500-Conference-Accessories/dp/B002BJ3CQC/ref=sr_1_3?ie=UTF8&s=electronics&qid=1271866699&sr=1-3 Policom)) oder ((http://www.snom.com/de/produkte/sip-conference-phone/snom-meetingpoint/ SNOM))\n * ((http://www1.euro.dell.com/de/de/business/Peripherals/projector-dell-4210x/pd.aspx?refid=projector-dell-4210x&s=pad&cs=RC1077931 Dell Projektor)) ( Beamer) ==> 2 x 900 EU -- ((http://www1.euro.dell.com/de/de/offentliche/Peripherals/projector-dell-4310wx/pd.aspx?refid=projector-dell-4310wx&s=pub&cs=RC1077933 HD und 170 EUR billiger )) , also wenn HD dann ((http://www.notebooksbilliger.de/index.php/projektorenbeamer/entertainment/full+hd+1080p+beamer Full HD)) oder?\n * 2 Presenter (z.B. Logitech R400 oder R800)\n * Software: Source Code Analyzer für PHP, Java, JavaScript?\n * Asterisk Server Komplettpaket 5000EU (z.B. http://www.pascom.net)\n * 20 SNOM VoiP Telefone + Headsets a 400EU: 9000EU\n\n===Emergent Semantic===\n * 12 Mitarbeiter = 12 Laptops incl. Dockingstation und ((http://www.notebooksbilliger.de/tftmonitore/69+132+cm+27+52/hannsg+hh281hpb 28 Zoll Monitor)) (=> 12 x 1700 EU)\n * oder ((http://accessories.euro.dell.com/sna/productdetail.aspx?c=de&l=de&s=pad&cs=RC1077933&sku=238199 22\" + Pivot))\n * Peripheriegeräte wie Mäuse und Tastaturen\n * 12 Mobile Devices (=> 12 x 600 EU)\n * Virtuelle Rechner\n * OntoWiki Data-Farm; 8 Cores, 16-32 GB RAM, 4 TB HDD\n * LOD2 Stack Service; 8 Cores, 16-32 GB RAM, 4 TB HDD\n * Continous Integration Server: 2 Cores, 4 GB RAM, 1 TB HDD\n\n===MOLE===\n * 5 Mitarbeiter:\n * Jens Lehmann: aktuell Dell Latitude E6500 => \"Entwicklungsrechner\" Notebook (möglichst zeitlich verschoben da E6500 noch gut) + 22-28 Zoll Monitor\n * Sebastian Hellmann: aktuell Dell Latitude E6500 => \"Entwicklungsrechner\" Notebook (siehe oben) + 22-28 Zoll Monitor\n * Claus Stadler: aktuell kein Notebook => \"Entwicklungsrechner\" Notebook + Monitor + Smartphone\n * Mohamed Mabrouk: aktuell kein Notebook => \"Entwicklungsrechner\" Notebook + Monitor + Smartphone **[amerikanische Tastatur]**\n * Lorenz Bühmann: aktuell kein Notebook => \"Entwicklungsrechner\" Notebook + Monitor + Smartphone\n * (alle Notebooks bitte mit Maus)\n * 1 HP OfficeJet All-In-One Drucker/Fax\n * 2 Workstation-PCs für SHK/WHK/Bachelor/Master\n * Virtuelle Server: \n * LinkedGeoData (ist bereits vorhanden) soll ausgebaut werden; 4-8 Cores, 32-96 GB RAM, 4-8 TB HDD (je nach Entwicklung)\n * DBpedia Mirror (neben offiziellem SPARQL Endpoint) + DBpedia Live Extraction: 4 Cores, 24 GB RAM, 4 TB HDD\n * Continuous Integration Server (abhängig von zukünftigen Projekten bzw. Nutzung der existierenden Server db0.aksw.org, exp0.aksw.org) für DL-Learner, NLP2RDF usw.: 2 Cores, 16 GB RAM, 2 TB HDD\n\n===SIMBA===\nWenn alles nach Plan laufen sollte, bräuchte ich\n * 4 Laptops\n * 2 Workstations für SHK/Praktikanten\n * 2 Virtuelle Server für Experimente und Berechnungen\n\n\n===Franks mail===\n\n%%\nDate: Mon, 12 Apr 2010 15:54:29\nFrom: Frank Schumacher \nTo: Sören Auer \nCc: Axel Ngonga ,\n Jens Lehmann ,\n Sebastian Tramp \nSubject: Wunschliste HBFG-Antrag\n\nLiebe AKSWler,\n\nunser Antrag auf das Stellen eines HBFG- bzw. Großgeräteantrages (Innovationslabor) ist\nbewilligt worden und wir können uns jetzt an das Ausarbeiten des eigentlichen Antrages machen.\nInsgesamt beläuft sich das Antragsvolumen auf ~200.000 Euro.\nDazu hätte ich jetzt gern von euch eine Wunschliste, die euren Bedarf widerspiegelt.\nRein von der \"Story\" her soll sich der Antrag in 3 Hauptbereiche gliedern:\n - Technolgieentwicklungscluster (das seit ihr ;) )\n - Serviceentwicklungscluster (Kyrills Gruppe)\n - Demonstrationszentrum (quasi das Frontoffice, Besprechungen, Präsentationen)\nDiese sollen eng miteinander verknüpft sein und sich in die Hardwarearchitektur des Institutes eingleidern.\n\nIch würde also, was Serverkapazität angeht, den \"Virtualisierungspark\" der Zentralen Dienste hardwaretechnisch erweitern wollen, der dann von uns exclusiv genutzt werden kann. Zum einen haben wir dann den Vorteil einer dynamischen Serverlandschaft und zum anderen könnten wir uns den Administrationsaufwand der zugrundeliegenden Hardware sparen.\n\nAuf der Benutzerseite würde ich eine Mischung aus mobilen Arbeitsstationen (WiMis) und festen Arbeitsplätzen (SHK, WHK, Labor ...) anstreben.\n\nEs wäre schön, wenn ich vom AKSW bis Anfang nächster Woche eine Liste (möglichst mit Zahlen, also x Laptops, y Workstations, z virtuelle Server, a dedizierte Server, sonstiges ...) bekommen könnte, damit diese in die weitere Planung einfließen können.\n\nFür Rückfragen stehe ich euch natürlich gern zur Verfügung.\n\nViele Grüße,\nFrank\n%%" . . . . "2011-05-06T16:12:32"^^ . "==Personen Namen Datei (PND)==\n\nThe first provides interlinking on mainly historical persons. The syndication based on the ((http://www.d-nb.de/standardisierung/normdateien/pnd.htm Personen Namen Datei (PND)-Key)) provided by the ((http://www.d-nb.de/eng/index.htm German National Library)). The PND is widely used in projects like\n\n * ((http://d-nb.info/gnd/ the catalogue of the German National Library))\n * ((http://de.wikipedia.org/wiki/ Wikipedia (de) )) \n * ((http://www.uni-leipzig.de/unigeschichte/professorenkatalog/ the Professorenkatalog of Leipzig University)) \n * ((http://toolserver.org/~apper/pd/person/pnd/ the Wikipedia People Search))\n * ((http://isgv.serveftp.org/saebi/ the Saxonian Biography | ISGV)).\n\n\nThe full list of projects that are linked are listed ((#list here)). \n\nEspecially the use in Wikipedia and the cross links to other languages in combination with DBpedia will syndicate more end more information about historic persons.\n\n===How to use it?===\n\nThe service link is http://linkedhistory.aksw.org/pnd/, followed by the PND.\n\nExample:\n\n * Prof. Dr. phil. Levin Ludwig Schücking (1878-1964)\n * http://linkedhistory.aksw.org/pnd/117124931\n\nThe output is configurable by using the HTML followed by an \"/\" or \".\" and one of the parameters.\n\n * HTML (default), RSS, RDF, RDFXML, NTRIPLES \n * Example: http://linkedhistory.aksw.org/pnd/117124931/RSS\n\n===How to participate?===\n\nWe like to invite all research groups to add their databases to this service.\n\n * publish your database on the web\n * provide a link to the persons in your database by using the PND key\n * create an PND-BEACON File and publish this on Wikipedia ((http://de.wikipedia.org/wiki/Wikipedia:PND/BEACON here)).\n \n\n===Implementation ===\n\nThe source code of the project is open and allowes to setup a own linked history service.\n((https://bitbucket.org/tausendeins/linkedhistory/)).\n\n====Current Status====\n\n * The Service was officially launched on 20th June 2010.\n * Only default HTML and RSS result sets will be supported at the moment.\n * Starting from 14th of February 2011 the Service has been improved\n * Format RDFXML and NTRIPLE added \n\n====Issues====\n\n * Implementation of other output formats\n * Providing the source code \n\n\n<# #>\n===List of projects or databases involved===\n * Katalog der Deutschen Nationalbibliothek\n * HeBIS-Verbundzentrale\n * Professorenkatalog der Universität Leipzig\n * Bayerische Staatsbibliothek\n * Wikimedia Commons\n * Deutschsprachige Wikipedia\n * Titel im Verbundkatalog des GBV\n * Biographische Informationen des Registers zu www.deutsche-biographie.de\n * Biographien in der Neuen Deutschen Biographie\n * Sächsische Biografie\n * Historische Vorlesungsverzeichnisse der Universität Leipzig\n * Eintrag im Biographisch-Bibliographischen Kirchenlexikon (BBKL)\n * Mitglieder der Vorgaengerakademien der Berlin-Brandenburgischen Akademie der Wissenschaften\n * Die Rektoren der Rektoratsreden.\n * Eintrag im Catalogus Professorum Rostochiensis (CPR)\n * Die Rektoren der Rektoratsreden.\n * Mitglieder der Bayerischen Akademie der Wissenschaften\n * Wikisource\n * Allgemeine Deutsche Biographie (Wikisource)\n * Biographien in der Allgemeinen Deutschen Biographie\n * Biogramm in der Online-Version der Edition \"Akten der Reichskanzlei. Weimarer Republik\"\n * Deutsche Zentralbibliothek für Wirtschaftswissenschaften (ZBW) - Leibniz-Informationszentrum Wirtschaft\n * Hessisches Landesamt fuer geschichtliche Landeskunde\n * Volltexte (und evtl. Biographie) bei Zeno.org\n * Titel im VD17\n * Eintrag im Historischen Lexikon der Schweiz (HLS)\n * Forschungsstelle für Personalschriften, Germany\n * Nachweise von Onlinetexten bei Liberley\n * Landesbibliothekszentrum Rheinland-Pfalz\n * Biographie in der Ostdeutschen Biographie (Kulturstiftung der deutschen Vertriebenen)\n\nBack to the main page of the ((/Projects/LinkedHistory/ Linked History Project)). " . . . . "2010-06-02T15:22:36"^^ . "==Software Projects==" . . . . "2010-06-24T12:26:58"^^ . "{{vcard name=\"sn\" value=\"Zaveri\"}}" . . . . "2012-02-11T12:41:10"^^ . "== ~AutoSPARQL ==\n\nThe aim of the ~AutoSPARQL is to provide robust question answering over RDF data by combining methods from several research areas, such as:\n * natural language processing for creating sophisticated semantic representations of questions\n * inductive active learning for incorporating user feedback\n * results of the ((http://aksw.org/Projects/BOA BOA project))\nThe underlying idea is to convert a natural language expression to a SPARQL query, which can then retrieve the answer of a question from a given triple store.\n\nPapers:\n * ((http://jens-lehmann.org/files/2011/autosparql_eswc.pdf ESWC 2011 AutoSPARQL Paper))\n\nLinks:\n * ((http://autosparql.dl-learner.org AutoSPARQL demo))\n * ((http://autosparql-tbsl.dl-learner.org AutoSPARQL-TBSL demo))\n\nSourcecode:\n * main: https://github.com/AKSW/AutoSPARQL\n * machine learning algorithms in ((http://sourceforge.net/projects/dl-learner/ DL-Learner))\n * natural language patterns in ((http://code.google.com/p/boa/ BOA))\n\n===Contact==={{a name=\"Contact\"}}\n{{vcard name=\"cn\" value=\"Jens Lehmann\"}}\n{{vcard name=\"sn\" value=\"Bühmann\"}}\n{{vcard name=\"sn\" value=\"Ngonga Ngomo\"}}\n{{vcard name=\"sn\" value=\"Gerber\"}}" . . . . "2011-05-12T23:12:58"^^ . "<#\n
    \n

    OntoWiki's CSV to RDF plug-in

    \n

    CSV to RDF conversion using OntoWiki's CSV Import plug-in.

    \n

    Converting multi-dimensional statistical data present in CSV files to RDF, using the RDF Data Cube Vocabulary, by using OntoWiki's CSV Import plug-in.

    \n\n
    \n\n#>\n\n{{toc}}\n\n=== Introduction ===\n\nThis page describes the OntoWiki CSV Import plug-in which assists in converting multi-dimensional statistical data present in CSV files to RDF. This plug-in uses the RDF Data Cube vocabulary, which is designed particular to represent multi-dimensional statistical data as RDF present in spreadsheets.\n\n=== The RDF Data Cube Vocabulary ===\n\nThe RDF Data Cube Vocabulary (((http://publishing-statistical-data.googlecode.com/svn/trunk/specs/src/main/html/cube.html#outline screenshot of vocabulary))) is based on the popular SDMX standard and designed particularly to represent multidimensional statistical data using RDF. The statistical dataset is considered a multi-dimensional cube which can be characterized by a set of dimensions that define what the values apply to (e.g. time, country, population), along with the metadata describing what was measured (e.g. death rate), how it is measured and how the observations are expressed (e.g. rate, status). Thus, a cube is organized according to a set of dimensions, attributes and measures collectively called components. A set of dimensions is sufficient to describe a single observation. The measure describes the phenomenon that is reported. The attribute, on the other hand, qualifies and interprets the observed value, such as the status of the observation. The dimensions, at- tributes and measures are represented as RDF properties. Each is an instance of the abstract qb:ComponentProperty class, which in turn has sub-classes qb:DimensionProperty, qb:AttributeProperty and qb:MeasureProperty. Another feature of the Data Cube vocabulary is that it allows defining the structure of the dataset, which enables verification that the dataset matches the expected structure. The qb:DataStructureDefinition allows a user to determine which dimensions are available for query. Thus, the data structure definition can be defined once and reused for similar structured files. The Data Cube vocabulary also uses the SDMX feature of content oriented guidelines (COG). COG define a set of common statistical concepts and associated code lists that can be re-used across datasets.\n\n=== CSV Import plug-in ===\n\nHow to install?\n\n\nHow does it work?\n\nAs illustrated in the Figure, when a spreadsheet containing multi-dimensional statistical data is imported into OntoWiki, it is presented as an HTML table. This presentation of the data gives the users the ability to configure (1) dimensions; (2) attributes by manually creating them and selecting all elements belonging to a certain dimension and; (3) the range of statistical items that are measured. The corresponding COG concepts are automatically suggested, using RDFa, when a user enters a word in the text box provided. It is also possible to save and reuse these configurations for other spreadsheets, which adhere to the same structure (e.g. for data in consecutive years). Once the transformation is configured by the user, the Data Cube importer plugin for OntoWiki takes care of automatically transforming the spread- sheets into RDF. \n\n=== Use Case ===\n\nThe World Health Organizations Global Health Observatory (GHO) dataset contains statistical death and DALY rates per country for each disease. The data in GHO is published in yearly increments as spreadsheets. Generating a transformation from the GHO spreadsheets to RDF based on the Data Cube Vocabulary in a fully automated way is not feasible, since the spreadsheet publication format contains many implicit information (such as formatting and indentation). For example, dimensions are often encoded in the heading or label of a sheet or figures may be given as a fraction of 1000 so as to save space. To facilitate the transformation, we developed a semi-automatic approach by integrating the algorithm as a plug-in extension into OntoWiki. In addition to ontology engineering tasks, OntoWiki provides ontology evolution functionality, which can be used to further transform the newly converted statistical data. Furthermore, OntoWiki provides various interfaces (in particular Linked Data and SPARQL interfaces) to publish and query RDF data.\n\n===Sample GHO data as RDF ===\n\nAn example of the death value 1098 is illustrated in the following listing:\n\n%%(php)\neg:o1 a qb:Observation;\n qb:dataset eg:dataset -in1; \n gho:country eg:Afghanistan; \n gho:disease eg:Tuberculosis;\n eg:value \"1098\" .\n%%\n\n===Contact==={{a name=\"Contact\"}}\n{{vcard name=\"sn\" value=\"Zaveri\"}}\n" . . . . "2012-04-20T10:41:49"^^ . "<#\n
    \n
    \n#>\n\n{{feed title=\"Latest news\" divclass=\"floatbox\" url=\"http://blog.aksw.org/category/projects/limes/feed/\" max=\"3\"}}\n\n===General Overview===\nLIMES implements novel time-efficient approaches for link discovery in metric spaces. Our approaches utilize the mathematical characteristics of metric spaces to compute estimates of the similarity between instances. These estimates are then used to filter out a large amount of those instance pairs that do not suffice the mapping conditions. By these means, LIMES can reduce the number of comparisons needed during the mapping process by several orders of magnitude.\n<##>\n\nThe general workflow implemented by the LIMES framework comprises four steps: Given a source, a target and a threshold, LIMES first computes a set exemplars for the target data source (step 1). This process is concluded by matching each target instance to the exemplar closest to it. In step 2 and 3, the matching is carried out. In the filterig step, the distance between all source instances and target instances is approximated via the exemplars computed previously (step 3). Obvious non-matches are then filtered out. Subsequently, the real distance between the remaining source and target instances are computed (step 3). Finally, the matching instances are are serialized, i.e., written in a user-defined output stream according to a user-specified format, e.g. ((http://www.w3.org/2001/sw/RDFCore/ntriples/ NTriples)) (step 4).\n\n===Architecture===\nThe LIMES framework consists of seven main modules of which each can be extended to accommodate new or improved functionality. The central modules of LIMES are the **controller module**, which coordinates the matching process and the **data module**, which contains all the classes necessary to store data.\nThe matching process is carried out as follows: First, the **controller** calls the **I/O-module**, which reads the configuration file and extracts all the information necessary to carry out the comparison of instances, including the URL of the SPARQL-endpoints of the knowledge bases, the restrictions on the instances to map (e.g., their type), the expression of the metric to be used and the threshold to be used. Examples of configuration files can be found in the distribution. \n<##>\n\nGiven that the configuration file is valid w.r.t. the LIMES Specification Language (LSL), the **query module** is called. This module uses the configuration for the target and source knowledge bases to retrieve instances and properties from the SPARQL-endpoints of the source and target knowledge bases that adhere to the restrictions specified in the configuration file. The query module writes its output into a **cache**, which can be a file (for large number of instances, not implemented yet) or main memory. Once all instances have been stored in the cache, the controller calls the **organizer module**. This module carries out two tasks: first, it computes the exemplars of the source knowledge base. Then, it uses the exemplars to compute the matchings from the source to the target knowledge base. Finally, the **I/O-module** is called to serialize the results. \n\n===Running LIMES===\nRunning LIMES can be done in two ways. You can use our hosted ((http://limes.aksw.org/ Linking Service)) or ((http://sourceforge.net/projects/limes/files/ download the LIMES package)) and run it locally on your server (faster).\n\n===Publications===\n * Axel-Cyrille Ngonga Ngomo und Klaus Lyko: ((http://svn.aksw.org/papers/2012/ESWC_EAGLE/public.pdf EAGLE: Efficient Active Learning of Link Specifications using Genetic Programming)). In: Proceedings of ESWC 2012\n * Mohamed Morsey, Jens Lehmann, Sören Auer, Axel Cyrille Ngonga Ngomo: ((http://svn.aksw.org/papers/2011/ISWC_AKSWBenchmark/public.pdf DBpedia SPARQL Benchmark – Performance Assessment with Real Queries on Real Data)). Proceedings of ISWC2011, 2011. !!Best Paper Award.!! \n * Axel-Cyrille Ngonga Ngomo and Sören Auer: ((http://ijcai.org/papers11/Papers/IJCAI11-385.pdf LIMES - A Time-Efficient Approach for Large-Scale Link Discovery on the Web of Data)). Proceedings of IJCAI 2011. \n * Axel-Cyrille Ngonga Ngomo: ((http://www.dit.unitn.it/~p2p/OM-2011/om2011_Tpaper1.pdf A Time-Efficient Hybrid Approach to Link Discovery)). ISWC'11 Workshop on Ontology Matching (OM-2011).\n * Axel-Cyrille Ngonga Ngomo, Jens Lehmann, Sören Auer and Konraf Höffner: ((http://www.dit.unitn.it/~p2p/OM-2011/om2011_Tpaper3.pdf RAVEN - Active Learning of Link Specifications)). ISWC'11 Workshop on Ontology Matching (OM-2011).\n\n===Further information===\n * A manual for configuring and using LIMES can be found ((http://aksw.org/Projects/LIMES/files?get=limes_manual.pdf here)).\n * A paper containing a detailed description of LIMES and its mathematical foundations can be found ((http://svn.aksw.org/papers/2011/WWW_LIMES/public.pdf here)).\n\n===Contact==={{a name=\"Contact\"}}\n{{vcard name=\"sn\" value=\"Ngonga Ngomo\"}}\n{{vcard name=\"sn\" value=\"Ermilov\"}}\n{{vcard name=\"sn\" value=\"Auer\"}}" . . . . "2010-10-20T12:28:47"^^ . "== Calendar Resources ==\n\nThis project provides calendar years as an URI. The project was initiated in conjunction with the historical project ((http://www.uni.leipzig.de/unigeschichte/professorenkatalog/ Catalogus Professorum Lipsiens)). Typical date information are coded as literals using //xsd:date// data type. But in this field the use of resources instead is promising to find more relation. Additional Wikipedia provides resources describing Years. Therefore we deliver at the Linked Data Interface DBpedia triples, too.\n\n===Using the Linked Data Interface===\n\nRequesting the URI results triples describing the year.\n\nhttp://cal.aksw.org/year/Y2010\n" . . . . "2010-09-16T09:50:29"^^ . "==Visual Query Builder==\n\nOntoWiki serves as a SPARQL endpoint, however, it quickly turned out that formulating SPARQL queries is too tedious for the historian domain experts.\nIn order to simplify the creation of queries for the historians, we developed the //Visual Query Builder// (VQB) as an OntoWiki extension, which is implemented in JavaScript and communicates with the triple store using the SPARQL language and protocol. VQB is available from the OntoWiki repository at ((http://code.google.com/p/ontowiki/))\n\nVQB allows to visually create queries to the stored knowledge base and supports domain experts with an intuitive visual representation of query and data.\nDeveloped queries can be stored and added via drag-and-drop to the current query.\nThis enables the reuse of existing queries as building blocks for more complex ones.\nVQB also supports the //set-based browsing// paradigm by visualizing different connectives, such as join, union, intersection, difference between queries.\nThe incremental query building is facilitated by displaying results already during query creation.\nThe VQB user interface is visualized in the Figure.\n\nhttp://ontowiki.net/Projects/OntoWiki/Extension/VQB/files?get=vqb.png\n\nIt consists of 5 panels, which visualize different aspects of the query creation:\n\n * //Center panel//: the main workspace, where the query is visualized as a graph. Individual elements of the graph can be selected, deleted or moved on the canvas.\n * //East panel:// displays information about the currently selected element. If the selected element is, for example, a class this panel contains the properties, which are used with instances of the class. The panel also contains controls for changing the query, such as via filter conditions.\n * //West panel:// contains available classes in a tree display. Queries are grouped with the classes contained in the query.\n * //South panel:// visualizes the result of the query.\n * //North panel:// shows notifications such as usage hints, error or event descriptions and the generated SPARQL query.\n\n\nThe user interface can be adjusted by scaling or deactivating unused panels.\n" . . . . "2011-06-27T15:29:16"^^ . "{{a name=\"News\"}}\n{{feed title=\"News\" divclass=\"floatbox\" url=\"http://blog.aksw.org/feed/?cat=10\" max=\"2\"}}\n\n<#\n
    \n

    Navigational Knowledge Engineering

    \n\n\n

    is a light-weight methodology for low-cost knowledge engineering by a massive user base.

    \n

    Although structured data is becoming widely available, no other methodology – to the best of our knowledge –\nis currently able to scale up and provide light-weight knowledge engineering for a massive user base. Using NKE, data\nproviders can publish flat data on the Web without extensively engineering structure upfront, but rather observe how structure is created on the fly by interested users, who navigate the knowledge base and at the same time also benefit from using it. The vision of NKE is to produce ontologies as a result of users navigating through a system. This way, NKE reduces the costs for creating expressive knowledge by disguising it as navigation.

    \n\n
    \n\n#>\n\n==About==\n===Authors of this document===\n * ((http://bis.informatik.uni-leipzig.de/SebastianHellmann Sebastian Hellmann)), AKSW/MOLE, University of Leipzig\n * ((http://jenslehmann.org/ Jens Lehmann)), AKSW/MOLE, University of Leipzig\n * ((http://bis.informatik.uni-leipzig.de/JoergUnbehauen Jörg Unbehauen)), AKSW/ES, University of Leipzig\n * ((http://www.kmi.tugraz.at/staff/markus/ Markus Strohmaier)), TU Graz\n===Links===\n * Web Demo HANNE\n * http://hanne.aksw.org \n * ((http://svn.aksw.org/papers/2011/WWW_NKE/hanne_tutorial/hanne_tutorial_public.pdf Tutorial Slides))\n * ((http://iswc2010.semanticweb.org/pdf/522.pdf HANNE - ISWC Demo paper))\n * ((http://code.google.com/p/nlp2rdf/ Google Code project))\n * //Corpus Linguistics//: ((https://dspace.utlib.ee/dspace/bitstream/10062/15937/1/tlt9_submission_33.pdf The TIGER Corpus Navigator))\n * Unpublished working draft: ((http://svn.aksw.org/papers/2011/WWW_NKE/nke_public_draft.pdf ISWC 2011 submission))\n\n{{toc}}\n\n===Introduction (explaining the methodology as understandably as possible)===\n\nWhenever a consumer enters a department store selling groceries, the way the shelves are sorted and arranged will have been predefined by the store owner. This order might be useful in some cases (where the tooth brush is next to the tooth paste), but in other cases it won't be. If one consumer is searching for protein-rich food, the ideal place to search would be a shelf, with food that is rich of protein. Imagine another consumer, who was searching for the same thing a day before. Imagine she would have taken the effort to go around the store, collect all matching food products and put it on one shelf. Wouldn't this be useful?\n\nIn a brick and mortar store such a reordering is impossible for the lack of space alone. But in a digital store, it would not be a shelf, but just another category in the category tree and reordering doesn't require lifting heavy things. With NKE the complexity of creating such categories is disguised as navigation and reduced to selecting examples.\n\n====A walkthrough example ====\nA user is entering the site http://amazon.com with the intention to find a selection \"2.5 inch external hard drive with 500 GB\". She might proceed as follows:\n 1. String search for \"hard drive\" ((http://www.amazon.com/s/ref=nb_sb_noss?url=search-alias%3Daps&field-keywords=hard+drive&x=0&y=0 Amazon search)).\n 2. Click on the category \"external harddrive\" on the left ((http://www.amazon.com/gp/search/ref=sr_nr_scat_595048_ln?rh=n%3A595048%2Ck%3Ahard+drive&keywords=hard+drive&ie=UTF8&qid=1291677843&scn=595048&h=d3e44641a0f454bc51210142a7d0d17e57d7b515 hierarchy)).\n 3. Instead of reformulating the string search, the user will now be able to switch into an \"Active Learning\" mode in which she can create a list of products, which she is searching for and the ones she she does not search. \n * Matching (positive examples): ((http://www.amazon.com/Toshiba-Canvio-Portable-External-E05A050CAU2XK/dp/B003ICWB5Y/ref=sr_1_6?s=pc&ie=UTF8&qid=1291678407&sr=1-6 Toshiba Canvio Plus 500 GB USB 2.0 Portable External Hard Drive)) , ((http://www.amazon.com/Seagate-Expansion-Portable-External-ST905004EXA101-RK/dp/B001UHWHO4/ref=sr_1_14?s=pc&ie=UTF8&qid=1291678407&sr=1-14 Seagate Expansion 500 GB USB 2.0 Portable External Hard Drive))\n * Not matching (negative examples): ((http://www.amazon.com/Passport-Essential-Portable-External-WDBACX0010BBK-NESN/dp/B0041OSQ9S/ref=sr_1_3?s=pc&ie=UTF8&qid=1291678407&sr=1-3 Western Digital My Passport Essential SE 1 TB USB 3.0 and USB 2.0)) , ((http://www.amazon.com/Western-Digital-Elements-External-WDBAAU0010HBK-NESN/dp/B002QEBMB4/ref=sr_1_1?s=pc&ie=UTF8&qid=1291678407&sr=1-1 Western Digital WD Elements 1 TB USB 2.0 Desktop External Hard Drive))\n\nBased on this input, an algorithm is able to produce a much preciser recommendation than by analyzing click behavior, because the user is now actually able to directly model the search enquiry by stating examples. In case the recommendation matches the conception of the user, she is able to save it and give it a name, i.e. \"2.5'' external hard drives with 500 GB\". This so created category is now available to be incorporated into Amazons hierarchy and will be shown to the next user with the same search intention. \n\nIf the Web 3.0 is about \"structured data created by a massive user base\" then it might mean on the one hand that facts are collected, but on the other hand it might as well mean that users will be able to structure data by navigating, searching and using it. Thus a reciprocal relation is formed between the information need of users and the structure gain through the created taxonomy.\n\n===Vision (defining and elaborating the concept of NKE)===\nMost of the text is taken from our yet unpublished ((http://svn.aksw.org/papers/2011/WWW_NKE/nke_public_draft.pdf WWW 2011 submission)).\n\n====Formal Definition====\n**Navigational Knowledge Engineering is the manifestation of labeled examples by interpreting user navigation, combined with the active correction and refinement of these examples by the user to create an ontology of user interests through supervised active machine learning.**\n\nThe NKE methodology consists of three distinct yet interrelated steps: \n 1. **Navigation:** NKE starts by interpreting navigational behavior of users to infer an initial (seed) set of positive and negative examples. \n 2. **Iterative Feedback:** NKE supports users in interactively refining the seed set of examples such that the final set of objects satisfies the users’ intent.\n 3. **Retention:** NKE allows users to retain previously explored sets of objects by grouping them and saving them for later retrieval. \n\nThe vision of NKE is to enable low-cost knowledge engineering on the largest possible scale - the Web. The most fundamental consequence of the paradigm is that value is added to data by just navigating and using it. A reciprocal relation is formed between the information need of users and the information gain through the created taxonomy. Although structured data is becoming widely available, no other methodology – to the best of our knowledge (Nov 2010) – is currently able to scale up and provide light-weight knowledge engineering for a massive user base. Using NKE, data providers can publish flat data on the Web without creating any structure **upfront**, but rather observe how structure is created **on the fly** by interested users, who navigate the knowledge base and at the same time also benefit from using it.\nAs an ontology is created by user navigation, it can be used directly to improve further navigation. For other purposes the ontology might not be used directly, but it can be seen as raw material, that needs to be refined and curated by an ontology expert, a system admin or moderator, employed by the data provider. Two users on Amazon.com searching for 2.5 inch external hard drives might save two intensionally different concepts with a similar extension: “hard drives without an extra power cord” and “hard drives measuring 2.5 inches”. An easy improvement by a knowledge curator would be to define equivalence between these concepts (e.g. via an owl:equivalentClass axiom). The knowledge curator could also review the user-generated ontology in regular intervals and select good concepts to be included into a domain ontology.\n\n=== Prototype (a description of our prototypical implementation)===\nThe methodology is demonstrated with ((http://hanne.aksw.org HANNE)), a Semantic Web system which enables users and domain experts to navigate over knowledge bases by selecting examples. From these examples, formal OWL class expressions are created and refined by a scalable Iterative Learning approach. When saved by users, these class expressions form an expressive OWL ontology, which can be exploited in numerous ways: as navigation suggestions, as a hierarchy for browsing and as input for a team of ontology editors. In particular, we developed an NKE tool named **HANNE** (**H**olistic **A**pplication for **N**avigational K**N**owledge **E**ngineering), which implements the NKE method. In this tool, users can search for resources and mark them as relevant (+) and irrelevant (-). Machine learning techniques use this to explore the underlying concept a user is looking for. The demo is available at ((http://hanne.aksw.org)), the source code can be downloaded from the ((http://code.google.com/p/nlp2rdf/ Google code project)) and a screenshot is shown below: http://aksw.org/Projects/NKE/files?get=screenshot_real_countries_refined.png\n\n===How to use NKE (A tutorial on how to integrate it into a custom system)===\n\nNKE is a methodology, which can be implemented with existing technology and on integrated easily with existing solutions. We will explain the three steps necessary to get a working NKE system and then show some Mockups of how existing portals can be upgraded with NKE. Please tell us, if you find an application, which employs NKE.\n\n==== 3 steps to NKE ====\n 1. Your data has to be in a resource-feature scheme. The RDF format for example provides it by design. The resources are objects, which are of interest to the users such as articles in Wikipedia and products on Amazon.com . These objects are described by features, which could be basically any additional data describing the objects such as tags, key-value pairs, any kind of metadata or concrete values such as title, birthdate, salary or price and weight. This is necessary, so a learning algorithm can be provided with the needed input.\n 2. Choose an entry point for NKE. Before users can actively indulge in NKE, they need to find initial seed examples to start the iterative feedback loop. A non-exhaustive list of displaying objects of interest is given here:\n * Browse down a hierarchy of categories and display the members: ((http://www.ukat.org.uk/thesaurus/hierarchy.php UKAT))\n * Choose facets: ((http://dbpedia.neofonie.de/browse/ Faceted Wikipedia Search)) \n * Anything ((http://lucene.apache.org/solr/ Solr)) has to offer\n * A string or keyword search\n 3. Implement some way for the user to choose positive and negative examples and give him the means to manage such lists. The main incentive for users is that they can manage and order their own dataspace or save those lists to come back later. Allow him to give names to the lists he created. These names are important as they will be the concept names of the resulting ontology. Use supervized active machine learning to find new matching examples so the user can refine the list. There are many off-the-shelf frameworks for machine learning algorithms that can be used. For HANNE we used the ((http://aksw.org/Projects/DLLearner DL-Learner)), which works on arbitrary ((http://jens-lehmann.org/files/2009_dllearner_sparql.pdf RDF/OWL knowledge bases of arbitrary size)). ((http://en.wikipedia.org/wiki/RapidMiner RapidMiner)) is also an option.\n\n**That's it**. As soon as users start to save the learned concepts and give them names, an ontology of user interests will start growing. Now it is your choice what to do. Here are three suggestons:\n 1. Show them back to the users as **Navigation Suggestions**\n 2. Integrate them into you category system for **Browsing**\n 3. Use it to create and extend your **Domain Ontology**\n\n{{anchor name=\"Mockups\"}}\n==== Mockups ====\n<#\n
    \n\n \n\n#>\n" . . . . "2010-10-06T13:10:13"^^ . " * required: Eclipse, Java 6 or higher, Maven 2\n * install Subclipse Plugin\n * install m2eclipse Plugin\n * in Eclipse: \"File\" >> \"New Project\" >> \"Project\" >> \"SVN\" >>\n \"Checkout Projects from SVN\"\n * use https://saim.svn.sourceforge.net/svnroot/saim/trunk/ As URL\n * if asked, configure project as Java project and assign it a name\n e.g. \"SAIM\"\n * exit Eclipse and run \"mvn eclipse:eclipse -DdownloadSources=true\n -DdownloadJavadocs=true\" on the command line (this performs basic\n Eclipse configuration and downloads required jars, sources and\n JavaDoc)\n * start Eclipse\n * right click on project >> Maven >> enable dependency management if\n necessary\n * go to project->properties->compiler, set \"compiler compliance level\" to \"1.6\" " . . . . "2011-03-02T15:46:32"^^ . "==~InfOnLight – Ein Werkzeug für kleinere wachsende Unternehmen zum leichtgewichtigen IT-Infrastruktur und Service Management==\n\nIm Rahmen der Kooperationsvereinbarung „Wirtschaft trifft Wissenschaft“ zwischen der Universität Leipzig und der IHK zu Leipzig wurde das Projekt „InfOnLight“ für eine Förderung im Jahr 2011 ausgewählt. Im Rahmen des Projektes entwickelt die Arbeitsgruppe Agile Knowledge Engineering and Semantic Web (AKSW) am Institut für Informatik zusammen mit dem der Kunert Business Software GmbH & Co.KG (KBS) ein Werkzeug für wachsende Unternehmen zum leichtgewichtigen IT-Infrastruktur und Service Management.\n\n<#\n\n\n#>" . . . . "2010-12-13T13:43:06"^^ . "==Linked Data Browser==\n\n * ((http://aksw.org/Projects/LinkedDataBrowser/description Projektbeschreibung))\n * ((http://aksw.org/Projects/LinkedDataBrowser/documentation Dokumentation))\n * ((http://aksw.org/Projects/LinkedDataBrowser/installation Installation))\n * ((http://aksw.org/Projects/LinkedDataBrowser/manual Benutzerhandbuch))\n\n===Hintergrund===\n\nDas Resource Description Framework (RDF, engl. (sinngemäß) „System zur Beschreibung von Ressourcen“) bezeichnet eine Familie von Standards des World Wide Web Consortiums (W3C) zur formalen Beschreibung von Informationen über Objekte, sogenannte Ressourcen, die durch eindeutige Bezeichner (URIs) identifiziert werden. Es ist ursprünglich als Datenmodell zur Beschreibung von Metadaten im World Wide Web (WWW, Web), wie z. B. Titel, Autor, Copyright einer Webseite, entwickelt worden. Durch eine Ausdehnung des Begriffs „Ressource“ aus dem ursprünglichen WWW-Kontext heraus auf jegliche durch URIs identifizierbaren Entitäten wird RDF heutzutage für eine Reihe von unterschiedlichen Anwendungen eingesetzt, z.B. für Katalogdienste, Aggregatoren für Nachrichten und Feeds oder zur allgemeinen Wissensrepräsentation. \n\n===Zielbestimmen===\n\nEs soll ein Unterprojekt ,das eine Plug-in ist,für die sogenannte „Semantic web“ ermoeglichen .Diese Plug-in soll die sinnvolle Inhalten aus der RDF-Dateien analysen und extrahieren . Für den Nutzer ist diese dann wie in einem Webseite anzuschauen. \n\n===Wegweiser===\n\n" . . . . "2010-12-13T13:43:20"^^ . "==Beschreibung des Projektes==\n\n * ((http://aksw.org/Projects/LinkedDataBrowser/description Projektbeschreibung))\n * ((http://aksw.org/Projects/LinkedDataBrowser/documentation Dokumentation))\n * ((http://aksw.org/Projects/LinkedDataBrowser/installation Installation))\n * ((http://aksw.org/Projects/LinkedDataBrowser/manual Benutzerhandbuch))\n\n===Allgemeines===\n\nDas Resource Description Framework (RDF, engl. (sinngemäß) „System zur Beschreibung von Ressourcen“) bezeichnet eine Familie von Standards des World Wide Web Consortiums (W3C) zur formalen Beschreibung von Informationen über Objekte, sogenannte Ressourcen, die durch eindeutige Bezeichner (URIs) identifiziert werden. Es ist ursprünglich als Datenmodell zur Beschreibung von Metadaten im World Wide Web (WWW, Web), wie z.B. Titel, Autor, Copyright einer Webseite, entwickelt worden. Durch eine Ausdehnung des Begriffs „Ressource“ aus dem ursprünglichen WWW-Kontext heraus auf jegliche durch URIs identifizierbaren Entitäten wird RDF heutzutage für eine Reihe von unterschiedlichen Anwendungen eingesetzt, z.B. für Katalogdienste, Aggregatoren für Nachrichten und Feeds oder zur allgemeinen Wissensrepräsentation.\n\nDie Plug-in für Semantik Web soll die sinnvolle Inhalt der RDF-Dateien Analysen und Extrahieren ermoglichen. Für den Nutzer ist diese dann wie in einem Webseite anzuschauen.\n\n\n\n===Produktübersicht===\n\nDas Produkt ermoeglicht die Darstellung der Daten im RDF als Web-Seite in einer Template. Zuerst soll die Daten im RDF aus Semantik-WebSeite identifiziert werden,und dann wird es extrahiert und in Template dargestellt.\n\nhttp://aksw.org/Projects/LinkedDataBrowser/description/files?get=umgebung.png\n\n===Struktur des Gesamtsystemes===\n\nDas Projekt wird nur als einziger Plug-in realisiert.\n\nhttp://aksw.org/Projects/LinkedDataBrowser/description/files?get=gesamtsystem.png\n\n===Struktur der Einzelkomponenten===\n\n====Klassenübersicht====\n\n**Main:**\nDiese Klasse ist die Haupt-Klasse,die die von Benutzer gegebene URL empfängen soll,und hat zwei Aufgaben.Einerseits sollt sie ein Objekt der Klasse „InfoModel“ mit eingegebene URL erzeugen.Die URL wird in der Klasse „InfoModel“ verarbeitet.Andererseits soll Main eine Template aufrufen, um die von „InfoModel“ analysierte und extrahierte RDF-Daten aus der Webseite anzuzeigen.\n\n**RDFModel:**\nDiese Klasse ist Abstract. In dieser Klasse werden die benotige RDFOperationen definiert.\n\n**InfoModel:**\n„InfoModel“ erbt die Klasse „RDFModel“.Die von Main gegebene URL wird in dieser Klasse analysiert,um die sinnvolle RDF-Daten(z.B. Inhalt,Label,Links) aus der Webseite rekursiv zu extrahieren,und alle Daten wird im dieser Klasse gespeichert.\n\nhttp://aksw.org/Projects/LinkedDataBrowser/description/files?get=gesamtsystem.png\n\n====Anwendungsszenario====\n\nhttp://aksw.org/Projects/LinkedDataBrowser/description/files?get=sequenzdiagramm.png\n\nSpezifikationsdokument als ((http://aksw.org/Projects/LinkedDataBrowser/description/files?get=ldb_entwurf.pdf PDF))\n" . . . . "2010-12-13T13:43:42"^^ . "==Installation==\n\n * ((http://aksw.org/Projects/LinkedDataBrowser/description Projektbeschreibung))\n * ((http://aksw.org/Projects/LinkedDataBrowser/documentation Dokumentation))\n * ((http://aksw.org/Projects/LinkedDataBrowser/installation Installation))\n * ((http://aksw.org/Projects/LinkedDataBrowser/manual Benutzerhandbuch))\n\nQuellecode Herunterladen: ((http://aksw.org/Projects/LinkedDataBrowser/installation/files?get=linkdateplugin_neu.zip linkeddatabrowser.zip))\n\nUm das Plugin nutzen zu können, müssen vier Technologien importieren. Sie können ((http://www.apachefriends.org/en/xampp.html XAMPP)) oder mit folgende Verlinkungen herunterladen und installieren.\n\n 1. PHP 4.3 ((http://php.net/downloads.php))\n 2. PHPLIB Version 7.4 ((http://sourceforge.net/projects/phplib/))\n 3. Apache ((http://httpd.apache.org/download.cgi))\n 4. ARC2 ((http://arc.semsol.org/download))\n\n\n" . . . . "2010-12-13T13:43:31"^^ . "==LOD Browser Documentation ==\n\n * ((http://aksw.org/Projects/LinkedDataBrowser/description Projektbeschreibung))\n * ((http://aksw.org/Projects/LinkedDataBrowser/documentation Dokumentation))\n * ((http://aksw.org/Projects/LinkedDataBrowser/installation Installation))\n * ((http://aksw.org/Projects/LinkedDataBrowser/manual Benutzerhandbuch))\n\n===Contents===\n\n 1. infoModel.php\n 2. rdfModel.php\n 3. Tab.php\n 4. Class InfoModel\n * Method getLabel\n * Method getProperties\n * Method getTypeLink\n 5. Class Main\n * Constructor Main\n * Method show\n 6. Class RDFModel\n * Constructor RDFModel\n * Method findTriple\n * Method getTriples\n * Method isEmpty\n 7. Appendix A - Class Trees\n * default\n\n===infoModel.php===\n\n * Package default\n * require_once “/arc/ARC2.php“ [line 3]\n * require_once „rdfModel.php“[line 2]\n\n===rdfModel.php===\n\n * Package default\n * require_once “/arc/ARC2.php“ [line 2]\n\n===Tab.php===\n\n * Package default\n * require_once “/arc/ARC2.php“ [line 10]\n * require_once „infoModel.php“[line 9]\n\n===Class InfoModel===\n\nA information set of one RDF Model, which contain detailed information of one web seit.\n\n * Package default\n * Access public\n\nstring function InfoModel::getLabel() [line 87]\nGet the label of this object.\n\n * Access public\n\narray function InfoModel::getProperties() [line 77]\nGet the property information with one array.\n\n * Access public\n\nstring function InfoModel::getTypeLink()[line 32]\nGet the resource link of the type.\n\n * Access public\n\n===Class Main===\n\nThis class is main class of the plugin. It build the object of InfoModel, load and * display Template.\n\n * Package default\n * Access public\n\nConstructor void function Main::Main($baseuri) [line 51]\n\n * Function Parameters:\n * string $baseuri\n * Constructor\n * Access public\n\nvoid function Main::show() [line 64]\nPage date build and display\n\n * Access public\n\n===Class RDFModel===\n\nA information set of one RDF Model, which is builded with an URI. This class is abstract and have some function for deal with Model\n\n * Package default\n * Abstract Element\n * Access public\n\n\nConstructor void function RDFModel::RDFModel($base) [line 34]\n\n * Function Parameters:\n * string $base\n * Constructor\n * Access public\n\nstring function RDFModel::findTriple($sub, [$pred = '']) [line 55]\nSearch one Triple by subject and predicate If predicate is empty, it will match anything.If no matching Triple find, the null array will be return.\n\n * Function Parameters:\n * string $sub\n * string $pred\n * Access public\n\narray function RDFModel::getTriples() [line 108]\nGet Tripleset from this model.\n\n * Access public\n\nboolean function RDFModel::isEmpty() [line 118]\nTests if this model is leer!.\n\n * Access public\n\n===Appendix A: Class Trees===\n\n * Package default\n * Main\n * RDFModel\n\nPDF-Format Herunterladen: ((http://aksw.org/Projects/LinkedDataBrowser/documentation/files?get=ldb_documentation.pdf ldb_documentation.pdf))\n" . . . . "2010-12-13T13:43:59"^^ . "==Linked Data Browser - Benutzerhandbuch==\n\n * ((http://aksw.org/Projects/LinkedDataBrowser/description Projektbeschreibung))\n * ((http://aksw.org/Projects/LinkedDataBrowser/documentation Dokumentation))\n * ((http://aksw.org/Projects/LinkedDataBrowser/installation Installation))\n * ((http://aksw.org/Projects/LinkedDataBrowser/manual Benutzerhandbuch))\n\n===1. Installation===\n\nUm das Plugin nutzen zu können,müssen vier Technologien importieren.\n\n * PHP 4.3\n * PHPLIB Version 7.4\n * Apache\n * ARC2\n\n===2. Startseiten===\n\n„Semantik web Plugin “ ist ein Softwareprogramm zur Druchsicht der RDFWebseiten. Für den Nutzer ist diese wie in einem Webseite anzuschauen. Nach dem Start der Anwendung sehen Sie eine leere Startseite in ihrem Browser(Siehe Abb.1).Diese besteht aus einem Einfügbereich , Radio-Buttons und noch einer „Weiter“ Button.\n\nhttp://aksw.org/Projects/LinkedDataBrowser/manual/files?get=ldb_startseit.jpg\nAbbildung 1:Startseite\n\n\nIn dem Einfügbereich können Sie eine URL,die RDF-Webseite ist, mit Form „http://...“ einfügen.Unter dem Einfügbereich steht Radio-Buttons,sie besteht aus einem „Automatisch“ und einem „Default“:\n\n * „Automatisch“:Das Template wird durch die Informationen aus der RDFDaten ausgewählt.\n * „Default“: Default Template wird benutzt.\n\nMit Radio-Buttons koennen Sie entscheiden, welcher Templaten benutzt wird.\n\n\n===3. Webseiten laden===\n\nNach Klicken „Weiter“ Button mit eingefügte URL und ausgewählte Radio- Buttons können Sie jetzt eine neue Webseite anschauen.Da es zwei unterschiedene Template gibt,dann Sie zwei unterschiedene Webseite anschauen können.\n\n\n====3.1 Automatisch Template====\n\nDiese Template ist abhängig von der RDF-Daten der eingegebene URL.Im Abb. 2 zeigt ein Beispiel mit URL=„http://www.uni-leipzig.de/unigeschichte/professorenkatalog/leipzig/Litt_96“. Klicken Sie auf Verlinkung „Index“ um die Startseite zurück zu gehen.Klicken Sie die Verlinkung der Resource um die Quelle Webseite anzuschauen.Wenn Sie auf die Verlinkungen von Label oder Inhalt klicken, können Sie auf andere Webseiten ,die auch Semantik Web sind,klicken.\n\n\nhttp://aksw.org/Projects/LinkedDataBrowser/manual/files?get=ldb_professortab_.jpg\nAbbildung 2:Webseite mit Automatisch Template\n\n\nhttp://aksw.org/Projects/LinkedDataBrowser/manual/files?get=ldb_defaulttab_2.jpg\nAbbildung 3: Webseite der Verlinkung\n\n\n====3.2 Default Template====\n\nIm Abb.3-3 zeigt die Webseite mit gleiche URL wie im Abb.3-1.In diesemTemplate gibt es kein Bild,und sonstige wie Abb.2\n\n\n\nhttp://aksw.org/Projects/LinkedDataBrowser/manual/files?get=ldb_defaulttab_.jpg\nAbbildung 4:Webseite mit Default Template\n\n\n===4.Entwickler===\n\nDas Softwareprogramm „Semantik Web Plugin“ wurde im Rahmen des Moduls Softwaretechnik-Praktikum an der Universität Leipzig entwicklet. Das Programm kann man unter http://www.megaupload.com/?d=N0N30L0Z unterladen. Mitgearbeitet haben:\n\n * Haijiang Yuan\n * Yuan Zhang\n\nProjektbetreuer:\n\n * Herr Thomas Riechert\n\n\nPDF-Format Herunterladen: ((http://aksw.org/Projects/LinkedDataBrowser/manual/files?get=ldp_handbuch.pdf ldp_handbuch.pdf))\n" . . . . "2011-07-11T10:40:08"^^ . "<#\n
    \n

    Mobile Social Semantic Web

    \n\n\n

    weaving a distributed, semantic social network for mobile users.

    \n

    An Android-based social web client as well as a contacts provider, which integrates your distributed FOAF/WebID social network into your mobile phone.

    \n

    Download

    \n
    \n
    \n{{Include page=\"/Projects/MobileSocialSemanticWeb/Menu\" nomark=\"1\"}}\n
    \n
    #>\n\n==Introduction==\n{{a name=\"Introduction\"}}The **Mobile Social Semantic Web Client (mssw)** is an Android-based social web client as well as a contacts provider, which integrates your distributed ((Architecture FOAF/WebID social network)) into your mobile phone.\n\nSmartphones, which contain a large number of sensors and integrated devices, are becoming increasingly powerful and fully featured computing platforms in our pockets. For many people they already replace the computer as their window to the Internet, to the Web as well as to social networks. Hence, the management and presentation of information about contacts, social relationships and associated information is one of the main requirements and features of today's smartphones.\n\nWe present a social network client which is able\n * to read your friends FOAF/WebID based data starting from your own ~WebID,\n * to transform the information into Android contacts (based on customizable rules),\n * to merge your FOAF contacts with your existing contacts,\n * to add new friends by searching for ~WebIDs via ((http://sindice.con Sindice)) or by scanning ((http://en.wikipedia.org/wiki/QR_Code QR-encoded)) ~WebIDs\n * to browse your friends friends (and maybe add them to your network)\n\n==News==\n{{a name=\"News\"}}{{feed divclass=\"box\" title=\"Project Updates\" url=\"http://blog.aksw.org/category/projects/ontowiki/ontowiki-mobile/feed/\" max=\"5\"}}\n\n==Screenshots==\n{{a name=\"Screenshota\"}}http://farm6.static.flickr.com/5285/5277103770_42e7df0667_z.jpg\nScreenshots of the Mobile Social Semantic Web Client, the FOAF Browser and the Android components which integrate the ~WebID account.\n(A) The client as well as the triple store can be found in the official Google application market.\n(B) After installation, users can add a ~WebID account the same way they add an LDAP or Exchange account.\n(C) The account can be synchronized on request or automatically.\n(D) A contacts profile page merges the data from all given accounts.\n(E) By using the FOAF browser, people can add contacts or browse the contacts of their friends.\n\n\n" . . . . "2010-12-20T12:45:00"^^ . " 1. About\n - ((/Projects/MobileSocialSemanticWeb#Introduction Introduction))\n - ((Architecture Architecture of a DSSN))\n - ((/Projects/MobileSocialSemanticWeb#News News))\n - ((/Projects/MobileSocialSemanticWeb#Screenshots Screenshots))\n 2. Get started\n - ((http://code.google.com/p/mssw/wiki/Installation Install Notes))\n - ((http://www.androidpit.de/de/android/market/apps/app/org.aksw.mssw/FOAF-WebID-Provider-Browser Market Link))\n - ((http://code.google.com/p/mssw/downloads/list Download))\n 3. Developing\n - ((http://code.google.com/p/mssw/source/list Sources))\n - ((http://code.google.com/p/mssw/issues/list Issues))\n - ((http://code.google.com/p/mssw/ Google Code Page))\n 4. Related Work\n - ((http://code.google.com/p/androjena/ Androjena))\n\n" . . . . "2010-12-21T12:15:30"^^ . "<#\n
    \n{{Include page=\"/Projects/MobileSocialSemanticWeb/Menu\" nomark=\"1\"}}\n
    \n
    #>\n\n{{toc divclass=\"floatbox\"}}\n==Architecture of a Distributed Semantic Social Network (DSSN)==\nOn this page we describe the main ingredients for a distributed, semantic social network as well as their interplay. The overall architecture is depicted in the Figure below. The semantic representation of personal information is facilitated by ~WebID. FOAF+SSL allow the use of a ~WebID for authentication and access control purposes. Semantic Pingback facilitates the first contact between users of the social network and subscription services allow obtaining specific information from people in ones social network as near-instant notifications.\n\nhttp://farm6.static.flickr.com/5244/5277103692_8e94b34668_z.jpg\n(1) A mobile user may retrieve updates from his social network via his ~WebID provider, e.g. from OntoWiki.\n(2) He may also fetch updates directly from the sources of the connected ~WebIDs.\n(3) A ~WebID provider can notify a subscription service, e.g. a PubSubHubbub server, about changes.\n(4) The subscription service notifies all subscribers.\n(5) As a result of a subscription notification, another node can update its data.\n(6) A mobile user can search for a new ~WebID by using a semantic search engine, e.g. Sindice.\n(7) To connect to a new ~WebID he sends a Pingback request which\n(8) notifies of the resource owner.}\n\n===WebID==\n((http://payswarm.com/webid/ WebID)) is a best-practice recently conceived in order to simplify the creation of a digital ID for end users. Since its focus lies on simplicity, the requirements for a ~WebID are minimal. In essence, a ~WebID is an de-referenceable RDF document (including RDFa) describing its owner (Note: The usage of an IRI with a fragment identifier allows the indirect identification of a WebID by reference to the FOAF profile document). That is, a WebID contains RDF triples, which have the IRI identifying the owner as subject. The description of the owner can be performed in any (mix of) suitable vocabularies, but ((http://xmlns.com/foaf/0.1/ FOAF)) emerged as the \"industry standard\" for that purpose. An example WebID comprising some personal information and two ##rel:worksWith## links to co-workers is shown in the Listing below.\n\n%%\n@prefix rdfs: .\n@prefix foaf: .\n@prefix rel: .\n a foaf:Person;\n rdfs:comment \"This is my public profile only, more information available with FOAF+SSL\";\n rel:worksWith ,\n ;\n foaf:depiction ;\n foaf:firstName \"Philipp\"; foaf:surname \"Frischmuth\";\n foaf:mbox ;\n foaf:phone ;\n foaf:workInfoHomepage .\n%%\n\n===FOAF+SSL===\nThe more technical ((http://esw.w3.org/Foaf%2Bssl FOAF+SSL)) best-practice aims to incorporate authentication functionality into the WebID concept. The main idea is to link an SSL client certificate to a WebID, thus allowing the owner of the FOAF+SSL enabled WebID to authenticate herself at 3rd party Websites. Another goal of FOAF+SSL is to provide access control functionality for a social network shaped by WebIDs in order to allow access to different kinds of information for different groups of contacts (e.g. as presented with ((http://www.uni-koblenz-landau.de/koblenz/fb4/AGStaab/Research/systeme/dgfoaf dgFOAF)) ). An example of a FOAF+SSL WebID extension is shown in the Listing below. This WebID now contains a description of an RSA public key, which is associated to the WebID by using the ##cert:identity## property from the W3C certificates and crypto ontology.\n\n%%\n@prefix rsa: .\n@prefix cert: .\n[] a rsa:RSAPublicKey;\n rdfs:comment \"used from my smartphone ...\";\n cert:identity ;\n rsa:modulus [ cert:hex \"C41199E ... 5AB5\" ];\n rsa:public_exponent [ cert:decimal \"65537\" ] .\n%%\n\n===Semantic Pingback===\nThe purpose of ((http://aksw.org/Projects/SemanticPingBack Semantic Pingback)) in the context of a distributed social network is to facilitate the first contact between different people using the network. The approach is based on an extension of the well-known ((http://hixie.ch/specs/pingback/pingback-1.0 Pingback technology)), which is one of the technological cornerstones of the overwhelming success of the blogosphere in the Social Web. The Semantic Pingback mechanism enables bi-directional links between WebIDs, RDF resources as well as weblogs and websites in general. It facilitates contact/author/user notifications in case a link has been newly established. It is based on the advertising of a lightweight RPC service, in the RDF document, HTTP or HTML header of a certain Web resource, which should be called as soon as a (typed RDF) link to that resource is established.\n\nThe Semantic Pingback mechanism enables people but also authors of RDF content, a weblog entry or an article in general to obtain immediate feedback, when other people establish a reference to them or their work, thus **facilitating social interactions**. It also allows to automatically publish backlinks from the original WebID (or other content) to comments or references of the WebID (or other content) elsewhere on the Web, thus **facilitating timeliness and coherence** of the Social Web. As a result, the distributed network of WebID profiles, RDF resources and social websites using the Semantic Pingback mechanism can be much tighter and timelier interlinked than conventional websites, thus rendering a network effect, which is one of the major success factors of the Social Web. Semantic Pingback is completely downwards compatible with the conventional Pingback implementations, thus allowing the seamless connection and interlinking of resources on the Social Web with resources on the Data Web.\nAn extension of our example profile with Semantic Pingback functionality making use of an external Semantic Pingback service is shown in the Listing below.\n\n%%\n@prefix ping: .\n ping:to .\n%%\n\n===Subscription Service===\nThe purpose of a WebID subscription service is to establish a publish/subscribe communication model to provide near-instant notifications of contact updates. The main idea here is to extend a WebID with a link to a ((http://code.google.com/p/pubsubhubbub/ PubSubHubbub)) service where any contact can subscribe to the WebIDs updates. PubSubHubbub is an open, server-to-server web-hook-based publish/subscribe protocol realized as an extension to Atom.\n\nAlthough such a behavior is described for SPARQL results with ((http://apassant.net/blog/2010/04/18/sparql-pubsubhubbub-sparqlpush SPARQLPush)), there is currently no standardized solution for publishing RDF change sets through PubSubHubbub as well as for saving the incoming changes from all friends of a user in some kind of cache or proxy while the mobile device (the subscriber) is not online. As a consequence, we does not yet support a full-fledged update subscription. As a fallback, updates are currently polled from the related WebIDs. This increases network bandwidth usage and might lead in some cases to slower user interfaces due to network latency.\n\n" . . . . "2011-01-17T19:10:53"^^ . "<#\n
    \n

    OntoWiki Mobile

    \n\"OntoWiki\n

    Knowledge Management in your Pocket

    \n

    OntoWiki Mobile was developed to address the need for a mobile web application for rapid and simple knowledge acquisition in a collaborative way. It allows users to collect instance data, refine the structure of knowledge bases and browse data using hierarchical or faceted navigation on-the-go even without a present data connection.\n

    \n

    OntoWiki on Google Code

    \n

    OntoWiki Mobile demo

    \n
    \n
    \n#>\n\n{{feed title=\"Project News\" divclass=\"floatbox\" url=\"http://blog.aksw.org/category/projects/ontowiki/ontowiki-mobile/feed/\" max=\"5\"}}\n\n===Overview===\nOnto Wiki Mobile is a generic, application domain agnostic tool, which can be utilized in a wide range of very different usage scenarios ranging from instance acquisition to browsing of semantic data on the go. OntoWiki Mobile is implemented as an HTML5 web application, thus being completely mobile device platform in-dependent. In order to allow offline use in cases with restricted network coverage (or in order to avoid roaming charges) it uses the novel HTML5 local storage feature for replicating parts of the knowledge base on the mobile device.\n\n===Running OntoWiki Mobile===\nRefer to OntoWiki installation from repository wiki ((http://code.google.com/p/ontowiki/wiki/Install_OntoWiki_on_fresh_Ubuntu_1004_using_Virtuoso page)) on Google Code. Use Feature-MobileExtension branch.\n\n===Further information===\n * A paper containing a detailed description of OntoWiki Mobile can be found ((http://svn.aksw.org/papers/2011/ESWC_OntoWiki_Mobile/public.pdf here)).\n\n===Contact==={{a name=\"Contact\"}}\n{{vcard name=\"sn\" value=\"Ermilov\"}}\n{{vcard name=\"sn\" value=\"Heino\"}}\n{{vcard name=\"sn\" value=\"Tramp\"}}\n{{vcard name=\"sn\" value=\"Auer\"}}" . . . . "2012-03-16T09:30:16"^^ . "<##>\n\n== LOD Query ==\n{{ToC}}\n=== **SINA:** **S**emantically **IN**terpreting user query towards question-**A**nswering ****===\n====Motivation====\nKnowledge bases published on the Web of Data can be used to answer challenging questions about a wide range of topics. They usually offer a SPARQL endpoint, which can be queried by the user. However, a novice user needs to acquire both knowledge about the underlying ontology and proficiency in formulating SPARQL queries in order to actually formulate a SPARQL query. In this project, we are working on constructing SPARQL queries based on user-supplied keywords. As a result ordinary users are empowered to formulate relatively expressive queries without knowledge of SPARQL and the underlying ontology structure.\n\n====Overview====\nThe following figure shows a birds-eye-view of the envisioned research. Based on a set of user-supplied keywords, candidate IRIs (Internationalized Resource Identi er) for each of the keywords issued by the user is computed. Then, by using an inference mechanism, a subgraph based on the identi ed IRIs is extracted and represented to the user as the answer.\n<##>\n\n=== First Phase ===\nIn an early phase, a novel method for generating SPARQL queries based on two user-supplied keywords was proposed. Since this method is based on simple operations, it can generate SPARQL queries very efficiently. Also it is completely agnostic of the underlying knowledge base as well as its ontology schema. We currently use DBpedia as the underlying knowledge base, but this method is easily transferable to the whole Data Web.\nThe implementation of this method is publicly available at: http://lod-query.aksw.org/\n\n**Contributers in this phase:**\n * Saeedeh Shekarpour\n * Sören Auer\n * Axel Ngonga Ngomo\n * Daniel Gerber\n * Sebastian Hellman\n * Clause Stadler\n\n=== Second Phase ===\nIn the next phase, we proposed a method for generating SPARQL queries for arbitrary number of keywords. Its base is an inference mechanism embedded in a graph traversal approach which both accurately and efficiently builds SPARQL queries for the straightforward interpretations of the user's queries. Implementation of this method is also available at: http://sina.aksw.org.\n This application generats SPARQL query for those keyword-based queries which can be converted to a conjunctive query. A conjunctive query is a conjunction of triple patterns.\n\n====Publishing Datasets used in Evaluation====\n\nwe compared the accuracy of our approach against the top-k exploration on a data set composed of 30 SPARQL queries extracted from the DBpedia query log3 and the QALD-1 benchmark4.\n* SPARQL queries dataset: http://aksw.org/Projects/lodquery/files?get=PublishedDBpediaQueries.xlsx \nIn our second experimental setting, we evaluated the precision and recall of our framework on the QALD-1 benchmark.\n* Keyword-based queries dataset: http://aksw.org/Projects/lodquery/files?get=PublishedQualdkeywordqueries.xlsx \n\n**Contributers in this phase:**\n * Saeedeh Shekarpour\n * Sören Auer\n * Axel Ngonga Ngomo\n \n\n\n=== Further Information ===\n* Do not hesitate to contact me for any question (shekarpourATinformatik.uni-leipzig.de - sa.shekarpourATgmail.com)\n* SINA is a Persian name: http://en.wikipedia.org/wiki/Sina\n* SINA is the name of a Persian physician and philosopher which his Latinized name is Avicenna: \n * http://www.iranchamber.com/personalities/asina/abu_ali_sina.php\n * http://en.wikipedia.org/wiki/Avicenna\n\n\n\n===Contact==={{a name=\"Contact\"}}\n{{vcard name=\"sn\" value=\"Shekarpour\"}}\n{{vcard name=\"sn\" value=\"Ngonga Ngomo\"}}\n{{vcard name=\"sn\" value=\"Auer\"}}" . . . . "2011-10-12T11:05:57"^^ . "<#\n
    \n

    ReDD-Observatory

    \n\"ReDD\n

    Using the Web of Data for Evaluating the Research-Disease Disparity

    \n

    The ReDD-Observatory is a project to evaluate the disparity between active areas of biomedical research and the global burden of disease using Linked Data and data-driven discovery.

    \n\n
    \n\n#>\n\n{{toc}}\n\n=== Background === \nIt is widely accepted that there is a large disparity between the availability of treatment options and the prevalence of diseases in the world, thus placing individuals in danger. This disparity is partially caused by the restricted access to information that would allow health- care and research policy makers to formulate more appropriate measures to mitigate this disparity. Specifically, this shortage of information is caused by the difficulty in reliably obtaining and integrating data regarding the disease burden for a given nation and the respective research investments. \n\nIn response to these challenges, the Linked Data paradigm provides a simple mechanism for publishing and interlinking structured information on the Web. In conjunction with the ever increasing data on diseases and healthcare research available as Linked Data, an opportunity is created to reduce this information gap that would allow for better policy in response to these disparities. \n\nWe present the ~ReDD-Observatory, an approach for evaluating the __Re__search-__D__isease __D__isparity based on the interlinking and integrating of various biomedical data sources. \n\n=== Methodology === \nThe figure below provides a birds eye-view of the methodology involved in the ~ReDD-Observatory.\n\nhttp://redd.aksw.org/images/overview.png\n\nWe first identified relevant datasets to be included that provided relevant information to evaluate the disparity. We not only consider the datasets already present as RDF but also those that are present in unstructured formats. These datasets are:\n 1. ((http://linkedct.org LinkedCT)) - the RDF representation of ((http://clinicaltrials.gov/ ClinicalTrials.gov)), which is the database of all clinical trials around the world.\n 2. ((http://pubmed.bio2rdf.org/sparql Bio2RDF's PubMed)) - the RDF representation of ((http://www.ncbi.nlm.nih.gov/pubmed/ PubMed)), which is a service of the US National Library of Medicine that includes bibliographic information and abstracts of over 19 million publications from MEDLINE and other life science journals.\n 3. WHO's ((http://apps.who.int/ghodata/ Global Health Observatory)) (GHO), which contains statistical information regarding the mortality and burden of disease classified according to the death and DALY (disability-adjusted life year) estimates grouped by countries and regions. \nHowever, since GHO is not available as Linked Data, as the next step we devised a method for representing unstructured data as RDF. We devised a plug-in in ((http://aksw.org/Projects/OntoWiki OntoWiki)) to represent statistical data from GHO as RDF. We used the Data Cube Vocabulary for this conversion. More information is present ((http://aksw.org/Projects/Stats2RDF here)). In order to ensure the completeness, conciseness and consistency for the selected datasets our next step is to assess the data quality of the datasets. The next challenging step is to interlink the datasets for a number of concepts such as (a) countries, (b) diseases and (c) publications. The assessment of the disparity is then performed with a number of parametrized SPARQL queries. We evaluate the results wrt. information quality and interlinking precision. As a consequence, we are, for the first time, able to provide reliable indicators for the extent of the research-disease disparity around the world in an semi- automated fashion, thus enabling healthcare professionals and policy makers to make more informed decisions.\n\n=== Further Information ===\n * ((http://redd.aksw.org/ ReDD Observatory)) - a user interface, which allows users to visualize the disparity for particular diseases and regions as well as drill-down to the underlying data such as trials and publications.\n * ((http://db0.aksw.org:8895/sparql SPARQL Endpoint)) - query the integrated datasets.\n * ((http://redd.aksw.org/queries/ Sample SPARQL queries))\n * ((http://redd.aksw.org/interlinks/ Interlinks between the three core datasets))\n * ((http://svn.aksw.org/papers/2011/WWW_ReDD/public.pdf Accepted paper)) at the ((http://liris.cnrs.fr/~wi-iat11/WI_2011/ WI-2011))\n * ((http://summerschool.eswc2011.org/sites/default/files/ReDD_Poster_ESWC2011.pdf Poster presented at the ESWC 2011 Summer School))\n * Presentation given at the WI-IAT 2011 conference held in Lyon: http://www.slideshare.net/amrapalijz/reddobservatory\n\n===Contributors==={{a name=\"Contact\"}}\n{{vcard name=\"sn\" value=\"Zaveri\"}}\n{{vcard name=\"sn\" value=\"Auer\"}}\n{{vcard name=\"cn\" value=\"Jens Lehmann\"}}\n{{vcard name=\"sn\" value=\"Ermilov\"}}\n{{vcard name=\"sn\" value=\"Martin\"}}\n**((http://goo.gl/DXnAU Dr.Ricardo Pietrobon))**\n\n=== Publications ===\n%%(exhibit jsonp=\"http://docs.aksw.org/BibsonomyProxy/exhibit-proxy.php?suffix=user/aksw/zaveri&callback=cb\")\n
    \n
    \n
    Navigation
    \n \n \n \n \n
    \n
    \n
    \n

    \n \n :\n \n \n \n (Editors:\n \n )\n \n \n \n \n

    \n
    \n%%\n" . . . . "2011-05-30T19:56:40"^^ . "<#\n
    \n

    3. Leipziger Semantic Web Tag (LSWT2011)

    \n\n\"LSWT\n

    Linked Data für die Massen

    \n

    Der Leipziger Semantic Web Tag (LSWT) bietet seit 2009 Unternehmen und Organisationen die Möglichkeit, sich zu Themen im Bereich semantischer Technologien auszutauschen. Im letzten Jahr wurden Semantic Web Technologien von vielen Firmen in größerem Umfang eingesetzt. Beispiele dafür sind der Einsatz von Linked Data bei der New York Times, das Open Graph Protokoll bei Facebook, die Unterstützung der GoodRelations-Ontologie durch Google sowie zahlreiche Initiativen für transparentes E-Government (z.B. data.gov). Im Fokus des diesjährigen LSWT steht das Thema \"Linked Data für die Massen\" und soll insbesondere Unternehmen helfen, einen leichten Einstieg in die Nutzung entsprechender Technologien zu finden.

    \n

    Tickets

    \n
    \n
    \n{{Include page=\"/Events/2011/LeipzigerSemanticWebDay/Menu\" nomark=\"1\"}}\n
    \n
    \n#>\n\n<#

    Sponsoren:

    \n\n\n\n
    \n
    \n
    \n
    \n
    \n
    \n
    \n
    \n
    \n
    \n\n

    Unterstützer:

    \n\"ITmitte.de\n\n

    Organisatoren:

    \n

    \n

    \n

    #>\n\n===Featured Video: Semantic Web - Hab ich was verpasst? (LSWT2011 Keynote von Andreas Blumauer)===\n<#\n

    Keynote Leipziger Semantic Web Tag 2011 - Andreas Blumauer from AKSW Research Group - Leipzig on Vimeo.

    \n#>\n===Neuigkeiten===\n{{feed url=\"http://blog.aksw.org/feed/?tag=lswt\"}}" . . . . "2011-03-23T08:24:16"^^ . "{{Include page=\"/Events/2011/LeipzigerSemanticWebDay/Header\" nomark=\"1\"}}\n===Einladung zur Teilnahme===\n Datum: **4. Mai** (Tutorials), **5. Mai** (Kerntag)\n Webseite: http://aksw.org/LSWT\n Einladung: http://aksw.org/LSWT/Einladung\n Kontakt: ((mailto:lswt2011@informatik.uni-leipzig.de lswt2011@informatik.uni-leipzig.de))\n\n<#\n#>\nDer Leipziger Semantic Web Tag (LSWT) gibt interessierten Unternehmen und Organisationen die Möglichkeit, semantische Technologien kennen zu lernen und Kontakte zu knüpfen. Anknüpfend an die Erfolge der Vorjahre wird auch 2011 wieder ein Semantic Web Tag in Leipzig stattfinden. Im Fokus der diesjährigen Veranstaltung steht das Thema \"Linked Data für die Massen\". Viele mittlere und große Unternehmen nutzen bereits die Vorteile von Linked Data. Der LSWT 2011 möchte daher allen Beteiligten die Gelegenheit bieten, mehr über Linked Data zu erfahren, um so den Einsatz semantischer Technologien auch in Ihrem Unternehmen voranzutreiben. \n\nWir laden Sie hiermit herzlich ein, sich am LSWT 2011 zu beteiligen. Wir bieten dazu folgende Möglichkeiten an: \n\n====Teilnahme als Besucher====\nUm die Teilnahme so einfach wie möglich zu gestalten, haben wir die Registrierungsgebühren so gering wie möglich gehalten, insbesondere für Studenten. Details und Registrierung entnehmen Sie bitte der ((/Events/2011/LeipzigerSemanticWebDay LSWT Webseite)).\n\n====Anmeldung eines Vortrags====\nWenn Sie sich mit einem Vortrag beteiligen möchten, schicken Sie bitte Vortragstitel und eine kurze Zusammenfassung (nicht mehr als 200 Wörter) an das ((#team Organisationsteam)). Die Einreichungsfrist für die Anmeldung von Vorträgen ist der **23.03.2011**.\n\n====Anmeldung eines Tutorials====\nAm 4. Mai werden Tutorials stattfinden, die den Wissenstransfer rund um semantische Technologien aus der Forschung in Unternehmen erleichtern sollen. Darin sollen insbesondere wichtige semantische Basistechnologien dem Publikum näher gebracht werden. Möchten Sie ein Tutorial organisieren, dann wenden Sie sich bitte an das ((#team Organisationsteam)).\n\n====Anmeldung eines Standes====\n Hinweis: Die Anmeldung eines Standes ist nicht mehr möglich, da die maximale Anzahl bereits gebucht wurde. ((/SebastianDietzold SebastianDietzold)) /21.03.2011 20:08/\n \n Nachtrag: Da das Interesse an Aussteller-Ständen sehr groß ist, versuchen wir die dafür zur Verfügung gestellte Fläche zu vergrößern. Bei Interesse bitte melden. ((/SebastianDietzold SebastianDietzold)) /23.03.2011 08:24/\n--Wie in den letzten Jahren können Sie sich als Aussteller am LSWT beteiligen. Es wird Platz für 2 A0 Poster, sowie ein Tisch bereitgestellt. Es fällt eine Gebühr von 100 Euro an. Bitte wenden Sie sich hierzu an das ((#team Organisationsteam)).--\n\n====LSWT-Sponsor====\n Hinweis: Die Anmeldung als Sponsor ist nicht mehr möglich, da die maximale Anzahl bereits erreicht wurde. ((/SebastianDietzold SebastianDietzold)) /21.03.2011 20:08/\n--Als Sponsor des Leipziger Semantic Web Tag bieten wir folgende Vorteile:\n * Bereitstellung eines LSWT-Standes\n * 3 Tickets inklusive\n * Präsentation von Logo und Link auf der ((http://aksw.org/LSWT LSWT 2011 Webseite))\n * Publikation von Logo und Link im offiziellen LSWT 2011 Flyer\n * Erwähnung der Sponsoren in der offiziellen Pressemittelung \n * Erwähnung in Blogeinträgen zum Thema\n * Erwähnung in allen Einladungen\nWir freuen uns über Ihre Unterstützung! Es fällt eine Gebühr von 500 Euro an. Bitte wenden Sie sich bei Interesse an das ((#team Organisationsteam)).--\n\nDatum: **4. Mai** (Tutorials), **5. Mai** (Kerntag)\nWebseite: http://aksw.org/LSWT\nEinladung: http://aksw.org/LSWT/Einladung\nKontakt: ((mailto:lswt2011@informatik.uni-leipzig.de lswt2011@informatik.uni-leipzig.de))\n\n====Organisationsteam====\n{{a name=\"team\"}}Der 3. Leipziger Semantic Web Tag wird organisiert von ((http://bis.informatik.uni-leipzig.de/NadineJaenicke Nadine Jänicke)), ((http://jens-lehmann.org Jens Lehmann)) und ((http://bis.informatik.uni-leipzig.de/SebastianTramp Sebastian Tramp)).\nDas Organisationsteam ist über die E-Mail-Adresse ((((mailto:lswt2011@informatik.uni-leipzig.de lswt2011@informatik.uni-leipzig.de)) erreichbar." . . . . "2011-02-09T16:51:00"^^ . "<#\n
    \n

    KeyNode.js

    \n\n

    Next level web presentations

    \n

    KeyNode.js tries to upgrade existing web-standards based slide show tools (as Slidy or slidedown) with presenter console like features such as personal notes on a different screen/browser, next slide preview and slide overview.

    \n

    Repository

    \n
    \n
    \n#>\n\n===Contact===\n{{vcard name=\"sn\" value=\"Frischmuth\"}}\n{{vcard name=\"sn\" value=\"Heino\"}}\n{{vcard name=\"sn\" value=\"Tramp\"}}" . . . . "2011-10-04T05:46:26"^^ . "This page was moved here permanently:\nhttp://nlp2rdf.org" . . . . "2011-11-16T10:32:21"^^ . "<#\n
    \n

    FOX

    \n\"FOX\n

    Federated knOwledge eXtraction Framework

    \n

    FOX is a framework that integrates the Linked Data Cloud and makes uses of the diversity of NLP algorithms to extract RDF triples of high accuracy out of NL. In its current version, it integrates and merges the results of Named Entity Recognition, Keyword Extraction and Relation Extraction tools.

    \n

    Try the Demo

    \n
    \n
    \n#>\n\n{{feed title=\"Latest AKSW news\" divclass=\"floatbox\" url=\"http://blog.aksw.org/category/projects/fox/feed/\" max=\"3\"}}\n\n===General Overview===\nSeveral services and frameworks have been developed to consume natural language and generate semi- to structured data. These tools are based on very diverse algorithms with a variety of strengths and weaknesses. FOX uses this algorithmic diversity to extract RDF of high accuracy out of natural language. It combines tools for natural language processing and aggregates their results by using efficient ensemble learning algorithms.\n\n===Evaluation===\nFOX has been evaluated on several corpora including general corpora such as news and website data sets and on domain-specific corpora from the area of tourism and renewable energy provided within the ((http://scms.eu SCMS)) project. In all evaluations, FOX outperformed state-of-the-art tools such as the Stanford NER tagger and the Illinois tagger significantly. A full description of the evaluation of FOX on general corpora can be found ((http://aksw.org/Projects/FOX/files?get=fox_evaluation.pdf here)). THe data used to evaluate FOX's named entity disambiguation approaches can be found ((http://aksw.org/Projects/FOX/files?get=annotated_wikinews.zip here)).\n\n===Contact==={{a name=\"Contact\"}}\n{{vcard name=\"sn\" value=\"Ngonga Ngomo\"}}\n{{vcard name=\"sn\" value=\"Heino\"}}\n" . . . . "2011-05-06T16:19:31"^^ . "{{Include page=\"/Events/2011/LeipzigerSemanticWebDay/Header\" nomark=\"1\"}}\n{{toc divclass=\"floatbox\"}}\n===Programm===\n((Einladung Einladung zur Teilnahme))\n====4. Mai - Tutorials ====\nAm Vortag zur Hauptveranstaltung finden zwei Tutorials und ein Social Event zum Kennenlernen statt.\n{{a name=\"Tutorien\"}}\n\n<#\n\n#>\n\n====5. Mai - Kerntag====\n{{a name=\"Kerntag\"}}\nSie können sich am ((!/Einladung Programm beteiligen)). Bitte wenden Sie sich bei Fragen zum LSWT-Programm an ((mailto:lswt2011@informatik.uni-leipzig.de lswt2011@informatik.uni-leipzig.de)).\n\n<#\n\n#>\n\n===Aussteller===\n{{a name=\"Aussteller\"}}\nAussteller präsentieren sich mit einem Stand im Foyer. Sie haben Interesse sich mit einem Stand vorzustellen? Bitte kontaktieren Sie ((/NadineJaenicke Nadine Jänicke)) über ((mailto:lswt2011@informatik.uni-leipzig.de lswt2011@informatik.uni-leipzig.de)).\n * ((http://www.netresearch.de Netresearch GmbG & Co.KG)) (TYPO3 Agentur und Magento Enterprise Partner)\n * ((http://www.sones.com Sones GmbH))\n * ((http://www.ontos.com Ontos AG))\n * ((http://www.fluidops.com Fluid Operations AG))\n * ((http://poolparty.punkt.at/ punkt. netServices))\n * ((http://www.cid.biz CID GmbH))\n * ((http://www.unister.de Unister Holding GmbH))\n * ((http://www.kbs-leipzig.de Kunert Business Software GmbH & Co.KG))\n * ((http://www.t-systems-mms.com/ T-Systems Multimedia Solutions GmbH))" . . . . "2011-04-16T18:21:33"^^ . " 1. Veranstaltung\n - <# Home / Neuigkeiten #>\n - ((/Events/2011/LeipzigerSemanticWebDay/Tickets Tickets / Anmeldung))\n - ((/Events/2011/LeipzigerSemanticWebDay/Anfahrt Anreise))\n - ((/Events/2011/LeipzigerSemanticWebDay/Kontakt Kontakt))\n 2. Programm\n - ((/Events/2011/LeipzigerSemanticWebDay/Einladung Einladung))\n - ((/Events/2011/LeipzigerSemanticWebDay/Programm Kerntag)) (5.Mai)\n - ((/Events/2011/LeipzigerSemanticWebDay/Programm#Tutorien Tutorien)) (4.Mai)\n - ((http://www.leipzigschoolofmedia.de/veranstaltungen/aktuell/veranstaltungen-singleansicht/details/zukunftsperspektiven-der-lokalen-und-regionalen-medien/ SoLoMo Local Media Konferenz)) (4.Mai)\n - ((/Events/2011/LeipzigerSemanticWebDay/Programm#Aussteller Aussteller))\n 3. Networking\n - ((http://www.facebook.com/event.php?eid=190613310967955 Facebook ))\n - ((https://www.xing.com/events/3-leipziger-semantic-web-2011-678480 Xing))\n - ((http://bit.ly/fBIW2v Google iCal))\n 4. Rückblick\n - ((/Events/2010/LeipzigerSemanticWebDay LSWT2010))\n - ((/Events/2009/LeipzigerSemanticWebDay LSWT2009))\n\n" . . . . "2011-01-31T16:14:40"^^ . "{{Include page=\"/Events/2011/LeipzigerSemanticWebDay/Header\" nomark=\"1\"}}\n\n===Anfahrt===\n\nAdresse: ((http://maps.google.com/maps?q=Mediencampus+Villa+Ida%3B+Poetenweg+28%3B+04155+Leipzig Mediencampus Villa Ida)); Poetenweg 28; 04155 Leipzig\n\n====Hinweis====\n\nAufgrund von längerfristigen Straßenbauarbeiten ist das Befahren des Poetenwegs nur eingeschränkt und das Parken überhaupt nicht möglich.\n\n====Anfahrt mit öffentlichen Verkehrsmitteln====\n\nDen Mediencampus erreichen Sie per Tram 4 vom “Hauptbahnhof” bis “Stallbaumstraße”, von der Haltestelle ca. 3 Minuten den Poetenweg hinauf. Oder mit Tram 12 bis “Fritz-Seger-Strasse”, von dort ca. 5 Minuten die Menckestrasse und Schlößchenweg bis zum Poetenweg hinunter.\n\nDen offiziellen Routenplaner der Leipziger Verkehrsbetriebe finden Sie ((http://www.lvb.de/ hier)).\n\n====Anfahrt mit dem PKW====\n\nMit dem PKW verlassen Sie die Autobahn A14 an der Anschlussstelle “Leipzig Mitte” in Richtung Leipzig/Zentrum, fahren aus der B2 “Essener Straße” nach rechts, an der zweiten Ampel nach links. Sie befinden sich auf der Virchow-Straße stadteinwärts. Folgen sie dieser in die Lützowstraße (immer geradeaus). Nach Passieren der Georg-Schumann-Straße folgt hinter einem scharfen Linksknick rechts die Einfahrt in die Menckestraße. Dort biegen Sie links in den Schlößchenweg ab und sehen auf der rechten Seite bereits den Mediencampus.\n\nEine weitere, detaillierte Anfahrtsbeschreibung (google maps) finden Sie ((http://www.google.de/maps?f=d&hl=de&geocode=&daddr=Poetenweg,+Gohlis+04155+Leipzig,+Leipzig,+Sachsen,+Deutschland&mrcr=0&mrsp=0&sz=12&mra=dme&sll=51.366345,12.381095&sspn=0.151545,0.31929&ie=UTF8&z=12&om=1 hier)).\n" . . . . "2011-02-06T23:19:05"^^ . "<#\n
    \n

    3. Leipziger Semantic Web Tag (LSWT2011)

    \n\n

    Linked Data für die Massen

    \n
    \n
    \n{{Include page=\"/Events/2011/LeipzigerSemanticWebDay/Menu\" nomark=\"1\"}}\n
    \n
    \n#>" . . . . "2011-01-31T15:42:02"^^ . "{{Include page=\"/Events/2011/LeipzigerSemanticWebDay/Header\" nomark=\"1\"}}\n===Tickets===\n{{a name=\"Tickets\"}}LSWT Tickets kosten EUR 60,- (Studenten EUR 20,-). Optional können Sie an einem Tutorial-Programm am Vortag (4. Mai, EUR 30,-) und an der Abendveranstaltung/Dinner (EUR 30,-) teilnehmen.\n\n<#\n

    Online Event Registration mit amiando

    \n#>" . . . . "2011-01-31T16:15:47"^^ . "{{Include page=\"/Events/2011/LeipzigerSemanticWebDay/Header\" nomark=\"1\"}}\n===Kontakt===\nDas Organisationsteam des LSWT2010 ist über den Verteiler ((mailto:lswt2011@informatik.uni-leipzig.de lswt2011@informatik.uni-leipzig.de)) erreichbar.\n\nProgramm: ((http://bis.informatik.uni-leipzig.de/SebastianTramp Sebastian Tramp)), ((http://jens-lehmann.org Jens Lehmann))\nOrganisation und Pressekontakt: ((/NadineJaenicke Nadine Jänicke))\n\n===Team===\n{{vcard name=\"sn\" value=\"Jänicke\"}}\n{{vcard name=\"cn\" value=\"Jens Lehmann\"}}\n{{vcard name=\"sn\" value=\"Tramp\"}}\n" . . . . "2011-02-01T09:44:26"^^ . "{{Redirect page=\"/SebastianTramp\"}}" . . . . "2011-02-06T23:18:45"^^ . "<#\n
    \n

    3. Leipziger Semantic Web Tag (LSWT2011)

    \n\n

    Linked Data für die Massen

    \n
    \n
    \n{{Include page=\"/Events/2011/LeipzigerSemanticWebDay/Menu\" nomark=\"1\"}}\n
    \n
    \n#>" . . . . "2011-03-11T15:22:36"^^ . "==Calendar Years as Resources for the Web==\n\nThe service http://cal.aksw.org/year/ provides resources of calendar years for the web. This resources are used for the prosopgraphical knowledgebase ((http://catalogus-professorum.org Catalogus Professorum Lipsiensis)).\n\n===How to use it?===\n\nThe service link is http://cal.aksw.org/year/Y, followed by the year..\n\nExample:\n\n * The year 2009\n * http://cal.aksw.org/year/Y2009\n\n\nBack to the main page of the ((/Projects/LinkedHistory/ Linked History Project)). " . . . . "2011-06-21T11:20:51"^^ . "===Future works on fuzzy extensions for DL-Learner===\nA formal paper (to be accepted in ((http://www.uco.es/isda2011/ ISDA2011))) describing the already done work in extending DL-Learner with fuzzy capabilities can be found ((http://svn.aksw.org/papers/2011/Fuzzy-DL-Learner here)) (it requires access permissions to AKSW Subversion Repository).\n * Fuzzy reasoning service component\n * Review OWLAPI wrapping: the fuzzy reasoner is wrapped inside an OWLAPI interface but some methods are developed using a crisp reasoner (in fact only those fuzzy-specific methods were developed using a fuzzy reasoner). This has to be reviewed (e.g., some of the methods to be developed using the fuzzy reasoner 'getSuperClasses()' and 'getSubClasses()'). Regarding this ...\n * Performance tests: some performance test regarding OWLAPI-based methods execution for the fuzzy reasoner should be performed. If compared to crisp-based OWLAPI methods performance, could lead to propose (or not) the co-habitation of both kinds of reasoners (crisp and fuzzy).\n * Fuzzy learning component algorithm\n * It should be checked if this algorithm needs more changes in order to be adapted to fuzzy environments (right now only a small change when comparing the individual belonging to a class and to its parent class was changed -'FuzzyRhoDRDown.getClassCandidatesRecursive()'-).\n * Fuzzy trains example:\n * Extend test case adding more fuzzy definitions\n * More examples\n * Script to automatically populate ontology with fuzzy concepts (in order to generate different ontologies with different numbers of individual to do performance tests).\n * It could be usefull to use ((http://www.google.es/url?sa=t&source=web&cd=1&ved=0CBoQFjAA&url=http%3A%2F%2Fwww.cs.huji.ac.il%2F~danieb12%2FESWC'11%2520-%2520GRR%2520(Generating%2520Random%2520RDF).pptx&rct=j&q=grr%20eswc&ei=iFgATtnXLcj1sgbPjuW6DQ&usg=AFQjCNHq7K53UXbtFdnmXfWB54xaP-eIaw&cad=rja this)).\n * More realistic test case (shopping assistant?). A test case to show what does fuzzy ILP inference improves regarding crisp one would be great.\n * Future paper:\n * not to structure the paper regarding the new fuzzy DL-Learner components but to focus in the new fuzzy concepts (fuzzy measures, noise, etc.)\n * Reduce:\n * background / state of the art (just reference previous paper)\n * Extend:\n * State of the art in fuzzy ILP.\n * Fuzzy predictive accuracy should be better explained and, maybe, compared to its crisp equivalent. The literature regarding this measure should be review in order to link our formulas to already done works.\n * fPrecision and fRecall explanations should be extended.\n * noise factor explanation also needs to be further extended.\n * extend fuzzy trains ontology (see above comment on this). This could be the main contribution of this future paper regarding the previous one.\n * Add comparison with other fuzzy ILP tools.\nIt coulb be usefull to follow ((http://trowl.eu/ this)) work.\n===Work in progress (old)===\n * __**Examples definition**__\n * Fuzzy adaptation of the Michalsky's trains problem --> ((http://users.iit.demokritos.gr/~konstant/dload/Pubs/fuzz10.pdf paper)) and ((http://yadlr.svn.sourceforge.net/viewvc/yadlr/trunk/examples/trains/ partial dataset))\n * Fuzzy OWL 2 ontology:\n * ((http://dl-learner.org/JosueIglesias/files?get=fuzzyTrains_v0.owl fuzzyTrains_v0.owl)) (Fuzzy OWL version of the original dataset)\n * fuzzyTrains_v1.x.owl: \"my\" new version:\n * v1.0: Cars can be short, medium or long (fuzzy concepts) depending on their length (double)\n * This kind of association between numerical values (car's length) and a fuzzy class (short, medium or long cars) can be also apply, e.g., to the load carried by each car (being the load in kg. associated to light, medium or heavy load), to the number of wheels, to the number of links between cars, etc.\n * v1.1: Cars can have load (Triangular or Rectangular)\n * v1.2: Change properties (Train) hasFirstCar (Car) + (Car) isInFrontOf (Car) for just (Train) hasCar (Car) in order to make the example easier\n * Iris ?? --> http://archive.ics.uci.edu/ml/machine-learning-databases/iris/ + http://yadlr.svn.sourceforge.net/viewvc/yadlr/trunk/examples/iris/\n * Fuzzy Wine Ontology ?? --> http://webdiis.unizar.es/~fbobillo/presentations/URSW2008.pdf\n\n * __**Parallel execution of the OWLAPIreasoner (Pellet) and a fuzzyReasoner (fuzzyDL) (II)**__\n * no pos nor neg examples in fuzzy reasoning but \"truthDegree\" added\n * fuzzy accuracy developed for \"fuzzy F-measure\" and \"fuzzy predictive accuracy\"\n * noise support (to check, Jens?)\n\n * !!__**UNRESOLVED \"PROBLEMS\"**__!!:\n * I need to \"fuzzify\" FuzzyPosNegLPStandard.computeScore\n * Do I need to use FuzzyPosNegLPStandard.coveredNegativeExamplesOrTooWeak????\n * The Concept Generator (FuzzyCELOE) uses a crisp reasoner to obtain concepts ... do I need to fuzzify this??? --> I may need to change some ... levels (noise, accuracy, etc.)\n * I need to adapt the \"solutions\" output to offer fuzzy data (what does \"getFMeasureOrTooWeakExact\" do?)\n * When comparing in parallel cripAccuracy and fuzzyAccuracy they are not always the same (to be solved, important)\n\n * !!__**OTHER ISSUES\"**__!!:\n * find and \"typical\" example for fuzzy ILP (like the one of the trains for crisp ILP)\n * I'm actually trying to get these examples (Section IV a and b): http://users.iit.demokritos.gr/~konstant/dload/Pubs/fuzz10.pdf\n * it'b be great to be able to mix crip and fuzzy definitions in the KB/examples (e.g. \"Josue hasAge 32\" or \"Josue hasAge around30\")\n * fuzzy examples like in the \"close friend\" example ...\n * fuzzyDL does not support cardinality restriction concepts\n\n * !!__**EXTERNAL TOOLS BUGS**__!!:\n * fuzzyDL crash when reasoning (min-instance? item1.50-250 (or MediumSizeItem MediumPriceItem))\n * --> developers are informed and next version of fuzzyDL will solve this bug\n\n\nFirst changes from DL-Learner to fuzzyDL-Learner:\n * __**Parallel execution of the OWLAPIreasoner (Pellet) and a fuzzyReasoner (fuzzyDL)**__\n * IF individual.hasFuzzyType(concept) == 0 THEN individual.hasCrispType(concept) == FALSE\n * IF individual.hasFuzzyType(concept) > 0 THEN individual.hasCrispType(concept) == TRUE\n * both reasoners works in parallel, checking that they offer the same output (the same accuracy)\n * in class \"FuzzyDLReasonerManager\" I'm doing as in \"FastInstanceChecker\": decompose the description in order to be able to use the proper fuzzyDL tools\n * I had to create a \"FuzzyExample\" class to store name and membership of the fuzzy examples, so the variables positiveExamples and negativeExamples are changing all over the development (an also some methods dealing with them)\n * I defined FuzzyCELOE as:\n * public class FuzzyCELOE extends AbstractCELA implements FuzzyClassExpressionLearningAlgorithm \n * SOLVED PROBLEMS:\n * Does make sense to generate \"numerical concepts\" (e.g. hasPrice <= 1,25) for a fuzzy-based reasoning\n * -> OK: fuzzyCeloe.useDoubleDatatypes = false;\n * Time affects the output; I need to tune this\n * -> OK: fuzzyCeloe.maxExecutionTimeInSeconds = 0 & fuzzyCeloe.maxClassDescriptionTests = 10000;\n * fuzzyDL execution time:\n * fuzzyDL increases its execution time at each query\n * its developers are already having a look to this problem\n * it take ~7 minutes to solve a problem that Pellet solve in ~2 seconds :S\n * -> OK: I need to clone the fuzzy KB before each query to be solved\n * After executing \"ConfigJavaGenerator\" I always have to uptade:\n * public class FuzzyCELOEConfigurator extends RefinementOperatorConfigurator implements Configurator\n * I'd need to change the conf file parse to add fuzzy membership degree to the examples but ...\n * Then positive and negative examples would change from Set to Set but ...\n * Changing Set to Set doesn't work ...\n * -> OK: Finally, I'm creating FuzzyExample and Set (= String + double) and a new configuration option type: ObjectSetConfigOption. At reasoner level I extended Individual class --> FuzzyIndividual.\n\nI'm currently working on finding SW tools supporting fuzzy logic extensions to OWL ontologies (in order to later extend DL-Learner with fuzzy logic capabilities). After analyzing several tools, these seems the more suitable, updated, etc.:\n\n * __**FuzzyOWL**__: OWL ontology model fuzzy extension.\n * Based on OWL 2\n * Fuzziness is introduced by means of annotations (so FuzzyOWL ontologies can be read by any OWL 2 compliant tool, as OWL API)\n * Protege4.1 plug-in available (quite visual and interesting)\n * General parsers \"FuzzyOWL ontologies format\" --> \"fuzzy reasoners format\" are available. Already developed for:\n * fuzzyDL fuzzy logic reasoner\n * DeLorean fuzzy logic reasoner\n * Closed source code / can be freely used for non comercial applications\n * More information:\n * http://gaia.isti.cnr.it/~straccia/software/FuzzyOWL/index.html\n\n * __**fuzzyDL**__: DL reasoner supporting fuzzy logic reasoning\n * Closed source code / can be freely used for non comercial applications\n * Particular Java API (not OWL API compliant)\n * More information:\n * http://gaia.isti.cnr.it/~straccia/software/fuzzyDL/fuzzyDL.html\n\n * __**NOTES**__:\n * Crisp and fuzzy ontologies are differents (Pellet can not reason over fuzzyDL ontologies, and viceversa)\n\n\n===Some interesting papers===\n * Fuzzy FOIL: A Fuzzy Logic Based Inductive Logic Programming System\n * http://www.ruor.uottawa.ca/fr/bitstream/handle/10393/9621/MM15707.PDF?sequence=1\n * Section 7 has some quite interesting examples, pretty related what I would like to do using DL-Learner\n\n\n===fuzzyDL-Learner sketch===\nhttp://aksw.org/JosueIglesias/files?get=fuzzydllearner.jpg\n\n\n===fuzzyDL-Learner example===\n[taken from \"Fuzzy FOIL\" paper]\nhttp://aksw.org/JosueIglesias/files?get=fuzzydllearner_example.jpg\n\n\n===Open issues/questions===\n * [**SOLVED**] Should I start adding \"fuzzy support\" to any of the \"complex\" algorithms -refinement, refinement2, GP, etc.- or it would be better to start from the \"basic\" ones -brute force, random guesser, etc-? (I started modifying FastInstanceChecker and OWLAPIReasoner --> FuzzyFastInstanceChecker and FuzzyDLReasoner) \n * I start \"tunning\":\n * Learning Algorithm: CELOE --> FuzzyCELOE\n * Reasoner: OWLAPIReasoner --> FuzzyOWLAPIReasoner\n * [**SOLVED**] org.dllearner.reasoning.fuzzy.FuzzyDLReasonerManager class uses FuzzyOWL and fuzzyDL APIs; I add the .jar's to the build path without maven.\n * Two .jar libraries added to the AKSW Maven repository:\n * FuzzyDL.jar (fuzzyDL reasoner) and\n * fuzzyowl2fuzzydlparser (parser from Fuzzy OWL 2 ontologies to fuzzyDL reasoner format)\n * [**SOLVED**] I don't understand how DL-Learner gets those __numerical__ solutions #5 and #6 in this example:\n * ((http://aksw.org/JosueIglesias/files?get=fooditems.conf config file))\n * ((http://aksw.org/JosueIglesias/files?get=fooditems_v1.owl ontology))\n * ((http://aksw.org/JosueIglesias/files?get=fooditemsoutput.txt output))\n * It seems DL-Learner generates \"numerical concepts\" in order to find the range where most +examples are (e.g. hasPrice <= 1.2, etc.). Has this sense in a fuzzy-oriented ILP reasoner? (I don't think so)\n * -> OK: this has sense but (maybe) not for a fuzzy-based reasoning:\n * this option can be turned off --> fc.getConfigurator().setUseDoubleDatatypes(false);\n * [**SOLVED**] How does execution time affects DL-Learner output? (I got different solutions if, e.g., I add a delay 'in the middle' of the code)\n * -> OK: time execution checks can be turned off --> fc.getConfigurator().setMaxExecutionTimeInSeconds(0);\n\n-----------\n\n===About me===\nMy name is Josué and I'm a PhD student in Telecommunications Engineering at the Data Processing and Simulation Group at the Technical University of Madrid.\n\nMy research group have a broad background in sensor data acquisition, being my PhD studies focused on the area of context information management, that is, trying to manage in an intelligent way different kinds of data related to the user and his/her environment (location, position, activity, biometric information, weather, hobbies, social networks, etc.) in order to offer intelligent services to the user, adapted to his/her circumstances. Since my PhD beginning, I've been working with ontological models and tools (Protege, Pellet, SOUPA, OWLAPI, Jena, etc.). I'm lately quite interested in embedded tools for lightweight ontological management and reasoning, that is, I'm studying feasible ways to apply these kind of reasoning processes to common mobile devices. As context data acquired from sensor is inherently uncertain, I'm also quite interested in extending semantic reasoning with probabilistic/fuzzy concepts.\n\nI'll be here in Leipzig for four months (until end of June probably), trying to do my best in AKSW and also willing to meet German culture ;)\n\n===Contact information===\n * josue@grpss.ssr.upm.es\n * +491747450111\n * Skype: josuephd\n" . . . . "2010-07-05T14:40:13"^^ . "{{Include page=\"/Projects/OntoWiki/EventPluginArchitectureMenu\" divclass=\"floatbox\" nomark=\"1\"}}\n ATTENTION: THIS PAGE IS OUTDATED\n==Plugin Examples==\n\n{{toc}}\n\nThis page is an summary of well working OntoWiki-Plugins and its documentation. The are mainly developed at student projects. Therefore most of the detailed information especially design documents are in German language.\n\n===Some Documents===\n\n * ((http://ontowiki.net/Projects/OntoWiki/EventPluginArchitecture/PluginDevelopment/PluginExamples/files?get=ontowikiframeworksynpkm.pdf General description of the OntoWiki architecture)) (german)\n * ((http://ontowiki.net/Projects/OntoWiki/EventPluginArchitecture/PluginDevelopment/PluginExamples/files?get=entwurfsynpkm.pdf Description of the SynPKM plugin design)) (german)\n * ((http://ontowiki.net/Projects/OntoWiki/EventPluginArchitecture/PluginDevelopment/PluginExamples/files?get=mappluginentwurf.pdf Description of the Map plugin design)) (german)\n\n\n===SynPKM Plugin===\n\n * /Projects/OntoWiki/Plugins/synPKM\n\n===Map Meshup Plugin===\n\n * /Projects/OntoWiki/MapPlugin" . . . . "2011-08-03T13:28:26"^^ . "{{toc divclass=\"floatbox\"}}\n==How To Find Us==\n\nThe Department of Business Information Systems is currently located in the interim building of Leipzig University at ((http://maps.google.com/maps?f=q&source=s_q&hl=en&geocode=&q=Leipzig+in+Johannisgasse+26&sll=40.016598,-75.611812&sspn=0.009614,0.025706&ie=UTF8&ll=51.337047,12.385583&spn=0.007842,0.025706&z=16&iwloc=addr Johannisgasse 26)). You will find the offices of the AKSW research group on the 5th floor in the aisle on your left-hand side.\n\n\n===Directions===\n\n====By car:====\n * Motorway A9 (Berlin - Munich): Exit on Großkugel to the highway B6 or exit on Leipzig West to the Interstate B181, then follow directions to Leipzig's city centre (‘Innenstadt Leipzig’)\n * Motorway A38 (Göttingen - Leipzig): Exit on Kreuz Rippachtal to the highway B87, then follow directions to Leipzig's city centre (‘Innenstadt Leipzig’)\n * Motorway A14 (Nossen – Magdeburg): Exit on Leipzig Mitte to the highway B2 or exit on Leipzig Nordost to the Interstate B87, then follow directions to Leipzig's city centre (‘Innenstadt Leipzig’)\n\nFollow the city's inner ring road until Augustusplatz and turn into Grimmaischer Steinweg. Please use this ((http://maps.google.com/maps?f=d&hl=de&daddr=Johannisgasse+26,+Leipzig,+Germany route finder)) for more detailed directions to our offices. There are temporary parking options in and around Johannisgasse. Otherwise you could use the underground car park at Augustusplatz, which is within 10-minute walking distance to our offices.\n\n====By train:====\nIntercity and Intercity-Express trains connect Leipzig with almost all European cities. Take a look at the ((http://www.bahn.de/i/view/DEU/en/index.shtml German Railways)) website for planning your journey. \n\nThe office building at Johannisgasse 26 is not far away from Leipzig’s Main Station (800m, 10 min walk). Public transportation is available right in front of the station. You can get a taxi or catch tram 4, 7, 12 or 15 heading eastward to reach our offices. If taking the tram, get off at Johannisplatz, go down Nürnberger Street and take the first turn right into Johannisgasse. From here you can see the office building on the right-hand side within the first 50 metres.\n\n<#\n
    View Larger Map\n#>\n\n====By plane:====\nIt takes about 30 minutes by car to get from Leipzig-Halle Airport to the city centre. There are also direct trains from the airport to Leipzig’s Main Station. They leave every 30 minutes and take you to the city centre in about 15 minutes. To reach Johannisgasse 26, please follow the directions described above. \n\nIf there are no direct flights to Leipzig from your city, you can also reach Leipzig via these airports:\n\n * Berlin (about one-hour train ride to Leipzig / approx. 40 Euro one way),\n * From Berlin Tegel (airport code TXL) take the TXL bus to Berlin Hauptbahnhof main train station and the direct IC/ICE train to Leipzig\n * From Berlin Schönefeld (airport code SXF) take the SXF bus to Berlin Südkreuz train station and the direct IC/ICE train to Leipzig\n * Frankfurt/Main (about 3.5 hours train ride / approx. 70 Euro one way)\n * Hannover (about three-hours train ride / approx. 50 Euro one way). \n\nTrains depart frequently (mostly hourly) from these cities to Leipzig. Please check the schedule at ((http://bahn.de Deutsche Bahn)).\n\nSee also ((http://www.leipzig-halle-airport.de/en/index.html?newLanguage=en www.leipzig-halle-airport.de)) for more information.\n\n\n===Accommodation===\n\nLeipzig offers a variety of hotels, hostels and apartments. We have shortlisted a few hotels for you ((http://aksw.org/FindUs/files?get=hotels_august20101.pdf here)). A decent option right in the center and conveniently located between the train station and our office is ((http://www.motel-one.com/uk/hotels/leipzig.html Motel One)) (other than the name suggests its a modern, convenient and elegant hotel).\n\n\n===Address===\n\nLeipzig University\nFaculty of Mathematics and Computer Science\nInstitute of Computer Science\nDept. Business Information Systems\nJohannisgasse 26\n04103 Leipzig, Germany\n\nPhone: +49 (341) 97 32 310\nFax: +49 (341) 97 32 329\n\nEmail: ((mailto:aksw@informatik.uni-leipzig.de aksw@informatik.uni-leipzig.de))\n\n\n" . . . . "2010-08-25T11:32:19"^^ . "===Features===\n * detection of inconsistencies and unsatisfiable classes\n * efficient computation of problematic axioms (justifications)\n * fine-grained justifications, e.g. only showing the relevant parts of the axioms to support a minimal semantic repair\n * displaying impact of selected repair actions\n * enrichment of an ontology by learning definitions and super class axioms using machine learning\n * guides the user through potential consequences of adding those axioms\n * supports debugging as well as enriching very large knowledge bases available as SPARQL endpoints" . . . . "2010-08-25T11:32:46"^^ . "The following screencasts shows how to use the tool:\n**((http://dl-learner.org/files/screencast/ore/0.1/ore.htm Basic Screencast (0.1) ))**\n**((http://dl-learner.org/files/screencast/ore/0.2/ore.htm Inconsistencies in SPARQL Endpoints (ORE 0.2) ))**" . . . . "2010-08-25T11:33:23"^^ . "===~ChangeLog===\n * Version 0.2:\n * enhanced support for inconsistency detection in large knowledge bases available as SPARQL endpoints\n * based on OWL API 3 and Pellet 2\n * Version 0.1: initial release" . . . . "2012-05-13T17:06:14"^^ . "<#\n
    \n

    Stats2RDF

    \n\n

    Representing multi-dimensional statistical data as RDF using the RDF Data Cube Vocabulary

    \n

    \n\n
    \n\n#>\n\n{{toc}}\n\n=== Motivation === \nBiomedical statistical data is often published as Excel sheets. Thus they have the advantage of being easily readable by humans. However, they cannot be queried efficiently. Also it is difficult to integrate with other datasets, which may be in different formats. Our approach is to convert the data into a single data model - RDF. But in these biomedical datasets, a single statistical value is described in several dimensions. Thus a simple row-based transformation is not possible. Therefore, we used ((http://publishing-statistical-data.googlecode.com/svn/trunk/specs/src/main/html/cube.html The RDF Data Cube vocabulary)) for the conversion as it is designed particularly to represent multidimensional statistical data using RDF. \n\n=== Methodology === \n\nTransforming CSV to RDF in a fully automated way is not feasible as there may be dimensions encoded in the heading or label of a sheet. Therefore, we introduce a semi-automated approach as a plug-in in ((http://aksw.org/Projects/OntoWiki OntoWiki)). More information ((http://aksw.org/Projects/ReDDObservatory/OntoWiki_sCSV2RDFPlugin here)). Using this plug-in, a CSV file can be converted to RDF using the Data Cube Vocabulary. We used the WHO's ((http://apps.who.int/ghodata/ Global Health Observatory)) dataset as a first use case. It is primarily available as Excel sheets. We converted them to CSV files and then transformed them into RDF.\n\nThe following screenshot displays a GHO table configured for conversion into RDF when imported into the ~OntoWiki CSV import plug-in:\n\nhttp://redd.aksw.org/images/stats2rdf.png\n\n=== Results === \nAfter converting the data reported for the mortality and burden of disease in GHO, classified according to countries and region, we obtained an RDF dataset containing 3 million triples.\nFollowing is the example of a single statistical item, the death value of 1098, from the GHO dataset represented using the Data Cube vocabulary:\n\n%%(php)\neg:o1 a qb:Observation;\n qb:dataset eg:dataset-in1;\n eg:refArea Afghanistan;\n eg:contact 3010;\n eg:stat_pop 11605;\n eg:disease Tuberculosis;\n eg:gbdcode W0003;\n eg:death 1098.\n%%\n\n\n=== Further Information === \n * This is a ((https://docs.google.com/leaf?id=0B8Mh-RR0aBWQNDRjM2UyMmEtOTNlZC00ZDIwLTg5ZDMtMGZkYTc1YWVjNDRh&hl=en&authkey=CIr8_MYN short presentation)) describing the process of conversion of the CSV files to RDF using the ((http://sw.joanneum.at/scovo/schema.html SCOVO)) (Statistical Core Vocabulary) in ((http://aksw.org/Projects/OntoWiki?v=1atc OntoWiki)). SCOVO is an earlier version of the Data Cube Vocabulary and the conversion process is similar for both.\n * This is a ((https://docs.google.com/fileview?id=0B8Mh-RR0aBWQODU1ZmM3M2QtOGNiNi00YWY0LTkzYjctYmVlMzViMDRkNGI1&hl=en&authkey=CMeV1cMC position paper)) that was accepted for a presentation at the ((https://wiki.imise.uni-leipzig.de/Gruppen/OBML/Workshops/2010en Ontologies in Biomedicine and Life Sciences)) workshop held at Mannheim (Germany) from September 9 - 10, 2010.\n * This dataset is also part of the LODD datasets. Click ((http://esw.w3.org/HCLSIG/LODD/Data here)) for more details.\n \n=== Download === \nTo use the plug-in, you need to install ~OntoWiki ((https://github.com/AKSW/OntoWiki/wiki/GetOntowikiUsers via github)) and enable the extension by:\n\"cd ontowiki/extensions\" and \"git clone git://github.com/AKSW/csvimport.ontowiki.git csvimport\".\n\n((http://code.google.com/p/ontowiki/ OntoWiki)) and enable this extension.\nThe RDFized GHO files can be downloaded from ((http://db0.aksw.org/downloads/ghodata.zip here)). The original data is present ((http://apps.who.int/ghodata/ here)).\n\n===Contact==={{a name=\"Contact\"}}\n{{vcard name=\"sn\" value=\"Zaveri\"}}\n" . . . . "2011-01-05T11:08:51"^^ . "==Overview==\n\nThe ORE (**O**ntology **R**epair and **E**nrichment) tool allows for knowledge engineers to improve an OWL ontology by fixing inconsistencies and making suggestions for adding further axioms to it. \n\n**Ontology Debugging:** ORE uses OWL reasoning to detect inconsistencies and satisfiable classes. State-of-the-art methods are then used to detect the most likely sources for the problems. In a simple process, the user can create a repair plan to resolve a problem, while maintaining full control over desired and undesired inferences.\n\n**Ontology Enrichment:** ORE uses the DL-Learner framework to suggest definitions and super classes for existing classes in the knowledge base. This works if instance data is available and can be used to detect potential problems and harmonise schema and data in the knowledge base.\n\n**Future Work:** In future versions, we also aim to support the detection of more modelling problems including non-logical errors. We will also extend support for knowledge bases available as SPARQL endpoints (in contrast to OWL files) and Linked Data.\n\n<#

    Click to show full size image.

    #>" . . . . "2010-09-06T13:22:45"^^ . "====Requirements====\n\nJava 6 is required. (All other libraries are included in the release.)\n\n====Installation====\n\nNo further installation is necessary. Just download and extract ORE.\n\n====Running Instructions====\n\nLinux (and other systems)\n\nMake sure the file \"ore\" is executable. You can run it on the command line either individually or \nfollowed by the name of the ontology to process, e.g. \"./ore examples/koala.owl\".\n\nWindows:\n\nRun \"ore.bat\" either individually or followed by the name of the ontology to process,\n e.g. \"ore.bat examples/koala.owl\"." . . . . "2010-09-06T13:24:37"^^ . "== Architecture ==\n\n//ORE is currently undergoing architectural changes and will be adapted to fit the goals of the ((http://lod2.eu LOD2 EU project)). Information about its architecture will be published in a few weeks.//\n" . . . . "2010-09-06T13:27:50"^^ . "== Developers ==\n\n{{vcard name=\"sn\" value=\"Bühmann\"}}\n{{vcard name=\"cn\" value=\"Jens Lehmann\"}}\n" . . . . "2010-09-06T14:51:59"^^ . "===ORE debugging view===\n((http://ore-tool.net/projects/ORE/Screenshots/files?get=ore_debugging_view.png ORE debugging view))\n\n===ORE learning view===\n((http://ore-tool.net/projects/ORE/Screenshots/files?get=ore_learning_view.png ORE learning view))" . . . . "2012-05-02T23:05:19"^^ . "{{vcard name=\"sn\" value=\"Khalili\"}}\n---------------------------------------------------------\n**Active Project(s):**\n((http://aksw.org/Projects/SlideWiki SlideWiki)): A Collaborative Platform for Building Interactive Online Presentations\n((http://aksw.org/Projects/RDFaCE RDFaCE)): RDFa Content Editor\n---------------------------------------------------------\n**Drafts:**\n * Ali Khalili, Sören Auer, Darya Tarasova, Ivan Ermilov: ((http://svn.aksw.org/papers/2012/EKAW_SlideWiki/public.pdf SlideWiki: Elicitation and Sharing of Corporate Knowledge using Presentations))\n * Ali Khalili, Sören Auer: ((http://svn.aksw.org/papers/2011/journal_SemanticContentAuthoring/public.pdf User interfaces for semantic content authoring: A systematic literature review))\n * Sören Auer, Ali Khalili, Darya Tarasova, Ivan Ermilov, Timofey Ermilov: ((http://svn.aksw.org/papers/2012/WWW_Slidewiki/public.pdf WikiApp - Engineering of Domain-specific Wiki Applications))\n\n**Publications:**\n\n * Ali Khalili, Sören Auer, Daniel Hladky:((http://svn.aksw.org/papers/2012/COMPSAC2012_RDFaCE/public.pdf The RDFa Content Editor - From WYSIWYG to WYSIWYM)) , COMPSAC 2012\n * Ali Khalili, Sören Auer:((http://svn.aksw.org/papers/2012/ESWC_RDFaCE-Lite/public.pdf RDFaCE-Lite: a WYSIWYM editor for user-friendly semantic text authoring)) , ESWC 2012 demo track\n * //Ali Khalili//, Shahriar Mohammadi, \" Semi-automatic Creation of Enterprise Mashups Using Semantic Descriptions \", 2010 IEEE Asia-Pacific Services Computing Conference, 2010\n * Shahriar Mohammadi, //Ali Khalili//, Sarah Ashoori, \" Using an Enterprise Mashup Infrastructure for Just-in-Time Management of Situational Projects\", ICEBE , pp. 3-10, 2009 IEEE International Conference on e-Business Engineering, 2009\n * //Ali Khalili//, Shahriar Mohammadi, \"Using Logically Hierarchical Meta Web Services to Support Accountability in Mashup Services\", apscc,pp.410-415, 2008 IEEE Asia-Pacific Services Computing Conference, 2008 \n * //Ali Khalili//, Ali Habibi Badrabadi, Farid Khoshalhan, \"A Framework for Distributed Market Place Based on Intelligent Software Agents and Semantic Web Services\" , services-2,pp.141-148, 2008 IEEE Congress on Services Part II (services-2 2008), 2008 \n * Shahriar Mohammadi, //Ali Khalil//i, \"A Semantic Web Service-Oriented Model for Project Management\" , citworkshops,pp.667-672, 2008 IEEE 8th International Conference on Computer and Information Technology Workshops, 2008 \n" . . . . "2011-10-05T05:29:03"^^ . "This page was moved here permanently:\nhttp://nlp2rdf.org" . . . . "2010-02-23T11:20:06"^^ . "==Workshop am 24.02.2010==\n\n===Teil 1 - OWL, Vokabulare===\n\n * RDF-Schema \n * OWL\n * Etablierte Vokabulare: SKOS, Dublin Core, FOAF\n\n===Teil 2 – Installation von Software===\n\n * Protégé\n * OntoWiki, auf dem Server der Lecos\n * mit Zend DB /Virtuoso folgt zum nächsten Termin\n\n===Weitere Terminvorschläge===\n\nJeweils Mittwochs von 10-15 Uhr\n\n\n * 10.03.2010\n * 17.03.2010\n * 31.03.2010\n" . . . . "2010-03-09T12:43:06"^^ . "<#\n
    \n

    Semantic Pingback

    \n

    Adding a social dimension to the Linked Data Web.

    \n

    The Semantic Pingback mechanism is an extension of the well-known Pingback method, a technological cornerstone of the blogosphere, thus supporting the interlinking within the Data Web.

    \n

    Download standalone Pingback Server

    \n
    \n
    \n#>" . . . . "2010-10-14T14:57:52"^^ . "{{toc divclass=\"floatbox\"}}\n\n==GI 2010 Workshop on \"Web Science\"==\n\n//co-located with the annual meeting of the German Society for Computer Science (GI) 2010 ((http://www.informatik2010.de/))//\n\nWeb science is often referred to as the \"science of decentralized information systems\".\nWhile novel technologies such as semantic web, web services, and cloud computing are germane to the broad proliferation of Web technologies, we also need to understand phenomena of the Web in the small as well as in the large, in order to retain its usefulness and benefit to people. This is in the center of attention of Web science and includes besides the mentioned technological approaches, research related to online communities, information diffusion on the Web, Web governance, global network structures beyond the individual communities on the Web, growth analysis, incentive and monetization systems.\n\nBecause the web itself is socially embedded a particular focus of this first GI workshop on Web Science are social computing applications, such as Wikipedia, Facebook, or del.icio.us, which are analysed with regard to the complex interdependencies between constraints imposed by the technical system as well as with regard to their use in social actions and interactions under varying social contexts. Understanding dynamics and evolution of these systems, as they depend on inherent social and informational structures, is of particular interest, because it is the dynamics of such communities that determines their final success or failure. In order to analyze social computing applications, interplay between aspects of computer science, for example computational network analysis, visualization techniques, graph theoretic models, semantic web technologies, and machine learning techniques, with social science and psychology is required. \n\nIn this interdisciplinary workshop we are aiming to bridge the gap between paradigms and encourage interdisciplinary collaborations as well as advance and deepen our understanding of web science. Joint efforts are needed to take advantage of the state-of-the-art research from multiple disciplines, such as computer science, information systems, sociology, and psychology. Moreover, this workshop provides a platform for researchers and practitioners to exchange preliminary results, new concepts and methodologies in this area.\n\n===Topics of interest ===\nTopics of interest include but not limited to:\n\n * Web Governance incl. Provenance, Licensing, Data Security, Access Control\n * Open Knowledge ecosystems on the Web, such as Open Governmental Data, Open Scientific Data\n * Information quality assessment\n * Quality, coherence and user interaction on the Linked Data Web\n * Social computing applications such as collaborative filtering, community-based information retrieval and recommendation, collaborative bookmarking, tagging and multi-agent systems\n * Static and dynamic models of Web structure and Web growth\n * Analysis of network structures within and beyond individual communities on the Web\n * Incentive and monetization systems\n * Information diffusion on the Web,\n * Web and Web application governance,\n * Novel visualisation techniques for Web related data \n * Integrating computational network analysis and semantic web techniques, for example to enhance the mainly structure-based network analysis by semantic information \n * Case studies of communities such as Wikipedia, Facebook, Twitter, World of Warcraft, open source software as well as empirical findings in social computing-related applications\n\nIn particular, we aim at collecting a set of requirements, architectural styles and metaphors for Web science.\nIt is the target of such terminology and figures to build bridges of understanding between the different communities serving the need to appropriately //analyse// and //develop// social Web applications.\n\n===Where and when===\n\nTuesday, 09/28/2010, 2pm to 5:30pm, S 21\n\n===Program===\n\n//Session 1// \n14:00 \nWelcome/Opening Remarks \n14:00 - 15:00 \n((http://www.slideshare.net/mstrohm/social-computationofemergentnetworksonusergeneratedcontent \"Social Computation of Emergent Networks on User-Generated Content\")) (Markus Strohmeyer)\n15:00 - 15:30 \n((http://blog.ag-nbi.de/wp-content/uploads/2010/09/webminingquality.pdf \"Towards Quality Measures for Web Network Extraction\")) (Robert Tolksdorf)\n\n15:30-16:00 Uhr: Break \n\n//Session 2//\n16:00 - 16:30\n((http://aksw.org/WebScienceWorkshop/files?get=webscitalk.pdf \"Group Evolution Patterns in World of Warcraft\")) (Christian Thurau and Christian Bauckhage)\n16:30 - 17:00 \n((http://aksw.org/WebScienceWorkshop/files?get=2010workshopwebscienceleipzig.pdf \"Estimating the relevance of search results in the Culture-Web: a study of semantic distance measures\")) (Laura Hollink and Mark van Assem)\n17:00 - 17:30 \n((http://aksw.org/WebScienceWorkshop/files?get=wp1_s_p_1.pdf \"Proposal: Standardized Vectorial Resource Descriptors on the Web\")) (Wolfgang Orthuber and Stefan Dietze)\n17:30 \nConcluding remarks\n\n===Contact and Organisation===\n\nSören Auer (auer@informatik.uni-leipzig.de), AKSW/Institute for Computer Science, University of Leipzig\nClaudia Müller-Birn (clmb@cs.cmu.edu), Institute for Software Research, Carnegie Mellon University\nSteffen Staab (staab@uni-koblenz.de), Institute for Web Science and Technologies, University of Koblenz-Landau\n\n\n===Program committee===\n\nChristian Bauckhage, International Center for Information Technology (B-IT), Bonn-Aachen \nUlrike Cress, Knowledge Media Research Center, Tuebingen\nDaniel Dietrich, Open Data Network\nRainer Fröse, IFM-Geomar / FishBase \nAndreas Geyer-Schulz, Institute of Technology Karlsruhe\nJonathan Gray, Open Knowledge Foundation \nDaniel Hladky, Ontos AG \nAndreas Hotho, University of Würzburg\nStefanie Lindstaedt, Graz University of Technology/Know-Center, Graz \nUlf Morgenstern, Historisches Seminar Uni Leipzig \nWolfgang Nejdl, University of Hanover\nChristian Stegbauer, Johann Wolfgang Goethe-Universität, Frankfurt am Main \nYork Sure, GESIS-Leibniz Institute for the Social Sciences, Bonn\nRobert Tolksdorf, Freie Universität Berlin \n\n" . . . . "2011-10-05T11:13:12"^^ . "{{feed title=\"Latest LGD news\" divclass=\"floatbox\" url=\"http://blog.aksw.org/category/projects/linked-geo-data/feed/\" max=\"5\"}}\n<##>\n\n==~LinkedGeoData==\n\nhttp://aksw.org/Projects/LinkedGeoData/files?get=linkedgeodatabrowserscreenshotleipzig.png\n\n===Background===\nSpatial data is crucial for the Semantic Data Web in order to interlink geographically linked resources.\nThe ((http://OpenStreetMap.org OpenStreetMap project)) collects, organizes and publishes geo data the wiki way. Currently the 80.000 OpenStreetMap users collected data about 22.000.000km ways (roads, highways etc.) on earth. 25.000km are added daily. The OpenStreetMap database also contains a vast amount of structured information about points-of-interest such as for example shops, amenities, sports venues, businesses, touristic and historic sights.\n\n===Aim===\n\nThe goal of this project is to publish OSM geo data, interlink it with other data sources and provide efficient means for browsing and authoring. We aim at working as closely as possible with both the OSM and LOD communities.\n\n===Components===\nThe project currently consists of three components:\n * **OpenStreetMap data extraction** currently works on the basis of OSM database dumps. A live-sync module keeps the data in our SPARQL endpoints up-to-date.\n * ((http://linkedgeodata.org/browser/ LinkedGeo Data browser)) is based on Javascript widgets, which can display the data from the LinkedGeoData SPARQL endpoints. Support for endpoints of other projects in the works.\n * A Server providing a Linked Data Interface and a REST API, that grant access to RDFized data based on a (relational) OSM database.\n\nThe data can be accessed via ((http://linkedgeodata.org/Datasets|Downloads)), ((http://linkedgeodata.org/OnlineAccess/SparqlEndpoints|SPARQL Endpoints)), and the ((http://linkedgeodata.org/OnlineAccess/RestApi|REST API)).\n\n====Publications===\n * Sören Auer, Jens Lehmann, Sebastian Hellmann: ((http://www.informatik.uni-leipzig.de/~auer/publication/linkedgeodata.pdf|LinkedGeoData - Adding a Spatial Dimension to the Web of Data.)) In Proceedings of 8th International Semantic Web Conference (ISWC 2009).\n * Claus Stadler, Jens Lehmann, Konrad Höffner, and Sören Auer: ((http://www.semantic-web-journal.net/content/linkedgeodata-core-web-spatial-open-data|LinkedGeoData: A Core for a Web of Spatial Open Data)) In: Semantic Web Journal //to be published in 2012//\n\n===Further information===\n\nFor further information about the project please go to: http://linkedgeodata.org\n\n===Contributors===\n\n * ((/SoerenAuer Sören Auer))\n * ((/JensLehmann Jens Lehmann))\n * ((/SebastianHellmann Sebastian Hellmann))\n * ((/ClausStadler Claus Stadler))\n * ((/MichaelMartin Michael Martin))" . . . . "2011-07-11T10:32:12"^^ . "{{feed title=\"Latest Triplify news\" divclass=\"floatbox\" url=\"http://blog.aksw.org/category/projects/triplify/feed/\" max=\"5\"}}\n==~Triplify==\n\n<##>\n\n===Background===\nTriplify provides a building block for the “semantification” of Web applications. Triplify is a small plugin for Web applications, which reveals the semantic structures encoded in relational databases by making database content available as RDF, JSON or Linked Data.\n\nTriplify is very lightweight: It consists of only a few files with less than 500 lines of code. For a typical Web application a configuration for Triplify can be created in less than one hour and if this Web application is deployed multiple times (as most open-source Web applications are), the configuration can be reused without modifications.\n\nTriplify makes Web applications easier mashable and lays the foundation for next-generation, semantics-based Web searches.\n\n====Publications===\n * Sören Auer, Sebastian Dietzold, David Aumueller, Jens Lehmann, Sebastian Hellmann: [[http://www2009.eprints.org/63/|Triplify - Light-weight Linked Data Publication from Relational Databases.]] In Proceedings of Semantic Data Web Track of 18th International World Wide Web Conference (WWW 2009), April 20th-24th 2009, Madrid, Spain.\n\n===Further information===\n\nFor further information about the project please go to: http://triplify.org\n\n===Contributors===\n\n * ((/SoerenAuer Sören Auer))\n * ((/SebastianDietzold SebastianDietzold))\n * ((http://dbs.uni-leipzig.de/person/david_aumueller David Aumueller))\n * ((/JensLehmann Jens Lehmann))\n * ((/SebastianHellmann Sebastian Hellmann))\n" . . . . "2009-07-10T20:17:34"^^ . "===Developing the xOperator further===\n\n\n====Factoring the Sparql over XMPP component out.====\n\n\n\n====Adoption to a use case scenario: Sharing information in a group====\n\nthe xOperator shares metadata of papers over a social network. Researches, that are in the same group, can search and view the papers of the other resarchers.\n\n\nRequires: \n\n * access control only for a group\n * File transfer by xmpp" . . . . "2010-02-05T11:32:26"^^ . "{{toc divclass=\"floatbox\"}}\n\n==Job Offers==\n\nFor collaborative research projects in the area of Linked Data technologies and Semantic Web the research group Agile Knowledge Engineering and Semantic Web (AKSW) at Universität Leipzig opens positions for:\n\n===1 Postdoctoral Researcher (TV-L E13/14)===\n\nThe ideal candidate holds a doctoral degree in Computer Science or a related field and is able to combine theoretical and practical aspects in her/his work. The candidate is expected to build up a small team by successfully competing for funding, supervising doctoral students, and collaborating with industry. Fluent English communication and software technology skills are fundamental requirements. The candidate should have a background in at least one of the following fields:\n\n * semantic web technologies and linked data\n * knowledge representations and ontology engineering\n * database technologies and data integration \n * HCI and user interface design for Web content \n\nThe position starts as soon as possible, is open until filled and will be granted for initially two years with the possibility for extension.\n\n\n===2 Doctoral Students (50% TV-L E13 or equivalent grant)===\n\nThe ideal candidate holds a MS degree in Computer Science or related field and is able to consider both theoretical and practical implementation aspects in her/his work. Fluent English communication and programming skills are fundamental requirements. The candidate should have experience and commitment to work on a doctoral thesis in one of the following fields:\n\n * semantic web technologies and linked data\n * knowledge representations and ontology engineering\n * database technologies and data integration \n * HCI and user interface design for Web content \n\nThe position starts as soon as possible, is open until filled and will be granted for initially one year with an extension to overall 3 years.\n\n===Student Research Assistants===\n\nPlease see: http://bis.informatik.uni-leipzig.de/de/OffeneStellen/\n\n===How To Apply===\n\nExcellent candidates are invited to apply with:\n * Curriculum vitae and copies of degree certificates/transcripts,\n * Writing samples/copies of relevant scientific papers (e.g. thesis),\n * Letters of recommendation. \n\nPlease send your application in PDF format indicating in the subject 'Application for Doctorate/PostDoc position‘ to SoerenAuer. General inquiries can be also directed to NadineJaenicke.\n\n===Further Information===\n\nApplicants will be embedded into an innovative and social ((/Team team)), working on successful research, community and open-source projects such as ((/projects/DBpedia DBpedia)), ((/projects/OntoWiki OntoWiki)) and ((/projects/DL-Learner DL-Learner)).\n\n((http://www.leipzig.de Leipzig)), the home of AKSW, is the largest city in eastern Germany, combines a high standard of living with lowest expenses of major German cities. Leipzig is well connected internationally (international Airport and ICE high-speed rail hub), and has rich and lively cultural, scientific and economic scenes.\n\nInformation about the salary scheme of German public sector, which applies to the positions can be found at: http://oeffentlicher-dienst.info/tv-l/ost/" . . . . "2009-08-17T18:57:58"^^ . "{{Include page=\"/Projects/DLLearner/Menu\" divclass=\"floatbox\" nomark=\"1\"}}\n==OntoWiki Plugin Page==\nThe OntoWiki DL-Learner plugin allows users to learn equivalence and super class axioms based on the instance data in the knowledge bases loaded in OntoWiki. It integrates seamlessly via the OntoWiki plugin mechanism.\n\n===How does it work?===\nYou can access the functionality of the plugin via a context menu of classes in OntoWiki. (TODO: small screenshot) If you click on a class and then select \"Learn Equivalent Class Expressions\", then the knowledge base is transferred to DL-Learner, which analyses the instances of the class. Say your class is called \"customer requirement\". An equivalent class could then be (depending on your data) \"is created by some customer\". This is called an ((http://www.w3.org/TR/owl2-syntax/#Class_Expressions OWL 2 Class Expression)), which is displayed in its ((http://www.w3.org/TR/owl2-manchester-syntax/ Manchester Syntax)). DL-Learner usually offers some of those suggestions and you can accept one of those. If you accept a suggestion, it is added to your knowledge base and can be used by reasoners for querying, consistency checking, or as an additional documentation of the purpose of a class.\n\n===Features===\n * learns definition and super class axioms based on existing instance data in an ontology\n * seamless integration through use of OntoWiki plugin mechanism\n * based on DL-Learner Machine Learning framework to generate suggestions\n * use of efficient and sophisticated machine learning algorithms\n * can handle cases where an ontology is already damaged, i.e. adding the desired axiom renders the ontology inconsistent - in this case it displays the instances causing inconsistency\n\n===Screenshot===\nTODO\n\n===Authors===\n * Sebastian Dietzold\n * Christian Kötteritzsch\n * Jens Lehmann\n * Vu Duc Minh\n * Maria Moritz\n\n===Contact===\nIf you have any questions or comments, please contact ((http://jens-lehmann.org me))." . . . . "2009-01-27T14:37:36"^^ . "==~WK-Potential Technologieplattform ~OntoWiki - Projekt Kick-off Meeting==\n\n20. Januar: ((http://www.mml-leipzig.de/index.php?id=38&L=1 Mediencampus Villa Ida)) ((http://maps.google.com/maps?f=q&hl=en&geocode=&q=Poetenweg,+Gohlis-S%C3%BCd+04155+Leipzig,+Leipzig,+Saxony,+Germany&sll=40.016598,-75.611812&sspn=0.009877,0.02605&g=Poetenweg,+Gohlis-S%C3%BCd+04155+Leipzig,+Leipzig,+Saxony,+Germany&ie=UTF8&z=16&iwloc=addr Karte))\n\n===Teilnehmer===\n\n* **Projektträger Jülich (PtJ)**: Gabriele Trahms\n* **Netresearch**: Thomas Fleck, Christian Weiske\n* **Ebrosia**: Rüdiger Kleinke, Mathias Lieber\n* **BI**: Jürgen Schubert, Tobias Gruß, Michael Zipfel\n* **Uni Leipzig/AKSW**: Sören Auer, Sebastian Dietzold, Michael Martin, Jörg Unbehauen, Norman Heino\n\n===Agenda===\n\n * 10:00-11:00 ((http://aksw.org/Events/2009/WKPotentialKickOff/files?get=saproject_overview.pdf Projekt Überblick)) (Sören Auer - Head AKSW, Universität Leipzig)\n * 11:00-12:00 **Anforderungen und OntoWiki Anwendungsszenarien**\n * ((http://aksw.org/Events/2009/WKPotentialKickOff/files?get=tfnetresearch.pdf Netresearch)) (Thomas Fleck)\n * ((http://aksw.org/Events/2009/WKPotentialKickOff/files?get=tgbi.pdf BI Business Intelligence)) (Tobias Gruß)\n * Ebrosia (Rüdiger Kleinke)\n * 12:00-13:00 **Mittagspause im Restaurant & Bistro CAMPUS**\n * 13:00-14:00 **OntoWiki Technologieplattform** (Sebastian Dietzold, AKSW)\n * 13:00 - 13:30 ((http://aksw.org/Events/2009/WKPotentialKickOff/files?get=sdontowikiwpkkickoff.pdf OntoWiki - ein visuelles semantisches Wiki)) (Sebastian Dietzold)\n * 13:30 - 14:00 ((http://aksw.org/Events/2009/WKPotentialKickOff/files?get=nhontowikiextensions.pdf Zend & OntoWiki Application Framework)) (Norman Heino)\n * 14:00-14:30 ((http://aksw.org/Events/2009/WKPotentialKickOff/files?get=saproject_overview.pdf Projektabgrenzung OntoWiki WK-Potential / OntoWiki FP7-SME)) (Sören Auer, AKSW)\n * 14:30-15:00 **Kaffee**\n * 15:30-17:00 **Nächste Schritte, Projekt Infrastruktur, Öffentlichkeitsarbeit/Planung des Leipzig Semantic Web Day, etc.**\n" . . . . "2010-07-05T14:41:33"^^ . " ATTENTION: THIS PAGE IS OUTDATED\n==Erfurt Data Structures==\n\n===Statements===\nStatements are kept in ((http://n2.talis.com/wiki/RDF_PHP_Specification RDF/PHP format)) internally\n\n===SPARQL Results===\nCurrent:\n%%(php)\n$sparqlResult = array(\n array(\n 'var1' => 'value 1', \n 'var2' => 'value 2'\n )\n)\n%%\n\nGoal:\n%%(php)\n$sparqlResult = array(\n array(\n 'var1' => array(\n 'literal' => 'value 1', \n 'lang' => 'en' \n ), \n 'var2' => array(\n 'uri' => 'http://example.com/r1'\n )\n ) \n)\n%%\n" . . . . "2009-05-15T12:43:01"^^ . "<#
    \n

    \n

    \n

    \n

    \n\n

    #>\n\n==Leipziger Semantic Web Tag (29. April)==\n{{toc from=\"h2\"}}\n\nSemantische Technologien ziehen mehr und mehr in Web- und Unternehmensanwendungen ein. Mit der Arbeitsgruppe AKSW der Universität Leipzig gibt es ein Team in der Region Halle-Leipzig, welches an zentralen Bausteinen für das semantische Daten-Web mitwirkt. Dazu gehören u.a. das Wikipedia-Wissensextraktions-Projekt ((http://DBpedia.org DBpedia)), das Semantifizierungs-Plugin für Webanwendungen ((http://triplify.org Triplify)) und das semantische Daten Wiki ((http://www.ontowiki.net OntoWiki)).\n\nGemeinsam mit den Unternehmen ((http://www.netresearch.de Netresearch)), ((http://www.bi-web.de Business Intelligence GmbH)) und ((http://www.ebrosia.de Ebrosia)) arbeitet die Universität Leipzig in den nächsten beiden Jahren daran soziale, semantische Anwendungen in Intranet, Internet und E-Commerce-Anwendungen zu integrieren. Ziel des Projektes ist es darüberhinaus Innovationen im Umfeld semantischer Technologien als Wettbewerbsvorteil für Unternehmen der Region zu etablieren. Dazu sind umfassende Wissens- und Technologietransfer Vorhaben angedacht.\n\nDer Semantic Web Day lädt interessierte Unternehmen ein, die Potentiale semantischer Technologien kennen zulernen.\n\n===News===\n{{feed url=\"http://blog.aksw.org/feed/?tag=lswt\"}}\n\n===Wo und Wann===\n<#
    \n\n\n
    #>\n\nOrt: ((http://www.mml-leipzig.de/index.php?id=38 Mediencampus Villa Ida)) ((http://maps.google.com/maps?f=q&hl=en&geocode=&q=Poetenweg,+Gohlis-S%C3%BCd+04155+Leipzig,+Leipzig,+Saxony,+Germany&sll=40.016598,-75.611812&sspn=0.009877,0.02605&g=Poetenweg,+Gohlis-S%C3%BCd+04155+Leipzig,+Leipzig,+Saxony,+Germany&ie=UTF8&z=16&iwloc=addr Karte))\n\nDatum und Zeit: **29. April 2009, 9-18 Uhr**\n\nAnmeldung: ((http://de.amiando.com/semantic.html Amiando)) (15 Euro Schutzgebühr, umfasst auch Mittagsimbiss und Pausenversorgung)\n\n\n===Programm===\n\n**Morgens (9:00-10:30 Uhr): Semantische Basistechnologien**\n\n * **Vision und Technologien des semantischen Daten Web**, Sören Auer (AKSW) ((http://aksw.org/Events/2009/LeipzigerSemanticWebDay/files?get=soeren_auer_introduction.pdf Folien))\n * **Semantische Suchtechnologien**, Michael Schroeder (Transinsight ~GmbH) ((http://aksw.org/Events/2009/LeipzigerSemanticWebDay/files?get=michaels_leipzig_semantic_auer_2009small.pdf Folien))\n * **DBpedia - ein Kristallisationspunkt für das Daten Web**, ((http://bis.informatik.uni-leipzig.de/SebastianHellmann Sebastian Hellmann)) (AKSW) ((http://aksw.org/Events/2009/LeipzigerSemanticWebDay/files?get=lswt_dbpedia.odp Folien))\n\n**Kaffeepause (10:30-11:00)**\n\n**Vormittags (11:00-12:30 Uhr): Semantische Basistechnologien II**\n * **Semantische (Daten) Wikis und ~OntoWiki**, ((http://bis.informatik.uni-leipzig.de/SebastianDietzold Sebastian Dietzold)) (AKSW) ((http://aksw.org/Events/2009/LeipzigerSemanticWebDay/files?get=semantischedatenwikis.pdf Folien))\n * **Semantische Portale mit Topic Maps**, Lutz Maicher (Topic Maps Lab) ((http://aksw.org/Events/2009/LeipzigerSemanticWebDay/files?get=lutz_maicher.pdf Folien))\n * **RDF Unterstützung in Oracle 11G**, Börtecin Ege (Consultant und XING Semantic Web Gruppe)\n * **loomp - Semantische Inhalte mit einem Klick**, Markus Luczak-Rösch (Freie Universität Berlin) ((http://aksw.org/Events/2009/LeipzigerSemanticWebDay/files?get=20090429loompleipzigsemwebday.pdf Folien))\n\n**Mittagspause (12:30-13:30 Uhr)**\n * Imbiss und Getränke stehen bereit\n\n**Nachmittag (13:30-15:00 Uhr): Anwendungsszenarien und Einsatzpotentiale**\n\n * **Semantisches Content-Management für die Tourismusbranche**, Thomas Fleck (Netresearch ~GmbH & Co. KG) und Jens Oellrich (((http://www.tourismus-zukunft.de Tourismuszukunft))) ((http://aksw.org/Events/2009/LeipzigerSemanticWebDay/files?get=thomas_fleck.pdf Folien))\n * **Wissensmanagement mit semantischen Unternehmens-Wikis - eine Notwendigkeit in kritischen Projektphasen**, Daniel Hansch (ontoprise ~GmbH) ((http://aksw.org/Events/2009/LeipzigerSemanticWebDay/files?get=hansch_smw.pdf Folien))\n * **Semantische Nachrichtenaufbereitung - Erfahrungsbericht aus Kundenprojekten**, Daniel Hladky (Ontos AG) ((http://aksw.org/Events/2009/LeipzigerSemanticWebDay/files?get=daniel_hladky_semantische_nachrichtenaufbereitung.pdf Folien))\n * **Anwendung semantischer Technologien im Jobmixer Karriere-Portal**, Marco Erbe (Inaudito ~GmbH)\n\n**Kaffeepause (15:00-15:30)**\n\n * **Der Professorenkatalog der Universität Leipzig**, Thomas Riechert (AKSW) ((http://aksw.org/Events/2009/LeipzigerSemanticWebDay/files?get=vortragprofkat.pdf Folien))\n * **Semantisches Content-Management für den Gas- und Energiemarkt**, Tobias Gruß (Business Intelligence ~GmbH)\n\n**Stand-Up Präsentationen, Lightning Talks, Paneldiskussion (15:30-17:00 Uhr)**\n * Jeder Teilnehmer kann hier einen 2-minütigen Spontanvortrag (mit max. 3 Slides oder einem kurzen Web-Demo) halten\n * Für das Ende der Veranstaltung ist eine moderierte Diskussionsrunde und ein get together geplant.\n * Sebastian Hellmann - Vorstellung ((http://www.slideshare.net/rumito/virtuoso-universal-server-overview-presentation Virtuoso Universal Server))\n===Vision===\nAufbauend aus den an diesem Tag geknüpften Kontakten hoffen wir informelle Netzwerke zu bestimmten Themen zu knüpfen (z.B. semantisches Content-Management, semantische Webapplikationen oder semantische Unternehmensanwendungen). Diese werden sich in regelmäßigen Abständen zum informellen Austausch oder auch konkreten Technologieworkshops zusammenfinden. Der Leipziger Semantic Web Tag wird darüberhinaus jährlich als feste Veranstaltung für die Semantic Web Gemeinde in der Region Mitteldeutschland etabliert." . . . . "2009-12-13T17:14:45"^^ . "{{foafcard sparql=\"http://trunk.ontowiki.net/service/sparql\" update=\"http://trunk.ontowiki.net/service/update\" graph=\"http://showcase.ontowiki.net/\" literal=\"Seebi\"}}\n\n{{publications sparql=\"http://trunk.ontowiki.net/service/sparql\" update=\"http://trunk.ontowiki.net/service/update\" graph=\"http://publications.aksw.org/\" literal=\"Seebi\"}}\n" . . . . "2010-05-17T14:29:13"^^ . "<#\n#>\n\n==Leipziger Semantic Web Tag (2010)==\n\n * am 5. (Tutorial) und 6. Mai (Hauptprogramm) 2010\n * Ort: ((http://www.mediencampus-villa-ida.de/anfahrt/ Mediencampus Villa Ida))\n * Anmeldung: ((http://www.amiando.com/semantic.html Amiando (Euro 30)))\n * Flyer: ((http://aksw.org/Events/2010/LeipzigerSemanticWebDay/files?get=lswt_flyer.pdf LSWT))\n * Rückblick: ((/Events/2009/LeipzigerSemanticWebDay Leipziger Semantic Web Tag 2009))\n\nDie Semantic Web Initiative gewann im letzten Jahr zunehmend an Fahrt. Dies belegen u.a. die Veröffentlichung des OWL2 Standards, die zunehmende Unterstützung semantischer Technologien durch namhafte Softwarehersteller wie z.B. Oracle und die Auswertung von semantischen RDFa-Annotationen durch Google. Ein weiterer wichtiger Impuls ging von der dynamischen Linked Data Bewegung aus, die aufzeigt, wie das Web zur Publikation und Integration von Daten genutzt werden kann.\n\n<#

    \n

    \n

    \n

    \n

    \n

    \n

    \n\n

    #>\n\nNeben diesen technischen Entwicklungen im Umfeld der Semantic Web Initiative rücken aber auch verstärkt die wirtschaftlichen und sozialen Aspekte ins Zentrum der Aufmerksamkeit. Auf Basis des Linked Data Paradigmas kann bspw. die //kosteneffiziente Integration von Unternehmensanwendungen// in Intra-Daten-Webs unter Einbeziehung von Hintergrundinformationen aus dem Linked Data Web (z.B. DBpedia) erreicht werden. Im Bereich der //öffentlichen Verwaltungen// können Daten Web Technologien helfen, Informationen für Bürger leichter zugänglich und wiederverwendbar zu machen. Auch in den Wissenschaften spielt neben dem freien Zugang zu wissenschaftlichen Veröffentlichungen, der freie, standardisierte Zugang zu wissenschaftlichen Daten eine zentrale Rolle.\n\nDiese Themen stehen im Fokus des 2. Leipziger Semantic Web Tages (LSWT 2010). Interessierte Unternehmen, öffentliche Verwaltungen und Organisationen sind herzlich eingeladen, die Potentiale des Einsatzes semantischer Technologien kennen zu lernen und eigene Anwendungszenarien vorzustellen. Ein besonderer Höhepunkt des LSWT 2010 ist die feierliche Gründungszeremonie des deutschen Zweiges der ((http://okfn.org Open Knowledge Foundation)). Die Open Knowledge Foundation ist eine gemeinnützige NGO, die sich für den freien und uneingeschränkten Zugang zu offenem Wissen im digitalen Zeitalter einsetzt.\n\n\n===Programm===\n\n====5. Mai ====\n\n**13:00-18:00** **Tutorial: Einsatz semantischer Technologien in Unternehmen und im E-Government** \nFolien: http://aksw.org/Events/2010/LeipzigerSemanticWebDay/files?get=tutorial.pdf\nLeitung: Sören Auer und Sebastian Tramp\nOrt: Kombiseminarraum, 1. OG, ((http://www.mediencampus-villa-ida.de/anfahrt/ Mediencampus))\n\n**ab 19:00** Semantic Biergarten in der ((http://www.gosenschenke.de/ Gosenschenke \"Ohne Bedenken\")), Poetenweg 6 (((http://maps.google.com/maps?f=q&source=s_q&hl=en&geocode=&q=Poetenweg+6,+Leipzig&sll=51.34527,12.36916&sspn=0.007171,0.022595&ie=UTF8&hq=&hnear=Poetenweg+6,+Gohlis-S%C3%BCd+04155+Leipzig,+Saxony,+Germany&z=16 Karte)))\n\n\n====6. Mai====\n\nBitte wenden Sie sich bei Fragen zum LSWT-Programm an ((http://www.informatik.uni-leipzig.de/~auer Sören Auer)).\n\n#|\n|| | Schillersaal I | Schillersaal II ||\n|| 9:00-9:45 | Begrüßung, **Keynotes I**\n * //((http://aksw.org/files/peter_reiser__community_equity.pdf Community Equity - Reputation und Zusammenarbeit in einem sozialen Netzwerk bei Sun Microsystems))//, ((http://blogs.sun.com/peterreiser/ Peter Reiser)), Sun Microsystems\n * //((http://aksw.org/files/daniel_hladky__semantikbasiertes_management_unstrukturierter_informationen.pdf Semantik-basiertes Management unstrukturierter Informationen))//, ((http://ontos.com Daniel Hladky)) (Ontos AG)\n||\n|| | Kaffeepause ||\n|| 10:00-11:30 | Session 1.1: **Semantische Technologien I**\n(Session chair: Sebastian Tramp)\n * //Current Developments around the Web of Data//, ((http://www.wiwiss.fu-berlin.de/en/institute/pwo/bizer/ Chris Bizer)) (FU Berlin)\n * //Word-sense disambiguation and the Semantic Web//, ((http://www.biotec.tu-dresden.de Dimitra Alexopoulou)) (BioTec TU Dresden)\n * //((http://aksw.org/files/hanschristian_brockmann__eccenca_for_enterprise.pdf Semantik-basierte Informationslogistik im Unternehmen mit SMILA/eccenca))//, ((http://www.brox.de Hans-Christian Brockmann)) (brox IT)\n * //((http://aksw.org/files/christian_weiske__less.pdf Syndikation von Linked Data Inhalten mit LESS))//, ((http://netresearch.de Christian Weiske)) (Netresearch)\n * //((http://aksw.org/Events/2010/LeipzigerSemanticWebDay/files?get=lswt_ontowikierfurt.pdf Entwicklung adaptiver, semantischer Web-Anwendungen mit OntoWiki/Erfurt))//, ((http://bis.informatik.uni-leipzig.de/PhilippFrischmuth Philipp Frischmuth)) (AKSW/Uni Leipzig)\n| Session 1.2: **Open Governmental & Public Data I** \n(Session chair: Daniel Dietrich)\n * //((http://aksw.org/files/martin_kaltenbcck__open_government_data_austria.pdf Die OpenGovData Initiative in Österreich)) (http://gov.opendata.at) inkl. emteba.at - österr. Forschungsprojekte in der LOD Cloud//, ((http://www.semantic-web.at Martin Kaltenböck)) (Semantic Web Company)\n * //((http://aksw.org/files/soeren_auer__perspektiven_des_einsatzes_von_linked_data_im_egovernment.pdf Perspektiven des Einsatzes von Linked Data im e-Government))//, ((http://www.informatik.uni-leipzig.de/~auer Sören Auer)) (AKSW/Uni Leipzig)\n * //((http://aksw.org/files/thomas_bandholtz__linked_environment_data_projekt_des_umweltbundesamtes.pdf Das Linked Environment Data Projekt des Umweltbundesamts))//, ((http://www.innoq.com Thomas Bandholtz)) (innoQ)\n * //((http://aksw.org/files/claus_stadler__linkedgeodata__semantisch_vernetzte_geodaten.pdf LinkedGeoData - semantisch vernetzte Geo-Daten))//, Claus Stadler (AKSW / Uni Leipzig)\n||\n|| | Kaffeepause ||\n|| 11:45-13:15 | Session 2.1: **Open Scientific Data I**\n(Session chair: Jens Lehmann)\n * //Zusammenarbeit in den Geschichtswissenschaften auf Basis semantischer Technologien am Beispiel des Professorenkatalogs//, ((http://www.uni-leipzig.de/histsem/244.html Ulf Morgenstern)) (Historisches Seminar/Uni Leipzig)\n * //FishBase: offene Daten zur Meeres-Biodiversität//, ((http://filaman.uni-kiel.de/ifm-geomar/rfroese/ Rainer Froese)) (IFM-Geomar)\n * //((http://aksw.org/files/dominik_bchler__balanceonline.pdf balanceonline.org: eine offene Forschungsplattform))//, Dominik Böhler (Friedrich-Alexander-University Erlangen-Nürnberg)\n * //((http://aksw.org/files/daniel_kinzler__strukturierte_daten_in_der_wikipedia.pdf Strukturierte Daten in Wikipedia))//, ((http://www.wikimedia.de Daniel Kinzler)) (Wikimedia Deutschland)\n * //((http://en.citizendium.org/wiki/User:Daniel_Mietchen/Talks/LSWT_2010/Integrating_wikis_with_scientific_workflows Integration von Wikis mit wissenschaftlichen Arbeitsabläufen))//, ((http://dbm.neuro.uni-jena.de/people/daniel-mietchen/ Daniel Mietchen)) (Friedrich Schiller Universität Jena)\n| Session 2.2: **Einsatzszenarien semantischer Technologien**\n(Session chair: Chris Bizer)\n * //((http://aksw.org/files/uwe_schrcder__ontologiebasiertes_begriffsmapping.pdf Ontologiebasiertes Mapping der Begriffswelt des Kunden auf die Fachdomäne im Beschwerdemanagement der Deutschen Telekom))//, ((http://www.t-systems-mms.com/ Uwe Schröder)) (T-Systems Multimedia Solutions)\n * //((http://aksw.org/files/tassilo_pellegrini__semantic_web_in_der_medienindustrie.pdf Anwendung semantischer Technologien im Mediensektor))//, ((http://www.semantic-web.at Tassilo Pellegrini)) (Semantic Web Company)\n * //((http://aksw.org/files/christian_dirschl__semantische_technologien_in_einem_juristischen_verlag.pdf Operationaler Einsatz semantischer Technologien bei einem juristischen Fachverlag))//, ((http://www.wolterskluwer.de Christian Dirschl)) (Wolters Kluwer)\n * //Anwendung einer semantischen Wissensplattform bei einem Pharma-Unternehmen//, ((http://www.ontoprise.com/ Philipp Zaltenbach)) (ontoprise ~GmbH)\n * //((http://aksw.org/files/christian_ehrlich__automatisches_annotieren_mit_der_ontos_api.pdf Automatische Annotation von Texten mit der Ontos API))//, ((http://ontos.com Christian Ehrlich)) (Ontos AG)\n||\n|| | Mittagspause ||\n|| 14:15-15:00 | **Gründung Open Knowledge Foundation Deutschland**\n(Session chair: Sören Auer)\nKeynote: //((http://aksw.org/files/rkvortragohne_offenes_wissen_keine_informationelle_selbstbestimmung97.pdf Ohne offenes Wissen keine informationelle Selbstbestimmung))//, ((http://www.kuhlen.name Rainer Kuhlen)) (Uni Konstanz, UNESCO-ORBICOM, Coalition \"Copyright for Education and Science\")\n||\n|| 15:00-16:30 | Session 3.1: **Open Governmental & Public Data II**\n(Session chair: Sören Auer)\n * //((http://aksw.org/files/jcrn_von_lucke__open_government.pdf Open Government - Partizipation2.0 & Kollaboration2.0))//, ((http://joern-von-lucke.eluhost.de Joern von Lucke)) (Zeppelin-Universität)\n * //Erfahrungsbericht zur Entwicklung von data.gov.uk//, ((http://okfn.org Jonathan Gray)) (OKFN)\n * //((http://aksw.org/files/daniel_dietrich__okfn_deutschland.pdf Open Government Data in Deutschland - Status Quo: App4Democracy Wettbewerb und ein Prototyp für ein Register für offene (Regierungs-) Daten))//, ((http://opendata-network.org/ Daniel Dietrich)) (Open Data Network)\n * //((http://aksw.org/files/matthias_spielkamp__lets_remix_the_wachstumsbeschleunigungsgesetz.pdf Let's remix the Wachstumsbeschleunigungsgesetz - offene Daten und freie Lizenzen))//, ((http://iRights.info Matthias Spielkamp)) (iRights.info)\n * //((http://aksw.org/files/sebastiantrampsocialsemanticweb.pdf Dezentralisierte Soziale Netzwerke auf der Basis semantischer Technologien))//, ((http://bis.informatik.uni-leipzig.de/SebastianTramp Sebastian Tramp)) (AKSW/Uni Leipzig)\n\n| Session 3.2: **Semantische Technologien II**\n(Session chair: Axel Ngonga)\n * //Web Data Integration//, ((http://dbs.uni-leipzig.de/personen/rahm.html Erhard Rahm)) (WDI Lab / Uni Leipzig)\n * //Inhalts- und Wissensmanagement mit Topic Maps//, ((http://www.topicmapslab.de/people/Lutz_Maicher Lutz Maicher)) (Topic Maps Lab/Uni Leipzig)\n * //((http://aksw.org/Events/2010/LeipzigerSemanticWebDay/files?get=2ter_lswt_dbpedia.pdf DBpedia Live - Kollaborative Ontologieerstellung durch die Wikipedia-Gemeinschaft))//, ((http://bis.informatik.uni-leipzig.de/SebastianHellmann Sebastian Hellmann (AKSW/Uni Leipzig)))\n * //RDF veröffentlichen, Daten verlinken. Und dann? Ein Bericht über den pragmatischen Einsatz von Linked Data.//, ((http://uberblic.com/ Georgi Kobilarov)) (Ueberblic Labs)\n||\n|| | Kaffeepause ||\n|| 17:00-18:30 | Session 4.1: 17:00-17:45 **Stand-Up Präsentationen, Lightning Talks**\n * //((http://aksw.org/files/christoph_bldsi__medienautomation__ein_neues_forschungsthema_in_mainz.pdf Medienautomation – ein neues Forschungsthema in Mainz))//, Christoph Bläsi\n * //((http://aksw.org/files/daniel_gerber__sparqltrainer.pdf SPARQLTrainer))//, Daniel Gerber\n * //((http://aksw.org/files/magnus_knuth__trial_item_manager.pdf Trial Item Manager))//, Magnus Knuth\n * //((http://aksw.org/files/michael_haschke__foafpress.pdf Foafpress))//, Michael Haschke\n * //((http://aksw.org/files/stefan_huber__tech_it_easy.pdf Tech it easy))//, Stefan Huber\n\n17:45-18:30 **Paneldiskussion** zum Thema //\"Open Government in Deutschland\"// mit den Diskutanten:\n * Moderation: Antje Matten, Government 2-0 Netzwerk Deutschland\n * Franz-Reinhard Habbel, Sprecher des Deutschen Städte- und Gemeindebundes\n * Prof. Dr. Joern von Lucke, Fraunhofer FOKUS und Zeppelin-Universität\n * Dr. Sören Auer, AKSW/Uni Leipzig\n\n\n| Session 4.2 ** Web Daten Integration**\n * //((http://aksw.org/files/sven_kitschke__semantische_webdatenintegration.pdf Semantische Webdatenintegration - Anwendungsfälle))//, Sven Kitschke\n * //((http://aksw.org/files/sabine_majamann__ermittlung_semantischer_korrespondenzen.pdf Ermittlung semantischer Korrespondenzen in Produktkatalogen))//, Sabine Maßmann\n * //((http://aksw.org/files/hanna_kcpcke__auffinden_von_dubletten.pdf Auffinden von Dubletten in e-commerce Datenbeständen))//, Hanna Köpcke\n||\n|| ab 19:00 | **Abendveranstaltung im ((http://www.mueckenschloesschen-leipzig.de/index.php?id=6 Mückenschlößchen am Rosental))** ||\n|#\n\n===Aussteller===\n\n * ((http://ontos.com Ontos AG))\n * ((http://netresearch.de Netresearch GmbH & Co. KG))\n * ((http://bi-web.de Business Intelligence GmbH))\n * ((http://wdilab.uni-leipzig.de/ WDI-Lab))\n * ((http://www.semantic-web.at Semantic Web Company))\n * ~OpenStreetMaps\n * AG AKSW\n * ((http://www.leipzigschoolofmedia.de/master-content-and-media-engineering/ Berufsbegleitender Masterstudiengang \"Content- & Media-Engineering\")) an der Leipzig School of Media\n\nAussteller präsentieren sich mit einem Stand im Foyer. Sie haben Interesse sich mit einem Stand vorzustellen? Bitte Kontaktieren Sie ((/NadineJaenicke Nadine Jänicke)).\n\n\n===Kontakt===\n\nProgramm: ((http://www.informatik.uni-leipzig.de/~auer Sören Auer))\n\nOrganisation und Pressekontakt: ((/NadineJaenicke Nadine Jänicke))\n\n\n===News===\n{{feed url=\"http://blog.aksw.org/feed/?tag=lswt\"}}\n\n" . . . . "2011-04-29T12:48:27"^^ . "<#\n
    \n

    SPARQLTrainer

    \n\"Screenshot\"\n\n

    learn to query the semantic web

    \n

    \nThe SparqlTrainer is an e-learning tool to practice SPARQL interactively. With the help of self-developed tests, consisting of individual questions, it is possible to train the different query forms (SELECT, CONSTRUCT, ASK and DESCRIBE). After entering a solution the learner will immediately see an evaluation of the request with the corresponding result. Due to different features, like password protection of tests and E-mail notification, an usage in support of courses is also possible.\n

    \n

    \nPlease feel free to test our latest version of SparqlTrainer at http://sparqltrainer.aksw.org. If you do want to provide feedback of your experience please send us an email to danielgerber at me dot com.\n

    \n

    You can find the paper presented at I-SEMANTICS 2010 here.

    \n
    \n#>\n\n{{toc}}\n\n===Contact===\nIf you are interested or have any kind of questions, please feel free to send us an email at mailto:danielgerber@me.com or mailto:marvin.frommhold@gmail.com.\n\n===Requirements===\n * Apache Ant >1.7.x\n * Apache Tomcat 6.x (may also work with previous versions)\n * Subversion\n\n===Obtaining===\nYou need to checkout the jawa and the kwieri project from googlecode:\n\nIf you do want to use SparqlTrainer in production use you should follow the instructions below. If you just want to use SparqlTrainer in a development environment you should not replace the ROOT context of tomcat and configure the context manually in the config.xml file located in $TOMCAT_HOME/config.\n\n=====Download the jawa framework=====\n\n * Make a backup of the tomcat ROOT folder in $TOMCAT_HOME/webapps ($ mv ROOT BACKUP_ROOT, $mkdir ROOT) \n * Go to $TOMCAT_HOME/webapps/ROOT folder\n * svn checkout http://fleischsalat.googlecode.com/svn/jawa .\n\n=====Download the kwieri extension for the jawa framework=====\n\n * Go to $TOMCAT_HOME/webapps/ROOT\n * Create a directory called kwieri (you could create the kwieri folder wherever you want, this is not really a webapplication)\n * Go to $TOMCAT_HOME/webapps/ROOT/kwieri\n * svn checkout http://fleischsalat.googlecode.com/svn/kwieri .\n\n===Configuration===\nJawa and its SparqlTrainer extension get both configured and installed through Apache Ant. So you need to specify the project's settings in the build.properties files in order to generate the corresponding XML-configuration files. For every config file example.xml, there is a template version called example.xml.in located in $TOMCAT_HOME/webapps/ROOT/WEB-INF/config. Ant then takes the filled in project settings from the build.properties and replaces the placeholders in the *.in files to generate the actual config file. \n\n=====Jawa=====\n * Go to $TOMCAT_HOME/webapps/ROOT\n * Copy build.properties.default to build.properties\n * Edit the build.properties according to your needs\n\n=====Kwieri=====\n * Go to $TOMCAT_HOME/webapps/ROOT/kwieri\n * Copy the build.properties.default to build.properties\n * Edit the build.properties according to your needs\n\n===Installation===\nIf you have finished configuring both projects you can then use ant to install these projects. Due to SparqlTrainer depends in the Jawa Framework it's neccessary that you install/compile Jawa first. Afterwards you can install/compile the SparqlTrainer which consists of the two parts, core and view. Both parts get independently packed together to two *.jar files which are then copied to the lib directory of the Jawa Framework. \n\n * Go to $TOMCAT_HOME/webapps/ROOT\n * $ ant install\n * Go to $TOMCAT_HOME/webapps/ROOT/kwieri\n * $ ant install.kwieriTrainer\n * $ ant install.resources\n * Go to $TOMCAT_HOME/webapps/ROOT/WEB-INF/config/jawa\n * $ cp jawa_extensions.xml.in jawa_extensions.xml\n * edit the property testDir according to where you want to store your test files\n * If you have installed jawa no in the ROOT directory of tomcat you need to specify the context path in $TOMCAT_HOME/conf/context.xml\n\n=====Advice=====\nDue to the project configuration it might be inconvenient to know all neccessary folders. So for example you want change translations you need to rebuild the SparqlTrainer, because these files are located in the generated jar files. It also would be nice to have instant access to the test and the models itself. Also the user management is file based (it's not possible to register new users trough the web interface), so a link to the \"user database\" should be helpful. For automation purposes you can use the two scripts at the end of this page (you probably need to adept them).\n\n * you should create a new user called sparqltrainer\n * and install the tomcat into the sparqltrainer's home directory\n * and create the following symlinks after you installed SparqlTrainer:\n * $ cd /home/sparqltrainer\n * to change the language files, you need to run $ ant install.kwieriTrainer (in the kwieri direcotory)\n * $ ln -s /home/sparqltrainer/$TOMCAT_HOME/webapps/kwieri/src/de/unileipzig/kwieri/jawaView/_i18n . \n * to be able to change the test easily \n * $ ln -s /home/sparqltrainer/$TOMCAT_HOME/webapps/kwieri/resources/kwieriTests/ .\n * to be able to change the models easily\n * $ ln -s /home/sparqltrainer/$TOMCAT_HOME/webapps/ROOT/public/kwieriTrainer/models/ .\n * to add new users, or if you don't want to do $ ant config (in the jawa directory) again\n than link the users.xml instead \n * $ ln -s /home/sparqltrainer/$TOMCAT_HOME/webapps/ROOT/WEB-INF/config/modules/in/users.xml.in .\n\n=====<#UpdateLocaleFiles.sh#>=====\n%%\n#!/bin/bash\n\nsudo -u sparqlTrainer /home/sparqlTrainer/apache-tomcat-6.0.20/bin/shutdown.sh\ncd /home/sparqlTrainer/apache-tomcat-6.0.20/webapps/kwieri\nant install.kwieriTrainer\nsudo -u sparqlTrainer /home/sparqlTrainer/apache-tomcat-6.0.20/bin/startup.sh\n%%\n\n=====<#UpdateUsersFile.sh#>=====\n%%\n#!/bin/bash\n\nsudo -u sparqlTrainer /home/sparqlTrainer/apache-tomcat-6.0.20/bin/shutdown.sh\ncd /home/sparqlTrainer/apache-tomcat-6.0.20/webapps/ROOT\nant config\nsudo -u sparqlTrainer /home/sparqlTrainer/apache-tomcat-6.0.20/bin/startup.sh\n%%\n\n===Usermanagement===\nIf you want to add a new system user you need to edit this file: $TOMCAT_HOME/webapps/ROOT/WEB-INF/config/modules/users.xml.\nPlease consider that if you do run $ ant configure again, the users.xml file gets recreated, so it might be better to edit the $TOMCAT_HOME/webapps/ROOT/WEB-INF/config/modules/in/users.xml.in file instead. You need to restart tomcat after you change the users file, or you simple you the script provided ((http://aksw.org/Projects/SparqlTrainer/Installation here)).\n\n=====Example user file=====\n<#\n\n<user> \n <login>newUser</login> // the user name\n <password>\n // md5 hash of the user password, create it with $ echo -n \"password\" | md5sum\n <md5>21232f297a57a5a743894a0e4a801fc3</md5> \n // sha1 hash of the user password, create it with $ echo -n \"password\" | sha1sum\n <sha>680990854eb710e7b862cb1311578dcb090aa92f</sha>\n </password>\n <groups>admin</groups> // at the moment you only need to add group admin\n</user>\n\n#>\n\n===Testmanagement===\nYour test files are located under $TOMCAT_HOME/webapps/kwieri/resources/kwieriTests/. A sample test file, with a short description of the elements could look like this:\nThe according XSD schema can be found ((http://aksw.org/Projects/SparqlTrainer/files?get=sparqlcourse.xsd here)).\n\n<#\n\n<?xml version=\"1.0\" encoding=\"UTF-8\" standalone=\"yes\"?>\n<kwieriTest>\n // true -> the test is activated and get's shown in the left menu bar\n <enabled>true</enabled>\n // if you set a password, people need to enter first name, last name,\n // email and this password to do the test\n // after they finished the test, an email is send to them and the admin\n <password>aksw</password>\n // the title of the test, get's shown in the left menu bar\n <title>Title</title>\n // you can see this descriptions before you start the test\n <description>a description of what the test is about</description>\n // true -> questions in this test get randomized\n <random>false</random> \n // you can only go to next question if you have successfully solved the actual question\n <stepByStep>false</stepByStep> \n // the email address of the person in charge of this test\n <email>admin@admin.de</email> \n // the number of question the attendees have to solve (if greater than number of questions,\n // than question count is equal to number to questions)\n <questionCount>5</questionCount> \n // a list of questions\n <questions>\n // a single question does consist of a title, description, defaultGraph,\n // the solution query and the result check\n <question> \n // simple title\n <title>Persons</title>\n // a brief description of what to do\n <description>What are the names of all persons! Use the properties rdf:type and foaf:name!</description> \n // either a resolvable url like http://www.w3.org/1999/02/22-rdf-syntax-ns# or\n // if it's a file it has to be located in \n // $TOMCAT_HOME/webapps/ROOT/public/kwieriTrainer/models/ and\n // you need to add \"model:\" before the filename, e.g. model:test.rdf\n <defaultGraph>model:aksw.rdf</defaultGraph>\n // the query needs to in a cdata field because of < or >,\n // it should be possible to use the prefixes defined in the test.rdf model\n <solutionQuery><![CDATA[\n select ?name where { \n ?s rdf:type foaf:Person .\n ?s <http://xmlns.com/foaf/0.1/name> ?name\n }]]>\n </solutionQuery> \n <resultCheck> \n <condition>columnCondition</condition>\n // noCondition - the order of the columns and row is not important\n // columnCondition - only the order of the columns is important\n // rowCondition - only the order of the rows is important\n // columnRowCondition - the order of the rows and the columns is important\n // askCondition - use this, if the question is and sparql ask question\n </resultCheck>\n </question>\n </questions>\n</kwieriTest>\n#>\n\n===TODO's===\n * provide feedback a lá number of lines is x, number of triple patterns is y, number of columns is z\n * create a proper test, extend the planets example in the Semantic Web Grundlagen book\n * make it possible to view the model in differnt serializations\n * support for test definition in rdf/xml (maybe a ontowiki component for easy creation)\n" . . . . "2010-01-23T10:53:36"^^ . "{{toc divclass=\"floatbox\"}}\n\n==Adaptive SPARQL Query Cache==\n\nIn order to get closer to the performance of relational database-backed Web applications, we developed an approach for improving the performance of triple stores by caching query results and even complete application objects. The selective invalidation of cache objects, following updates of the underlying knowledge bases, is based on analysing the graph patterns of cached SPARQL queries in order to obtain information about what kind of updates will change the query result.\n\n\n=== Overview ===\nWe implemented our approach as a small proxy layer, which resides between the Semantic Web application and the SPARQL/SPARUL endpoint. All SPARQL queries and SPARUL updates are routed through this proxy. Once the proxy receives a query, it checks whether a result for this query is cached in its local store. \n\n<##>\n\n\nIf that is the case, the result is directly delivered to the client without accessing the triple store. If the query was not previously stored and is not excluded from caching by user-supplied rules, the query is routed to the triple store and, before results are returned to the client, these are stored in the cache’s local result store.\n\n\n===Implementation ===\nWe developed two implementations of the SPARQL cache:\n\n====PHP Implementation====\nThe PHP implementation is integrated into the Erfurt layer of OntoWiki. The caching component is part of the latest release and is also used by other web applications build on the Erfurt middleware. This implementation furthermore supports application specific object caching with SPARQL dependencies.\n\n====Java Implementation ====\nThe Java implementation is a web application which runs within a servlet container. It provides a SPARQL/SPARUL endpoint proxy, requests to this endpoint are forwarded to the original SPARQL/SPARUL endpoint and cached.\nThe caching servlet is backed by the popular ((http://ehcache.org/ ehcache)). For query parsing we use ((http://jena.sourceforge.net Jena)).\n\nThe prototype can be downloaded ((file:sparqlcache4j.zip here)). The archive consists of the Java sources and a Maven project descriptor. A simple ##mvn jetty:run## should do the trick to get it running. Point your browser then to ##localhost:8080##. The self-explanatory configuration of the cache is done via a simple web interface:\n\n<##>\n\n Please note, that this implementation is currently a proof-of-concept prototype and therefore lacks some features essential for a productive deployment (e.g. the configuration is currently not yet stored persistently and has to be re-entered with every start of the query cache). We are working on releasing a stable, full-featured version soon.\n\n\n===Evaluation===\nWe evaluated our approach by extending the ((http://www4.wiwiss.fu-berlin.de/bizer/BerlinSPARQLBenchmark/spec/ BSBM)) triple store benchmark with an update dimension as well as in typical Semantic Web application scenarios. We present here a short overview of the results acquired using the BSBM, which are discussed in greater detail the paper M. Martin, J. Unbehauen, S. Auer:((http://www.informatik.uni-leipzig.de/~auer/publication/caching.pdf Improving the Performance of Semantic Web Applications with SPARQL Query Result Caching)).\n\n<##>\n\nUsing the BSBM with ((http://mathworld.wolfram.com/ParetoDistribution.html Pareto distributed)) queries we varied query repetition, benchmarked the implementation against various store sizes and observed significant performance improvements in most cases.\n\n<##>\n\nIn addition, we measured the impact of updates on the cache and we found that only a high update frequency (i.e. more than one update per 25 queries) reduces overall performance.\n\n\n===Contributions and Support===\nThe following people of AKSW created this project and provide support:\n * ((/SoerenAuer Sören Auer))\n * ((/MichaelMartin Michael Martin)) supports the PHP implementation\n * ((/JoergUnbehauen Jörg Unbehauen)) supports the Java implementation\n\n" . . . . "2010-01-22T20:26:07"^^ . "{{vcard name=\"sn\" value=\"Unbehauen\"}}\n\nPlease see my homepage at: http://bis.informatik.uni-leipzig.de/JoergUnbehauen" . . . . "2010-12-16T11:31:53"^^ . "<#\n
    \n

    RDFauthor

    \n\"RDFauthor\n

    is an editing solution for distributed and syndicated structured content on the World Wide Web.

    \n

    The system is able to extract structured information from RDFa-enhanced websites and to create an edit form based on this data.\nTo this end, we make use of semantics-aware editing widgets that hide most of the RDF data model from the user, thus allowing more people to author semantic content.\nIf the embedded data does not suffice to create a rich user-supporting editing view, the underlying Semantic Web infrastructure is used to retrieve additional schema-related information about the elements used.\n

    RDFauthor Google Code project page

    \n

    RDFauthor API Documentation

    \n
    \n
    \n
    \n
    #>\n\n There is another project called RDFAuthor ((http://rdfweb.org/people/damian/RDFAuthor/ here)).\n\n===Overview===\nThe idea of RDFauthor is to make arbitrary RDFa-annotated web pages editable. By ((http://buzzword.org.uk/2009/rdfa4/spec extending RDFa with named graphs)), it is even possible to edit information originating from different sources within the same form.\n\n<#\"RDFauthor#>The basic cycle of how the RDFauthor approach works is depicted on the right. It consists of the following processes:\n\n * Page creation and delivery (a): An HTML page is created based on data from e.g. an RDF store. Triples are embedded using RDFa with named graphs extension. Additionally, for each writable graph, a SPARQL/Update endpoint is defined.\n * Client-side page processing (b): Embedded triples are extracted and placed into rdfQuery databanks, one for each named graph.\n * Form creation (c): Based on the triples extracted, an edit form is created. It contains widgets for all the triples based on ##rdf:type##, property, datatype etc.\n * Update propagation (d): Changes are sent back to the sources via SPARQL/Update for each named graph separately. Access control rules can therefore be ovserved on the graph level.<#
    #>\n\n===Provenance===\nIn order to be able to use RDFauthor, a few requirements must be met. All triples that are to be editable must beembedded in the page by means of ((http://www.w3.org/TR/xhtml-rdfa-primer/ RDFa)). If triples for the page originate from different sources, they have to be placed in different named graphs. We use the ((http://buzzword.org.uk/2009/rdfa4/spec named graphs extension proposed by Toby Inkster)). Additionally. the page must contain provenance information for each named graph as RDFa triples. To this end, we provide an update vocabulary. It allows to define for each named graph an update endpoint and optionally a query endpoint. The update endpoint is assumed by RDFauthor to understand SPARQL/Update queries. RDFauthor uses a subset of SPARQL/Update (##INSERT DATA## syntax) where each triple to be inserted is explicitely given. It is sufficient to support only this subset.\n\n===Examples===\nAs of version 0.9, the ((http://ontowiki.net/ OntoWiki Project)) uses RDFauthor as its primary editing system. To make use of RDFauthor, ~OntoWiki had to be extended in two ways:\n * all resource templates have been upated to include RDFa and provenance information, \n * a SPARQL/Update enpoint was added.\n\nAdditional examples will be added subsequently.\n\n===Contact==={{a name=\"Contact\"}}\n{{vcard name=\"sn\" value=\"Heino\"}}\n{{vcard name=\"sn\" value=\"Tramp\"}}\n\n" . . . . "2010-04-24T17:24:39"^^ . "{{Include page=\"/Projects/SemanticPingback/Teaser\" nomark=\"1\"}}\n{{toc divclass=\"floatbox\"}}\n\n===Overview==={{a name=\"Overview\"}}\nSemantic Pingback tackles the //quality//, //timeliness// and //coherence// as well as //direct end user benefits// of the emerging Linked Data Web. Semantic Pingback extends the well-known ((http://www.hixie.ch/specs/pingback/pingback Pingback)) method, which is technological cornerstone of the blogosphere. It is based on the advertising of an RPC service for propagating typed RDF links between Data Web resources. It is downwards compatible with conventional Pingback implementations, thus allowing to connect and interlink resources on the Social Web with resources on the Data Web.\n\nhttp://aksw.org/Projects/SemanticPingBack/files?get=architecture.png\n\n 1. A //linking resource// (depicted in the upper left) links to another (Data) Web resource, here called //linked resource//. The linking resource can be either an conventional Web resource (e.g. wiki page, blog post) or a Linked Data resource. Links originating from Linked Data resources are always typed (based on the used property), links from conventional Web resources can be either untyped (i.e. plain HTML links) or typed (e.g. by means of RDFa annotations).\n 2. The //Pingback client// (lower left) is either integrated into the data/content management system or realized as a separate service, which observes changes of the Web resource.\n 3. Once the establishing of a link was noted, the Pingback client tries to autodiscover a Pingback server from the linked resource.\n 4. If the autodiscovery was successful, the respective Pingback RPC server is called, with the parameters linking resource (i.e. source) and linked resource (i.e. target).\n 5. In order to verify the retrieved request (and to obtain information about the type of the link in the semantic case), the Pingback server fetches (or dereferences) the linking resource.\n 6. Subsequently, the Pingback server can perform a number of actions, such as updating the linked resource (e.g. adding inverse links) or notifying the publisher of the linked resource (e.g. via email).\n\n===XML/RPC vs. Simplified Post Request==={{a name=\"simplepost\"}}\nWhile the Pingback 1.0 specification defines a XML/RPC call for request a pingback on a Pingback Server, ((http://lists.foaf-project.org/pipermail/foaf-protocols/2010-April/ we discussed a simplified request representation)) using only HTTP-post attributes.\n\nThe simplified pingback post request has two obligatory and one optional post parameter:\n * **source** is the source resource URI (obligatory)\n * **target** is the target resource URI (obligatory)\n * **comment** is an optional comment for the pingback request given by the source owner or the source owners application.\n\nTo distinguish these two request methods, the pingback vocabulary defines two different object properties: ((http://purl.org/net/pingback/service pingback:service)) (XML/RPC) and ((http://purl.org/net/pingback/to pingback:to)) (Simplified Post Request). Both properties can be used to link a pingback target resource with its pingback server.\n\n===Available Implementations==={{a name=\"Implementations\"}}\nWe implemented the Semantic Pingback mechanism in three different scenarios:\n * Semantic Pingback server and client functionality is available for ((/Projects/OntoWiki OntoWiki)).\n * Semantic Pingback server functionality was integrated in ((/Projects/Triplify Triplify)), thus supporting the interlinking with relational data on the Data Web.\n * A prototype of a standalone Semantic Pingback server was implemented in PHP, that can be utilized with arbitrary resources that do not provide a Pingback service themselves.\n\n====~OntoWiki====\nIn order to enable the Semantic Pingback extension for ((/Projects/OntoWiki OntoWiki)) you need to make sure that\n * the Linked Data plugin is enabled (should be enabled by default, ##extensions/plugins/linkeddata##),\n * the Pingback plugin (##extensions/plugins/pingback##) is enabled and\n * the Pingback component (##extensions/components/pingback##) is enabled.\n \nThe plugin and component can be enabled by simply renaming the ##plugin.ini-dist## respectively ##component.ini-dist## to ##plugin.ini## respectively ##component.ini##.\n\n====Triplify====\nA pingback-enabled version of Triplify will be released soon.\n\n====Standalone Semantic Pingback Server====\nA prototype of a standalone Semantic Pingback server is ((http://code.google.com/p/ontowiki/downloads/list?q=label:SemanticPingback available for download here)).\n\nTo setup the Semantic Pingback server follow these steps:\n 1. Copy the contents of the folder in a Web application directory on your Web server.\n 2. Copy the distributed configuration file (##config.inc.php-dist##) to ##config.inc.php##. Open the file in a text editor and adjust the settings to fit your configuration. At least a valid database connection needs to be supplied. If you want to use the mail feature, make sure that your PHP environment is configured correctly to be able send emails.\n 3. Congratulations! Your Semantic Pingback is ready to receive Pingbacks now. You should now start propagating the URL of the service. If you place the files in a directory like ##/pingback/## and the ##index.php## file is located in ##~\n\n\n \n\n\n\n%%\n\n===How to add Semantic Pingback functionality to your application==={{a name=\"HowTo\"}}\nIf you plan to implement the Semantic Pingback mechanism, you should generally follow the conventional ((http://www.hixie.ch/specs/pingback/pingback Pingback specification)), since Semantic Pingback is downward compatible with the original Pingback method. We will focus in this section on the differences.\n\n====Semantic Pingback Client====\nOne basic design principle of the original Pingback specification is to keep the implementation requirements of a Pingback client as simple as possible. Consequently, Pingback clients to not even need an XML/HTML parser for basic functionality. There are three simple actions to be followed by a Pingback client:\n 1. Determine suitable links to external target resources,\n 2. detect the Pingback server for a certain target resource (autodiscovery) and\n 3. send an XML-RPC post request via HTTP to that server.\n\nThe only modification to the client behavior is an additional autodiscovery method for Linked Data resources which is based on RDF and integrates better with Semantic Web technologies. We defined an OWL object property ##~http://purl.net/pingback/service##, which is part of the Pingback namespace and links a RDF resource with a Pingback XML-RPC server URL. Consequently, a Semantic Pingback client should (if no ##X-Pingback## HTTP header field is available) try to fetch an RDF representation of the target resource and check for a ##pingback:service## statement.\n\n====Semantic Pingback Server====\nWe did not touch the XML-RPC interface, but a Semantic Pingback server should handle Pingback requests different than conventional Pingback servers would handle them. We describe some guidelines in terms of backlinking, spam prevention and provenance tracking.\n\n=====Backlinking=====\nThe idea behind propagating links from the publisher of the source resource to the publisher of the target resource is to automate the creation of backlinks. In pingback-enabled blogging systems, for example, a backlink is rendered in the feedback area of a target post together with the title and a short text excerpt from the source resource. \n\nTo retrieve all required information from the source resource (e.g. in order to verify links), a Semantic Pingback server should:\n 1. Try to obtain an RDF representation by requesting RDF with respective HTTP ##Accept## header.\n 2. If this is not possible, try to obtain RDF by employing an RDFa parser.\n 3. If this fails, check for an untyped (X)HTML link in the body of the source resource.\n \nDepending on the type of data which was retrieved from the source resource, the server can react as follows:\n * If there is only an //untyped// (X)HTML link in the source resource, this link can be added as RDF triple with a generic RDF property (e.g. ##~dc:references##, ##~sioc:links_to##) to the servers knowledge base.\n * If there is at least on //direct link// from the source resource to the target resource, this triple should be added to the servers knowledge base.\n * If there is any other triple in the source resource where either the subject or the object of the triple corresponds to the target resource, the target resource can be linked to the source resource using the ##rdfs:seeAlso## property.\n\nIn addition to the statements which link the source and the target resource, metadata about the source resource (e.g. a label and a description) can be stored as well.\n\n=====Spam Prevention=====\nThe Semantic Pingback mechanism prevents spamming by fetching the linking resource and checking for the existence of a valid incoming link or an admissible assertion about the target resource. E.g.:\n * //Information analysis.// The Pingback server can, for example, dismiss assertions which have logical implications (such as domain, range or cardinality restrictions), but allow label and comment translations into other languages.\n * //Publisher relationship analysis.// E.g. based on the trust level of the publisher of the linking resource. A possibility to determine the trust level is to resolve ##~foaf:knows## relationships from the linked resource publisher to the linking resource publisher.\n\n=====Provenance Tracking=====\nProvenance information can be recorded using the ((http://trdf.sourceforge.net/provenance/ns.html provenance vocabulary)).\n\n===Further Information===\nPlease have a look at our paper:\n\nSebastian Tramp, Philipp Frischmuth, Timofey Ermilov, Sören Auer: ((http://www.informatik.uni-leipzig.de/~auer/publication/SemanticPingback.pdf Weaving a Social Data Web with Semantic Pingback))\n\nAlso the original ((http://www.hixie.ch/specs/pingback/pingback Pingback specification)) provides additional information.\n\n\n===Contact==={{a name=\"Contact\"}}\n{{vcard name=\"sn\" value=\"Tramp\"}}\n{{vcard name=\"sn\" value=\"Frischmuth\"}}\n{{vcard name=\"sn\" value=\"Auer\"}}\n\n" . . . . "2010-02-02T17:06:51"^^ . "==Workshop: Das Semantic Web ausprobieren==\n\nDiese Webseite enthält eine Sammlung interessanter Anwendungen des Semantic Webs.\n\n\n===Explore the Link Open Data Web===\n\nFür das \"surfen\" im LOD-Web existieren verschieden Browser. Der folgende Link öffnet die DBpedia Resource http://dbpedia.org/resource/Leipzig. Am Ende der Seite gibt es eine Zusammenstellung verschiedener Linked Data Browser, wie z.B. ((http://dig.csail.mit.edu/2005/ajar/release/tabulator/0.8/tab.html?uri=http://dbpedia.org/resource/Leipzig Tabulator)), ein generischer Browser, entwickelt von Tim Berners-Lee, der die ((http://www.w3.org/DesignIssues/LinkedData.html Idee zu LinkedData)) hatte und formulierte. Daten können auf einer Karte oder in einem Kalender angezeigt werden. Es können Suchanfragen mit der SPARQL-Sprache gestellt werden. Ist auch als Extention für Firefox oder als Opera-Widget verfügbar.\n * http://aksw.org/Teaching/Workshops/DasSemanticWebAusprobieren/files?get=leipzigtabulator.png\n\nWeiter interesante Links die den Tabulator benutzen:\n\n ((http://dig.csail.mit.edu/2005/ajar/release/tabulator/0.8/tab.html?uri=http://catalogus-professorum.org/lipsiensis/Everth_33 Erich Evert)) Professor an der Universität Leipzig\n\n ((http://dig.csail.mit.edu/2005/ajar/release/tabulator/0.8/tab.html?uri=http://philipp.frischmuth24.de/resource/export/f/rdfxml%3Fr%3Dhttp%3A%2F%2Fphilipp.frischmuth24.de%2Fid%2Fme Phillip Frischmuth)) OntoWiki Entwickler\n\n ((http://dig.csail.mit.edu/2005/ajar/release/tabulator/0.8/tab.html?uri=http://musicbrainz.org/mm-2.1/album/dc60e2bd-7fbc-4586-acac-a99acff7e6a3 Angels Fall First)) Titel des Debütalbums der finnischen Metal-Band Nightwish\n\n ((http://dig.csail.mit.edu/2005/ajar/release/tabulator/0.8/tab.html?uri=http://data.linkedmdb.org/resource/film/77 Pulp Fiction)) Achtung. Zeitüberschreitungen beim Laden\n\n===Realtionen zwischen Ressourcen finden===\n\nEin weiteres interessantes Tool stellt der Relationship-Finder dar.\n\n Beziehungen zwischen ((http://relfinder.semanticweb.org/RelFinder.swf?obj1=QmF5ZXJufGh0dHA6Ly9jYXRhbG9ndXMtcHJvZmVzc29ydW0ub3JnL2xpcHNpZW5zaXMvQmF5ZXJu&obj2=RnJlaXN0YWF0IFNhY2hzZW58aHR0cDovL2NhdGFsb2d1cy1wcm9mZXNzb3J1bS5vcmcvbGlwc2llbnNpcy9GcmVpc3RhYXRTYWNoc2Vu&obj3=RmVsaXggS2xlaW58aHR0cDovL2NhdGFsb2d1cy1wcm9mZXNzb3J1bS5vcmcvbGlwc2llbnNpcy9LbGVpbl84NzM=&name=Q2F0YWxvZ3VzIFByb2Zlc3NvcnVtIChmcm9tIFVSTCBwYXJhbWV0ZXJzKQ==&abbreviation=cHJvZjEyNjQ1NzY4NzAzMzY=&description=UHJvZmVzc29ycyBjYXRhbG91Z2UgZnJvbSBVbml2ZXJzaXR5IExlaXB6aWc=&endpointURI=aHR0cDovL2NhdGFsb2d1cy1wcm9mZXNzb3J1bS5vcmc=&defaultGraphURI=aHR0cDovL2NhdGFsb2d1cy1wcm9mZXNzb3J1bS5vcmcvbGlwc2llbnNpcy8=&isVirtuoso=ZmFsc2U=&useProxy=ZmFsc2U=&autocompleteURIs=aHR0cDovL3d3dy53My5vcmcvMjAwMC8wMS9yZGYtc2NoZW1hI2xhYmVs&abstractURIs=aHR0cDovL2NhdGFsb2d1cy1wcm9mZXNzb3J1bS5vcmcvY3BtL2Z1cnRoZXJJbmZvcm1hdGlvbg==&imageURIs=aHR0cDovL2NhdGFsb2d1cy1wcm9mZXNzb3J1bS5vcmcvY3BtL3BpY3R1cmUsaHR0cDovL3htbG5zLmNvbS9mb2FmLzAuMS9kZXBpY3Rpb24=&linkURIs=aHR0cDovL2NhdGFsb2d1cy1wcm9mZXNzb3J1bS5vcmcvY3BtL3dlYkxpbmtzLGh0dHA6Ly94bWxucy5jb20vZm9hZi8wLjEvcGFnZQ==&maxRelationLegth=Mg== Freistaat Sachen, Felix Klein und Bayern))\n\n Beziehungen zwischen ((http://relfinder.semanticweb.org/RelFinder.swf?obj1=TGVpcHppZ3xodHRwOi8vZGJwZWRpYS5vcmcvcmVzb3VyY2UvTGVpcHppZw==&obj2=QmVybGlufGh0dHA6Ly9kYnBlZGlhLm9yZy9yZXNvdXJjZS9CZXJsaW4=&name=REJwZWRpYQ==&abbreviation=ZGJw&description=TGlua2VkIERhdGEgdmVyc2lvbiBvZiBXaWtpcGVkaWEuIFRoZSBEQnBlZGlhIGRhdGEgc2V0IGN1cnJlbnRseSBwcm92aWRlcyBpbmZvcm1hdGlvbiBhYm91dCBtb3JlIHRoYW4gMS45NSBtaWxsaW9uIOKAnHRoaW5nc+KAnSwgaW5jbHVkaW5nIGF0IGxlYXN0IDgwLDAwMCBwZXJzb25zLCA3MCwwMDAgcGxhY2VzLCAzNSwwMDAgbXVzaWMgYWxidW1zLCAxMiwwMDAgZmlsbXMuIFByb3ZpZGVzIGRlc2NyaXB0aW9ucyBpbiAxMiBkaWZmZXJlbnQgbGFuZ3VhZ2VzLiBBbHRvZ2V0aGVyLCB0aGUgREJwZWRpYSBkYXRhIHNldCBjb25zaXN0cyBvZiAobW9yZSB0aGFuKSAxMDMgbWlsbGlvbiBSREYgdHJpcGxlcy4gVGhlIGRhdGEgc2V0IGlzIGludGVybGlua2VkIHdpdGggdmFyaW91cyBvdGhlciBkYXRhIHNvdXJjZXMu&endpointURI=aHR0cDovL2RicGVkaWEub3JnL3NwYXJxbA==&defaultGraphURI=aHR0cDovL2RicGVkaWEub3Jn&isVirtuoso=dHJ1ZQ==&useProxy=ZmFsc2U=&autocompleteURIs=aHR0cDovL3d3dy53My5vcmcvMjAwMC8wMS9yZGYtc2NoZW1hI2xhYmVs&ignoredProperties=aHR0cDovL3d3dy53My5vcmcvMTk5OS8wMi8yMi1yZGYtc3ludGF4LW5zI3R5cGUsaHR0cDovL3d3dy53My5vcmcvMjAwNC8wMi9za29zL2NvcmUjc3ViamVjdCxodHRwOi8vZGJwZWRpYS5vcmcvcHJvcGVydHkvd2lraVBhZ2VVc2VzVGVtcGxhdGUsaHR0cDovL2RicGVkaWEub3JnL3Byb3BlcnR5L3dvcmRuZXRfdHlwZSxodHRwOi8vZGJwZWRpYS5vcmcvcHJvcGVydHkvd2lraWxpbms=&abstractURIs=aHR0cDovL2RicGVkaWEub3JnL3Byb3BlcnR5L2Fic3RyYWN0&imageURIs=aHR0cDovL2RicGVkaWEub3JnL29udG9sb2d5L3RodW1ibmFpbCxodHRwOi8veG1sbnMuY29tL2ZvYWYvMC4xL2RlcGljdGlvbg==&linkURIs=aHR0cDovL3B1cmwub3JnL29udG9sb2d5L21vL3dpa2lwZWRpYSxodHRwOi8veG1sbnMuY29tL2ZvYWYvMC4xL2hvbWVwYWdlLGh0dHA6Ly94bWxucy5jb20vZm9hZi8wLjEvcGFnZQ==&maxRelationLegth=Mg== Leipzig und Berlin))\n\n Beziehungen zwischen den Filmen ((http://relfinder.semanticweb.org/RelFinder.swf?obj1=S2lsbCBCaWxsfGh0dHA6Ly9kYXRhLmxpbmtlZG1kYi5vcmcvcmVzb3VyY2UvZmlsbS83MTY=&obj2=UHVscCBGaWN0aW9ufGh0dHA6Ly9kYXRhLmxpbmtlZG1kYi5vcmcvcmVzb3VyY2UvZmlsbS83Nw==&name=TGlua2VkIE1vdmllIERhdGEgQmFzZQ==&abbreviation=bG1kYg==&description=QWltcyBhdCBwdWJsaXNoaW5nIHRoZSBmaXJzdCBvcGVuIGxpbmtlZCBkYXRhIGRlZGljYXRlZCB0byBtb3ZpZXMsIHdpdGggaGlnaCBxdWFsaXR5IGFuZCBxdWFudGl0eSBvZiBpbnRlcmxpbmtzIHRvIG90aGVyIExPRCBkYXRhIHNvdXJjZXMgYW5kIG1vdmllLXJlbGF0ZWQgd2Vic2l0ZXMu&endpointURI=aHR0cDovL2RhdGEubGlua2VkbWRiLm9yZw==&isVirtuoso=ZmFsc2U=&useProxy=dHJ1ZQ==&autocompleteURIs=aHR0cDovL3d3dy53My5vcmcvMjAwMC8wMS9yZGYtc2NoZW1hI2xhYmVsLGh0dHA6Ly94bWxucy5jb20vZm9hZi8wLjEvbmFtZSxodHRwOi8veG1sbnMuY29tL2ZvYWYvMC4xL1BlcnNvbg==&linkURIs=aHR0cDovL3htbG5zLmNvbS9mb2FmLzAuMS9wYWdl&maxRelationLegth=Mg== Kill Bill und Pulp Fiction))\n\n===Anfragen an Wissensdatenbanken stellen und Ergebnisse Anzeigen===\n\nDie folgenden Beispiele entstammen der ((http://wiki.dbpedia.org/OnlineAccess DBpedia Projekt Homepage)).\n\nSuche\n * Suchen in DBpedia: http://dbpedia.org/fct/\n\nSPARQL-Queries:\n * ((http://dbpedia.org/snorql/?query=SELECT+DISTINCT+%3Fpage++{%0D%0A%3Fs+foaf%3Apage+%3Fpage.%0D%0A%3Fs+rdf%3Atype+%3Chttp%3A%2F%2Fdbpedia.org%2Fontology%2FSoccerPlayer%3E+.%0D%0A%3Fs+dbpedia2%3Aposition+%3Chttp%3A%2F%2Fdbpedia.org%2Fresource%2FGoalkeeper%3E+.%0D%0A%3Fs+%3Chttp%3A%2F%2Fdbpedia.org%2Fontology%2Fclub%3E+%3Fclub+.%0D%0A%3Fclub+%3Chttp%3A%2F%2Fdbpedia.org%2Fontology%2Fcapacity%3E+%3Fcap+.%0D%0A%3Fs+%3Chttp%3A%2F%2Fdbpedia.org%2Fontology%2FbirthPlace%3E+%3Fplace+.%0D%0A%3Fplace+%3Fpopulation+%3Fpop%0D%0AFilter+%28xsd%3Aint%28%3Fcap%29+%3E40000+%29+.%0D%0AFilter+%28xsd%3Aint%28%3Fpop%29+%3E10000000+%29+.%0D%0AFilter+%28%3Fpopulation+in+%28%3Chttp%3A%2F%2Fdbpedia.org%2Fproperty%2FpopulationEstimate%3E%2C+%3Chttp%3A%2F%2Fdbpedia.org%2Fproperty%2FpopulationCensus%3E%29%29%0D%0A}+Limit+1000 Alle Fußballspieler, die als Torwart in einen Klub spielten, mit einem Stadion mit mehr als 40.000 Plätzen und die in einem Land mit mehr als 10 Millionen Einwohnern geboren sind))\n * ((http://dbpedia.org/snorql/?query=PREFIX+dbo%3A+%3Chttp%3A%2F%2Fdbpedia.org%2Fontology%2F%3E%0D%0A%0D%0ASELECT+%3Fname+%3Fbirth+%3Fdeath+%3Fperson+WHERE+%7B%0D%0A+++++%3Fperson+dbpedia2%3AbirthPlace+%3Chttp%3A%2F%2Fdbpedia.org%2Fresource%2FBerlin%3E+.%0D%0A+++++%3Fperson+dbo%3AbirthDate+%3Fbirth+.%0D%0A+++++%3Fperson+foaf%3Aname+%3Fname+.%0D%0A+++++%3Fperson+dbo%3AdeathDate+%3Fdeath%0D%0A+++++FILTER+%28%3Fbirth+%3C+%221900-01-01%22%5E%5Exsd%3Adate%29+.%0D%0A%7D%0D%0AORDER+BY+%3Fname Personen die in Berlin vor 1900 geboren wurden))\n * ((http://dbpedia.org/snorql/?query=PREFIX+dbo%3A+%3Chttp%3A%2F%2Fdbpedia.org%2Fontology%2F%3E%0D%0A%0D%0ASELECT+%3Fname+%3Fbirth+%3Fdescription+%3Fperson+WHERE+{%0D%0A+++++%3Fperson+dbo%3AbirthPlace+%3Chttp%3A%2F%2Fdbpedia.org%2Fresource%2FBerlin%3E+.%0D%0A+++++%3Fperson+skos%3Asubject+%3Chttp%3A%2F%2Fdbpedia.org%2Fresource%2FCategory%3AGerman_musicians%3E+.%0D%0A+++++%3Fperson+dbo%3AbirthDate+%3Fbirth+.%0D%0A+++++%3Fperson+foaf%3Aname+%3Fname+.%0D%0A+++++%3Fperson+rdfs%3Acomment+%3Fdescription+.%0D%0A+++++FILTER+%28LANG%28%3Fdescription%29+%3D+%27en%27%29+.%0D%0A}%0D%0AORDER+BY+%3Fname Deutsche Musiker, die in Berlin geboren wurden))\n * ((http://dbpedia.org/snorql/?query=SELECT+%3Ffilm%0D%0AWHERE+{+%3Ffilm+skos%3Asubject+%3Chttp%3A%2F%2Fdbpedia.org%2Fresource%2FCategory%3AFrench_films%3E+} Französische Filme))\n * ((http://dbpedia.org/snorql/?query=PREFIX+dbo%3A+%3Chttp%3A%2F%2Fdbpedia.org%2Fontology%2F%3E%0D%0A%0D%0ASELECT+%3Fmanufacturer+%3Fname+%3Fcar%0D%0AWHERE+{%0D%0A++++%3Fcar+skos%3Asubject+%3Chttp%3A%2F%2Fdbpedia.org%2Fresource%2FCategory%3ALuxury_vehicles%3E+.%0D%0A++++%3Fcar+foaf%3Aname+%3Fname+.%0D%0A++++%3Fcar+dbo%3Amanufacturer+%3Fman+.%0D%0A++++%3Fman+foaf%3Aname+%3Fmanufacturer%0D%0A}%0D%0AORDER+by+%3Fmanufacturer+%3Fname%0D%0A Luxusautos))\n\n===Navigation durch Wissensdatenbanken===\n\nFacetten-basierte Navigation am Beispiel DBpedia\n * http://www.gfacet.org/dbpedia/\n\n===Explore the Catalogus Professorum Lipsiensis===\n\n * http://catalogus-professorum.org\n\n\n\n\n\n" . . . . "2010-07-05T17:06:00"^^ . " ATTENTION: THIS PAGE IS OUTDATED - FOR A CURRENT VERSION, HAVE A LOOK AT http://code.google.com/p/ontowiki/wiki/UsingOntoWikiWithVirtuoso\n\n===Using ~OntoWiki with Virtuoso===\n\nThis guide explains the necessary steps to use ~OntoWiki with ((http://virtuoso.openlinksw.com/wiki/main/Main/ OpenLink Virtuoso)).\n\n====Overview====\nThis is the basic procedure. For details see below.\n\n 1. Check out the ~OntoWiki source code (trunk/ontowiki/src) from ((http://code.google.com/p/ontowiki/source/checkout Google Code)).\n 2. Download ((http://sourceforge.net/projects/virtuoso/ Virtuoso Open-Source Edition)) and compile it according to the instructions for your operating system.\n 3. Install and configure Virtuoso.\n 4. ((http://iodbc.org/index.php?page=languages/php/odbc-phpHOWTO Set up ODBC)) and make sure, PHP can connect to Virtuoso via ODBC.\n 5. Set up ~OntoWiki to be used with Vrituoso.\n\n====Compiling Virtuoso====\nFor some OS binaries exist, e.g. ((http://sourceforge.net/project/showfiles.php?group_id=161622&package_id=182118 Windows)) and ((https://launchpad.net/~wdaniels/+archive/ppa Debian (experimental))). If you have to compile it, it is recommended to give a ****, which will be the path where Virtuoso will be installed. \n**Ubuntu** recommendation: use ./configure --prefix=/opt/virtuoso\nVirtuoso also comes along with a good README with further instructions.\n\nCompiling Virtuoso requires the following build tools be installed.\n\n#|\n|| Package | Version | From ||\n|| autoconf | 2.57 | http://www.gnu.org/software/autoconf/ ||\n|| automake | 1.7 | http://www.gnu.org/software/automake/ ||\n|| libtool | 1.5 | http://www.gnu.org/software/libtool/ ||\n|| flex | 2.5.33 | http://flex.sourceforge.net/ ||\n|| bison | 2.3 | http://www.gnu.org/software/bison/ ||\n|| gperf | 2.7.2 | http://www.gnu.org/software/gperf/ ||\n|| gawk | 3.1.1 | http://www.gnu.org/software/gawk/ ||\n|| m4 | 1.4.1 | http://www.gnu.org/software/m4/ ||\n|| make | 3.79.1 | http://www.gnu.org/software/make/ ||\n|| OpenSSL | 0.9.7 | http://www.openssl.org/ ||\n|#\n\n**Ubuntu**: apt-get install autoconf automake libtool flex bison gperf gawk m4 make openssl libssl-dev \n\nHaving these tools, compiling Virtuoso is just a matter of configure/make.\n\n====Configuring Virtuoso====\nVirtuoso keeps all the files for a database in a folder along with a configuration file. An example configuration file which we will use as a base for our configuration is provided with the default database. To create a Virtuoso database for ~OntoWiki perform the following steps:\n 1. Create a folder named \"ontowiki\" under /lib/virtuoso/.\n 2. Copy the file /lib/virtuoso/db/virtuoso.ini to /lib/virtuoso/ontowiki/virtuoso.ini\n 3. Open /lib/virtuoso/ontowiki/virtuoso.ini in a text editor\n 4. Find the option \"DirsAllowed\", it is a comma-separated list of dirs from which Virtuoso is allowed to open files. Add your home directory, your PHP's temp directory (usually /tmp) and your ~OntoWiki directory under your webroot.\n====Setting up ODBC====\nDatabase connection to Virtuoso happens through ODBC. ODBC is configured by two files, odbc.ini and odbcinst.ini. On Linux systems they can be found under /etc, on Mac OS X systems under ~/Library/ODBC. In case they don't exist, create them.\n 1. Add the following lines to the odbcinst.ini file: %%[virtuoso-odbc]\nDriver = /lib/virtodbc.so%%\n 2. Add the following lines to the odbc.ini file: %%[ODBC Data Sources]\nVOS = Virtuoso\n\n[VOS]\nDriver = virtuoso-odbc\nDescription = Virtuoso Open-Source Edition\nServerName = localhost:1111%%\n\nNow make sure, PHP can connect to Virtuoso via ODBC. On some Linux systems you may have to install the ODBC package for PHP (php5-odbc). To test the connection, create a file called odbctest.php in you webroot with the following PHP code in it:\n%%(php)\n\n
      \n\n
      • \n\n
    \n%%\n\nExecute it by clicking on this link: ((http://localhost/odbctest.php http://localhost/odbctest.php)). You should see a list of graphs stored in your Virtuoso RDF store. On a vanilla Virtuoso installation this list should include the following two graphs:\n * ~http://www.openlinksw.com/schemas/virtrdf#\n * ~http://localhost:8890/DAV\n\nIf you se this list and no error messages along the way, go ahead configuring ~OntoWiki.\n====Configuring ~OntoWiki====\nPerform the following steps to set up ~OntoWiki:\n 1. Copy config.ini-dist to config.ini and open it in a text editor\n 2. Under [private], set the following options:%%store.backend = virtuoso\nstore.virtuoso.dsn = VOS\nstore.virtuoso.username = dba\nstore.virtuoso.password = dba%%\n 3. Optional 1: to enable ~OntoWiki's debug mode, add the line “debug = yes”\n 4. Optional 2: If you didn't change any other config option, create the following directories relative to your ~OntoWiki installation and make them writable to the web-server user.\n * /cache\n * /log\n * /files\n 5. Optional 3: For the ((http://linkeddata.org/ Linked Data)) plug-in to work, copy the htaccess-dist file to .htaccess make sure your Apache's mod_rewrite module is installed and ~AllowOverwrite is set to “All” for your ~OntoWiki directory in your httpd.conf.\n\n===FAQ===\n * SQL Error: [unixODBC][OpenLink][Virtuoso iODBC Driver][Virtuoso Server]FA011: Access to /var/www/ontowiki/libraries/Erfurt/include/SysOntLocal.rdf is denied due to access control in ini file (37000) **Solution:** do Configuring Virtuoso Step 4\n * Uncaught exception 'Zend_Cache_Exception' with message 'Cannot use SQLite storage because the 'sqlite' extension is not loaded in the current PHP **Solution:** go to ibraries/Erfurt/config/config.ini and set cache.enable = 0\n\n===Platform-specific Notes===\n====GNU/Linux====\n====Mac OS X====\nTo auto-start Virtuoso on Mac OS X 10.5 use a config file for the launchd service. It should be placed under /Library/LaunchDaemons. The following is an example file, replace the paths with your settings where necessary.\n%%(html)\nmacbook-pro:~ norman$ cat ~/Library/LaunchDaemons/com.openlinksw.virtuoso.plist \n\n\n\n\n UserName\n root\n GroupName\n wheel\n RunAtLoad\n \n Label\n com.openlinksw.virtuoso\n OnDemand\n \n ProgramArguments\n \n /usr/local/bin/virtuoso-t\n -f\n -c\n /usr/local/var/lib/virtuoso/ontowiki/virtuoso.ini\n \n\n\n%%\n====Windows====\nFollow ((http://virtuoso.openlinksw.com/dataspace/dav/wiki/Main/VOSUsageWindows these instructions)) in order to set up Virtuoso as an ODBC data source on Windows.\n\n====Setting up ODBC on Windows====\nAt installation time two ODBC data source names (DSN's) are created with default values by the Virtuoso installer, the first DSN named \"Local Virtuoso\" provides a link to a local default Virtuoso database server instance, while the other named \"Local Virtuoso Demo\" provides a link to a local Virtuoso server for the Virtuoso demonstration database.\n\nThe process of creating additional ODBC DSN's for you Virtuoso drivers for ODBC is explained in the steps that follow:\n\n 1. Go to the Windows Control panel.\n 2. Double click on the ODBC Administrator applet. On Windows 2000 / XP the ODBC Administrator applet may be called Data Source (ODBC) and may be found under Administrative tools icon of the Control Panel.\n 3. Once the ODBC Administrator has been loaded choose by selecting the appropriate panel whether you want a new User or System Data Source. User Data Sources will only be available to the user that created them. System Data Sources will be available to all users and applications on the system.\n 4. Click on the Add Data Source Name button\n 5. Select the Driver named OpenLink Virtuoso Driver\n 6. Enter values into the fields presented by the Virtuoso Driver's DSN configuration dialog\n\nCheck for the available drivers in the directory path\\to\\Windows\\ODBC. \n\n====Changes to the php file above====\n\nReplace \"VOS\" in\n$conn = odbc_connect('VOS', 'dba', 'dba');\nwith Data Source Name (see step 6.)\n\n====Possible problems when testing OntoWiki====\n\nWarning: domdocument::domdocument() expects at least 1 parameter, 0\ngiven in path\\to\\Zend\\Feed.php on line #\n\nThe solution is to comment out extension=php_domxml.dll in your path\\to\\apache\\bin\\php.ini file:\n\n;extension=php_domxml.dll\n" . . . . "2011-01-21T11:35:45"^^ . "{{Redirect to=\"/Events/2011/LeipzigerSemanticWebDay\"}}" . . . . "2011-01-21T11:36:11"^^ . "{{Redirect to=\"/Events/2011/LeipzigerSemanticWebDay/Einladung\"}}" . . . . "2009-08-10T00:43:53"^^ . "==Friederike Bulka==\n((http://friederike-bulka.de Homepage))\n\n===Diplomarbeit: Geschichtswissenschaftliche Datenbanken als Linked Data im World Wide Web am Beispiel des Professorenkatalogs der Universität Leipzig===\nbearbeitet von: Friederike Bulka\nBetreuer: ((ThomasRiechert Thomas Riechert)) / ((http://www.uni-leipzig.de/histsem/244.html Ulf Morgenstern))\nAbgabetermin: 1.9.2009\n\n{{tree}}\n\n===Links===\n * ((http://professoren.ontowiki.net Professorenkatalog Ontologie))\n * ((http://www.uni-leipzig.de/unigeschichte/professorenkatalog Professorenkatalog Webseite))\n * ((https://addons.mozilla.org/de/firefox/addon/3504 Zotero)) (FF Plugin)\n * ((http://dia-installer.de/index_de.html Dia für Windows)) (Programm zum erstellen von Grafiken)\n" . . . . "2011-11-21T12:10:03"^^ . "<#\n
    \n

    BOA

    \n\"BOA\n

    BOotstrapping linked datA

    \n

    \n

    Try the Beta

    \n
    \n
    \n#>\n\n{{feed title=\"Latest AKSW news\" divclass=\"floatbox\" url=\"http://blog.aksw.org/feed/?cat=22\" max=\"3\"}}\n\n===General Overview===\nMost knowledge sources on the Data Web were extracted from structured or semi-structured data. Thus, they encompass solely a small fraction of the information available on the document-oriented Web. In this paper, we present BOA, an iterative bootstrapping strategy for extracting RDF from unstructured data. The idea behind BOA is to use the Data Web as background knowledge for the extraction of natural language patterns that represent predicates found on the Data Web. These patterns are used to extract instance knowledge from natural language text. This knowledge is finally fed back into the Data Web, therewith closing the loop. We evaluate our approach on two data sets using DBpedia as background knowledge. Our results show that we can extract several thousand new facts in one iteration with very high accuracy. Moreover, we provide the first repository of natural language representations of predicates found on the Data Web.\n\n===Presentation===\nThe following presentation was held at We~KEx at ISWC 2011 in Bonn:\n<#
    BOA - Bootstrapping Linked Data
    #>\n\n===Paper===\nYou can find additional information on how BOA works in this ((http://aksw.org/Projects/BOA/files?get=boa.pdf paper)) presented at the Web Scale Knowledge Extraction Workshop @ ISWC 2011.\n\n===Architecture===\n((http://aksw.org/Projects/BOA/files?get=architecture_new.png))\n\n===Source Code===\nThe source code can be found at the ((http://code.google.com/p/boa Mercurial Google Code Repository)). \n\n===Background Knowledge===\n\n===Generated Knowledge===\nThe generated knowledge can be accessed at the BOA ((http://dydra.com/daniel-gerber/boa dydra repository)).\n\n===Library of Natural-Language Representations of Formal Relations===\nThe results of the BOA approach can be downloaded in form of an Lucene Index. The pattern in this index were derived from applying DBpedia background knowledge on the English Wikipedia. The index was created as follows:\n%%Document doc = new Document();\ndoc.add(new Field(\"uri\", mapping.getProperty().getUri(), Field.Store.YES, Field.Index.NOT_ANALYZED));\ndoc.add(new Field(\"nlr\", pattern.getNaturalLanguageRepresentationWithoutVariables().trim(), Field.Store.YES, Field.Index.ANALYZED));\ndoc.add(new NumericField(\"confidence\", Field.Store.YES, true).setDoubleValue(pattern.getConfidence()));\nwriter.addDocument(doc);%%\nYou can query the index like this:\n%%\nQuery query1 = new TermQuery(new Term(\"nlr\", searchPhrase));\nQuery query2 = NumericRangeQuery.newDoubleRange(\"confidence\", confidenceThreshold, 1D, true, true);\n\nBooleanQuery booleanQuery = new BooleanQuery();\nbooleanQuery.add(query1, BooleanClause.Occur.MUST);\nbooleanQuery.add(query2, BooleanClause.Occur.MUST);\n \nScoreDoc[] hits = indexSearcher.search(booleanQuery, 100).scoreDocs;\n\nfor (int i = 0; i < hits.length && i < 5; i++) {\n \n System.out.println(indexSearcher.doc(hits[i].doc).get(\"uri\"));\n System.out.println(indexSearcher.doc(hits[i].doc).get(\"nlr\"));\n System.out.println(indexSearcher.doc(hits[i].doc).get(\"confidence\"));\n}\n%%\nYou can download this index ((http://aksw.org/Projects/BOA/files?get=pattern_library_en_dbpedia_wikipedia.tar here)). Keep in mind that you need Lucene in at least Version 3.0. We applied very strict rules during pattern filtering, so very few patterns were actually generated. Also there are no score constrains applied to the patterns contained, leading to very weak patterns inside the index.\n\n\n===Contact==={{a name=\"Contact\"}}\n{{vcard name=\"sn\" value=\"Ngonga Ngomo\"}}\n{{vcard name=\"sn\" value=\"Gerber\"}}" . . . . "2011-08-18T06:45:24"^^ . "===An Architecture of a Distributed Semantic Social Network===\n\n * ((http://aksw.org/Projects/MobileSocialSemanticWeb/Architecture Architecture))\n * ((http://aksw.org/Projects/SemanticPingback Semantic Pingback))\n" . . . . "2012-03-07T15:55:43"^^ . "<#\n
    \n

    SlideWiki

    \n

    a Wiki for Presentations

    \n

    SlideWiki is a collaboration platform which enables communities to build, share and play online presentations.

    \n\n
    \n#>\n{{toc}}\n===Main Components===\n====Presentation====\nthemes, transitions\n\n * ((https://github.com/imakewebthings/deck.js deck.js))\n * ((http://twitter.github.com/bootstrap/ Twitter Bootstrap))\n * ((http://www.jstree.com/ JS Tree))\n * Dynamic Stylesheet\n * ((http://sass-lang.com/ SCSS))\n * ((http://lesscss.org/ LESS))\n\n====Revision Management====\ncreating new slide/deck/theme/transition revisions\n\n====Slide Authoring====\nWYSIWYG in-place editor\n * ((http://www.mathjax.org/ MathJax))\n\n====Import/Export====\nsupport of pptx, TeX, html, pdf\n\n====Search====\nsearch slide/deck/tests\n\n====E-Learning====\nquestions, tests\n\n====Social Networking====\nfollow slide/deck/user, discussion\n\n====Synchronization====\n * ((https://github.com/seppo0010/deck.remote.js clients for deck.js))\n\n===Related Resources===\n * ((http://benjeavons.com/web-presentation-tools Survey of web presentation tools))\n\n===Demo===\nAvailable at ((http://slidewiki.aksw.org/ http://slidewiki.aksw.org/))\n\n===Publications===\n * Sören Auer, Ali Khalili, Darya Tarasova, Ivan Ermilov, Timofey Ermilov: ((http://svn.aksw.org/papers/2012/WWW_Slidewiki/public.pdf WikiApp - Engineering of Domain-specific Wiki Applications))\n===Team Members===\n * Sören Auer \n * Ali Khalili \n * Timofey Ermilov \n * Ivan Ermilov \n * Darya Tarasowa\n * Alrik \n * Michael Haschke \n" . . . . "2011-09-02T09:09:58"^^ . "== Maven ==\n\nDL-Learner uses Maven. You can easily include it in your Maven project by adding the following to your pom.xml.\n\nInclude our AKSW group repository:\n%%(html)\n snapshot.maven.aksw\n http://prod1.aksw.org:8081/archiva/repository/snapshots/\n%%\n\nSpecify DL-Learner as dependency, most likely the components-core module:\n\n%%(html)\n org.dllearner\n components-core\n insert version number here\n%%\n\nYou can find existing version numbers at http://maven.aksw.org/archiva/browse/org.dllearner/components-core ." . . . . "2012-03-05T13:39:00"^^ . " Note: There is more information at ((NewPhdStudents)).\n\n\nNew International ~PhD Students\nThis page contains all the Information required for International ~PhD Students.\n\n{{toc}}\n\n====Visa====\nCheck out this website; it tells you what visa to apply for and where to inquire about the documents you need to provide:\n\nhttp://www.zv.uni-leipzig.de/en/study/international-study/general-information/before-your-course-starts/visa-and-entry-regulations.html\n\nAnother place to get information from is the 'Auswärtige Amt': \n\nhttp://www.auswaertiges-amt.de/EN/EinreiseUndAufenthalt/Visabestimmungen_node.html#doc480844bodyText8 \n\nNormally, we provide the following documents for international students:\n- a scholarship contract\n- a letter of invitation in English\n- a letter of confirmation in German regarding the student's position at Uni Leipzig \n\nEven if we call the newcomer's position a research internship, they should principally apply for a study visa (it is the least troublesome type of visa). The important point for the people at the embassy to know is that the contract covers a six-month scholarship, so technichally speaking research interns are scholarship holders at the university of Leipzig. This status is similar to being a student and, thus, it should entitle them to apply for a study visa for which they do not need a work permit (= troublesome procedure). After all, the money they receive is not a salary, i.e. they will not pay any tax or other social costs. Moreover, the position at the department is exclusivcely about research (as a prerequisite for doing a Ph~D).\n\n====Enrollment at the University of Leipzig====\n\nContact: Frau Dr. Stresing\nOffice: Gotherstraße 6, Room 402\nOffice Hours: Tuesdays 13-17, Thursdays 13-15, Fridays 9-11\nPhone: +49 341 9732027\n\n * How to obtain student card for Mensa?\n * How to access the library?\n\n==== Bürgerämt====\n * Register at the Bürgerämt in the first few days when you come.\n * Address: Markgrafenstraße 3, 04109 Leipzig\n * Timings: Mon-Wed, Fri: 9.00-20.00, Thu: 13:00- 20:00, Sat 9:00-16:00\n\n====Ausländerbehörde====\nDocuments Required:\n * Passport\n * Registration confirmation of the resident's office (Burgeramt)\n * Letter of award or contract from university\n * Insurance policy\n * Tenancy agreement\n * Passport photo\n\nAddress:\nPrager Strasse 128 (input B 1) \n04317 Leipzig\n\nOpening Timings:\nMonday: 9.00 - 12.00\nTuesday: 9.00 - 12.00 and 13.00 - 18.00 \nThursday: 9.00 - 12.00 and 13.00 - 16.00\n\nhttp://www.leipzig.de/de/buerger/service/dienste/ausland/index.shtml \n\n====Accommodation====\nThere are basically four options:\n\n1) You may be able to get a room in the university's halls of residence. Officially, there are some restrictions: rooms are usually let only in October each year, contracts must be signed for at least a year and you need to be enrolled as a student. Go here for your online application and check out the halls of residence: \n\nhttp://www.studentenwerk-leipzig.de/wohnen/wohnheime\n\n2) A room that you rent privately in a shared apartment is usually between 150-250 Euro. You can search the electronic bulletin board of the university:\n\nhttp://dsb.uni-leipzig.de/posts?[ad_type]=angebot&[location]=leipzig&[category]=wohnen&full_text=&commit=Anzeigen!\n\n3) Finally, you can rent a small apartment between 250-300 Euro. Take a look at this website:\n\nhttp://www.immobilienscout24.de/Suche/WAZ/Sachsen/Leipzig/Gohlis-Sued_Reudnitz-Thonberg_Stoetteritz_Suedvorstadt_Zentrum_Zentrum-Nord_Zentrum-Nordwest_Zentrum-Ost_Zentrum-Sued_Zentrum-Suedost_Zentrum-West/EURO--400,00/-/0\n\nThese are furnished apartments not far from the university.\nYou can also try to call people (many of them should be able to speak English).\n\n4) Here are a list of hostels in Leipzig:\n * ((http://www.aohostels.com A & O Hostel))\n * ((http://www.globetrotter-leipzig.de Central Globetrotter Hostel))\n * ((http://www.hostel-leipzig.de Hostel Sleepy Lion))\n * ((http://pensionleipzig.net/ Pension Leipzig))\n * ((http://www.leipzig.jugendherberge.de Jugendherberge Leipzig))\n\nMore information on living in Leipzig is provided by the university's international Centre here:\nhttp://www.zv.uni-leipzig.de/en/study/international-study/general-information/before-your-course-starts/living-in-leipzig.html\n\nWebsites to look for houses:\n * http://www.immobilienscout24.de/de/finden/wohnen/index.jsp\n * http://dsb.uni-leipzig.de/\n * http://www.youniq.de/?newLanguage=en\n\nInformation and FAQ's about contracts, maintenance, movements:\n * What is Kaltmiete?\n\n====German language courses====\n * ((http://www.vhs-leipzig.de/ Volkshochschule))\n * ((http://www.uni-leipzig.de/interdaf/ interDaF))\n\n====~PhD Grant Applications====\n * DAAD: ((http://www.daad.org/ DAAD)) \n\n====Miscellaneous====\n\n* Insurance (contracts and workflows)\n * Mawista: http://www.mawista.com/side/\n* Mobile / cell phone contracts\n * BlauWorld: http://www.blauworld.de/ - very cheap for international calls and can be obtained from an EPlus Store\n* Internet contracts / installation\n * Alice: http://www.alice-dsl.de/\n * Kabel Deutchland: http://www.kabeldeutschland.de/\n* Bank accounts\n * Deutche Bank: http://www.deutsche-bank.de/index.htm\n * Location: Martin-Luther-Ring 2, 04109 Leipzig\n * Opening Times: Monday, Tuesday, Thursday: 9:30 - 18:00; Wednesday, Friday: 9:30 - 16:00\n * Student account, Credit Card, Online Banking\n * Sparkasse: https://banking.sparkasse-leipzig.de\n* Credit cards\n * Deutsche Bank\n*((http://www.study-in.de/en/life/job-money/cost-of-living/--11994 How much does it cost to live in Germany?))" . . . . "2010-07-05T17:04:07"^^ . " ATTENTION: THIS PAGE IS OUTDATED\n==Inferenz Plugin für OntoWiki==\n\nZiel des Projektes ist die Konzeption und Implementierung einer Inferenz Komponente für Onto Wiki. Die Komponente soll implizites vorhandene Daten aufdecken und z.B. bei der Eingabe von Semantischen Daten automatisch Ergänzen. Weiterhin soll es die Möglichkeit geben die inferierten semantischen Daten nach einem gewissen Zeitablauf neu zu generieren. \nDass verwenden von Regeln für RDF/OWL Inferenzen in einem Ontologie Editor (in unserem Fall Onto Wiki) stellt hierbei eine Neuerung dar, da es bisher nur von wenigen umgesetzt wird. \n\nDie Umsetzung findet unter anderem im Professorenkatalog Anwendung, wo es den Benutzern erweiterte Suchmöglichkeiten bieten soll. Ein einfaches Beispiel wäre hierbei, die Erweiterung der Wissensbasis um das inverse Gegenstück einer property. Wenn ein Professor einen gewissen Lebensabschnitt hat, so soll an Hand von einfachen geschlossen werden, dass dieser Lebensabschnitt auch zum Professor gehört. (Wenn A hatLebensabschnitt B und hatLebensabschnitt ist invers, dann B istLebensabschnitt von A). \n\nAnforderungen: \n- theorethisches Vorwissen ist nicht nötig, da Wert auf die praktische Anwendung gelegt wird und die einfachsten Regeln, s.o. bereits den Großteil der Use-Cases abdecken.\n\nBesonders an diesem Projekt ist auch, dass an der Unterstützung und Leitung des Projektes eine Diplomantin beteiligt ist, die das Thema in ihrer Arbeit behandelt. (Vorteil: gute Betreuung)\n\nLinks\n\n * http://ontowiki.net\n * http://professoren.ontowiki.net" . . . . "2009-03-05T18:36:49"^^ . "==SWORE Version 1.02==\n\n ((.. SoftWiki Ontology for Requirements Engineering - SWORE))\n \n<#\nDownload SWORE (Version 1.02)\n#>\n\nThe following partners participated in the development: Dirk Fritsch, Jens Lehmann, Kim Lauenroth, Steffen Lohmann, Thomas Riechert and Sebastian Dietzold\n\nThe figure visualises the core of the RE ontology, which we developed in accordance with [2,3,4,5]. Central to our approach are the classes Stakeholder and Abstract Requirement as well as the properties details and defines. Abstract requirements have the subclasses Goal, Scenario, and Requirement, each of which are defined by stakeholders and can be detailed by other abstract requirements. This enables the specification of abstract requirements at different levels of granularity. We emphasise the collaborative aspects of requirements engineering by integrating discussions amongst the stakeholders and voting (with the criteria of agreement and importance) in the model. In the RE process this documentation is often relevant for future decisions.\n\nhttp://powl.svn.sourceforge.net/viewvc/powl/trunk/models/SWORE/swore800.png\n\n===References===\n\n[1] Sören Auer, Klaus-Peter Fähnrich, and Thomas Riechert. ((http://softwiki.de/HomePage SoftWiki)) – Agiles Requirements-Engineering fur Softwareprojekte mit einer großen Anzahl verteilter Stakeholder. In ((http://softwiki.de/RequirementsOntology/files GeNeMe’ 06)) – Gemeinschaft in neuen Medien, 2006.\n\n[2] Peter Haumer, Klaus Pohl, and Klaus Weidenhaupt. Requirements elicitation and validation with real world scenes. IEEE Transactions on Software Engineering, 24(12):1036–1054, December 1998.\n\n[3] Klaus Pohl. Process-centered requirements engineering. Research Studies Press, Advanced Software Development, 1996.\n\n[4] Klaus Pohl: ((http://www.bibsonomy.org/bibtex/23d3fe69cfc985a731293a2051f688458/tausendeins Requirements Engineering)). Grundlagen, Prinzipien, Techniken. Dpunkt Verlag,2007.5. Axel van Lamsweerde. \n\n[5] Goal-oriented requirements engineering: A guided tour. In Fifth IEEE International Symposium on Requirements Engineering (RE’01), pages 249–263. IEEE Computer Society Press, August 2001\n" . . . . "2011-03-11T15:22:14"^^ . "==Linked History==\n\nThe idea of the project derived during our research on prosopographical knowledgebases. We set up together with historians of the University of Leipzig the ((http://catalogus-professorum.org Catalogus Professorum Lipsiensis)) project. This projects contains detailled informations about more then 2000 professors in the university history. \nTo enable collaborative research in the field of prosopographical research existing databases have to be interlinked. Within this project, the AKSW research group and the group of the professors cataloge is developing some services to support this idea.\n\nThe first established service uses the PND-key to interlink persons. \n((!/pnd Detailed Information))\n\nThe second service provides interlinking of calender years.\n((!/calendar Detailed Information))\n \n\nContact: ((/ThomasRiechert Thomas Riechert)) riechert@informatik.uni-leipzig.de\n\n" . . . . "2010-11-29T16:49:42"^^ . "==Bürobedarf==\n\nLE4SW Limit laut Romy: ca. 6000 EUR\n\n**Please all, use the table, other stuff will be IGNORED, we either need the order number for Sobotta or a link to the product**\n**Romy just needs a list of things, doesn't matter where it comes from**\n((http://www.mgoshop.de/cgi-bin/partner/iboshop.cgi?logoffshow0,ID2300000 Link to Sobotta))\n\n#|\n||Description | Order Nr or Link | Name shortcut | Room | Stückpreis | Total | Priority||\n||Chair Younico PRO 2456 Black| PRS2456-5800 | SH, LB, CS, JL| 5-10 | 199 | 796 | High ||\n||Chair Younico PRO 2456 Black| PRS2456-5800 | Sa~S, PK | 5-22 | 199 | 398 | High ||\n||Chair Younico PRO 2456 Black| PRS2456-5800 | PF, NH | 5-08 | 199 | 398 | High ||\n||Chair Younico PRO 2456 Black| PRS2456-5800 | MM, JU, TE | 5-20 | 199 | 597 | High ||\n||Chair Younico PRO 2456 Black| PRS2456-5800 | DG | 5-21 | 199 | 199 | High ||\n||Armrest for Younico (height adjustable to fit under desk) | PRS0950 | SH, LB, CS, JL | 5-10 | 54,90 | 219,60 | High ||\n||Armrest for Younico (height adjustable to fit under desk) | PRS0950 | MM, JU, TE | 5-20 | 54,90 | 164,7 | High ||\n||Armrest for Younico (height adjustable to fit under desk) | PRS0953 | PF, NH | 5-08 | 54,90 | 109,80 | High ||\n||Armrest for Younico (height adjustable to fit under desk) | PRS0953 | DG | 5-21 | 54,90 | 54,90 | High ||\n||Expedit Regal BIRKENACHBILDUNG| ((http://www.ikea.com/de/de/catalog/products/70103085 IKEA)) | MM, JU | 5-20 | 59,00 | 118,00 | High || \n||Expedit Regal BIRKENACHBILDUNG| ((http://www.ikea.com/de/de/catalog/products/70103085 IKEA)) | SH | 5-10 | 59,00 | 59,00 | High || \n||Expedit Einsatz mit Tür WEIß| ((http://www.ikea.com/de/de/catalog/products/40166569 IKEA)) | MM, JU| 5-20 | 16,00 | 64,00 | High || \n||Expedit Einsatz mit Tür WEIß| ((http://www.ikea.com/de/de/catalog/products/40166569 IKEA)) | SH | 5-10 | 16,00 | 32,00 | High || \n||Expedit Einsatz mit 2 Schubladen WEIß| ((http://www.ikea.com/de/de/catalog/products/80166567 IKEA)) | MM, JU | 5-20 | 25,00 | 100,00 | High || \n||Expedit Einsatz mit 2 Schubladen WEIß| ((http://www.ikea.com/de/de/catalog/products/80166567 IKEA)) | SH | 5-10 | 25,00 | 50,00 | High || \n||Schreibtisch BS 12, AHORN| ((http://www.moebelshop24.de/buero/index_bueromoebel.html Möbelshop24)) | JL, LB | 5-10 | 179,00 | 358,00 | High ||\n\n||Wireless Keyboard + mouse | LGTMK250 | LB | 5-10 | 24,90 | 24,90 | Low ||\n|| Maus | ((http://www.amazon.de/Logitech-Optical-optisch-Tastenrad-schwarz/dp/B0029QPJJK/ Amazon)) | JL | 5-10 | 6,99 | 6,99 | Medium ||\n||Keyboard| ((http://www.amazon.de/Cherry-Multimedia-Tastatur-Tasten-schwarz/dp/B001PMRB1S/ref=sr_1_1?ie=UTF8&qid=1287050855&sr=8-1 Amazon)) | SH | 5-10 | 19,55 | 19,55 | Medium ||\n||Drehstuhl Pro-Tec 200 hellbraun | ((http://www.buerostuhl24.com/buerostuhl-drehstuhl-pro-tec-200-stoff-hellbraun.20532.html Link)) | TR | 5-09 | 194,80 | 194,80 | Medium ||\n||Dreifachverteiler | ((http://www.conrad.de/ce/de/product/625075/3FACH-STECKDOSENLEISTE-WEISS Conrad)) | TR | 5-09 | 1,99 | 1,99 | Medium ||\n||Mobile Festplatte für Notebookbackup|((http://www.conrad.de/ce/de/product/412687/FREECOM-HDD-MOBILE-DRIVE-XXS-500GB/0413120 Conrad)) | TR | 5-09 | 77,95 | 77,95 | Medium ||\n||Beamer | ((http://www.amazon.de/eMachines-V700-DLP-Projektor-Kontrast-3200/dp/B003IKOK8M/ Amazon)) | AKSW | 5-10 | 499,00 | 499,00 | Medium ||\n||2x Optische Mause | ((http://www.conrad.de/ce/de/product/908699/TRUST-IZZY-LASER-MAUS-BLUE/ Conrad)) | TR | 5-09 | 14,95 | 29,90 | Medium ||\n||Notebook Cleaning Kit| ((http://www.conrad.de/ce/de/product/775090/HAMA-NOTEBOOK-CLEANING-KIT Conrad)) | TR | 5-09 | 4,95 | 4,95 | High ||\n||Headset| ((http://www.conrad.de/ce/de/product/908478/LOGITECH-H110-HEADSET Conrad)) | TR | 5-09 | 14,95 | 14,95 | High ||\n||2 x USB Stick| ((http://www.conrad.de/ce/de/product/412866/INTENSO-USB-STICK-4GB-MICRO-LINE/ Conrad)) | TR/ST | 5-09 |12,95 | 12,95 | Medium || \n||Dell Reise-Ersatzakku| ((http://accessories.euro.dell.com/sna/productdetail.aspx?c=de&l=de&cs=dedhs1&sku=451-11218 Dell)) | ST | 5-09 | 182,36 | 182,36 | Medium || \n||Laptop SSD| ((http://www.heise.de/preisvergleich/a571272.html Heise Preise)) | ST | 5-09 | 244,36 | 244,36 | Medium || \n||Optimus Maximus keyboard| ((http://www.artlebedev.com/everything/optimus/ other)) | SH | 5-10 | 1667,00 |1667,00 | Super High || \n\n\n||ALREADY ORDERED and paid by SH |((http://cgi.ebay.co.uk/Apple-macbook-pro-15-US-Keyboard-922-8350-backlit-new-/130432856932?pt=UK_Computing_ComputerComponents_KeyboardsMice&hash=item1e5e677364#ht_1608wt_836 macbook pro keyboard)) | AZ | - | 31,57 | - ||\n||ALREADY ORDERED and paid by SH |((http://www.amazon.de/gp/product/B002I8QXHG/ref=oss_product cooling pad )) | AZ | - | 20,15 | - ||\n\n\n\n\n|#\n\n****\n**Preis (2010-10-15 15:32:22): 4247,93 + 12,95**\n\n\n05-08 \n(ST, PF, NH)\n * ((http://www.mgoshop.de/cgi-bin/partner/iboshop.cgi?showd691!,506479315423045,ALC958-11 Arbeitsplatzleuchte mit Doppelgelenk und stabilem Standfuß))\n * ((http://www.mgoshop.de/cgi-bin/partner/iboshop.cgi?showd34!,506479315423045,DUR5718-00 PC-Reinigungsset))\n * ((http://www.mgoshop.de/cgi-bin/partner/iboshop.cgi?showd107!,506479315423045,ALC2854 Türstopper))\n * ((http://www.mgoshop.de/cgi-bin/partner/iboshop.cgi?showd129!,506479315423045,OK6429 3-fach-Verteiler))\n * Weißwandtafel (100 × 150)\n * ((http://www.mgoshop.de/cgi-bin/partner/iboshop.cgi?showd690!,506479315423045,HAN1401-13 Schrank-Set))\n * Hängeregistratur (PF, NH)\n * Regal (B:1m/H:2m/T:30-40cm tief für Ordner/Hängeregistratur)\n\n05-09 \n(So~A, TR)\n\n * Bürostuhl, komfortabel (TR)\n\n05-10 \n(AZ, SH, MM, JL, CS, LB)\n * fixed Beamer at ceiling? (man kann schneller und einfacher etwas präsentieren und es wäre tatsächlich immer ein Beamer da; Einsatz für Reading Group, Gäste und MOLE-Treffen) => geht ev. über HBFG-Antrag (aber wenn wir ein halbes Jahr darauf warten müssen, dann lohnt sich das wg. Umzug ins Hauptgebäude nicht mehr)\n * 2 desks (JL, LB)\n * 1 cupboard (about 2 meter high for storing things, 40 - 60cm deep )\n * 1 American keyboard (MM)\n * 3 PC mouses (JL, ?)\n\n\n05-11 \n(NJ, ...)\n\n05-20 \n(MM, JU, TE)\n * Bürostuhl (Komfortabel: mit Armlehnen, höhenverstellbar und getrennt kippbarer Sitzfläche)\n * Regal (B:1m / H:2m / T:30-40cm tief für Ordner / Hängeregistratur)\n * Hängeregistratur (Tim)\n * 3 x Laser-Mouse (wireless) z.B. ((http://www.winner-leipzig.de/product_info.php/info/p37331_Logitech-VX-Nano-Cordless-Laser-Mouse.html diese hier)) \n * 3 x Keybord (silent! one american)\n * 1 x Holzbank (1 Meter für Pflanzen sowie Studentensitzfläche)\n * Ventilator / alternativly an aircondition / icecrusher ;-)\n * 3x höhenverstellbare Monitore ;-) -> wahrscheinlich erst durch HBFG\n * 3x 3-fachsteckdose mit langem Kabel\n * 1x Verlängerungskabel 5m\n * 1x Mehrfachsteckdose mit vielen Dosen\n * Geschirr: (2x + y) Schüsseln für Müsli etc.\n * Weisswandtafel (100x150)\n\n05-21 \n(Studenten / Prakikanten)\n\n * Papierkorb\n * extra Stühle?\n * Gaderobe\n * Tische sind auch irgendwie verschwunden ;) (SH: einen hat Amrapali, ausserdem sind die prinzipiell zu klein)\n\n05-22 \n(AN, ...)\n * 2x Stuhl\n * 3x 24\" Monitors (HBFG?)\n * 3 Laptops (HBFG?)\n * Tisch" . . . . "2010-07-23T13:37:39"^^ . "==Wachstumskern: ~ReTeVeDa - Regionale Technologieplattform für Vernetzte Daten==\n\nErstes Treffen am 9.7. 14:00 Uhr bei ~LeCoS, Teilnehmer:\n\n * Andreas Both, ((http://www.unister.de Unister)): ((http://aksw.org/Wachstumskern/files?get=unister_vorstellung_am_20100709.pdf Vorstellung))\n * Sören Auer, Sebastian Tramp, Michael Martin, ((http://www.aksw.org AKSW/Uni Leipzig)): ((http://aksw.org/Wachstumskern/files?get=reteveda.pdf Überblick))\n * Lars Nöbel, ((http://www.itcampus.de itCampus)) ((http://aksw.org/Wachstumskern/files?get=itcampus_vorstellung_20100709.pdf Vorstellung))\n * Gerald Saalfeld, Peter Bormann, ((http://www.lecos-gmbh.de LeCoS))\n * Christian Ehrlich, ((http://www.ontos.com Ontos AG)) ((http://aksw.org/Wachstumskern/files?get=ontos.pdf Vorstellung))\n * Thomas Fleck, Michael Ablass, ((http://www.netresearch.de/ Netresearch)) ((http://aksw.org/Wachstumskern/files?get=agenturvorstellung__netresearch_wachstumskern.pdf Vorstellung))\n * Andreas Dürselen, ((http://www.ebrosia.de/ Ebrosia)) ((http://aksw.org/Wachstumskern/files?get=prdsentation_ebrosia.pdf Ebrosia))\n * Manuela Lentzsch, Tobias Gruss, ((http://www.bi-web.de/ BI))\n\nNächstes Treffen am 30.7., 14:00 Uhr bei Unister (Barfußgäßchen 11, 3. Etage, Sekretariat).\n\n * Erarbeitung des Innovationskonzeptes, siehe ((http://www.unternehmen-region.de/_media/wtk_leitfaden%281%29.pdf Leitfaden))\n * Ziel des Treffens:\n * Beantwortung der Frage: Welche Forschungsthemen/Aufgabenpakete erscheinen aus Erfahrung als schwerwiegend?\n * Erweiterung der (bereits geäußerten) Gedanken/Ideen zu konkreten Themenkomplexen\n * besonderes Augenmerk sollte dabei auf den gewünschten Synergie-Effekten liegen \n" . . . . "2011-07-11T11:13:39"^^ . "<#\n
    \n

    ORE

    \n \n

    is a tool for debugging and enriching OWL knowledge bases.

    \n\n

    The ORE (Ontology Repair and Enrichment) tool allows for knowledge engineers to improve an OWL ontology by fixing inconsistencies and making suggestions for adding further axioms to it.

    \n\n

    Ontology Debugging: ORE uses OWL reasoning to detect inconsistencies and satisfiable classes. State-of-the-art methods are then used to detect the most likely sources for the problems. In a simple process, the user can create a repair plan to resolve a problem, while maintaining full control over desired and undesired inferences.

    \n\n

    Ontology Enrichment: ORE uses the DL-Learner framework to suggest definitions and super classes for existing classes in the knowledge base. This works if instance data is available and can be used to detect potential problems and harmonise schema and data in the knowledge base.

    \n

    \n

    Download ORE

    \n
    \n
    \n{{Include page=\"/Projects/ORE/Menu\" nomark=\"1\"}}\n
    \n
    \n#>\n\n{{a name=\"News\"}}\n{{feed title=\"News\" divclass=\"box\" url=\"http://blog.aksw.org/category/projects/ore/feed/\" max=\"5\"}}\n\n" . . . . "2010-11-20T10:38:06"^^ . " 1. About\n - <# Overview #>\n - <# Features #>\n - <# Screenshots #>\n - <# Demo #>\n - ((http://sourceforge.net/projects/dl-learner/files/ORE/0.2/ore-0.2.tar.gz/download Download))\n 2. Docs\n - Manual (TODO)\n - <# Installation #>\n - <# Javadoc #> \n 3. Development\n - <# Architecture #>\n - <# ChangeLog #>\n - <# Eclipse & ORE #>\n - <# Contact Developers #>\n 4. Community\n - ((http://code.google.com/p/ore/ GoogleCode Project Page))\n - ((http://groups.google.com/group/ore-tool Mailing List))\n\n\n" . . . . "2012-05-02T18:25:44"^^ . "== SAIM (Semi-Automatic Instance Matcher) ==\n\n\n{{toc}}\n\nSAIM (pronounced like \"same\") does instance matching on SPARQL endpoints in the Semantic Web. Users can either manually or automatically generate a class matching, property matching and a metric expression. Machine learning algorithms such as RAVEN (RApid actiVE liNking) are integrated in SAIM. Currently, SAIM supports the high-performance ((http://limes.sf.net LIMES)) framework with ((http://www4.wiwiss.fu-berlin.de/bizer/silk/ SILK)) support planned in future work.\n\nArticles:\n * ((http://jens-lehmann.org/files/2011/raven.pdf ISWC 2011 Ontology Matching Workshop Paper about RAVEN))\n\nHomepage: http://saim.sf.net\n\n=== User Interface ===\n\n<##>\n\nThe first beta version of the SAIM user interface will be available soon.\n\nSAIM is localized (the screenshot shows it in a german browser) with english and german localization existing. If you want to provide an additional language just let us know and we can provide you with a resource file template.\n\n=== Game Based Link Verification ===\n<# \n

    As a module of SAIM, we developed an interlinking game with a prupose (GWAP). By verifying links, you earn points, which you can use in the main game to defend against invadors (and save world - as usual). If you disagree with many other users, then you can also get penalties. In the admin console, arbitrary linksets can be uploaded. Depending on the data, facts about resources are displayed in lists or on a map.

    \n

    Try it: http://verilink.aksw.org

    #>\n\n=== Developing SAIM using Eclipse ===\n 1. Make sure you have Java 6, Maven 2 and Eclipse (preferably JEE) installed. \n 2. Install the ((http://subclipse.tigris.org/ Subclipse plugin)) for Subversion support.\n 3. Install the ((http://m2eclipse.sonatype.org/sites/m2e Eclipse m2e Maven plugin )) for Maven support and ((http://m2eclipse.sonatype.org/sites/m2e-extras m2e extras)) \"Maven SCM handler for Subclipse\".\n 4. \"File >> New >> Other...\" >> \"Checkout Maven Projects from SCM\"\n 5. Set SCM URL type to \"svn\" and enter https://saim.svn.sourceforge.net/svnroot/saim/trunk as URL\n 6. Choose \"Finish\"" . . . . "2009-12-16T13:56:23"^^ . "==Publications==\n\n%%(exhibit jsonp=\"http://www.bibsonomy.org/json/user/aksw?items=1000&callback=cb\")\n\n
    \n
    Facets
    \n \n \n \n \n \n
    \n\n
    \n

    \n \n :\n \n \n \n (Editors:\n \n )\n \n \n \n \n

    \n
    \n\n%%" . . . . "2012-03-07T10:40:59"^^ . "<#\n
    \n

    RDFaCE

    \n

    RDFa Content Editor

    \n

    RDFaCE is an RDFa Content Editor based on TinyMCE. It supports different views for semantic content authoring and uses existing Semantic Web APIs to facilitate the annotation and editing of RDFa contents.

    \n\n
    \n#>\n{{feed title=\"Latest news\" divclass=\"floatbox\" url=\"http://blog.aksw.org/category/projects/rdface/feed/\" max=\"5\"}}{{toc}}\n===About===\n<#\n

    RDFaCE is an online RDFa content editor based on TinyMCE. It supports different views for semantic content authoring and uses existing semantic Web APIs to facilitate annotating and editing of RDFa contents. As depicted in the following picture, the RDFaCE system architecture consists of three layers: Rich Text Editor, RDFaCE plugin and External Services layer.

    \n
    \n#>\n**RDFaCE** supports //four different views for semantic text authoring//:\n * WYSIWYG View. What-You-See-Is-What-You-Get\n * WYSIWYM View. What-You-See-Is-What-You-Mean\n * RDF Triple View.\n * Source Code View.\nThe views are synchronized such that changes made in one of the views automatically update the others.\n<#\n
    \n#>\nFurthermore, RDFaCE employs ((http://sindice.com/developers/api Sindice)), ((http://swoogle.umbc.edu/ Swoogle)) and ((http://prefix.cc/ Prefix.cc)) APIs for resource suggestion (providing appropriate URIs for subjects, properties and namespaces).\n\nAnother feature supported by RDFaCE is //combining the results of multiple NLP APIs//. Using this approach, we can harness synergies arising from the combination of different approaches for automatic text annotation. Currently, RDFaCE supports 7 NLP APIs namely ((http://www.alchemyapi.com/api/ Alchemy)),((http://wiki.extractiv.com/w/page/29179775/Entity-Extraction Extractiv)), ((http://www.opencalais.com/APIkey Open Calais)), ((http://www.ontos.com/ Ontos)),((http://www.evri.com/developer/api-registration Evri)), ((http://saplo.com/ Saplo)),((http://lupedia.ontotext.com/ Lupedia)) and ((http://dbpedia.org/spotlight DBpedia spotlight)).\n\nThe RDFaCE approach is very versatile and can be applied in a vast number of use cases. ((http://dev.iptc.org/rNews rNews)), ((http://ontowiki.net/ Ontowiki)) and ((http://wordpress.org/ Wordpress)) are three use cases of RDFaCE.\n===RDFaCE-Lite===\nRDFaCE-Lite is a lite version of RDFaCE which is specifically developed to support the ((http://dev.iptc.org/rNews rNews)) standard for annotating news and blog posts. It supports user-friendly editing of entities by only one click. It also provides support for ((http://www.w3.org/TR/microdata/ Microdata)) (according to ((http://schema.org Schema.org))) as an alternative annotation format.\nThe demo is available at ((http://rdface.aksw.org/lite/ http://rdface.aksw.org/lite/)).\n<#\n
    \n\n
    \n#>\n===Demo===\nTo see RDFaCE in action, please go to:((http://rdface.aksw.org http://rdface.aksw.org))\n<#\n
    \n\n
    \n#>\n===How to Use===\nThe normal annotation process in RDFaCE consists of four steps:\n 1. Defining appropriate namespaces by clicking http://rdface.aksw.org/test/tinymce/jscripts/tiny_mce/plugins/rdface/img/namespace.png button.\n 2. Selecting a fragment of the text.\n 3. Assigning the subject (and type) to be used for the selected fragment by clicking http://rdface.aksw.org/test/tinymce/jscripts/tiny_mce/plugins/rdface/img/about.png button.\n 4.Inserting triples by assigning properties using http://rdface.aksw.org/test/tinymce/jscripts/tiny_mce/plugins/rdface/img/property.png button.\n \nTriples can be seen by launching the triple browser (http://rdface.aksw.org/test/tinymce/jscripts/tiny_mce/plugins/rdface/img/graph.png button).\nYou can go to setting http://rdface.aksw.org/test/tinymce/jscripts/tiny_mce/plugins/rdface/img/setting.png and select one or multiple NLP APIs plus your combination strategy to automatically annotate your content by clicking http://rdface.aksw.org/test/tinymce/jscripts/tiny_mce/plugins/rdface/img/connect.png.\nTo see a report on the entities found by each API, you can press http://rdface.aksw.org/test/tinymce/jscripts/tiny_mce/plugins/rdface/img/stat.png after determining your desired combination.\nTo instantly add a triple using ((http://dev.iptc.org/rNews rNews)) vocabulary, just select a part of the text and then on the context menu (which appears on mouse right click) select your desired type or property.\n===Download===\nYou can download the beta version of RDFaCE from ((https://bitbucket.org/ali1k/rdface/ here)).\nRDFaCE is also available as a ((http://wordpress.org/extend/plugins/rdface/ Wordpress Plugin)).\n===Configuration===\nTo configure RDFaCE plugin you need to follow the normal procedure of adding a plugin in TinyMCE (((http://tinymce.moxiecode.com/wiki.php More info...))).\nTo enable automatic annotation, you need to register for each API and get an API key for it.\nThen go to RDFaCE\\php folder and open proxy.php file. In this file you can set API keys for your desirable enrichment APIs. You can register for current five available APIs at:\n *((http://www.alchemyapi.com/api/ Alchemy))\n *((http://wiki.extractiv.com/w/page/29179775/Entity-Extraction Extractiv))\n *((http://www.opencalais.com/APIkey Open Calais))\n *((http://www.ontos.com/ Ontos))\n *((http://www.evri.com/developer/api-registration Evri))\n *((http://saplo.com/signup/free Saplo))\n *((http://lupedia.ontotext.com/ Lupedia))\n *((http://dbpedia.org/spotlight DBpedia spotlight))\nThen you need to go to rdface/js/util/config.php and set the path of your proxy file.\n===Publication===\nAli Khalili and Sören Auer: ((http://svn.aksw.org/papers/2011/ISWC_RDFaEditor/public.pdf The RDFa Content Editor - From WYSIWYG to WYSIWYM))\n===Contributors===\n{{vcard name=\"sn\" value=\"Khalili\"}}\n{{vcard name=\"sn\" value=\"Auer\"}}\n===Sponsors===\n<# #>\n" . . . . "2011-05-18T15:43:53"^^ . "<#\n
    \n

    Erfurt

    \n\n

    is a PHP / Zend based Semantic Web API for Social Semantic Software.

    \n

    ...

    \n

    Go to erfurt-framework.org

    \n
    \n
    \n\n
    \n
    \n#>\n\n{{toc divclass=\"floatbox\"}}\n===News===\n{{feed title=no divclass=\"afloatbox\" url=\"http://blog.aksw.org/feed/?cat=18\" max=\"2\"}}\n===Features===\n====RDF Parser / Serializer====\n====Triple Storage====\nErfurt uses a storage abstraction layer to access RDF stores as well as includes its own ZendDB based RDF store.\n=====Storage Abstraction=====\nAt the moment, Erfurt implements two different interfaces for the storage abstraction: ZendDB and Virtuoso.\n=====Access Control======\nAccess Control can be managed based on Actions, Models/Graphs ans Statements (currently not in trunk). More Information can reviewed at the ((http://ontowiki.net/Projects/OntoWiki/AccessControl Access Control OntoWiki page)).\n=====Erfurt RDF Store (ZendDB)=====\nThe Erfurt RDF Store consists of an SPARQL to SQL rewriter and a corrsponding relational table layout.\n\n====Versioning====\n====SPARQL Query / Update====\n====Caching====\nThe performance of triple stores is one of the major obstacles for the deployment of semantic technologies in many usage scenarios. In particular Semantic Web applications, which use triple stores as persistence backends, trade performance in for the advantage of flexibility with regard to information structuring. In order to get closer to the performance of relational database-backed Web applications, Erfurt provide a Caching solution for improving the performance of configured triple stores by caching query results and even complete application objects. The selective invalidation of cache objects, following updates of the underlying knowledge bases, is based on analysing the graph patterns of cached SPARQL queries in order to obtain information which updates will change the query result.\nErfurt uses this caching solution internal (if configured) for all needed SPARQL-Queries, but also provide an interface for the usage of applications based on this API.\n\n====Plugins / Trigger====\n====Datagathering / Data Wrapper====\n\n===Tutorial===\n\n===Documentation===\nThe Erfurt API Documentation is available at http://docs.ontowiki.net/api/" . . . . "2009-10-19T11:37:20"^^ . "==AKSW Groups==\n\nThe following subgroups belong to AKSW:\n\n{{tree}}" . . . . "2011-11-11T08:39:32"^^ . "==Research Group Machine Learning and Ontology Engineering (MOLE)==\nMOLE is a subgroup of AKSW.\n\n===Description===\nThe MOLE group focuses on combining Semantic Web and supervised Machine Learning technologies. The goal is to improve both quality and quantity of available knowledge by extracting, analysing, enriching and linking existing data. To make obtained results readily available for use in other applications, the group also provides several established open source tools, frameworks and demonstrators.\n\n===Research Areas===\n\n * Supervised Machine Learning in OWL/RDF knowledge bases\n * Creating knowledge bases from weakly structured data\n * Semi-automatic instance matching\n * Quality assurance and enhancement in ontologies\n\n===Projects===\n\n * ((/Projects/DL-Learner DL-Learner))\n * ((/Projects/DBpedia DBpedia))\n * ((/Projects/LinkedGeoData LinkedGeoData))\n * ((/Projects/NLP2RDF NLP2RDF))\n * ((/Projects/ORE ORE))\n * ((/Projects/ReDDObservatory ReDD))\n * ((/Projects/SAIM SAIM))\n * ((/Projects/AutoSPARQL AutoSPARQL))\n\n===Members===\n#||\n||{{vcard name=\"cn\" value=\"Jens Lehmann\"}}|{{vcard name=\"sn\" value=\"Hellmann\"}}||\n||{{vcard name=\"sn\" value=\"Stadler\"}}|{{vcard name=\"sn\" value=\"Morsey\"}} ||\n||{{vcard name=\"sn\" value=\"Zaveri\"}} |{{vcard name=\"sn\" value=\"Bühmann\"}} ||\n||#\n\n===Publications===\n%%(exhibit jsonp=\"http://www.bibsonomy.org/json/user/aksw/mole?items=1000&callback=cb\")\n\n \n \n \n \n \n
    \n

    \n\n:\n\n\n\n(Editors:\n\n)\n\n\n\n\n

    \n     		\n

    \n\n\n\n\n

    \n
    \n\n%%\n\nGoal: The main goal of MOLE is to simplify or enable the creation, extension, analysis, and linkage of knowledge bases in the Semantic Web by using Machine Learning techniques.\n\n((http://aksw.org/Groups/MOLE/intern MOLE internal area))" . . . . "2011-08-13T10:15:04"^^ . "==Research Group Semantic Abstraction (SIMBA)==\nSIMBA is a subgroup of AKSW.\n\n===Goals===\nSIMBA's focus lies on knowledge extraction, integration, linking and consumption for porting the document-oriented web to the Data Web. For this purpose, SIMBA develops novel and scalable approaches for RDF/OWL extraction, link discovery and graph analysis. In addition, SIMBA provides tools and frameworks that implement these approaches and allow for their swift integration into industry projects.\n\n===Research Areas===\n * Natural Language Processing\n * Extraction of RDF and OWL from unstructured data\n * Link Discovery \n * Machine Learning\n\n===Projects===\n * ((http://aksw.org/Projects/ALOE ALOE))\n * ((http://sourceforge.net/projects/borderflow/ BorderFlow))\n * ((http://aksw.org/Projects/BOA BOA))\n * ((http://sourceforge.net/projects/borderflow/ Cluster Visualization Kit))\n * ((http://disco.informatik.uni-leipzig.de/disco DISCO)) with ((http://bis.uni-leipzig.de/FrankSchumacher Frank Schumacher))\n * ((http://aksw.org/Projects/FOX FOX))\n * ((http://aksw.org/Projects/LIMES LIMES and LIMES++)) with a Research Grant from Amazon\n * ((http://lod2.eu LOD2))\n * ((http://www-tsujii.is.s.u-tokyo.ac.jp/GENIA/home/wiki.cgi?page=Relation+annotation GENIA))\n * ((http://scms.eu SCMS))\n * ((/Projects/SAIM SAIM))\n===Members===\n\n#||\n||{{vcard name=\"sn\" value=\"Heino\"}}|{{vcard name=\"sn\" value=\"Ngonga Ngomo\"}}||\n||{{vcard name=\"sn\" value=\"Jänicke\"}}|{{vcard name=\"sn\" value=\"Gerber\"}}||\n||{{vcard name=\"sn\" value=\"Shekarpour\"}}| ||\n||#\n\n===Publications===\n\n%%(exhibit jsonp=\"http://docs.aksw.org/BibsonomyProxy/exhibit-proxy.php?suffix=user/aksw/simba&callback=cb\")\n\n
    \n
    Navigation
    \n\n\n\n\n\n\n
    \n\n
    \n\n

    \n\n :\n\n\n\n(Editors: )\n\n\n\nlink\n\n

    \n%%\n" . . . . "2011-05-26T10:28:28"^^ . "==Research Group Emergent Semantics==\n\nResearch in Emergent Semantics revolves around supporting semantic collaboration scenarios in an adaptive way. This work includes especially research on engineering and adoption of semantic collaboration software, semantic collaboration protocols as well as research on distributed / federated semantic social networks. To bootstrap semantic collaboration and the semantic web in general, the Emergent Semantics group also investigates basic semantic technologies and semantic web infrastructures.\n\n===Research Areas===\n * Linked Data\n * Distributed / Federated Social Networks\n * Semantic Software Engineering\n * Semantic Web Infrastructure\n * Agile Knowledge Engineering\n\n===Projects===\n====Linked Data====\n * DBpedia\n * OntoWiki\n * Triplify\n\n====Distributed / Federated Social Networks====\n * Mobile Social Semantic Web\n * OntoWiki (DSSN Branch)\n * Semantic Pingback\n * xOperator\n\n====Engineering of Semantic Software====\n * Erfurt\n * RDFauthor\n\n====Semantic Web Infrastructure====\n * Semantic Pingback\n * Triplify\n * Semantic LDAP\n\n====Agile Knowledge Engineering====\n * OntoWiki\n * SoftWiki\n\n===Member===\n\n#||\n||{{vcard name=\"sn\" value=\"Auer\"}}|{{vcard name=\"sn\" value=\"Ermilov\"}}||\n||{{vcard name=\"sn\" value=\"Frischmuth\"}}|{{vcard name=\"sn\" value=\"Heino\"}}||\n||{{vcard name=\"sn\" value=\"Martin\"}}|{{vcard name=\"sn\" value=\"Riechert\"}}||\n||{{vcard name=\"sn\" value=\"Tramp\"}}|{{vcard name=\"sn\" value=\"Unbehauen\"}}||\n||#\n" . . . . "2011-07-08T12:55:08"^^ . "== ORE-Tool ==\n\n!!ORE has moved to its own separate project. See ((http://ore-tool.net)). The content below is deprecated.!!\n\n\n===Overview===\n\nThe ORE (**O**ntology **R**epair and **E**nrichment) tool allows for knowledge engineers to improve an OWL ontology by fixing inconsistencies and making suggestions for adding further axioms to it. \n\n**Ontology Debugging:** ORE uses OWL reasoning to detect inconsistencies and satisfiable classes. State-of-the-art methods are then used to detect the most likely sources for the problems. In a simple process, the user can create a repair plan to resolve a problem, while maintaining full control over desired and undesired inferences.\n\n**Ontology Enrichment:** ORE uses the DL-Learner framework to suggest definitions and super classes for existing classes in the knowledge base. This works if instance data is available and can be used to detect potential problems and harmonise schema and data in the knowledge base.\n\n**Future Work:** In future versions, we also aim to support the detection of more modelling problems including non-logical errors. We will also extend support for knowledge bases available as SPARQL endpoints (in contrast to OWL files) and Linked Data.\n\nTool download: https://sourceforge.net/projects/dl-learner/files/ORE/\n\nThe following screencasts shows how to use the tool:\n**((http://dl-learner.org/files/screencast/ore/0.1/ore.htm Basic Screencast (0.1) ))**\n**((http://dl-learner.org/files/screencast/ore/0.2/ore.htm Inconsistencies in SPARQL Endpoints (ORE 0.2) ))**\n\nThe tool was created by Jens Lehmann and Lorenz Bühmann. If you have any questions or comments, please contact ((http://jens-lehmann.org me)).\n\n===Features===\n * detection of inconsistencies and unsatisfiable classes\n * efficient computation of problematic axioms (justifications)\n * fine-grained justifications, e.g. only showing the relevant parts of the axioms to support a minimal semantic repair\n * displaying impact of selected repair actions\n * enrichment of an ontology by learning definitions and super class axioms using machine learning\n * guides the user through potential consequences of adding those axioms\n * supports debugging as well as enriching very large knowledge bases available as SPARQL endpoints\n===~ChangeLog===\n * Version 0.2:\n * enhanced support for inconsistency detection in large knowledge bases available as SPARQL endpoints\n * based on OWL API 3 and Pellet 2\n * Version 0.1: initial release\n\n\n\n\n" . . . . "2009-10-22T12:22:35"^^ . "== Notes on LOD2 Proposal ==\n\n===TODO (Sebastian+Jens)===\n * wird es eine Tabelle mit einer Übersicht wie bei Weknowit bei Scientific and Technological Base geben ??\n * gebe Chris bescheid, dass er kurz den state of the art und die WPs reviewed morgen\n * dürfte reichen, ich müsste allerdings nochmal drüberlesen --Deliverables für WP3 in einigen Sätzen beschreiben, inklusive konkreter Beteiligung der Partner--\n * --Deliverables für WP4 ausformulieren--\n * --State-of-the-Art Interlinking and Fusion (Sebastian)--\n * WP3 und WP4-Tabelle anpassen nachdem die WP beschreibungen vollendet sind.\n * Section 1.1.3 wie bei ((http://docs.aksw.org/kbpedia/fp7-ict-kbpedia_final.odt KBpedia)), aber angepasst an das ((http://aksw.org/JensLehmann/LOD2/files?get=c_wp_201001_en.pdf aktuelle Work Programme Seite 53-55)) \n * Ganttchart, z.B. mit http://www.ganttproject.biz\n * Milestones für alle Arbeitspakete\n\n===DONE===\n * WP3 Draft\n * WP4 Draft (mit Chris Bizer)\n * Giovanni T. wegen WP3+WP4 nochmal kontaktieren => einige Änderungen im Antrag gemacht und ein Task von Giovanni integriert\n * State-of-the-Art in Machine Learning Based Entity Classification auf 2 Seiten ausbauen (Jens)\n * Section \"Concepts und Objectives\" lesen und teilweise verbessern\n\n===Allgemeine Guidelines===\n\n * pro Tabelle in Abschnitt 1.3d sollen zwei Seiten verwendet werden\n * jede Tabelle enthält:\n * kurze Beschreibung der Objectives\n * Liste von Tasks mit jeweils einem Satz Beschreibung pro Tasks\n * Liste von Deliverables mit jeweils einem Satz Beschreibung pro Deliverable\n * Liste von Milestones für das WP mit jeweils einem Satz Beschreibung pro Milestone\n * die Beschreibungen am Anfang von Abschnitt 1.3 sind ausführlicher -> eine Tabelle sollte aus einer WP-Beschreibung innerhalb von einer halben Stunde erstellt werden können\n * jedes Deliverable in der ausführlichen Beschreibung sollte eine Erklärung enthalten wer konkret an was arbeiten wird (erhöht Glaubwürdigkeit des Antrags)" . . . . "2009-05-12T11:49:08"^^ . "===DL-Learner===\nThe DL-Learner software learns concepts in Description Logics (DLs) from examples. Equivalently, it can be used to learn classes in OWL ontologies from selected objects. It extends Inductive Logic Programming to Descriptions Logics and the Semantic Web. The goal of DL-Learner is to provide a DL/OWL based machine learning tool to solve supervised learning tasks and support knowledge engineers in constructing knowledge and learning about the data they created.\n\n====Purposes of Class Expression Learning====\n 1. Learn Definitions for Classes: Based on existing instances of an OWL class, DL-Learner can make suggestions for class definitions to be included as an owl:equivalentClass or rdfs:subClassOf Axiom. As the algorithm is biased towards short and human readable definitions, a knowledge engineer can be supported when editing the TBox of an ontology (see ((http://dl-learner.org/wiki/ProtegePlugin Protege Plugin))).\n 2. Find similar instances: DL-Learner's suggested class expressions can be used to find similar instances via retrieval (Concept definitions as search). Scalable methods allow the generation of recommendations on the fly, e.g. in a web scenario (see ((http://navigator.dbpedia.org DBpedia Navigator)) - in experimental stage).\n 3. Classify instances: The learned class descriptions can be used in a typical classification scenario, i.e. to decide for unknown instances whether they belong to a certain class. Common ILP benchmarks have been tested with DL-Learner. On the ((http://dl-learner.org/wiki/Carcinogenesis Carcinogenesis)) page, DL-Learner competes with other state-of-the-art ILP algorithms.\n\n=====Example=====\n 1. Instance Classification: A user maintains a list of favorites. Based on these favorites, OWL Concepts are learned with DL-Learner and presented to the user in Natural Language. Such a concept could be all articles about proteins that are written by researchers from Germany (e.g. in Manchester syntax: Proteins and hasAuthor some (Person and hasLocation some Germany)). New articles, which fall in this category and are added to the knowledge base, are presented to the user automatically, like a customized RSS feed.\n 2. Protégé: In a family ontology, a Protégé user wants to create a definition for the Concept 'Father'. He/She already asserted some instances to the class Father. Now, the DL-Learner Protege plugin presents the definition (in Manchester OWL syntax): Male and hasChild some Thing.\n\n====Implementation====\nThe application is written in Java. A user manual can be found ((http://dl-learner.org/files/dl-learner-manual.pdf here)). Also there is an ((http://dl-learner.org/wiki/Overview overview)), a page about its ((http://dl-learner.org/wiki/Architecture architecture)) , and a feature list ((http://dl-learner.org/wiki/Features Features)). DL-Learner is available as Open-Source at ((http://sourceforge.net/projects/dl-learner/ Sourceforge)).\n\nIt has different learning algorithms, which offer several parameters for fine-tuning. It can solve four closely related learning problems: learning based on positive and negative examples, positive only learning, and learning definitions and subclass relationships in ontologies.\n\n====Scalability==== \nAs reasoning is heavily used by DL-Learners algorithms, special methods were introduced to increase performance:\n 1. Fast Instance Checker is a reasoning component, that is custom tailored for the needs of DL-Learner. After an initial reasoning step on the basis of Pellet, results are pre-calculated and cached. Besides the significant performance boost, the component can optionally apply a form of closed world reasoning, which allows to learn expressions like forall and max/min cardinality. It is an approximate reasoning method, where as usual rare cases of incomplete reasoning results are justified by a huge increase in performance.\n 2. DL-Learner can also provide class suggestions for very large knowledge bases, since it uses local fragment reasoning, i.e. only the relevant part (which is small) is used for learning new classes. This enables class learning in real time on knowledge bases like DBpedia. More information can be found ((http://jens-lehmann.org/files/2009_dllearner_sparql.pdf here)).\n\n%%(comments)\nIt has different learning algorithms, which can learn even more efficiently, if parameters are tuned.\n We have not took the effort to investigate formal proofs of correctness. An empirical evaluation showed however, that results are the same. Correctness becomes a minor issue in navigation/recommendation scenarios as it is more important to provide suggestion fast than be formally correct.\n%%" . . . . "2009-05-26T16:48:17"^^ . "===Matching zwischen ~LinkedGeoData und DBpedia===\n\nÜbersicht über Klassen der DBpedia-Ontologie und deren Darstellung in OSM. Klassen, die im Matching nicht berücksichtigt werden sollen, bitte durchstreichen. Klassen, die bereits vom Mapping unterstützt werden, kursiv markieren. Neben der Nutzung für ein besseres Matching zwischen beiden Wissensbasen, könnte das auch verwendet werden um zum Beispiel POIs in ~LinkedGeoData direkt die entsprechende DBpedia-Klasse zuzuweisen.\n\n#|\n|| **DBpedia-Klasse** | **Häufigkeit** | **OSM** | **Quelle/Kommentar** ||\n|| --Actor-- | 6 | - | kein POI ||\n|| --Aircraft-- | 3 | - | kein POI||\n|| --Airline-- | 3 | - | kein POI||\n|| Airport | 7721 | airport=aerodrome | http://wiki.openstreetmap.org/wiki/Mapping/Features/Airport ||\n|| --Album-- | 1 | - | kein POI ||\n|| --Architect-- | 2 | - | kein POI ||\n|| Area | 101099 | - | zu allgemein || \n|| --Artist-- | 11 | - | kein POI||\n|| --Book-- | 2 | - | kein POI ||\n|| Bridge |884 | bridge = ?something | - ||\n|| Broadcast|1724 ||\n|| Building |16748 | - | zu allgemein ||\n|| Cave |36 ||\n|| City | 38668 | place = city/town/village/suburb | http://wiki.openstreetmap.org/wiki/Key:place ||\n|| Cleric |3 ||\n|| College |64 ||\n|| ComicsCharacter| 1 ||\n|| Company |259 ||\n|| Country |556 | place = country | http://wiki.openstreetmap.org/wiki/Map_Features ||\n|| Criminal |3 ||\n|| Disease |3 ||\n|| EducationalInstitution |5051 ||\n|| EthnicGroup | 1 ||\n|| Event |470 ||\n|| FictionalCharacter| 1 ||\n|| Film |7 ||\n|| FilmFestival | 2 ||\n|| GrandPrix |13 ||\n|| Grape |1 ||\n|| HistoricPlace | 9599 ||\n|| Hospital |174 ||\n|| Infrastructure | 55 ||\n|| Island |1057 | place = island | http://wiki.openstreetmap.org/wiki/Map_Features ||\n|| Lake |4479 | natural = water | http://wiki.openstreetmap.org/wiki/Map_Features ||\n|| Language |26 ||\n|| Legislature |18 ||\n|| Lighthouse |588 | man_made = lighthouse | - ||\n|| LunarCrater |1444 ||\n|| Magazine |2 ||\n|| MeanOfTransportation |3 ||\n|| MilitaryConflict | 433 ||\n|| MilitaryPerson | 3 ||\n|| MilitaryUnit | 60 ||\n|| Mountain | 5461 | natural = peak | - ||\n|| Municipality | 8095 ||\n|| MusicFestival | 21 ||\n|| MusicalArtist | 4 ||\n|| MusicalWork | 4 ||\n|| Newspaper | 16 ||\n|| Non-ProfitOrganisation | 14 ||\n|| Organisation | 13213 ||\n|| Park | 221 ||\n|| Person | 33 ||\n|| Place | 191116 ||\n|| PopulatedPlace | 148293 ||\n|| ProtectedArea | 2309 ||\n|| RadioStation | 6042 | amenity = studio | etwas allgemeiner als radio station ||\n|| RecordLabel | 1 ||\n|| Resource | 204877 ||\n|| River | 804 | waterway = ?something bzw. river | riverbank | - ||\n|| Road | 55 ||\n|| Saint | 3 ||\n|| School | 3409 | amenity = school | http://wiki.openstreetmap.org/wiki/Map_Features ||\n|| Scientist | 1 ||\n|| ShoppingMall | 378 ||\n|| Single | 2 ||\n|| ~SiteOfSpecial ~ScientificInterest | 202 ||\n|| SkiArea | 175 ||\n|| Skyscraper | 803 ||\n|| SoccerClub | 47 ||\n|| Song | 1 ||\n|| Species | 12 ||\n|| SportsEvent | 14 ||\n|| SportsTeam | 47 ||\n|| Stadium | 1726 | leisure = stadium | http://wiki.openstreetmap.org/wiki/Map_Features ||\n|| Station | 3747 | railway = station | http://wiki.openstreetmap.org/wiki/Map_Features ||\n|| ~SupremeCourtOf ~TheUnitedStatesCase | 1 ||\n|| TelevisionShow | 7 ||\n|| TradeUnion | 5 ||\n|| University | 1578 | amenity = university | - ||\n|| Weapon | 4 ||\n|| WineRegion | 6 ||\n|| ~WomensTennis ~AssociationTournament | 1 ||\n|| Work | 38 ||\n|| WorldHeritageSite | 799 ||\n|#\n\nDie Häufigkeit wurde durch folgenden Query ermittelt: \n\n%%\nselect ?type, count(DISTINCT(?object))\nwhere {\n?object ?lat .\n?object ?long .\n?object rdf:type ?type .\nFILTER regex ( ?type, \"^http://dbpedia.org/ontology/\" ) .\n}\nGROUP BY ?type\nORDER BY ?type\n%%\n\nDer Query listet alle Klassen alphabetisch auf mit deren Häufigkeit von POIs (POI = latitude/longitude definiert).\n" . . . . "2009-05-19T11:35:25"^^ . "<#
    \n

    \n\n

    \n\n

    #>\n\n==Präsentation des Professorenkatalogs der Universität Leipzig auf dem Campus Tag 2009==\n{{toc from=\"h2\"}}\n\nProfessorenkatalog\n\n===News===\n{{feed url=\"http://www.uni-leipzig.de/unigeschichte/professorenkatalog/blog/?feed=rss2\" max=2 time=yes}}\n \n===Wo und Wann===\n\nOrt: ((http://de.wikipedia.org/wiki/Augustusplatz_(Leipzig) Augustusplatz Leipzig))\n<#\n
    Augustusplatz auf einer größeren Karte anzeigen\n#>\n\nDatum und Zeit: **06./07. Juni 2009, 11-18 Uhr* ** (am Sonnabend bis 21 Uhr)\n\n\n===Programm===\n" . . . . "2009-05-31T03:57:21"^^ . "upUOfS wmienboajzkd, [url=http://fprynnnjvsmc.com/]fprynnnjvsmc[/url], [link=http://kfjyzikrkqlq.com/]kfjyzikrkqlq[/link], http://dnjebdwxxbki.com/" . . . "2009-08-06T19:13:35"^^ . " * Features\n * RDF Parser / Serializer\n * Storage Abstraction / RDF Store\n * Versioning\n * SPARQL Query / Update\n * Caching\n * Plugins / Trigger" . . . . "2010-07-14T10:57:38"^^ . "#summary One-sentence summary of this page.\nInstructions on how to install the OntoWiki VAD\n**Note** the VAD does not yet exist, but here is a collection of steps, which will be turned in a documentation later\n\n== Compiling Virtuoso with PHP ==\n\n=== Ubuntu ===\n * iodbc\n%%(sql)\nsudo su\nmkdir /opt/lib\ncd /opt/lib\nwget 'http://www.iodbc.org/downloads/iODBC/libiodbc-3.52.6.tar.gz'\ntar xfvz libiodbc-3.52.6.tar.gz\ncd /opt/lib/libiodbc-3.52.6/\n./configure --prefix=/opt/lib/iODBC\nmake \nmake install\n%%\n\n * php with correct options\n%%(sql)\nsudo su\nmkdir /opt/lib\ncd /opt/lib\nwget 'http://de2.php.net/get/php-5.2.10.tar.gz/from/de.php.net/mirror'\ntar xfvz php-5.2.10.tar.gz\ncd /opt/lib/php-5.2.10/\n./configure --prefix=/opt/lib/php5 --enable-maintainer-zts --with-tsrm-pthreads --enable-embed=shared --disable-static --with-config-file-path=. --disable-cgi --disable-cli --disable-ipv6 --disable-pdo --without-mysql --without-pear --with-zlib --with-iodbc=/opt/lib/iODBC\nmake \nmake install\n%%\n * virtuoso (libreadline is optional)\n%%(sql)\nLinux 32-bit\n------------\n CFLAGS=\"-O2\"\n export CFLAGS\n ./configure ...\n\nLinux 64-bit\n------------\n CFLAGS=\"-O2 -m64\"\n export CFLAGS\n ./configure ...\n%%\n%%(sql)\nsudo su\nmkdir /opt/lib\ncd /opt/lib\nwget 'http://downloads.sourceforge.net/sourceforge/virtuoso/virtuoso-opensource-5.0.11.tar.gz?use_mirror=dfn'\ntar xfvz virtuoso-opensource-5.0.11.tar.gz\ncd /opt/lib/virtuoso-opensource-5.0.11/\n./configure --prefix=/opt/mynewvos --enable-php5=/opt/lib/php5 --with-iodbc=/opt/lib/iODBC --with-readline=/usr/lib/libreadline.so\nmake \nmake install\n%%\n\n * copy libphp5.so\n%%(sql) \nsudo cp /opt/lib/php5/lib/libphp5.so /opt/lib/virtuoso/lib/virtuoso/hosting/libphp5.so\n%%\n * checkout ow\n%%(sql) \ncd /opt/lib/virtuoso/var/lib/virtuoso/vsp/\nsvn checkout https://ontowiki.googlecode.com/svn/trunk/ontowiki/src/ ontowiki --username xyz\ncp ontowiki/config.ini-dist ontowiki/config.ini\n\n%%\n * configure ow: config.ini\n * change rewrite to true in index.php\n * configure virtuoso ini\n * Load7 = attach, libphp5.so\n * Load8 = Hosting, hosting_php.so\n * dirsAllowed\n * conductor> web app server> virtual directories\n * add new directory ontowiki to default website\n * add rewrite rules in NORMAL mode:\n * upper Rule : %%(sql)/OntoWiki/(.*)$ to /OntoWiki/index.php %%\n * lower Rule: %%(sql)/OntoWiki/(extensions|application|libraries)(.*)\\.(js|ico|gif|jpg|png|css|php|swf)(.*)$ to /OntoWiki/$s1$s2.$s3$s4 %%\n= Rewrite Rules =\n * to me: dont forget\n * adjust index.php\n * change default user from dba\n * ontowiki -> OntoWiki" . . . . "2010-01-10T22:39:57"^^ . "test\n" . . . . "2011-08-10T14:23:37"^^ . "==Developing ORE using Eclipse==\nInstructions on how to prepare Eclipse for developing ORE:\n\n 1. Make sure you have Java 6, Maven 2 and Eclipse installed. \n 2. Install the ((http://subclipse.tigris.org/ Subclipse plugin)) for Subversion support.\n 3. Install the ((http://m2eclipse.sonatype.org/sites/m2e Eclipse m2e Maven plugin )) for Maven support and ((http://m2eclipse.sonatype.org/sites/m2e-extras m2e extras)) \"Maven SCM handler for Subclipse\".\n 4. \"File >> New >> Other...\" >> \"Checkout Maven Projects from SCM\"\n 5. Set SCM URL type to \"svn\" and enter https://ore.googlecode.com/svn/trunk/ as URL\n 6. Choose \"Finish\"" . . . . "2012-01-09T08:58:28"^^ . "<#\n
    \n

    ALOE

    \n\"ALOE\n

    Assisted Linked Data Consumption Engine

    \n\n

    The consumption of Linked Data is a task of increasing complexity on the Web of Data. This complexity is due to several factors, including the sheer size of the Web of Data, the diversity of vocabularies used to describe this data and the lack of schema information in knowledge bases. ALOE provide a semi-automatic solution to address this problem.

    \n\n

    \n

    Try the demo

    \n

    Get the user manual

    \n
    \n
    \n#>\n\n{{feed title=\"Latest news\" divclass=\"floatbox\" url=\"http://blog.aksw.org/category/projects/aloe/feed/\" max=\"3\"}}\n\n===Background===\nThe Linked Open Data (LOD) Cloud contains more than ((http://www4.wiwiss.fu-berlin.de/lodcloud/state/ 31 billion triples)). This wealth of knowledge is expressed by using a large number of vocabularies (e.g., FOAF, VCard, SKOS), leading to a schema mismatch between the different knowledge bases that express knowledge about the same types of entities (e.g., persons). Mismatches at instance level are similarly common, including the use of different units of measure (e.g., cm vs. inch for heights) or data types (e.g., strings instead of doubles for geographical coordinates of locations). The integration of this data is yet central for tasks such as large-scale inference, cross-ontology question answering, graph traversal and especially business applications that require all data to be available from their local servers in a particular format.\n\n===Aim===\nThe aim of the ALOE (Assisted Linked data cOnsumption Engine) project is to provide an engine for the semi-automatic generation of consumption configurations. For this purpose, ALOE can automatically discover class and property mappings across endpoints even when no schema information is available. In addition, ALOE can generate initial specifications for the consumption of Linked Data. For this purpose, it provides several functions for transforming the data from the source knowledge base into a format that corresponds to that of the target knowledge base. Therewith, ALOE enables lay and experienced users to consume Linked Data with great ease. The ALOE process can be controlled via the ((http://134.93.12.38:8080/ALOE?restartApplication interface)) shown below. Please note that the demo only consumes 1000 triples.\n\n<# \"ALOE #>\n\n===Contact===\n{{vcard name=\"sn\" value=\"Ngonga Ngomo\"}}" . . . . "2012-03-24T00:57:48"^^ . "<#\n
    \n

    LODStats

    \n\"Logo\"\n

    LODStats is a statement-stream-based approach for gathering comprehensive statistics\nabout datasets adhering to the Resource Description Framework (RDF).\nLODStats is based on the declarative description of statistical dataset\ncharacteristics.

    \n

    Look at LODStats

    \n
    \n
    \n#>\n\n{{feed title=\"Latest AKSW news\" divclass=\"floatbox\" url=\"http://blog.aksw.org/category/projects/lodstats/feed/\" max=\"3\"}}\n\n===Overview===\nOne of the major obstacles for a wider usage of Web Data is the difficulty to obtain a clear picture of the available datasets. In order to reuse, link, revise or query a dataset published on the Web it is important to know the structure, coverage and coherence of the data.\n\nLODStats is a statement-stream-based approach for gathering comprehensive statistics about datasets adhering to the Resource Description Framework (RDF). LODStats is based on the declarative description of statistical dataset characteristics. Its main advantages over other approaches are a smaller memory footprint and significantly better performance and scalability. We integrated LODStats into the CKAN dataset metadata registry and obtained a comprehensive picture of the current state of the Data Web.\n\n\n=== Demo ===\nA demo installation collecting statistics from all LOD datasets\nregistered on CKAN is available from:\n\n((http://stats.lod2.eu))\n\n=== Installation and Download ===\nLODStats is available via ((http://pypi.python.org/pypi/lodstats PyPI)) (e.g. pip install lodstats) and ((https://github.com/AKSW/LODStats GitHub)) (((https://github.com/AKSW/LODStats))).\n\nInstallation instructions (from ((http://pypi.python.org/pypi/lodstats PyPI))):\n $ sudo apt-get install python-librdf python-virtualenv gcc python-dev python-setuptools\n $ virtualenv $HOME/lodstats-env\n $ . $HOME/lodstats-env/bin/activate\n (lodstats-env) $ pip install lodstats\nInstallation instructions (from source):\n $ git clone https://github.com/AKSW/LODStats\n $ sudo apt-get install python-librdf python-virtualenv gcc python-dev python-setuptools\n $ virtualenv $HOME/lodstats-env\n $ . $HOME/lodstats-env/bin/activate\n (lodstats-env) $ cd LODStats\n (lodstats-env) $ python setup.py install\nUsing LODStats from the command-line:\n $ . $HOME/lodstats-env/bin/activate (if not active already, watch for the altered prompt) \n (lodstats-env) $ lodstats --help\n Usage: lodstats [options] [-m model.{rdf,nt,...}] file/URI\n [...]\n (lodstats-env) $ lodstats -vp some_rdf_file.nt\n\n===Further Information===\n\n * Jan Demter, Sören Auer, Michael Martin, Jens Lehmann: ((http://svn.aksw.org/papers/2011/RDFStats/public.pdf LODStats - An Extensible Framework for High-performance Dataset Analytics)), submitted to ESWC2012\n\n===Contact==={{a name=\"Contact\"}}\n * Jan Demter\n{{vcard name=\"sn\" value=\"Auer\"}}\n{{vcard name=\"sn\" value=\"Martin\"}}\n{{vcard name=\"cn\" value=\"Jens Lehmann\"}}" . . . . "2012-04-26T20:54:44"^^ . "== Sparqlify ==\n**Sparqlify** is a SPARQL-SQL rewriter that enables one to define RDF views on relational databases and query them with SPARQL. It is currently in alpha state and powers the Linked-Data Interface of the ((http://linkedgeodata.org/ LinkedGeoData Server)) - i.e. it provides access to billions of virtual triples from the OpenStreetMap database.\n\n====Key Features====\n * A novel syntax for view definitions inspired by SQL's CREATE VIEW statement. We believe this to lower the learning curve for defining RDB-RDF mappings.\n * A query is rewritten into a single SQL statement, giving all control over query planning to the underlying database system.\n * Support of geo-spatial functions: In general, Sparqlify supports mapping custom SPARQL functions to relational ones. Some mappings for ~PostGIS are already provided (e.g. intersection with polygons).\n\n====Limitations====\nPlease be aware that Sparqlify is currently in alpha state and the following limitations hold:\n * For the moment, only the ~PostgreSQL database system is supported.\n * Only a subset of SPARQL 1.0 + Sub-Queries is supported: For instance, the implementation of aggregate functions including COUNT is still pending.\n * Support for Sparql 1.1 property paths is very unlikely in the near future.\n\n====Download & Source Code====\nhttps://github.com/AKSW/Sparqlify\n\n===Contact==={{a name=\"Contact\"}}\n{{vcard name=\"sn\" value=\"Stadler\"}}\n{{vcard name=\"cn\" value=\"Jens Lehmann\"}}\n{{vcard name=\"sn\" value=\"Auer\"}}\n" . . . . "2012-05-07T13:32:40"^^ . "<#\n
    \n

    4. Leipziger Semantic Web Tag (LSWT2012)

    \n\n\"LSWT\n

    Enterprise Linked Data

    \n

    \nDer Leipziger Semantic Web Tag (LSWT) bietet seit 2009 Unternehmen und Organisationen die Möglichkeit, sich zu Themen im Bereich semantischer Technologien auszutauschen. Im den letzten Jahren wurden Semantic Web Technologien von vielen Firmen in größerem Umfang eingesetzt. Insbesondere das Linked Data Paradigma hat sich von einem forschungszentrischen Thema zu einem Satz von insdustrierelevanten Technologien und Anwendungen entwickelt. Im Fokus der LSWT 2012 mit dem Motto \"Enterprise Linked Data\" steht das Showcasing dieser Technologien im Rahmen von Vorträgen von Experten aus der Industrie und aus der Wissenschaft. \n

    \n
    \n
    \n{{Include page=\"/Events/2012/LeipzigerSemanticWebDay/Menu\" nomark=\"1\"}}\n
    \n
    \n#>" . . . . "2012-03-26T13:38:52"^^ . " 1. Veranstaltung\n - <# Home / Neuigkeiten #>\n - ((/Events/2012/LeipzigerSemanticWebDay/Anfahrt Anreise))\n - ((/Events/2012/LeipzigerSemanticWebDay/Kontakt Kontakt))\n 2. Programm\n 3. Networking\n - ((http://www.facebook.com/event.php?eid=190613310967955 Facebook ))\n 4. Rückblick\n - ((/Events/2011/LeipzigerSemanticWebDay LSWT2011))\n - ((/Events/2010/LeipzigerSemanticWebDay LSWT2010))\n - ((/Events/2009/LeipzigerSemanticWebDay LSWT2009))\n" . . . . "2012-04-17T16:23:05"^^ . "== SPARQL2NL ==\n\n...\n\nInvolved CITEC members:\n\n((http://www.sc.cit-ec.uni-bielefeld.de/people/cunger Christina Unger))\n\nInvolved AKSW members:\n\n#||\n||{{vcard name=\"sn\" value=\"Ngonga Ngomo\"}}|{{vcard name=\"sn\" value=\"Bühmann\"}}||\n||{{vcard name=\"sn\" value=\"Gerber\"}}|{{vcard name=\"cn\" value=\"Jens Lehmann\"}}||\n||#" . . . . "2012-04-26T13:33:51"^^ . "===GeoViz Project===" . . . . "2012-04-26T13:34:12"^^ . "==CubeViz Project==" . . . . "2012-05-15T16:12:19"^^ . "===SparqlMap===\n\nSparqlMap is a SPARQL-to-SQL rewriter. It allows the execution of a SPARQL query fully inside a relational database and does not require dumping the data first. The translation is a light weight process with low requirements on processing power. The mapping of the relational database is expressed using R2RML, the mapping language being currently standardized by a W3C working group.\n\n\n\n===Status===\n\n\n\n===Benchmark results===\n\n\n\n\n\n" . . . . "2012-05-16T15:26:19"^^ . "== ~DeFacto (Deep Fact Validation) ==\n\n~DeFacto (Deep Fact Validation) is an algorithm for validating statements by finding confirming sources for it on the web. It takes a statement (such as ... TODO ...) as input and then tries to find evidence for the truth of that statement by searching for information in the web. In contrast to typical search engines, it does not just search for textual occurences of parts of the statement, but tries to find web pages, which contain the statement phrased in natural language. It presents the user with a confidence score for the input statement as well as a set of excerpts of relevant web pages, which allows the user to manually look at the evidence.\n\nThe project has two use cases:\n * given a statement it can be used to find provenance information for the statement\n * it can directly try to check whether a statement is likely to be true\n\nThe project is currently in alpha status. A description of the approach will be made available soon.\n\nLinks:\n * ((http://defacto.aksw.org/ DeFacto Web Application))\n * ((http://139.18.2.164:8080/boa Boa Pattern Library))\n\n\n===Contact==={{a name=\"Contact\"}}\n{{vcard name=\"cn\" value=\"Jens Lehmann\"}}\n{{vcard name=\"sn\" value=\"Gerber\"}}\n{{vcard name=\"sn\" value=\"Morsey\"}}\n{{vcard name=\"sn\" value=\"Ngonga Ngomo\"}}\n" . . . . "a984d5ac2d92e49750d630db00b5568fb8872e0e" . . "a984d5ac2d92e49750d630db00b5568fb8872e0e" . . "09ac456515dee0896e8eba4b06ae589bef2069cf" . . "e446d8a664490aee5773192d2b0c594acd86475c" . . "ec32af083ec3c2ac6caf31382b923cb3b5ff259f" . . "893930369e250ed883cb5185a1cfc3d13a69e6da" . . "5f927f2afb1042c1fbd1e49c6da04a6e71897775" . . "f573c7cf859e0924ed074c08d0099f9bdd08211b" . . "0c139859a3fa6e69d5ef37916956b5d3f2ec24b1" . . "034052ccc6eab0a231a3c704ac63906a2aa3954a" . . "f39ecce70694ea335714f559eeeae4c82b500435" . . "01fee219e665ecea3905f361517b2bd4a344975d" . . "541fd95f1ce7cc5ae19237fee6022b1bf120e529" . . "a12883c255c1558c868346a8e84991b242ecf7d4" . . "daa8d80e9ad31de26bfe2e8243b58bb8d5b48f74" . . "e6427e417efa4bc9b2057477673c19b99693382f" . . "f27bfe80f5efdafeb57959a4a0e2d3c01d5fe022" . . "da1424f0c235a426122173fabc3f3eedecf84926" . . "55ad9dee88c7ebfee99a2aef3d4b8bf01838e9ce" . . "405360cfbcb0254f2397d9a302f592600b42f216" . . "6ce0644c921cabcad08c10a55da6609d9a02b451" . . "908d870692f13ece257eacea53b581582d912d3d" . . "9a11cd401b5c8395221f81979a457c25d18b9c78" . . "6bdc8369cbc221f498ff01b245f3efcac2f24708" . . "f7f762f0aaa17e577865094ddbb4d0169dd89608" . . "3683d6336c7c99c295e8ff87028decf2d1573712" . . "3d951b646b88aef211561f77c341a9bfd0fc1a17" . . "2ce37bf12d91908001565397d26f981b5c0b1961" . . "5990889506e5dfffcd4b3856573d5143992a0aff" . "Hakuna Matata. :)" . . "fb50a0c9f1ccae1653b2f05cc6ab64969e08e567" . . "4358de5e12239867ff5555b02ef28092db18bf9f" . . "1595bba6c2050fe3962336fb98e08ddcbe9dcf6f" . . "f66f3551ec9cd9fc37d89b852b1b25d77896210d" . . "f633558d38439808aea4f8ce442a63e268c01f62" . . "3f2fe7f1a506dd858fbcf067089df89bf347723c" . . "9bb670e40b9b10956fbe85e6d2296e9c29990a69" . . "c23eb00f82ee89d63e1bffc668d7b48068646d2f" . "Fuck the duck before the duck you fuck" . . "a707115b6842c50d15f4d0d5104df078dea8fcf2" . . "f3901311d6ccfdab186852e4ae63ab8f4fad8206" . . "20541740ae1cbeea50a5153f63bc6f8e4c9f2a6c" . . "5c068011341bd4c3d63a0c337271a82318310a43" . . "ed7848791e7dbe9fddbfb6fed5cfd548f027eac8" . . "de0449c110834d2846a36483b5ab5c174f54c970" . . "106378bbc3e7a3103413229bfc16bef74404d087" . . "8fa0857845d46ec3a190b2721978196279ff9d71" . . "894557f040e1b2e39062c4ec1c3b2a683cc4c03b" . . "269c1bc2c91eb957c63b01a8a8c385d79691bf44" . . "3e873fc82e7405de39cb8dc6f2d2c2e445f8c043" . . "51d78079733f3f51f6a2ded7b543ac6e598b08a1" . . "6ee6fbd8b4b0d98ca0f572ec43bfee4b3e699f9c" . . "91e8a43c4faa3b90f23665ccc6fd5bc9a322d3c5" . . "85bc327c478be042a68d52f06d4417a1450c2486" . . "7bc0a1f3d03b08f27c7373a09d8be81f170904bc" . . "a0dd0e4d394c40b1c3257912a844950005a4b348" . . "bcb9bc13362f0e54a650f2932c85a4493d8f5820" . . "6b7f915da290fced0cfa7b4420aca637df200b99" . . "be82264b1be2a1ac433c143415209d168df39832" . . "4cdf580d4a3e9047530f17e45f1a8371fee68b78" . . "28f98c0bab67ddfca17f2f1d8f9372465f1ecda7" . . "c0ca6780a82159d29215c676948d0a4bb9551ba2" . . "9b0de15067a71e7b98111b1ab041f9181475d70f" . . "e1d1b5678769d5bb646b0359826e7f8bad04b35e" . . "1fdd3f361a4f54d8817ffb1799bbccac0ce9976a" . "It's not easy to feed a rocking horse." . . "d079c9892ba365d91c0514350b17b1fc3fc708d3" . . "3fd9d737e387e750e3b704a450cfb66e1970bfc4" . . "28ce7805ed37e8da5b4d5dd34501e78f794f010c" . . "8c37e32b338737ccce2c7d92f3e9f9924355ac2a" . . "aab7810d3c32b5b425ba0ddbc403ca3a11a57278" . . "af1de740b3b72f056f403d27ffbb01f1a84c8c8f" . . "fb85d8cd04ad80afc6737ce3a6238d548abb0be4" . . "8cde24f26105710228d096928aca5c2af2bd73d4" . . "184120799a7cbae5b4ce678260515f353e5874b5" . . "bba4f4d5bc0123110d8ef279f13e252194a3a18c" . . "a360c6e2cccaaf25e7b99c75670da0c53a307e79" . . "4641d3119e5748b8b3705629c2e4700a49c5572e" . . "3b9d1ae846fc5e5419030b359e8a2a7bf35eb193" . . "4cb5e40703c48bb59c97451a915b04e854f76149" . . "d4081a72eb8b4c18d0b752946ad4b20995c105a1" . . "d81ec2c79acbfa2cdb2533c124e462c0d367cf9d" . . "d26a005fe701703ecd26e8dcf29873b22b9c4edc" . . "812be7e60378fe9e30151b1cc674226c89021345" . . "cc4883e3f9adaab9b23913981cfe63acc3719a0f" . . "df1ac3127e536ef7ec911c9ceaedff18995cba21" . "josue" . . "ad66aef85e6db2478c66604ba5e00bcfcef74711" . . "821c119df9a64c6b88de38b13851bad66f8dc1a8" . . "4557501dd9b465161681b942f9176f5ea7bdd762" . . "9001fd7d048c938942a460cc1c72ad255a3b2e5a" . . "de07d5c4ae571777b0950d4d33b112c6d478676f" . . "0e3b1530182becf9897f79279aef162732367db3" . . "4fc0b25937ba09ac428fa1f21c2162c2f711db8b" . . "e3191d9363d7a24690b14c565b6ef48e6515625b" . . "51e85fa69650311841256c0f41ee82133a4e55ff" . . "e94cf56e89abd5dcd54631b0d8bcdc6ec6839c24" . . "64951a16b073cf68c0e0f291ad9f834bfbf839eb" . . "eba2d2d9ef66b4da6353c55b4cff6316b16cc2fa" .