Download presentation
Presentation is loading. Please wait.
Published byElinor Morgan Modified over 8 years ago
1
The Cross Lingual Wiki Engine Project Alain Désilets National Research Council of Canada alain.desilets@nrc-cnrc.gc.ca
2
We Live in Exciting Times
3
The Future of Content Creation? In near future, a significant portion of the content we consume might be created using this kind of massively collaborative paradigm. Not appropriate for “serious” commercial organisations producing “serious” proprietary content? Think again! This is exactly what the software industry used to say about Open Source Yet today, successful software companies have learned to thrive in a complex eco-system of Open Collaboration
4
What about Multilingual Content? Not everyone in the world is fluent in English. Consequently, many of the largest and most popular wiki sites provide multilingual content. Wikipedia Wikitravel But by and large, most are unilingual, eventhough some would benefit from multilingual content. Ex: Fluwikie Even Wikipedia and Wikitravel need more synergy between the different languages.
5
The Cross Lingual Wiki Engine project Design, implement and evaluate lightweight tools and processes for collaborative creation and maintenance of multilingual wiki content. In other words, we are trying to figure out what it means to: “Translate in the WikiWay” http://www.wiki-translation.com/tiki- index.php?page=Cross+Lingual+Wiki+Engine+Project
6
Content Happens In a Massive Online Collaboration world, content creation and translation is not mandated. It just “happens”. Traditional top-down, command-and-control translation paradigms are simply not appropriate.
7
Content Happens (2) English French Chinese Japanese German Farsi Korean = Page creation = Page modification English French Chinese Japanese German FarsiKorean Traditional environment Single Master language Massive Online Collaboration Multiple Pivot languages
8
Content Happens (3) In a massively collaborative environment, it is also hard to guarantee timely translation. Not appropriate to delay publication until translation is done. The system must be able to deal with partially translated content.
9
Visitor Reading from Foreign Language Help visitors deal better with out of date pages.
10
Translator Translating from a Foreign Language Help translators in translating from a language they don’t know.
11
Today’s Agenda Q: What do users actually need from a Cross Lingual Wiki Engine, and how do we provide end-to-end business value early on in the project? 10:30-12:00: Storyboarding, Typical Organizations, User Roles, User Tasks, Product Vision 13:00-13:30: Release Planning 13:30-14:30: Technical Architecture Planning 14:30-16:30: Coding
12
Designing a CLWE (2) 10:30-12:00: User-Centered Design Exercice (~ 90 mins) StoryBoarding: Participants tell stories where a particular user working in a particular organisation uses the system in a particular way to meet a particular goal (~30 mins) Based on these stories, we generate: –List of Typical Organizations that might use a Cross Lingual Wiki engine, each for specific goals (~15 mins). –List of Typical Users and their respective goals (~15 mins) –List of User Tasks, i.e. a list of typical things that the user needs to do WITH the system in order to meet his goals –Product Vision: A paragraph that describes the product. Who is it for? What does it allow them to do? What is its competitive advantage compared to similar products? (~15 mins)
13
Questions?
14
Contact Info Alain Désilets National Research Council of Canada alain.desilets@nrc-cnrc.gc.ca
Similar presentations
© 2025 SlidePlayer.com. Inc.
All rights reserved.