 Right Welcome everybody And thank you for being here and thank you for getting me in to me It's an honor to be in Houston at the EMW conference. I am Sabine Milnitski from Wiki Ahoy I'm from Vienna, Austria, and I'm together with the Lex Sultzer from Dataspext from Switzerland We are sort of the Germans speaking European delegation as we call it or country ambassadors We will be Working closely together Yes, I have a small Digital consultancy in Austria and working with semantic media Wiki for a couple of years now This was meant to be a beginners training a beginners tutorial That's how it was set up and planned, but We were saying it doesn't look like there will be so many people not having Been worked with semantic media Wiki whatsoever So we decided to find a little bit of a different approach May I ask you how many of you haven't ever used semantic media Wiki before I get one I get before this conference Yes Yes, you said you would be working with it for for for a while now Just media Wiki not semantic media Wiki. I see you because we've got one and two three. Okay The idea is that we we would like to introduce our our concept our idea our approach But if you're interested we might be splitting up later on and do that kind of just add up that beginners tutorial later on Yeah I'd like to be we're gonna start slow and easy and I'd like to keep this interactive So anytime you feel like you're having a question or a concern, please interrupt and and we love questions So this is a tutorial and not a talk. Yeah Okay I'd like to show you we start with three questions when working with knowledge management in a wiki using a wiki for knowledge transfer we ask ourselves three questions and What do our users want what do they need in in the company context, of course What enables knowledge transfer? And how can a wiki support that? I'm coming from the direction my background is a little bit different than Lex for example He's coming more from the technical side. I'm coming from the language content part so What's it called the more Traditional knowledge management, okay So Yeah The first question. What do you what do our users want? I believe our users are want an intuitive platform. They're used men reading a manual is very 1990s users are Used to apps that they understand in an instant, okay They don't want to Start with an empty page in their wiki. They want to have some certain structure some Guidelines they can follow they want to be guided through so What do we try to do is design a structure for the independent autonomous user We don't want the user to have to learn anything to use our system. It should be intuitive He should be able to guide himself through without our help. Yeah We Can help him doing this by providing a very logical and easy structure and easy and logical navigation Good well-working error messages, what else is there? Yeah, and in general good usability, okay, of course The user's time is scarce and his patience is ending You know that in the context context of the web Seconds are a long time to wait for pages to load and everything so Nowadays a user doesn't have the time to he doesn't land on our page on in the wiki or whether the website or the or in the wiki Lend there click himself through Browse a little bit. That's usually not what's happening anymore. He's searching He's hitting his question into a search bar and lands on our page and if he doesn't find the information He's looking for he's gonna be gone in a second. So What we design for now is we design our pages for the searches and not for the browsers Which is a very important approach because it makes the pages We need to design the pages in a different way We don't guide the person through our website on a long pathway step by step But you only have the chance to catch the user on this page. All he needs to know Should be on this one page, right and the last one Our users are clever intelligent and informed. Yeah, we're working with We take that positive approach towards our users our readers But they are dependent on our system. They land on our website and I can't change anything by themselves They're dependent on what we provide them. So We design for an easy structure easy usability But with qualified content with good high-level quality quality in our content Yeah, to sum that up We design a structure for autonomous users for searches instead of browsers and for Qualified readers any questions so far up to here Good, that's fine What is important in the context of knowledge Transfer, I'm sure you've heard that before but let's just quickly go through it To be able to to reuse and to work with knowledge It needs to be explicit and not tested. We talked about this yesterday It depends a little bit on how you define knowledge in my in my definition of knowledge knowledge is something in the people's minds It's as soon as you Communicate it as soon as you write it down. It's Information it's data, but I guess that's a matter of definition. Yeah Okay, so what you need to What you need to do to make knowledge explicit is to write it down to communicate it to put it in in any format written down Knowledge needs to be in a transferable format It needs to be able to put into other formats from one format to the other that means Yeah, of course, it's not a good way anymore to put it on paper You want it online you want to maybe in a structured way so you can reuse it You can reuse the data for other for other purposes and Last but not least, it's needs to be comprehensible. You need to write down the Knowledge not for yourself, but for others you write for others for your future self in a way That you and the others can understand you Definitely if as soon as he starts right he or she does writes it down. That's a good thing I Don't know our approach is from an administrator point of view to to make it as easy as possible for the user To actually produce comprehensible content It's a difficult if it's it's a difficult task, of course because you know every human is different But if we agree on something that we understand I understand this way. This is a way we Name things maybe then it makes it easier for every every one of us. So Knowledge is as I see it as it's in the heads of the humans. Yes, and it's inside ourselves But if we agree on something we talk about I guess it's easier to understand. This is yeah Okay How can the wiki help with that With that idea the wiki can motivate to write down. Okay, it can help us It can motivate to write down. What's what's why is it good to write it down? Maybe because I can use the data for something else. Maybe I can generate generate queries reports Graphs some information that I didn't know I know yeah I do something with my with my data with information. I have some extra added value out of Writing it down. Not just for myself, but also for others I Can keep the information for later. I can look it up. These are all added values Compared to just keeping it to myself It can motivate to only use the wiki as a single point of information as my first step for my questions for guidance yeah, and It can motivate me to write to be read So I don't really just know down things for myself Legs always keep saying from a future self. So it's like me and the other person but in the company for all also for my colleagues for my employees And we do this we provide Structure that supports this idea that motivation so and what I'd like to go on with is the idea of Apple or Jesse as I'd like to call it Apple is a Manifest a concept by Mark Baker. He wrote this book in 2013 It's one okay and It's not like he invented something new or he's basically just Describing what's already there? It's not a prescriptive idea or prescriptive manifest. It's very descriptive. It just looks at what's there and I'd like to call it Jesse. That's the German version either side is side the ends because we'd like to adapt his idea for our purposes Mark Baker looked at how web is Constructed how technical documentation is written on the web And documented that and we adapt that in our Jesse system for the week. Okay. I'd like to guide you through a few general concepts Yes Every page is page one he says Included all filtered afterwards. It's not We don't decide on what's valuable or not. This is something up to search We put everything in there and search is finding the information. I'd like to I have my search question I can filter this search question. I drill it down, whatever, but I have all the content and Choose what's valuable afterwards. This is why search has such an important function in in this concept and of course Google nowadays is at the centers at the heart of the web and it also should be at the heart of any wiki. Yeah Distributed nature of the distributed nature of the web. We don't have a hierarchical structure anymore. We don't use these What are they called these Anyway, the systems the core rated systems. We have a network of connected pages We have a semantic structure. This is just how it developed and bottom up architecture is Something that I Don't know mark Baker's proclaiming that bottom out bottom up architecture is the way we develop content. We write content Yeah, legs Sorry Hmm Just one quote for both bottom up organization bottom up organization appears messier than top-down organization Top-down organization, of course, we have the classic Navigation for browsing bottom up is this every page is page one system It is only because it is more accurate accurately Reflecting the messiness of the real world. Yeah, the real world isn't structured. It doesn't have an end to its pages and This is what happens in the week as well. So Famous examples for yes Yes, yes, you could say so and the idea is with the bottom up architecture You also have bottom up navigation Top-down navigation is hierarchical as is the menu the classical one Bottom up is a lot of like you have local navigation compared to global navigation You have a lot of hyperlinks interlinking on this level. Yeah, it was the other way Good point. Did you say you you start with the content and maybe Structure it collect it put it together Courage it afterwards and don't provide an empty structure and fill it up with content I'm sure you all know the most famous example is Wikipedia and this is why this this idea so well fits with the wiki Because every wiki, you know wiki pd is the most famous wiki as we know stack overflow is the technical Does anybody not know stack overflow and never been yes, okay, and wordpress codex, which I believe Also runs on a media wiki if I'm right. Yes. Yeah Yes, what press codex is very good example for technical Documentation on on this basis the quality is very different because you have different writers of Certain topics. Okay, let's move on For basic concepts for basic parts of this idea are the topic the topic type The context which is the most important part for me and the content What is a topic? A topic in in Apple in the jesse system is Self-contained it stands alone. It functions alone. It works alone. It doesn't Need any other page To be understood Yes, how does this how does this work again with the bottom up idea that we have a local Navigation we have rich hyperlinks We have all the information we need on this page. We set up the context Yes for the context you mean or We are talking about in a wiki, of course We're talking a topic will be one single page Okay, but we need to distinguish what's a topic and what's not a topic what makes up What makes a topic what's too much for a topic what's not enough is that what you what you're trying? What do you want to say? Yes, absolutely. Yes, very well done No, well very very good the topic assumes reader Qualification this is very important We go on and say that our user knows everything he needs to know to be able to follow this page Except what we are telling him on the page so everything that he needs to know to understand what's there He knows Only accept this information only accept the recipe of spaghetti carbonara and in case He doesn't know any of these bits and pieces and parts. We link him to the content We don't include it, but we link so he can follow his way through in case he doesn't know any of these parts Okay Okay Yes, I'd call it I'd call it a little bit differently. Let me let me go back to this It's this is the main part for me the most interesting bit is to establish context So if you if we are on the spaghetti carbonara page I start by I Set up You say what it's part of you say what parts you have you establish the context of that page So we're talking about spaghetti spaghetti is Nutritious meal We have a recipe here It comes spaghetti are a part of a type of pasta pasta is Comes from Italy all these sort of sort of ideas. What is it not? What what does it include? What parts do we have what am I part of so I get an idea? That's that's where I am. This is like this is the frame of what I'm on this page And if I'm looking for something else, oh, I wasn't looking for spaghetti The the food I was looking for spaghetti the software. I need to go somewhere else like this, okay Let me see what I what I skipped Yeah, the topic has a limited purpose it's its purpose can be to get an give information to bring an overview to Show task to show instructions So this single page only always has one purpose if I want To give an overview over the history of spaghetti. This would be a topic and the recipe of cooking spaghetti carbonara would be another topic just because it's a very different purpose In the in the context of the context I really like this quote. It says a well-designed information set is like a well-designed Transportation system. It allows the passengers to travel individual itineraries along shared routes So I set up the routes the possible ways He can travel and because I can't cover every Readers needs I make it possible for them to to click themselves through the information, okay? Difficult part of the topic is it conforms to a type. We had a lot of discussion of what makes up a type and and What doesn't a type is very closely related to a purpose the purpose of the page defines the type And in the context of semantic media wiki one type one topic type would Translate into one form and template structure Yeah, okay and The last part Yes Having defined our purpose and our topic type we stay on one abstraction level I'm not talking about pasta in general and I'm not talking about Whipping cream for the last bit after the recipe. I'm talking about spaghetti carbonara. So It's it's not up to me to to give everything possible Every to serve every abstraction level is again up to the user to decide I want to go one deeper one level up through Rich linking I make that possible through through the links Yes establishes context So it's really a qualification And links richly of course we are we're in the web hyperlinks are the heart at the heart of the web. We need links To guide the user to to give him all these possibilities. So Again to sum it up topics are self-contained. They stand alone They have a limited purpose conformed to type and stay on one level. That sort of just goes together They establish a context at what they're in and they assume a qualified reader. So how does this? Possibly look Is in German, but it doesn't matter and you can see an idea of What this could transform into a form into a structure that the Writer is actually writing his topic. You have the topic on the on the top. You have the purpose And the content the topic type You have the context and and the content and I go a little bit more into detail with the topic We're talking paid pitch title. We're talking URL we're talking wiki words, for example, that's FOSS wiki is working with wiki words. That's their linking system That's all the same thing. I need to Decide on these Purpose Again is The Transforms into the topic type into this the special local navigation into a repeating structure into my fields in the form, etc The context or as we'd like to call it the blurb Is this little first paragraph at the beginning of every page? If you look in in certain wikis wikipedia is very good with that. They have very good Context setup if you have a page about Argentina you find okay, Argentina is a country as a republic country in South America It has is neighbor by by these countries so many inhabitants, etc. They set up the context Context can be a definition of terms. What are we talking about? What synonyms are we talking about synonyms antonyms word origins? What subordinates and the umbrella terms? might apply What scope the magical scope and a time scope are we talking about and We can describe the development. How did this term? Where did this term come from? Also what future plans can we expect? What require weak? requirements to any to Have to be able to to work with this topic to understand the subject. Yes And again a very important part in this context is to link richly in this paragraph you find a lot of links to see to To make it possible for the user to Go to other pages Last one is the content. This is the free text We're writing about the topic itself. That's That's basically it yes The keywords It's doubling queries more is working with ontologies right it's an ontology Yes, yes, I'm not too much into it, but I know yes, well I made a data a lot of like this. Yeah Mm-hmm It's it's a little bit of a different approach again It's more like the technical side of it the way I see it for Jesse is really More from the content side if I have a lot of text a lot of Running text free text. How can I still structure that and how can I still guide my my users through? Yeah Lex then I well, thank you for up to now up to here