. "2010-03-11T13:58:42"^^ . "<#\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}}" . . . . "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." . . . . "2010-03-05T14:09:17"^^ . "{{toc divclass=\"floatbox\"}}\n==Projects==\n===Funded Projects===\n\nASKW is funded by regional, national and European research funding programmes.\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====SCMS – Semantic Content Management Systems====\nSCMS 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\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===Incubator Projects===\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====NLP2RDF====\nNLP2RDF is a framework for integrating NLP tools with the aim of producing RDF.\n\nMore information: http://code.google.com/p/nlp2rdf/\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====RDFauthor - Edit RDFa Websites====\nRDFauthor completely hides syntax as well as RDF and ontology data model difficulties from end users and allows to edit information on arbitrary RDFa annotated web pages. RDFauthor extends RDFa with representations for provenance and update endpoint information. It is based on extracting RDF triples from RDFa annotations and transforming the RDFa-annotated HTML view into an editable form by using a set of authoring widgets. As a result, every RDFa annotated web page can be easily made writable, even if information originates from different sources. \n\nMore information: ((Projects/RDF-Author Projects/RDF-Author))\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" . . . . "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))." . . . . "2010-02-09T00:13:49"^^ . "{{toc divclass=\"floatbox\"}}\n==Contact==\nPlease send emails to ((mailto:aksw@informatik.uni-leipzig.de aksw@informatik.uni-leipzig.de)).\n\nOur offices are located in the ((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 center of Leipzig at Johannisgasse 26)) on the 5th floor.\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=\"Frischmuth\"}}\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=\"Martin\"}}\n{{vcard name=\"sn\" value=\"Ngonga Ngomo\"}}\n{{vcard name=\"sn\" value=\"Riechert\"}}\n{{vcard name=\"sn\" value=\"Tramp\"}}\n{{vcard name=\"sn\" value=\"Unbehauen\"}}\n\n===Student Assistents===\nNatanael Arndt\nJonas Brekle\nMarvin Frommhold\nDaniel Gerber\nChristoph Riess\nChristian Würker\nLorenz Bühmann\nChristian Kötteritzsch\n\n===Bachelor / Master Students===\n\n#|\n|| **Student** | **Degree** | **Topic** ||\n|| Claus Stadler | Diplom | DBpedia Live Extraktion ||\n|| Jan Rausch | Diplom | Evaluation of Graph Evolution Algorithms ||\n|| Marvin Frommhold | Master | Entwicklung von domänenspezifischen Ontology-Evolution-Pattern am Beispiel eines holländischen Tourismusportals ||\n|| Daniel Gerber | Master | Semantisches Multimedia-Management ||\n|| Claudius Henrichs | Bachelor | Semantisches Geodatenmanagement ||\n|#\n\n\n===Former Bachelor / Master Students===\n====2010====\nLorenz Bühmann - Master: Reparatur und Erweiterung von OWL Ontologien\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\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===\nJinesh George (summer intern 2009)\nTimofey Ermilov (summer intern 2009)\n\n===Alumni===\n{{vcard name=\"sn\" value=\"Aslam\"}}\n" . . . . "2010-03-01T18:00:18"^^ . "{{Include page=\"/Projects/OntoWiki/Teaser\" nomark=\"1\"}}\n 2009-05-08: All pages for developer are moved to ((http://code.google.com/p/ontowiki/ google code)).\n===News==={{a name=\"News\"}}\n{{cofundos tag=\"OntoWiki\" divclass=\"floatbox\"}}\n{{feed title=no divclass=\"afloatbox\" url=\"http://blog.aksw.org/feed/?cat=5\" max=\"2\"}}\n<#
#>\n\n===Overview==={{a name=\"Overview\"}}\n<##>\n~OntoWiki is a tool providing support for agile, distributed knowledge engineering scenarios. ~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. It fosters social collaboration aspects by keeping track of changes, allowing to comment and discuss every single part of a knowledge base, enabling to rate and measure the popularity of content and honoring the activity of users.\n~OntoWiki enhances the browsing and retrieval by offering semantically enhanced search strategies. All these techniques are applied with the ultimate goal of decreasing the entrance barrier for projects and domain experts to collaborate by using semantic technologies. In the spirit of the Web 2.0 ~OntoWiki implements an \"architecture of participation\" that allows users to add value to the application as they use it.\n\n===Publications==={{a name=\"Publications\"}}\n\n\n%%(exhibit jsonp=\"http://www.bibsonomy.org/json/user/aksw/ontowiki?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" . . . . "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==" . . . . "2009-11-04T16:06:18"^^ . "==DBpedia - Querying Wikipedia like a Semantic Database==\n{{feed title=\"Latest dbpedia news\" divclass=\"floatbox\" url=\"http://blog.aksw.org/feed/?cat=6\" 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." . . . . "2009-05-12T10:00:13"^^ . "<#\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/feed/?cat=10\" 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" . . . . "2007-08-23T19:55:32"^^ . "{{Include page=\"/Projects/DLLearner/Menu\" divclass=\"floatbox\" nomark=\"1\"}}\n==Demo==\n\nWe are currently in the process of developing a web service module for DL-Learner, which makes it possible to implement a web demo. You will find the link pointing to the web demo here, once it is available." . . . . "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-01-21T13:08:25"^^ . "==Publications==\n\n%%(exhibit jsonp=\"http://www.bibsonomy.org/json/user/aksw/aksw?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" . . . . "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))" . . . . "2009-08-02T04:38:03"^^ . "{{Include page=\"/Projects/OntoWiki/Menu\" divclass=\"floatbox\" nomark=\"1\"}}\n The OntoWiki Command Line Interface is only supported in 0.86 and needs to be re-released for OntoWiki > 0.9\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" . . . . "2009-12-15T19:09:58"^^ . "{{vcard name=\"sn\" value=\"Dietzold\"}}\n\n==Publications==\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" . . . . "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)))" . . . . "2009-08-07T14:28:07"^^ . "{{Include page=\"/Projects/OntoWiki/Menu\" divclass=\"floatbox\" nomark=\"1\"}}\n==Changelog==\n{{toc}}\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" . . . . "2010-02-14T15:58:52"^^ . "==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 white circle icon in upper left of 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" . . . . "2008-06-10T08:58:26"^^ . "==Features==\nThis page is intended to give a short description on all relevant ~OntoWiki features. You can also use it as a starting point for detailed documentation (if existing).\n\n{{toc}}\n\n===Installation and Management===\n===={{a name=\"guided-install\"}}Guided Installation====\nInstallation of ~OntoWiki is very easy:\n * Unpack the archive to your directory\n * Start your Browser\n * Go to the OntoWiki directory and follow the instructions\n\nIf you are new to ~OntoWiki, you maybe want to the read the ((FirstSteps First Steps Documentation)).\n\n===={{a name=\"model-acl\"}}User Management====\n\n===={{a name=\"model-acl\"}}Access Control====\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 for an account or a group. We distinguish two types of access (read and write).\n\nA detailed description of access control setup options can be found ((AccessControl here)).\n\n===User Interface===\n====Facet-based Browsing====\nTaxonomic structures give users exactly one way to access the information. Furthermore, the development of appropriate taxonomic structures (whether e.g.\nclass or SKOS keyword hierarchies) requires significant initial efforts. As a pay-as-you-go strategy, facet-based browsing allows to reduce the efforts for a priori knowledge structuring, while still offering efficient means to retrieve information.\nTo enable users to select objects according to certain facets, all property values (facets) of a set of selected instances are analyzed. If for a certain property the instances have only a limited set of values, those values are offered to restrict the instance selection further. Hence, this way of navigation through data will never lead to empty results.\n\n====Inline Editing====\nTo enable users to rapidly edit or add statements as soon as they notice mistakes or missing information OntoWiki features an inline editing mode. A double click on a specific literal or resource presents statement editor based on a widget.\n\n====Map Tab====\nIf selected data (either a single instance or a list of instances) contains property values representing geographical information (i.e. longitude and latitude coordinates) a map view provides information about the geographical location of the selected data.\nTechnically, this view is realized by integrating the ((http://www.google.com/apis/maps/ Google Maps API)). However, the integration is bi-directional, since objects displayed in the map can be expanded and instance details are dynamically fetched from the knowledge base and displayed directly within the map view. The selection of instances to be displayed can be furthermore the result of a facet-based filtering.\n\n====Calendar Tab====\nInstances having property values with the associated datatype xsd:date can be displayed in a calendar view. As for the map view the selection of instances displayed in the calendar view can be the result of a facet-based filtering. Each item displayed is linked to the individual view of the corresponding instance.\n\n====Resource Auto Suggestion====\n\n====Property Configuration====\n\n\n{{a name=\"AdvancedInterface\"}}\n===Advanced User Interface===\n====History / Versioning Tab====\nThis tab provides the opportunity to track, review and selectively rolled-back changes.\n\n====SPARQL Query Shell====\nWith the SPARQL Query Shell advanced users are able to query knowledge bases with arbitrary SPARQL queries.\n\n===={{a name=\"files\"}}File / Document Manager====\nThe File / Document Manager allows users to upload documents (e.g. PDF files). These documents get an identifier as normal resources and can be equipped with meta data as normal resources. In addition to that, these file resources can be received over the net as normal download if they have an URI which is part of the the managed namespace of OntoWiki (e.g. OntoWiki is installed at ##\"\"http://ow.example.com\"\"## and the document has the URI ##\"\"http://ow.example.com/files/example.pdf\"\"##)). The File Manager is accessible over the main menu -> Extras -> File Manager.\n\n===Extensibility===\n===={{a name=\"themes\"}}Themes====\nFrom version 0.6 on, OntoWiki can use different than the default theme. To create a new theme, copy the directory ##themes/default## to ##themes/NewThemeName##.\n\nThe most important theme files are:\n * ##css/default.css## - the default style sheet, change colors and fonts here\n * ##templates/main.php## - the main screen, change overall arrangement here\n\n===={{a name=\"widgets\"}}Widgets====\nWidgets are reusable components of the OntoWiki user interface that the user interacts with. OntoWiki uses the Erfurt Semantic Web Application Framework for a basic set of RDF related widget. Developers can add widgets for specific relations or schema datatypes.\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" . . . . "2008-05-27T17:17:36"^^ . "{{vcard name=\"cn\" value=\"Sebastian Hellmann\"}}\nsee also my ((http://bis.informatik.uni-leipzig.de/SebastianHellmann Workpage))\n\n\n{{tree}}\n\n" . . . . "2008-06-10T19:46:26"^^ . "<#\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{{Include page=\"/Projects/OntoWiki/Menu\" nomark=\"1\"}}\n
\n
\n#>" . . . . "2009-08-02T03:40:16"^^ . "==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**Feel free to add your screenshots** together with a short note about the ~OntoWiki version and an explanation!\n\n{{toc}}\n\n===Contact management with ~OntoWiki===\n<##>\nContact management with ~OntoWiki 0.8 (FOAF / SWRC vocabularies)\n\n===Map view===\n<##>\nMap display filtered by attribute values.\n\n===Editing multiple instances===\n<##>\nEditing multiple instances at once.\n\n===Inline editing===\n<##>\nInline editing of instance data. \n\n===Powl user interface===\nPowl user interface with opened classes tab.\n<##>\n\n\n===Calendar view.===\n<##>\nOntoWiki's calendar view." . . . . "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" . . . . "2008-10-24T13:12:10"^^ . "==Michael Martin==\n\n{{vcard name=\"sn\" value=\"Martin\"}}\n\n{{ToC numerate=0 from=h2 to=h6}}\n\n=== Projekte ===\n((http://aksw.org/Internal/Vakantieland http://aksw.org/Internal/Vakantieland))" . . . . "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." . . . . "2007-07-26T22:27:33"^^ . "===Extending OntoWiki===\n====Creating a new Stylesheet====\n====Creating Themes====\n====Adding Boxes====\n====Adding Tabs====\n====Adding Editing Widgets====\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" . . . . "2009-08-19T15:42:28"^^ . "{{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 and Eclipse installed. \n 2. Install the ((http://subclipse.tigris.org/ Subclipse Plugin)) for Subversion support.\n 3. \"File >> New >> Project\" >> \"Checkout Projects from SVN\"\n 4. Repository Location: https://dl-learner.svn.sourceforge.net/svnroot/dl-learner (If you are not a developer in the DL-Learner project, you can use http instead of https, but you will only have read access to the repository.)\n 5. Choose \"trunk\" and \"Finish\".\n 6. Another project creation wizard should start now. We choose \"Java Project\".\n 7. Project name \"DL-Learner\" (of course you can use a different name). Choose \"Next\".\n 8. Note: The next two steps can also be done later, after all the files have been downloaded from SVN. To access them just right click on the project and change the project settings (Java Build Path, tab Source). (Optionally you can just remove all source folders and then go to \"src/dl-learner\" right-click >> \"BuildPath\" >> \"use as source-folder\".)\n 9. Now you need to add src/dl-learner/ as only source folder in the project. (If Eclipse, for instance, has src/ as source folder by default then disable it - the package symbol disappears - and add src/dl-learner/.)\n 10. Choose DL-Learner/classes/ as output folder (or $project/classes if you used a different project name). Click \"Finish\".\n 11. Eclipse now checks out, so wait for a while. Then select your project in the package explorer and go to \"Project\" >> \"Properties\" >> \"Java Build Path\" >> \"Libraries\". Click Add JARs there and add all JARs in the lib folder (you can select several at once using the Ctrl key).\n 12. Go to \"Project\" >> \"Properties\" >> \"Java Compiler\" >> \"Compiler Compliance Level\" and set it to 6.0. (Previous compiler levels will report errors.)\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\nSimilar instructions apply to other IDEs.\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" . . . . "2010-01-04T11:37:46"^^ . "==Publications==\n\n**Note on Citing**: If you want to refer to the software DL-Learner, please cite the 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 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" . . . . "2009-09-22T15:52:56"^^ . " 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 - <# Basic Installation #>\n - <# Reasoner Installation #>\n - <# Web Service Installation #> \n - <# First Steps #> \n - <# Javadoc #> \n 3. Development\n - <# Architecture #>\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" . . . . "2009-11-30T18:40:49"^^ . "{{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.\n\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" . . . . "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" . . . . "2008-10-29T12:00:01"^^ . "<#\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/feed/?cat=12\" 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%%" . . . . "2008-07-22T20:20:21"^^ . "{{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!)." . . . . "2009-05-06T15:42:56"^^ . "{{Include page=\"/Projects/DLLearner/Menu\" divclass=\"floatbox\" nomark=\"1\"}}\n==~ChangeLog==\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" . . . . "2008-02-02T14:49:58"^^ . "{{Include page=\"/Projects/OntoWiki/Menu\" divclass=\"floatbox\" nomark=\"1\"}}\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" . . . . "2008-07-22T19:26:14"^^ . "{{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" . . . . "2008-07-22T19:25:09"^^ . "{{Include page=\"/Projects/OntoWiki/EventPluginArchitectureMenu\" divclass=\"floatbox\" nomark=\"1\"}}\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" . . . . "2008-05-29T20:59:23"^^ . "==Example Sparql Queries from OntoWiki for testing purposes==\n\nConferences model required!\n\n%%\n# resource list\nSELECT DISTINCT ?resourceUri ?TYPEOBJECT ?TYPELITERAL ?TYPEOBJECT1 ?TYPEOBJECT2\nFROM \nWHERE {\n {\n ?resourceUri ?TYPEOBJECT. \n OPTIONAL {?TYPEOBJECT ?TYPEOBJECT1} \n OPTIONAL {?TYPEOBJECT ?TYPEOBJECT2}\n }\n UNION\n {\n ?resourceUri ?TYPELITERAL\n } \n FILTER (isURI(?TYPEOBJECT)) \n FILTER (isLiteral(?TYPELITERAL)) \n FILTER (\n str(?resourceUri) = || \n str(?resourceUri) = || \n str(?resourceUri) = || \n str(?resourceUri) = || \n str(?resourceUri) = || \n str(?resourceUri) = || \n str(?resourceUri) = || \n str(?resourceUri) = || \n str(?resourceUri) = || \n str(?resourceUri) = \n )\n}\n%%\n%%\n#resource view\nSELECT DISTINCT ?predicate ?predicate1 ?objectResource1 ?predicate2 ?objectResource2 ?objectResource ?objectLiteral\nFROM \nWHERE {\n {\n ?predicate ?objectResource. \n OPTIONAL {?objectResource ?objectResource1} \n OPTIONAL {?objectResource ?objectResource2}\n FILTER (isUri(?objectResource))\n }\n UNION\n {\n ?predicate ?objectLiteral. \n FILTER (isLiteral(?objectLiteral))\n }\n OPTIONAL {?predicate ?predicate1} \n OPTIONAL {?predicate ?predicate2}\n FILTER (str(?predicate) != ) # hide rdf:type\n}\n%%\n%%\n# hierarchy\nSELECT DISTINCT ?classUri ?sub ?subsub ?classUri1 ?classUri2 ?sub1 ?sub2 ?subsub1 ?subsub2\nFROM \nWHERE {\n {?classUri a } \n UNION \n {?classUri a } \n UNION {?instance a ?classUri.} \n UNION {?subtype ?classUri.}\n OPTIONAL {?classUri ?classUri1.}\n OPTIONAL {?classUri ?classUri2.} \n FILTER (isURI(?classUri)) \n FILTER (regex(str(?super), \"^http://www.w3.org/2002/07/owl#\") || !bound(?super)) \n OPTIONAL {?sub ?classUri. \n OPTIONAL {?subsub ?sub.\n OPTIONAL {?subsubsub ?subsub}\n OPTIONAL {?subsub ?subsub1.}\n OPTIONAL {?subsub ?subsub2.}\n }\n OPTIONAL {?sub ?sub1.}\n OPTIONAL {?sub ?sub2.}\n }\n OPTIONAL {?classUri ?super. \n FILTER(isUri(?super))\n }\n FILTER (!regex(str(?classUri), \"^http://www.w3.org/1999/02/22-rdf-syntax-ns#\")) \n FILTER (!regex(str(?classUri), \"^http://www.w3.org/2000/01/rdf-schema#\")) \n FILTER (!regex(str(?classUri), \"^http://www.w3.org/2002/07/owl#\"))\n}\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))" . . . . "2008-12-08T18:42:33"^^ . "{{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-09-26T13:58:14"^^ . "{{files divclass=\"floatbox\"}}\n((http://aksw.org/Internal/Akquise/COST2008/edit edit me)), ((http://aksw.org/Internal/Akquise/COST2008?show_files=1#files turn filesmask on))\n==Internal Area for COST2008==\n((http://infosys1.elfak.ni.ac.yu/InfosysWiki/Wiki.jsp?page=MiloradTosic Milorad Tosic)), ((//SörenAuer Sören Auer)), ((/SebastianDietzold Sebastian Dietzold))\n\n((http://www.cost.esf.org/ COST: Homepage))\n\nCost Open Call: The next collection date for Preliminary Proposals will be 26 September 2008, 17:00 (Brussels time).\n * Past and running actions are available at http://www.cost.esf.org/index.php?id=actions. Download MoU that contains text of full proposal.\n * Title: Semantic social Web\n * COST2008 Project proposal\n\n==Semantic social Web==\n\n\n==Pre-Proposal Structure==\nlimit: 10.000 characters\ncurrent: 10.191 characters\n\n===Abstract ( max 1000 characters, approx. 150 words )===\n\nAn inherent conflict exists between high-risk high-reward nature of R&D and globalized, “flat” funding schemes with short-cycle ROI requirements. Solving the conflict is of crucial strategic importance for success in the future global knowledge-based economy. The main objective of the Action is to establish Community Of Practice about how Semantic and Social Web technologies can be integrated to facilitate: a) short-cycle development of new innovative value added services, and b) it’s integration with participative learning and higher education. Social Web approaches will be applied to nurture participation in the heterogeneous community while semantic technologies are employed to foster adaptive knowledge management. A Wiki-based repository will be used for life-cycle management of generated artifacts: algorithms, methodologies, ideas, ontologies, requirement specification units, and software code. The repository will support end-user participation through applications mashups.\n\n===Key Words ( open format, max 400 characters, approx. 50 words)===\nCommunity development, Agile management, Community Of Practice, R&D Return On Investment, Semantic Web, Social Computing, Social networks, Agile methodologies, Web 2.0\n\n===Preferred COST Domain: ISCH===\n\n\n===BACKGROUND, PROBLEMS===\n\nValue add of basic research is recognized as an enabling factor for bringing efficiency and effectiveness of applied research to a higher level. Applied research is expected to deliver strategic innovation that is of crucial importance for enterprises to sustain and being able to compete in a global economy. However, the extremely short life cycle of products and services, global outsourcing as well as commoditization of technology makes transforming R&D results into measurable competitive advantages a very difficult task. \n\nTraditional R&D return-on-investment models are too rigid to adapt to short-cycle product and service development of the future global knowledge-based economy. For example, IEEE-USA Board of Directors’ Position Statement cites that Return-On-Investment (ROI) for basic research of 28 percent establishes a reasonable order of magnitude, but cautioned that the actual figure may be significantly higher or lower. The main contribution is recognized in products in use in everyday that are direct results of basic research conducted in past 40 to 50 years, as well as creating high paying jobs and development of new ideas and technologies. However, in spite of the conclusion that no other federal investment generates a greater long-term return to the economy and society, recent study indicates that 77% of new R&D sites planned over the next three years by private industry will be located in India or China. Solving the conflict between high-risk high-reward nature of R&D and globalized, “flat” funding schemes with short-cycle ROI imperatives is of strategic importance for success of EU in global knowledge-based economy. \n\nFor the first time, we are able to establish research that would address extreme short-cycle R&D ROI models. Even more, we would reflect on our own research results and establish Community Of Practice (COP) to foster participation. Thanks to the Social Semantic Web technologies, we will integrate basic research, higher education and innovation in the single participative platform.\n\n===BENEFITS===\n\nThe Action aims to remove the gap between creators and users of technology through aligning and integrating support services for heterogeneous communities along the value chain of a knowledge product. It assumes people with diverse competences and knowledge working together and interacting within a community around a single product or service. We envision a growing knowledge base about social interaction patterns emerging within such communities as the main result. We expect to lower barriers for understanding between stakeholders, such as: different languages, geographical locations, different conceptualization of a problem, etc. For example, end-user programming on top of the massive repository of mashups on the Web is used to bridge the chasm between marketing, IT and R&D people. Personalization of social E-Learning applications and services in higher education may be achieved in a similar way.\n\nBeneficiary parties of the Action are multiple: Researchers will gain experience in short cycle participatory development as a base for new ways of thinking necessary for developing innovative research proposals. University professors and educators would get experience in new knowledge creation, engineering, and transfer relevant for participative higher-education learning process. Last but not the least, enterprises involved and/or affiliated with the Action would get the test bed for developing new marketing strategies for short-cycle value-driven knowledge-intensive products and services.\n\n\n===OBJECTIVES, DELIVERABLES AND EXPECTED SCIENTIFIC IMPACT===\n\nThe main objective of the Action is to exchange experiences and knowledge about how Semantic and Social Web technologies can be used for short-cycle development of new innovative value added services driven by a repository of research artifacts. Semantic Web technology is adopted for effective and adaptive management of heterogeneous domain-specific knowledge. Research Collaboration Support Systems and Collaborative Decision Support Systems are integrated in a social computing system. It is envisioned as a Web-based participative open system based on the latest Web technologies (such as Semantic Web and web 2.0) and agile management techniques (such as social decision making, global distributed teams, extremely short development cycles, etc.). \n\nThe platform is going to be used for nurturing diverse communities. The Action’s partners will constitute the core of the community eco-system but we will stimulate participation from other parties also, particularly undergraduate and graduate students, teachers, and industry partners. Reflection on the experience will provide valuable insight into developing such infrastructure for adaptive and interactive knowledge engineering on the Web.\n\nThe Action’s deliverables include:\n1. Community Wiki – a public knowledge log of all activities, experiences, and best practices, \n2. Conference and Workshops materials, \n3. Short time study visits,\n4. Research papers published in Journals and Conferences, \n5. Working Group and Activity reports,\n6. Distributed collaborative student’s projects sponsored by the Action or an industry partners.\n\n\n===SCIENTIFIC PROGRAMME AND INNOVATION===\n\nThe main objective of the proposed Action is to establish synergistic exchange between different research disciplines in order to enable more adaptive, Web enabled ICT applications. Social Web approaches will be applied to nurture participation in the heterogeneous community while semantic technologies are employed to foster adaptive knowledge management. A Wiki-based repository will be used for life-cycle management of generated artifacts: algorithms, methodologies, ideas, ontologies, requirement specification units, and software code. The repository will support end-user participation through applications mashups.\n\nWe identify four generic Competency Profiles (CP): \n * CP-I Infrastructure, \n * CP-T Technology, \n * CP-V Value, and \n * CP-K Knowledge. \nFor each of them, we select several concepts as of crucial importance: Massive storage, algorithms (parallel), cloud/grid computing, and end-user programming constitute infrastructure. On top of the infrastructure, we jointly develop technology (we identify Semantic Web, Social computing or Web 2.0, and Open Source) on one side and value management mechanisms (such as Business models, Licensing, and Economics of participation) on the other side. Knowledge is considered an added value (we expect to identify niche applications in the domains of learning and/or teaching, innovation, science, and enterprise).\n\nIn the center, the platform provides support for dynamic value-generating interaction in a form of a social network: 1) Virtual open space, 2) Semantic Wikis, 3) Collaboration, 4) Participation, 5) On-demand platform. \n\nProspective workgroups are:\n * WG1 Knowledge evolution\n * WG2 Knowledge base authoring and publishing\n * WG3 Integration and interlinking\n * WG4 Legal aspects / IPR clearance\n * WG5 Business models\n * WG6 Learning, teaching and training\n * WG7 Interaction and mashup services repository\n * WG8 Open Space office management \n * WG9 Scalability\n\n\n===ORGANISATION===\nThe overall activities of the Action will be organized and managed in accordance to the open nature of the Action itself. Management of the Action will be carried out by the following //**management units**//: \n 1. Management Committee, \n 1. Working Groups (several), and \n 1. Open Space Office (one). \nThe Management Committee will act as a single contact point for all participants and will be responsible for the overall coordination of the Action. The Management Committee, together with Work Group chairs and the Open Space Office chair, will be responsible for assuring and overseeing organizational, communicational and scientific resources necessary for achieving planned results within the four-year duration of the Action. The Management Committee will meet twice a year: once with Work Groups chairs and once at the Annual Open Work Group Meeting Conference. The Open Space Office will be responsible for the Virtual Open Space as well as for all necessary IT infrastructures. Also, it will manage and organize the Annual Open Work Group Meeting Conference. It will be responsible for dissemination and open participation activities, including Virtual Lobby for additional researchers that are interested in joining the community.\n\nThe Annual Open Work Group Meeting Conference will consist of the two parts: One part of the conference will be a workshop limited to the Action’s members only scope. The second part will be a workshop or conference open for all, where some academics outside the Action, researches and professionals from industry will be invited.\n\nWorking Groups management will be agile such that the Action facilitates the interaction framework for Work Groups, while the work scope, target domain, and even number of the Working Groups is expected to reflect ongoing results of the Action. Each project member is expected to participate in several Work Groups. Initially, we plan to seed the Action with the following //**Working Groups**//:\n 1. Common understanding, \n 1. Knowledge evolution,\n 1. Scalability,\n 1. Business models,\n 1. Multilingualism,\n 1. CHI challenges,\n 1. Legal and IPR\n 1. Privacy and Security\n 1. Learning and Higher education\n 1. Innovation,\n 1. Economics of participation\n\nIn addition to the management units (Management Committee, Working Groups, and Open Space Office), the Action specifies the following //**Activity Forms**//: \n 1. Virtual Open Space, \n 1. Wiki based interactive community Web spaces, \n 1. Wiki books,\n 1. Open Internship Office, \n 1. Virtual Lobby\n 1. short-term visits, \n 1. Journal publications, \n 1. Conferences and \n 1. Workshops.\n\nPerformance evaluation of the Action will be based on the success of activities planned for management units as well as quantitative measures of results based on the proposed activity forms.\n\n==Potential Partners==\n * Milorad Tosic, InfoSys Lab, Faculty of Electronic Engineering, University of Nis - Serbia\n * Sören Auer, AKSW, Universität Leipzig - Germany\n * Sebastian Schaffert, Salzburg Research - Austria\n * Marija Cubric, Blended Learning Unit, University of Hertfordshire - UK\n * Rinke Hoekstra, Leibniz Center for Law, University of Amsterdam - Netherlands\n * Peter Mika, Yahoo! Research - Spain\n * Bey Youcef, GETALP (Group d'Etude et Traitement de Langue et Parole), LIG (Laboratoire de Grenoble), Joseph Fourier University - France\n * KMi, Open University - UK\n * DERI Galway - Ireland\n * Josef Stefan Insitute - Slovenia\n * Claudia Müller, Universität Stuttgart - Germany\n * Universität Karlsruhe - Germany\n * Bulgaria\n * Turkey\n * Portugal\n * Greece\n * Finland\n * Italy\n\nhttp://aksw.org/Internal/Akquise/COST2008/files?get=costproposal.png\n" . . . . "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" . . . . "2008-07-11T18:13:03"^^ . "==OntoWiki Plugin==\n\n" . . . . "2008-12-08T18:35:58"^^ . "{{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" . . . . "2008-07-11T18:23:24"^^ . "!! 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" . . . . "2008-07-11T18:22:52"^^ . "Um 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-12-05T18:53:14"^^ . "==Plugins and Events==\n\n * ((/Projects/OntoWiki/EventPluginArchitecture Overview: Plugins and Events))\n * ((/Projects/OntoWiki/EventPluginArchitecture/PluginDevelopment Plugin Development))\n * ((/Projects/OntoWiki/PluginCookbook Plugin Cookbook)) (work in process)\n * ((/Projects/OntoWiki/EventPluginArchitecture/PluginDevelopment/PluginExamples Examples))" . . . . "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))" . . . . "2008-10-03T11:39:41"^^ . "==OntoWiki 1.0 SPARQL Queries==\n\n===Resource View===\nGetting all predicates for #### with name properties for the predicate and object IRIs. Variables with numbers are automatically produced from an array of possible name properties. Literal objects are speperated by datatype.\n%%(sql)\nSELECT DISTINCT ?predicate ?predicate0 ?objectResource0 ?predicate1 ?objectResource1 ?objectResource \n ?objectLiteralstring ?objectLiteralboolean ?objectLiteralinteger ?objectLiteraldate ?objectLiteralanyURI\nFROM \nWHERE {\n {\n ?predicate ?objectResource. \n OPTIONAL {?objectResource ?objectResource0} \n OPTIONAL {?objectResource ?objectResource1}\n FILTER (isUri(?objectResource))\n }\n UNION\n {\n {\n ?predicate ?objectLiteralstring. \n FILTER(datatype(?objectLiteralstring) = )\n }\n UNION\n {\n ?predicate ?objectLiteralboolean. \n FILTER(datatype(?objectLiteralboolean) = )\n }\n UNION\n {\n ?predicate ?objectLiteralinteger. \n FILTER(datatype(?objectLiteralinteger) = )\n }\n UNION\n {\n ?predicate ?objectLiteraldate. \n FILTER(datatype(?objectLiteraldate) = )\n }\n UNION\n {\n ?predicate ?objectLiteralanyURI. \n FILTER(datatype(?objectLiteralanyURI) = )\n }\n FILTER (isLiteral(?objectLiteral))\n }\n OPTIONAL {?predicate ?predicate0} \n OPTIONAL {?predicate ?predicate1}\n FILTER (?predicate != )\n #FILTER (str(?predicate) != str()) \n #FILTER (str(?predicate) != )\n}\nORDER BY ?predicate\n%%\n\n===Hierarchy===\nGetting any resource that is possibly a class along with subclasses and subclasses thereof. Blank node on the first level as well as resources from RDF, RDFS, OWL namespaces are ignored.\n%%(sql)\nSELECT DISTINCT ?classUri ?sub ?subsub ?subsubsub ?classUri0 ?classUri1 ?sub0 ?sub1 ?subsub0 ?subsub1\nFROM \nWHERE {\n {?classUri a }\n UNION\n {?classUri a } \n UNION {?instance a ?classUri.} \n UNION {?subtype ?classUri.}\n OPTIONAL {?classUri ?classUri0.}\n OPTIONAL {?classUri ?classUri1.} \n FILTER (isURI(?classUri))\n FILTER (regex(str(?super), \"^http://www.w3.org/2002/07/owl#\") || !bound(?super)) \n OPTIONAL {?sub ?classUri. \n OPTIONAL {?subsub ?sub.\n OPTIONAL {?subsubsub ?subsub}\n OPTIONAL {?subsub ?subsub0.}\n OPTIONAL {?subsub ?subsub1.}\n } \n OPTIONAL {?sub ?sub0.}\n OPTIONAL {?sub ?sub1.}\n }\n OPTIONAL {?classUri ?super. \n FILTER(isUri(?super))\n }\n FILTER (!regex(str(?classUri), \"^http://www.w3.org/1999/02/22-rdf-syntax-ns#\")) \n FILTER (!regex(str(?classUri), \"^http://www.w3.org/2000/01/rdf-schema#\")) \n FILTER (!regex(str(?classUri), \"^http://www.w3.org/2002/07/owl#\"))\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" . . . . "2010-03-03T12:25:58"^^ . "{{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/project/showfiles.php?group_id=203619&package_id=303679 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 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.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" . . . . "2009-09-25T12:49:13"^^ . "==~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/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" . . . . "2009-10-02T09:35:24"^^ . "===((http://aksw.org/SebastianHellmann/wortschatz/edit EDIT))===\n\nOrt: Zingst Aussenstelle Leipzig\nhttp://www.uni-leipzig.de/dezernat1/sg14/zingst_komplett.pdf\n\nPlanungskommitee: \n * Matthias Q.\n * Sebastian H. \n * Olaf H. ?\n * Jörg W. ?\n * Jörg U. ?\n\nKosten 8 eur pro Tag und Person für Mitarbeiter und Studenten der Uni Leipzig\n18 für andere\nmaximal 18 Personen.\n\nBesetzte Tage in Zingst;\n\n18.1.-24.1.\n6.5.-17.5.\n4.6.-7.6.\n17.6.-20.6.\n7.7.-11.7.\n23.9.-29.9\n" . . . . "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" . . . "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" . . . . "2010-02-26T10:11:28"^^ . "===TIGER Corpus Navigator===\n\nClick ((http://db0.aksw.org:8080/navigator-0.0.1-SNAPSHOT/org.nlp2rdf.navigator.Application/Application.html here)) to go to the navigator.\n\nMore information can be found ((http://bis.informatik.uni-leipzig.de/SebastianHellmann?v=po4#h520-5 on this page)) in Sebastian Hellmann, Jörg Unbehauen, Christian Chiarcos, Axel Ngonga PDF DocumentThe TIGER Corpus Navigator submitted to ACL System Demonstrations 2010 " . . . . "2010-03-02T06:52:19"^^ . "ocJ7b6 rlywvetrtlin, [url=http://tjqqlcotixdw.com/]tjqqlcotixdw[/url], [link=http://hursjckhuhzg.com/]hursjckhuhzg[/link], http://euwrinhjdtly.com/" . . . "2008-12-08T18:34:12"^^ . "{{Include page=\"/Projects/OntoWiki/EventPluginArchitectureMenu\" divclass=\"floatbox\" nomark=\"1\"}}\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" . . . . "2010-02-25T19:00:58"^^ . "<#\n
    \n

    NLP2RDF

    \n\n\n

    is a framework that integrates multiple NLP tools in order to assess the semantic meaning of the annotated text by means of RDF/OWL descriptions.

    \n

    Natural language (a character sequence) is converted into a more expressive formalism -- in this case OWL-DL --\nthat grasps the underlying meaning and serves as input for (high-level) algorithms and applications with a focus on machine learning. Read more ...

    \n\n
    \n\n
    \n#>\n\nThe project is in an early phase and a software release is scheduled next month.\nUntil then, the source code is available on ((http://code.google.com/p/nlp2rdf/ Google Code))\n\nCurrently, we are deploying the TIGER Corpus Navigator ((http://bis.informatik.uni-leipzig.de/SebastianHellmann?v=po4#h520-5 read more...)).\nReachable ((http://db0.aksw.org:8080/navigator-0.0.1-SNAPSHOT/org.nlp2rdf.navigator.Application/Application.html here))\n{{a name=\"News\"}}\n{{feed title=\"News\" divclass=\"box\" url=\"http://blog.aksw.org/feed/?cat=10\" max=\"5\"}}" . . . . "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-03-11T14:45:01"^^ . "{{toc divclass=\"floatbox\"}}\n==GI 2010 Workshop on \"Web Science\"==\n\n//co-located with ((http://www.informatik2010.de/ GI-Jahrestagung 2010))//\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===Extent, structure, and selection of contributions===\n\nSubmitted papers should not exceed the maximum length of six (6) pages for the printed proceedings. In addition authors can submit an 12-pages extended version of their articles for the online proceedings and distribution on USB stick during the conference. Papers should be submitted to the ((http://139.18.8.225:8080/ConfISS/portal/conferenceOverview.html?cid=4 GI conference management system)).\nPapers will be evaluated anonymously by two independent evaluators from the program committee.\nAccepted papers are published in the proceedings of the GI conference.\nThe paper layout must conform to the guidelines provided by \"Lecture Notes in Informatics (LNI)\" (http://www.gi-ev.de/service/publikationen/lni/).\nPlease adhere to the GI formatting style.\nIt is expected that at least one author of each accepted paper officially registers for the conference.\nSubmissions will be accepted in German and English (preferred language).\n\n===Important Dates===\n * 25.04.2010 **Paper Submission**\n * 24.05.2010 **Acceptance Notification**\n * 30.06.2010 **Final paper version due**\n * 28.09.2010 **Workshop in conjunction with the GI-Jahrestagung**\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 (requested)\nDaniel Dietrich, Open Data Network\nRainer Fröse, IFM-Geomar / FishBase (requested)\nAndreas Geyer-Schulz, Institute of Technology Karlsruhe (requested)\nJonathan Gray, Open Knowledge Foundation \nDaniel Hladky, Ontos AG \nAndreas Hotho, University of Würzburg\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 (requested)\nRobert Tolksdorf, Freie Universität Berlin \n\n" . . . . "2009-11-04T15:09:56"^^ . "{{feed title=\"Latest LGD news\" divclass=\"floatbox\" url=\"http://blog.aksw.org/feed/?cat=16\" max=\"5\"}}\n<##>\n\n==~LinkedGeoData==\n\nhttp://aksw.org/Projects/LinkedGeoData/files?get=linkedgeodata_browser_1228843461681.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 bi-directional live integration of OSM and our Linked Geo Data browser and editor is currently in the works.\n * ((http://linkedgeodata.org/ Triplify spatial data publishing)), the ((http://Triplify.org Triplify script)) for publishing linked data from relational databases is extended for publishing geo data, in particular with regard to the retrieval of information about geographical areas.\n * ((http://linkedgeodata.org/browser/ LinkedGeo Data browser and editor)) is a facet-based browser for geo content, which uses an OLAP inspired hypercube for quickly retrieving aggregated information about any user selected area on earth.\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\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))" . . . . "2009-11-04T15:16:25"^^ . "{{feed title=\"Latest Triplify news\" divclass=\"floatbox\" url=\"http://blog.aksw.org/feed/?cat=15\" 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" . . . . "2009-01-28T21:40:27"^^ . "==Erfurt Data Structures==\n\n===Statements===\nStatements a