|
|
| Line 1: |
Line 1: |
| I attended http://semantic-mediawiki.org/wiki/Spring_2010_SMWCon at the MIT CSAIL Lab in sunny Boston and microblogged (on Twitter) comments on most sessions; my talk is at [[Encouraging Semantic Mediawiki use with non technical people]].
| |
|
| |
|
| == State of the software - Yaron Koren ==
| | Now that carrier frequencies are more standardized, like the "desktop" Internet it'd be better if we bought handsets from a free market, which would lead to more competition, better prices, and no contortions around "contracts." |
|
| |
|
| * First challenge for smw: visibility
| | Carriers like Rogers embed a 'subsidy fee' for handsets (phones) which is a substantial part of every bill (about 20% of a smartphone bill), if you want to get your own handset you're paying nearly double. In the future a smartphone will be many people's only computer, so choice, competition, and free will from the carrier's decisions are all very important, yet today buying a handset is very different from buying a computer. |
| * Second challenge for smw: communication ... duplicate effort
| |
| * "no brick walls separating users from developers," everyone welcome to contribute
| |
| * Third challenge, less important, funding ... too much money can hurt a project
| |
| * "Semantic" is an abused word, use alternatives.. platform.. but semantic will be the breakthrough?
| |
|
| |
|
| == Welcome address - David Karger ==
| | Do you think it'd be worthwhile to try to create a movement around subsidy-free pricing? |
|
| |
|
| * @karger - many tools are wrong, developers 'guessing' - smw lets users emerge their data/structure, see more tools like smw
| | Feel free to add your name and comments by clicking edit. |
| * Philip of @Ontoprise plan fine access controls; rich editor w annotations, queries; social/dashboard; wikibooks; facet browse, rules
| |
|
| |
|
| == Halo: Current status and future developments in 2010 - Philipp Zaltenbach ==
| |
|
| |
|
| * @Ontoprise dev'ing linked open data #LOD between sites — integrate DBPedia (WP), etc; q about dependencies on their proprietary sw
| | [[Category:Advocacy]] |
| * side skype chat discussing problems with rich text editors that mangle output, same problem for many systems
| | [[Category:Android]] |
| | |
| == Mashup of LexWiki and WebProtege for collaborative ontology authoring - Guoqian Jiang ==
| |
| | |
| * Guoqian Jiang @MayoClinic Lexwiki collab ontology dev ('propose' tab), curate, integrity; SMW to scale/distrib experts, hierch probs
| |
| | |
| | |
| ==The Unbearable Lightness of Wiking - A Study of SMW Usability - Jie Bao ==
| |
| * Jie Bao SMW usability (map.rpi.edu, data.gov) UI trumps low level abilities; forms limited; page model restrictive; devs prefer dev
| |
| * RDF model 'deeply right' for flexbl DB. Fixes: small cadre dev semantics, most use; inline triples; support mult POV; SMW != RDF
| |
| | |
| == Applying SMW on the Wikia environment - Timothy Quievryn ==
| |
| * Timothy Quievryn SMW impact on @wikia (mostly entertainment); Forms great advance, biggest wikis use it; soon all, dynamic games?
| |
| | |
| == WikiTags: Connecting SMW with MS Office users - Jesse Wang ==
| |
| * Jesse Wang connects SMW to MS Office for user workflow, usability: uses MS SMartTags. Browse values, easy Outlook export nonfree
| |
| | |
| == Flexible, purposive SMW use - Clarence Dillon ==
| |
| * Clarence Dillon @DeptofDefense Flexible, purposive SMW use: mil takes 5 years to roll out; hesitate to collab.
| |
| * "Power corrupts; PowerPoint corrupts absolutely"
| |
| * simpler comm model for mil w SMW. huge money/time savings. spread via peer pressure. organic, private wikis, gov2gov, triage, social
| |
| * social networking critical. remote data, vocabularies. encouraging not using Office at all, directly in wiki. wikipatterns
| |
| * avoid noisy data w forms, "nobody above Major/above 35 uses it" (with exceptions) intel. comm. "learn to collab or lose job"
| |
| | |
| ==SIMILE, Exhibit, Wibit, Datapress, and Dido - David Karger ==
| |
| * @karger SIMILE, Exhibit, Dido: structured data in embedded novel interfaces for everyone in author society — lenses, views, facets
| |
| * @karger "You only need one person to be interested in something for it to show up on the Web" [http://shawnday.com/drink.html Ontario breweries 1914-1915]
| |
| * online course catalog in 4 days, took 6 months to get data from registrar; easy reuse data; datapress embed in wordpress cross site
| |
| * Dido inline view/data editor — no need to learn schemas, "Make the data look the way you want" separate representation from backend
| |
| | |
| ==The future of Semantic Forms - Yaron Koren ==
| |
| * Yaron Koren @wikiworks Next steps for Semantic Forms better integrated; easier SMW class maint; sep model/view, device UIs; use XML?
| |
| * wiki markup vs xml, issues moving away from wiki model to create richer, simpler UIs, markup too complicated: a crossroads
| |
| | |
| ==Handling n-ary data - Yaron Koren ==
| |
| * No great answers for n-ary data in SMW — no rich page editing, problems with page model?
| |
| | |
| | |
| {{Blikied|May 23, 2010}}
| |
Wordpress is like Barbie's Kitchen. You get a kit that lets you do what it shows on the box... blogs, RSS feeds, blog management, with extensions you can create maps, events, and so on.
Semantic Mediawiki (SMW) is like lego blocks. You can combine the basic blocks to make just about any shape, with extensions you can create your own content types, special views and functions.
Wordpress is easier to use (except when it comes to quick hypertext document editing, where wikis, after a quick introduction, rule). But with SMW, you can recreate most typical functions, and also recombine pieces. You can take the pieces of a "table" (a map location embedded in a page) and make a mosaic (a collection of map locations about a topic). The SMW approach is less rounded, but you can re-use the pieces and constantly build on your knowledge.
This is a characteristic of semantic sites. Each piece of content is well defined and re-usable.
Wordpress supports some semantic features now, but I prefer the "lego" approach, where people can more easily create different components, without resorting to a complex and difficult to maintain low level language.
There is more and more re-usable content and components on the Web; MIT's SIMILE project was created to make it easy to embed interactive views across sites and is supported by SMW and Wordpress, Microformats and RDFa make it possible to aggregate content in one place, whether it's restaurant reviews or departmental budgets.
SMW can support these functions for any site user, in a culture of transparently exchanging knowledge, but users have to learn the markup, which at times is not easy. A SMW site is best represented by a collection of people, some of whom are expert helpers.
