77 lines
2.6 KiB
Markdown
77 lines
2.6 KiB
Markdown
---
|
||
title: 'BlogTalk Reloaded 1.4'
|
||
date: '2006-10-02T04:30:01-04:00'
|
||
permalink: /blogtalk-reloaded-14/
|
||
tags:
|
||
- conferences
|
||
---
|
||
|
||
Panel 3: Alexandre Passant and Suw Charman
|
||
|
||
(tags: [blogtalkreloaded](http://technorati.com/tag/blogtalkreloaded))
|
||
|
||
alexandre passant (philippe laublet and jean-david sta)
|
||
|
||
“folksonomies, ontologies, and corporate blogging”
|
||
|
||
idea: use weblogs to store and exchange the rich but unstructured information that has previously been exchanged via email and coffee breaks
|
||
|
||
corporate blogging and folksonomies — post annotation
|
||
|
||
visualization — tag clougs and maps
|
||
|
||
problems with folksonomies:
|
||
|
||
— too many tags only get used once; not helpful in retrieval of posts
|
||
|
||
— tag redundancy and ambiguity
|
||
|
||
— flat organization (need related/suggested tags)
|
||
|
||
linguistic analysis of tag variations
|
||
|
||
— elision — reducing compound word to one word
|
||
|
||
— synonymy
|
||
|
||
— abbreviation
|
||
|
||
— morphological variation
|
||
|
||
— typographic variation
|
||
|
||
— errors in typing
|
||
|
||
set up system to help users choose tags
|
||
|
||
going further with the semantic web
|
||
|
||
— semantic web: unified description of resources; ontologies, representation of domain using common vocabulary
|
||
|
||
— wanted to mix folksonomies and ontologies — keep open spirit of folksonomies; use ontology layer as a formal way to represent data; remove data and add meaning to tags — link tags to ontologies
|
||
|
||
— users create and tag post; tag is linked to ontology; thus post is linked to ontology; later posts whose tags are connected to the same ontology are inferred to be related
|
||
|
||
— developed semantic search engine: search tags and concepts; display blog posts for searched concept; find related posts
|
||
|
||
suw charman
|
||
|
||
“social software in business – an adoption strategy”
|
||
|
||
consulting work — how to get social software actually adopted by users in organizations
|
||
|
||
two ways to encourage adoption: top-down (thou shalt use it!); bottom-up (grass roots adoption) — but neither by themselves is enough — must encourage experimentation from bottom up while also encouraging support from top down
|
||
|
||
steps in encouraging bottom-up adoption
|
||
|
||
— understand your users (who are they? what do they do? how does software really make their lives better?)
|
||
|
||
— how will you introduce them to the software? (can’t just hand them a manual; must lower barrier to entry, make it interesting)
|
||
|
||
— how will ongoing support work? (chat channel; email — can ask for help without asking for help)
|
||
|
||
— how can you get initial adopters to become evangelists? and get them to be further trainers?
|
||
|
||
also need to get management buy-in (top-down adoption)
|
||
|