DOCSLIB.ORG

Wikigateway: a Library for Interoperability and Accelerated Wiki Development

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Wikigateway: a Library for Interoperability and Accelerated Wiki Development WikiGateway: a library for interoperability and accelerated wiki development Bayle Shanks http://communitywiki.org/BayleShanks Computational Neurobiology University of California San Diego, La Jolla, CA 92093 bshanks at ucsd.edu ABSTRACT Related resources WikiGateway is an open-source suite of tools for automated Related resources may be found at http://purl.net/bshanks/ interaction with wikis: work/papers/wikigateway_wikisym05/. These may include talk slides, amended or hypertext versions of this paper, and pointers to related work. It is suggested that the reader • Python and Perl modules with functions like getPage, check there for updates before reading this paper. putPage, getRecentChanges, and more. • A mechanism to add DAV, Atom, or XMLRPC capa- bilities to any supported wiki server. 1. INTRODUCTION • A command-line tool with functionality similar to the WikiGateway is a suite of tools that allows developers to Perl and Python modules. write programs that act as clients to wiki servers. Wiki- Gateway provides a unified interface to different types of • Demo applications built on top of these tools include a wiki engines. “Wiki engine” refers to a type of wiki server wiki copy command, a spam-cleaning bot, and a tool to software; for example, MoinMoin is a wiki engine. recursively upload text files inside a directory structure as wiki pages. There are a few different ways of communicating with wiki servers using WikiGateway tools. These options can be grouped in two categories; either the client software uses All WikiGateway tools are compatible with a number of WikiGateway components installed on the local machine, or different wiki engines. Developers can use WikiGateway to it communicates with a WikiGateway web service installed hide the differences between wiki engines and build applica- elsewhere. tions which interoperate with many different wiki engines. The simplest way to interact with wikis is for software run- Categories and Subject Descriptors ning on the client machine to call a WikiGateway library D.2 [Software engineering]: Interoperability function or tool. WikiGateway provides modules for Python ; H.5.3 [Information Interfaces and Presentation]: Group and Perl, and also a command-line client. Appendix A gives and Organization Interfaces; H.4 [Information systems a demonstration of various WikiGateway Python module applications]: Communications Applications functions. Appendix B shows example invocations of the WikiGateway command-line client. General Terms Standardization, Design However, WikiGateway also allows people to run web servers that act as gateways; these intermediaries accept requests Keywords from the client using a standardized protocol, and translate them into requests to the actual wiki server (which may be wiki, interwiki, interoperability, WikiGateway, client-side running on yet another machine). WikiGateway provides wiki, WikiClient, middleware, Atom, WebDAV, WikiRPCIn- tools to run servers that understand the WebDAV, Atom, terface, wiki XMLRPC or WikiRPCInterface protocols [37, 11, 21, 2, 13, 23]. Wiki- Gateway also provides a server that exposes an XML-RPC interface to the Python WikiGateway module. Permission to make digital or hard copies of all or part of this work for personal or classroom use is granted without fee provided that copies are WikiGateway includes a few “demo applications” to show not made or distributed for profit or commercial advantage and that copies how it can be used. These include a despamming bot, a bear this notice and the full citation on the first page. To copy otherwise, or script to copy an entire wiki onto another wiki, and a script republish, to post on servers or to redistribute to lists, requires prior specific to upload a hierarchial directory structure of text files to permission and/or a fee. WikiSym ’05, October 16-18, San Diego, CA, U.S.A. a wiki (treating each text file as wiki markup source for a Copyright 2005 ACM 1-59593-111-2/05/0010 ...$5.00 single wiki page). This paper will begin by describing the reasons for building 1. The existence of software that can read and write to a WikiGateway, including why WikiGateway will help wiki variety of different types of wiki engines. technology to develop faster, and what kinds of software WikiGateway will allow others to build. Next, potential 2. The existence of software that knows how to convert disadvantages of building something like WikiGateway are the wiki markup between a variety of different types explored. The design and implementation of WikiGateway of wiki engine markup styles. are described, followed by a description of demo applications which were written as examples of WikiGateway usage. Fi- nally, future plans for WikiGateway are discussed, including WikiGateway currently can do (1), and the plan is for it also a list of additional demo applications to be developed. to do (2) in the future (see Section 6, “Future Work”). 2. MOTIVATIONS 2.4 Client-side tool development There are quite a few reasons that a project like Wiki- Gateway is needed. First, developers are already writing Problem: fragmentation of developer effort “screen-scraping”-style code to interact with wiki servers; it There are over 250 different wiki engines1. There are even would be more efficient for the community to write this code quite a few different “popular” wiki engines23. Even though “once and only once” in a single library. Second, there are there are many wiki software developers, their combined de- standardized protocols that wiki servers could support, but velopment effort is split into hundreds of small projects (see often don’t; WikiGateway provides gateway servers to al- Figure 1)[8]. low clients which speak standard protocols to communicate with wiki servers. Third, making wikis more interoperable One way to solve this problem would be to convince devel- will aid communications not only with other types of tools, opers to pool their efforts and focus development on a small but also between different wiki sites. For example, giving number of wiki engines. This is difficult because it would programs the ability to automatically talk to wiki servers involve a lot of individual developers and small teams giving is a prerequisite for automated wiki page interchange. Fi- up creative control and joining large organizations. nally, by allowing new ideas to be implemented as “uni- versal” client-side tools rather than as server-side features, Another answer is to allow developers who are working on a WikiGateway will help with the problem of the division of new feature to write a single implementation of that feature developer effort among different wiki engines. These moti- which will be compatible with multiple wiki engines. For vations are elaborated upon below. many features, this could be done by implementing features client-side rather than server-side. 2.1 A central collection of screen-scraping code Developers are already spending time implementing inter- Solution: implement new features client-side faces to wiki engines [22, 35, 20, 31, 19, 33, 32]. As long With the ability to download and upload the page source as developers are spending their time writing what is essen- from remote wiki servers, it is now possible to implement tially “screen scraping” code to talk to specific wiki engines, wiki user interfaces (UIs) partially or completely on the why not collect all of these efforts into a single library? client. Advanced features such as a revert button, Sub- scribedPages, “filtered Recent changes”, a collaborative rat- In addition to making it easy for developers to know where ing system for wiki pages, or “unified recent changes”4, could to go to find wiki interface code, WikiGateway has the added all be written without altering the software running at the advantage of providing clients with a single, unified API to server. use, regardless of which specific type of software the wiki server is running. There are also some features that seem to “naturally” be- long in the client. Examples include a browsing interface In the future, perhaps developers who want to write screen- based on an animated, clickable, graphical/spatial “map” of scraping code for a particular wiki engine will spend their nearby wiki pages; or a Refactoring Browser, that is, a pro- time writing a driver for WikiGateway. gram specifically designed for refactoring text in wiki pages, with special tools for moving blocks of text around between 2.2 Interoperability with standard protocols and within pages [28]. Many useful software clients use protocols such as WebDAV 1 or Atom. However, there are few wiki engines which support 252 was the result of a very superficial count of the number these protocols. WikiGateway provides a way for a DAV or of entries on http://c2.com/cgi/wiki?WikiEngines, on April 21, 2005, in the “sorted by language of implementation” Atom client to access a wiki server, even if the wiki engine section. running on the server does not know anything about DAV 2This is hard to quantify, but [38] lists 9 wiki engines with or Atom. over 100,000 Google hits; [41] lists 5 popular wiki engines; [15] lists 5 popular wiki engines; but these two 5-engine lists have only 2 engines in common. 2.3 Wiki page interchange 3 One much-discussed feature of the future is the ability to I don’t mean to claim that these lists are authoritative or exhaustive, but they do show that it is not the case that programmatically move or copy a page from one wiki to aggregate developer effort is being concentrated on two or another one, even if the source and destination wiki use three wiki engines different wiki software [17, 39, 27, 1, 16, 29, 7, 36]. This 4 “Unified recent changes” is a single list of the Re- would require two things: centChanges of multiple wikis. Client-side wiki software has not yet been widely developed wiki administrator because, before WikiGateway, it was difficult for client-side must programs to communicate with the wiki server.
Load more

Recommended publications
  • Which Wiki for Which Uses
    Which wiki for which uses There are over 120 Wiki software available to set up a wiki plateform. Those listed below are the 13 more popular (by alphabetic order) wiki engines as listed on http://wikimatrix.org on the 16th of March 2012. The software license decides on what conditions a certain software may be used. Among other things, the software license decide conditions to run, study the code, modify the code and redistribute copies or modified copies of the software. Wiki software are available either hosted on a wiki farm or downloadable to be installed locally. Wiki software Reference Languages Wikifarm Technology Licence Main audience Additional notes name organization available available very frequently met in corporate environment. Arguably the most widely deployed wiki software in the entreprise market. A zero- Confluence Atlassian Java proprietary 11 confluence entreprise cost license program is available for non-profit organizations and open source projects aimed at small companies’ documentation needs. It works on plain DokuWiki several companies Php GPL2 50 small companies text files and thus needs no database. DrupalWiki Kontextwork.de Php GPL2+ 12 entreprise DrupalWiki is intended for enterprise use Entreprise wiki. Foswiki is a wiki + structured data + Foswiki community Perl GPL2 22 entreprise programmable pages education, public Wikimedia Php with backend MediaWiki is probably the best known wiki software as it is the MediaWiki GPLv2+ >300 wikia and many hostingservice, companies private Foundation and others database one used by Wikipedia. May support very large communities knowledge-based site MindTouchTCS MindTouch Inc. Php proprietary 26 SamePage partly opensource and partly proprietary extensions Jürgen Hermann & Python with flat tech savy MoinMoin GPL2 10+ ourproject.org Rather intended for small to middle size workgroup.
    [Show full text]
  • Biodynamo: a New Platform for Large-Scale Biological Simulation
    Lukas Johannes Breitwieser, BSc BioDynaMo: A New Platform for Large-Scale Biological Simulation MASTER’S THESIS to achieve the university degree of Diplom-Ingenieur Master’s degree programme Software Engineering and Management submitted to Graz University of Technology Supervisor Ass.Prof. Dipl.-Ing. Dr.techn. Christian Steger Institute for Technical Informatics Advisor Ass.Prof. Dipl.-Ing. Dr.techn. Christian Steger Dr. Fons Rademakers (CERN) November 23, 2016 AFFIDAVIT I declare that I have authored this thesis independently, that I have not used other than the declared sources/resources, and that I have explicitly indicated all ma- terial which has been quoted either literally or by content from the sources used. The text document uploaded to TUGRAZonline is identical to the present master‘s thesis. Date Signature This thesis is dedicated to my parents Monika and Fritz Breitwieser Without their endless love, support and encouragement I would not be where I am today. iii Acknowledgment This thesis would not have been possible without the support of a number of people. I want to thank my supervisor Christian Steger for his guidance, support, and input throughout the creation of this document. Furthermore, I would like to express my deep gratitude towards the entire CERN openlab team, Alberto Di Meglio, Marco Manca and Fons Rademakers for giving me the opportunity to work on this intriguing project. Furthermore, I would like to thank them for vivid discussions, their valuable feedback, scientific freedom and possibility to grow. My gratitude is extended to Roman Bauer from Newcastle University (UK) for his helpful insights about computational biology detailed explanations and valuable feedback.
    [Show full text]
  • Pipenightdreams Osgcal-Doc Mumudvb Mpg123-Alsa Tbb
    pipenightdreams osgcal-doc mumudvb mpg123-alsa tbb-examples libgammu4-dbg gcc-4.1-doc snort-rules-default davical cutmp3 libevolution5.0-cil aspell-am python-gobject-doc openoffice.org-l10n-mn libc6-xen xserver-xorg trophy-data t38modem pioneers-console libnb-platform10-java libgtkglext1-ruby libboost-wave1.39-dev drgenius bfbtester libchromexvmcpro1 isdnutils-xtools ubuntuone-client openoffice.org2-math openoffice.org-l10n-lt lsb-cxx-ia32 kdeartwork-emoticons-kde4 wmpuzzle trafshow python-plplot lx-gdb link-monitor-applet libscm-dev liblog-agent-logger-perl libccrtp-doc libclass-throwable-perl kde-i18n-csb jack-jconv hamradio-menus coinor-libvol-doc msx-emulator bitbake nabi language-pack-gnome-zh libpaperg popularity-contest xracer-tools xfont-nexus opendrim-lmp-baseserver libvorbisfile-ruby liblinebreak-doc libgfcui-2.0-0c2a-dbg libblacs-mpi-dev dict-freedict-spa-eng blender-ogrexml aspell-da x11-apps openoffice.org-l10n-lv openoffice.org-l10n-nl pnmtopng libodbcinstq1 libhsqldb-java-doc libmono-addins-gui0.2-cil sg3-utils linux-backports-modules-alsa-2.6.31-19-generic yorick-yeti-gsl python-pymssql plasma-widget-cpuload mcpp gpsim-lcd cl-csv libhtml-clean-perl asterisk-dbg apt-dater-dbg libgnome-mag1-dev language-pack-gnome-yo python-crypto svn-autoreleasedeb sugar-terminal-activity mii-diag maria-doc libplexus-component-api-java-doc libhugs-hgl-bundled libchipcard-libgwenhywfar47-plugins libghc6-random-dev freefem3d ezmlm cakephp-scripts aspell-ar ara-byte not+sparc openoffice.org-l10n-nn linux-backports-modules-karmic-generic-pae
    [Show full text]
  • Index Images Download 2006 News Crack Serial Warez Full 12 Contact
    index images download 2006 news crack serial warez full 12 contact about search spacer privacy 11 logo blog new 10 cgi-bin faq rss home img default 2005 products sitemap archives 1 09 links 01 08 06 2 07 login articles support 05 keygen article 04 03 help events archive 02 register en forum software downloads 3 security 13 category 4 content 14 main 15 press media templates services icons resources info profile 16 2004 18 docs contactus files features html 20 21 5 22 page 6 misc 19 partners 24 terms 2007 23 17 i 27 top 26 9 legal 30 banners xml 29 28 7 tools projects 25 0 user feed themes linux forums jobs business 8 video email books banner reviews view graphics research feedback pdf print ads modules 2003 company blank pub games copyright common site comments people aboutus product sports logos buttons english story image uploads 31 subscribe blogs atom gallery newsletter stats careers music pages publications technology calendar stories photos papers community data history arrow submit www s web library wiki header education go internet b in advertise spam a nav mail users Images members topics disclaimer store clear feeds c awards 2002 Default general pics dir signup solutions map News public doc de weblog index2 shop contacts fr homepage travel button pixel list viewtopic documents overview tips adclick contact_us movies wp-content catalog us p staff hardware wireless global screenshots apps online version directory mobile other advertising tech welcome admin t policy faqs link 2001 training releases space member static join health
    [Show full text]
  • Open Technology Development (OTD): Lessons Learned & Best Practices for Military Software
    2011 OTD Lessons Learned Open Technology Development (OTD): Lessons Learned & Best Practices for Military Software 2011-05-16 Sponsored by the Assistant Secretary of Defense (Networks & Information Integration) (NII) / DoD Chief Information Officer (CIO) and the Under Secretary of Defense for Acquisition, Technology, and Logistics (AT&L) This document is released under the Creative Commons Attribution ShareAlike 3.0 (CC- BY-SA) License. You are free to share (to copy, distribute and transmit the work) and to remix (to adapt the work), under the condition of attribution (you must attribute the work in the manner specified by the author or licensor (but not in any way that suggests that they endorse you or your use of the work)). For more information, see http://creativecommons.org/licenses/by/3.0/ . The U.S. government has unlimited rights to this document per DFARS 252.227-7013. Portions of this document were originally published in the Software Tech News, Vol.14, No.1, January 2011. See https://softwaretechnews.thedacs.com/ for more information. Version - 1.0 2 2011 OTD Lessons Learned Table of Contents Chapter 1. Introduction........................................................................................................................... 1 1.1 Software is a Renewable Military Resource ................................................................................ 1 1.2 What is Open Technology Development (OTD) ......................................................................... 3 1.3 Off-the-shelf (OTS) Software Development
    [Show full text]
  • Dtwiki: a Disconnection and Intermittency Tolerant Wiki
    DTWiki: A Disconnection and Intermittency Tolerant Wiki Bowei Du Eric A. Brewer Computer Science Division Computer Science Division 445 Soda Hall 623 Soda Hall University of California, Berkeley University of California, Berkeley Berkeley, CA 94720-1776 Berkeley, CA 94720-1776 [email protected] [email protected] ABSTRACT which the users can participate in writing Wikipedia articles. The Wikis have proven to be a valuable tool for collaboration and con- popularity of “wikis” [4] as website content management software tent generation on the web. Simple semantics and ease-of-use make also speaks to the usefulness of the medium. Generally speaking, wiki systems well suited for meeting many emerging region needs wikis have proven to be an excellent tool for collaboration and con- in the areas of education, collaboration and local content genera- tent generation. tion. Despite their usefulness, current wiki software does not work Several aspects of wikis are interesting for the emerging regions well in the network environments found in emerging regions. For context. First, there is a great need in emerging regions for content example, it is common to have long-lasting network partitions due that is locally relevant. Local content can take a variety of forms, to cost, power and poor connectivity. Network partitions make a from a local translation of existing online material to the commu- traditional centralized wiki architecture unusable due to the un- nity knowledge bases. Most of the content on the web today is availability of the central server. Existing solutions towards ad- written in English and targeted towards in the industrialized world.
    [Show full text]
  • Stardas Pakalnis) • the Contextit Project
    Streamspin: Mobile Services for The Masses Christian S. Jensen www.cs.aau.dk/~csj Overview • Web 2.0 • The mobile Internet • The Streamspin system • Tracking of moving objects AAU, September 10, 2007 2 Web 2.0 • Web 2.0 captures the sense that there is something qualitatively different about today's web. • Leveraging the collective intelligence of communities • New ways of interacting • Sharing of user-generated content • Text Wiki’s, e.g., Wikipedia Blogs • Photos E.g., Flickr, Plazes, 23 • Video E.g., YouTube AAU, September 10, 2007 3 Web 2.0 • Community concepts abound… • Feedback and rating schemes E.g., ratings of sellers and buyers at auctions, ratings of content • Social tagging, tag clouds, folksonomies • Wiki’s Collaborative authoring • RSS feeds • Active web sites, Ajax • Fueled by Google-like business models Google 2006 revenue: USD 10.6 billion; net income: USD 3.1 billion; 12k employees Microsoft now has 8k people in Online Services AAU, September 10, 2007 4 Flickr • From the Flickr entry on Wikipedia • “In addition to being a popular Web site for users to share personal photographs, the service is widely used by bloggers as a photo repository. Its popularity has been fueled by its innovative online community tools that allow photos to be tagged and browsed by folksonomic means.” • Launched in February 2004. Acquired by Yahoo! in March 2005. Updated from beta to gamma in May 2006. • “On December 29th, 2006 the upload limits on free accounts were increased to 100Mb a month (from 20Mb)” AAU, September 10, 2007 5 YouTube • From the YouTube entry on Wikipedia • “The domain name "YouTube.com" was activated on February 15, 2005…” • “According to a July 16, 2006 survey, 100 million clips are viewed daily on YouTube, with an additional 65,000 new videos uploaded per 24 hours.” • “Currently staffed by 67 employees, the company was named TIME magazine's "Invention of the Year" for 2006.
    [Show full text]
  • Which Postgres Is Right for Me?
    Which Postgres is Right for Me? PostgreSQL, Postgres Plus Standard Server, or Postgres Plus Advanced Server An EnterpriseDB White Paper for DBAs, Application Developers, and Enterprise Architects February 2010 http://www.enterprisedb.com Which Postgres is Right for Me? 2 Table of Contents Introduction ...............................................................................................................3 What is PostgreSQL? ...............................................................................................3 Who is EnterpriseDB? ..............................................................................................4 EnterpriseDB Services and Support ............................................................................... 4 EnterpriseDB Products.................................................................................................... 4 PostgreSQL ...............................................................................................................5 Overview ......................................................................................................................... 5 Feature List ..................................................................................................................... 6 Working with Open Source Software .............................................................................. 7 Postgres Plus Standard Server ...............................................................................8 Overview ........................................................................................................................
    [Show full text]
  • Feasibility Study of a Wiki Collaboration Platform for Systematic Reviews
    Methods Research Report Feasibility Study of a Wiki Collaboration Platform for Systematic Reviews Methods Research Report Feasibility Study of a Wiki Collaboration Platform for Systematic Reviews Prepared for: Agency for Healthcare Research and Quality U.S. Department of Health and Human Services 540 Gaither Road Rockville, MD 20850 www.ahrq.gov Contract No. 290-02-0019 Prepared by: ECRI Institute Evidence-based Practice Center Plymouth Meeting, PA Investigator: Eileen G. Erinoff, M.S.L.I.S. AHRQ Publication No. 11-EHC040-EF September 2011 This report is based on research conducted by the ECRI Institute Evidence-based Practice Center in 2008 under contract to the Agency for Healthcare Research and Quality (AHRQ), Rockville, MD (Contract No. 290-02-0019 -I). The findings and conclusions in this document are those of the author(s), who are responsible for its content, and do not necessarily represent the views of AHRQ. No statement in this report should be construed as an official position of AHRQ or of the U.S. Department of Health and Human Services. The information in this report is intended to help clinicians, employers, policymakers, and others make informed decisions about the provision of health care services. This report is intended as a reference and not as a substitute for clinical judgment. This report may be used, in whole or in part, as the basis for the development of clinical practice guidelines and other quality enhancement tools, or as a basis for reimbursement and coverage policies. AHRQ or U.S. Department of Health and Human Services endorsement of such derivative products or actions may not be stated or implied.
    [Show full text]
  • Software Knowledge Management Using Wikis: a Needs and Features Analysis
    FACULDADE DE ENGENHARIA DA UNIVERSIDADE DO PORTO Software Knowledge Management using Wikis: a needs and features analysis Rafael Araújo Pires FINAL VERSION Report of Dissertation Master in Informatics and Computing Engineering Supervisor: Ademar Manuel Teixeira de Aguiar (PhD) Co-Supervisor: João Carlos Pascoal de Faria (PhD) March 2010 Software Knowledge Management using Wikis: a needs and features analysis Rafael Araújo Pires Report of Dissertation Master in Informatics and Computing Engineering Approved in oral examination by the committee: Chair: Maria Cristina Ribeiro (PhD) ____________________________________________________ External Examiner: Isabel Ramos (PhD) Internal Examiner: Ademar Manuel Teixeira de Aguiar (PhD) March 25, 2010 Abstract Knowledge Management is a sub-section of management that pursuits improvement in business performance. It increases the organization's ability to learn, to innovate, to solve problems and aims to enhance organizational knowledge processing. It is looking for the available and required knowledge assets that are divided as tangible and intangible. Tangible assets, which are related to explicit knowledge, include manuals, customer information, news, employees, patent licenses, proposals, project artifacts, etc. Intangible assets, which are related to tacit knowledge, include skills, experiences and knowledge of employees within the organization. It is a method that simplifies the process of sharing, distributing, creating, capturing, and understanding a company’s knowledge. The challenges involved
    [Show full text]
  • Table of Contents Interwikis
    Table of Contents InterWikis............................................................................................................................................................1 Inter-Wiki Link Rules (or Links to other Sites)......................................................................................1 How to define Inter-Site links..........................................................................................................1 General Inter-Site Links...................................................................................................................1 Inter-Wiki Links...............................................................................................................................1 i InterWikis Inter-Wiki Link Rules (or Links to other Sites) This topic lists all aliases needed to map Inter-Site links to external wikis/sites. Whenever you write ExternalSite:Page it will be linked automatically to the page on the external site. The link points to the URL corresponding to the ExternalSite alias below, concatenated to the Page you choose. Example: Type Wiki:RecentChanges to get Wiki:RecentChanges, the RecentChanges page at the original Wiki site. How to define Inter-Site links • Inter-Site links are defined in the tables below. • Each entry must be of format: | External site alias | URL | Tooltip help text |. • The Alias must start with an upper case letter and may contain alphanumeric letters. • The URL and Tooltip Text may contain optional $page formatting tokens; the token gets expanded
    [Show full text]
  • Wiki Content Templating
    Wiki Content Templating Angelo Di Iorio Fabio Vitali Stefano Zacchiroli Computer Science Computer Science Computer Science Department Department Department University of Bologna University of Bologna University of Bologna Mura Anteo Zamboni, 7 Mura Anteo Zamboni, 7 Mura Anteo Zamboni, 7 40127 Bologna, ITALY 40127 Bologna, ITALY 40127 Bologna, ITALY [email protected] [email protected] [email protected] ABSTRACT semantic wikis (e.g. [11, 16, 17]) exploit the content medi- Wiki content templating enables reuse of content structures ation performed by the wiki engine to deliver semantically among wiki pages. In this paper we present a thorough rich web pages and give to authors simple interfaces (some- study of this widespread feature, showing how its two state times even invisible interfaces based on syntactic quirks!) to of the art models (functional and creational templating) are semantically annotate their content or to import semantic sub-optimal. We then propose a third, better, model called metadata. lightly constrained (LC) templating and show its implemen- Though (lowercase) semantic web and semantic wikis fill tation in the Moin wiki engine. We also show how LC tem- a technological gap inhibiting authors to provide metadata, plating implementations are the appropriate technologies to the question of how to actually foster the creation of seman- push forward semantically rich web pages on the lines of tically rich web pages is still open. By analogy, we observe (lowercase) semantic web and microformats. that a similar goal has been traditionally pursued by wiki content templating mechanisms1 which have been available since the first wiki clones under the name of seeding pages.
    [Show full text]