Practical Semantic Mediawiki

From zooid Wiki
Jump to navigation Jump to search

This hands-on session for non technical users emphasizes the "need to know" aspects of Web publishing, wikis, information design and Semantic Mediawiki.

Acronyms

  • SMW = Semantic Mediawiki
  • MW = Mediawiki
  • CC = Creative Commons

Web publishing

Access models

  • Fully open, no login required
  • Require login for editing
  • Require created accounts to edit (closed editing)
  • Require created accounts to access (fully private)
    • Encryption to avoid snooping

Access models can be changed over time; avoid starting a wiki with jargon or unsympathetic content.

Site users

  • Levels
    • De-emphasize control, make it as flat as possible
    • Bureaucrats still exist
  • OpenID signin

Accessibility

Here, accessibility refers to supporting people with vision, keyboard control or cognitive difficulties.

  • Making sites accessible generally increases usability
    • Works on more devices from text browser to handheld
    • Typically more straightforward navigation
    • Accessible hot keys can be used by any expert user
    • The curb cuts principle
  • Mediawiki is accessible, SMW has issues (forms)
  • Value content over appearance
  • Good tags for images, image maps
Copyright continuum, from traditional copyright to public domain

Terms of use

  • Creative Commons - share with options for attribution, non-commercial, changes
  • Traditional copyright - by permission only


Using Mediawiki

MediaWiki logo without tagline.png

Mediawiki is the underlying software of Wikipedia. It is robust, supported by a large community and supports hundreds of useful extensions.

Progressive uses

  • Basic site with pages and categories
    • You just need to know a few things for your wiki to be as useful as most Web sites
  • Add widgets for more interactivity
  • Wiki gardening to reorganize content
  • Add semantic classes for reusable data
  • Guide users of the site

Creating pages

  • How to name pages
    • One topic per page
  • Short, avoid special symbols, sentence form
  • Code and matching brackets

Basic markup

A picture of clouds with the sun poking through in case people start to panic

Rather than using a rich text editor, Mediawiki uses a progressively learned set of markup, that's designed to be human-readable, consistent and enforces meaning over appearance. It's not dependant on special programs, and could be carved into a park bench and retain its meaning.

  • ''Italic'', '''Bold'''
  • * List heading level one — use # for numbered list
    • ** List level two — ## for numbered list
      • ...
  • =Heading one=
    • ==Heading two==
      • ...
  • [[Mypage]] — A wiki link
    • [[File:Mypicture.png]] — Media (inline or link)
    • [[Mypage|This is my page]] Alternate link text (using pipe symbol)
  • [http://theirsite.com] — A non-wiki link
    • Use a space after the link to use your own link text. [http://theirsite.com Their site].
  • {{My Template}} — A template (reusable content, function or variable)
    • Don't Repeat Yourself
    • Pipe symbol is used to pass parameters — {{Show Something|Something}}
  • {{ #geocode: Montréal, Quebec}} — Template function, in this case geocode turns a place name into geographic coordinates
  • {{{1}}} — SMW variable, in this case the first value passed to a template
  • Proactive linking
    • Brainstorm using links
  • Categories
    • Subcategories
  • Uploading images and files
  • Moving pages
  • Deleting pages
  • Templates - used for consistently reused content

Making pages look good

CSS is the style system of Web pages and can also be used in Mediawiki. Like wiki markup, learning can be progressive.

Placeography | Biofuel Visions

  • Re-using CSS styling <div style="background: orange">Hello world</div>
    • Avoid losing meaning (don't use <big> for headers), keep it simple
  • Re-using styles MediaWiki:Common.css
  • Hiding MW's menus and changing the 'skin'

Semantic Mediawiki

SMW logo 180px.png

SMW is an extension ecology of MW that allows marking up content for re-use and create easier to use forms and views.

  • Meaning through annotations and relationships
    • Triples
  • What properties does your content need to be useful?

Inline property annotation

Single instances of data can be marked-up using annotations.

[[Date::Jan 1, 2011]]

Classes

  • Creating a class (template, properties, forms)
    • One topic per page
    • Formlink {{#formlink:Comment|comment||Comment[Topic]={{PAGENAME}}}}</formlink>

Views

Basic inference

Future directions

  • Relating ontologies
  • Reusing content
  • Creating a big picture where anyone can ask questions and add their data


Mediawiki Widgets

Mediawiki Widgets allow embedding third-party site content for rich media (Youtube, photo sites, etc) and interactive discussions (DISQUS, Twitter, etc) without needing to set it up or host it on your site.

  • DISQUS discussion
    • Register with DISQUS
    • Get key
    • Create widget
    • Embed widget on pages

Converting content or sites

Hosting

  • Export a site, modularize by category
    • Complete site export
  • Special:Version
  • Free light/startup hosting
  • Inexpensive Mediawiki with SMW option
  • Wikia
  • Self-hosting

Getting help