Changes between Initial Version and Version 1 of Notes/SemanticWiki

05/01/2015 01:23:28 PM (4 years ago)



  • Notes/SemanticWiki

    v1 v1  
     3= Semantic Wikis = 
     5Semantic Wikis exist in not that many different flavours, if you like flavours ... see [[Wikis]] 
     7|| Semantic !MediaWiki || see [[SemanticMediawiki]] 
     8|| !KiWi - Java EE and JBoss Seam based semantic wiki engine || || 
     9|| ||  || 
     11See [[Java#SemanticWikis]] 
     13== Python !SemWiki == 
     15 !SemWiki -  in Python  || || 
     17 This project is written in Python, and depends on rdfrest, which is available as a part of 
     19 Python kTBS 
     21 This project is actually made of two subprojects: 
     23  rdfrest: A framework for RDF-based REST-ful services 
     25  kTBS: A kernel for trace-based systems (python implementation) 
     29 This tutorial aims at helping you install kTBS and running it, either as a standalone service or behind an Apache HTTP server. It has been written using Ubuntu server 12.10, but should be applicable with only minor changes (if any) to other flavours of Linux, and a few adaptation on MacOS or MS Windows. 
     32== Federated Wiki == 
     36== Document Or Data ? == 
     38... that is is the question.  The Infobox concept might be the answer, or at least a partial answer. 
     42 An infobox is a fixed-format table designed to be added to the top right-hand corner of articles to consistently present a summary of some unifying aspect that the articles share and sometimes to improve navigation to other interrelated articles. 
     44 Many infoboxes also emit structured metadata which is used by DBpedia and others. 
     46 The generalized infobox feature grew out of the original taxoboxes (taxonomy infoboxes) that editors developed to visually express the scientific classification of organism ... 
     48 For example: 
     52{{Infobox person 
     53|name    = 
     54|image   = 
     55|caption = 
     57|website = 
     62 might be filled out like this: 
     66{{Infobox person 
     67|name    = Casanova 
     68|image   = Casanova_self_portrait.jpg 
     69|caption = A self portrait of  Casanova 
     71|website = 
     76 In this example, the names of the parameters ("name", "image", "caption", "website") are fixed in the design of the infobox and described in its documentation. 
     78 A parameter that is misspelled, falsely capitalized, or is not supported by the infobox implementation does not display at all. To find out exactly which parameters are functional, look at the infobox's template page. Anything not listed there will be ignored, even if it works in some other infobox. If you believe that another parameter needs to be added to a given infobox template, then suggest that on the infobox's talk page. 
     80In other words, what I don't want !  It's '''not''' an input template - it's an input macro at edit tie and a dictionary passed to a rendering template at run time. 
     82Whatever attributes appear in an 'infobox' gets added to a database at edit time and then a fixed subset of the infobox ( not wiki text ) gets displayed at run time with a link to the infobox itself ( including wiki text and the rest of it ).  
     84It is a fairly pure data entity rather than a document or content.  It is always shared, generally documents are not.   
     86== Microformat == 
     88MetaTags: [[search:?q=%23Markup|#Markup]]  
     93 A microformat (sometimes abbreviated μF) is a web-based approach to semantic markup which seeks to re-use existing HTML/XHTML tags to convey metadata and other attributes in web pages and other contexts that support (X)HTML such as RSS. This approach allows software to process information intended for end-users (such as contact information, geographic coordinates, calendar events, and similar information) automatically. 
     95 Although the content of web pages is technically already capable of "automated processing", and has been since the inception of the web, such processing is difficult because the traditional markup tags used to display information on the web do not describe what the information means. 
     97 Microformats can bridge this gap by attaching semantics, and thereby obviate other, more complicated, methods of automated processing, such as natural language processing or screen scraping. The use, adoption and processing of microformats enables data items to be indexed, searched for, saved or cross-referenced, so that information can be reused or combined. 
     99 As of 2013, microformats allow the encoding and extraction of events, contact information, social relationships and so on. Established microformats such as hCard are published on the web more than alternatives like schema (microdata) and RDFa. 
     105See [[SemanticWeb#RDF]] 
     108== Also See ==