Asian Canadian Wiki

Category:Type: Difference between revisions

Category Discussion

Category:Type (edit)

Revision as of 22:31, 18 June 2010

No change in size ,  18 June 2010
no edit summary
No edit summary
No edit summary
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‎]].


If you entered an actor, you should see them below, they will also be present on other queries:
== State of the software - Yaron Koren ==


{{ #ask: [[born::+]]
* First challenge for smw: visibility
|?born
* Second challenge for smw: communication ... duplicate effort
|?died
* "no brick walls separating users from developers," everyone welcome to contribute
|?is from
* Third challenge, less important, funding ... too much money can hurt a project
|?died in
* "Semantic" is an abused word, use alternatives.. platform.. bur semantic will be the breakthrough?
|?died of
}}


== Summary ==
== Welcome address - David Karger  ==


In these pages, you've seen how to build on the existing, widely available, hypertext web by adding re-usable data. Going from the flexibility of wikis, we've encoded re-usable information that can be used for queries and views. Form front ends can simplify entering field data.
* @karger - many tools are wrong, developers 'guessing' - smw lets users emerge their data/structure, see more tools like smw
* Philip of @Ontoprise plan fine access controls; rich editor w annotations, queries; social/dashboard; wikibooks; facet browse, rules


What hasn't been covered is re-using data across sites. Semantic Mediawiki extensions allow auto completion based on ontologies from other sites. So your site about actors could query a site about locations or causes of death. Semantic Mediawiki can also query and include data from RDF data sources, tab separated values and database data locally or on other sites.
== Halo: Current status and future developments in 2010 - Philipp Zaltenbach ==


While Semantic Mediawiki is just one approach to SemWeb, it practically builds on the underlying principals of wikis and the most popular open source Wiki software that has many extensions and supporters and users, including Wikipedia. When Wikipedia flips a switch, all its data will become semantic (evidenced today in sites like [http://dbpedia.org DBPedia]) and the culture will evolve to expect more and more refined and re-usable data.
* @Ontoprise dev'ing linked open data #LOD between sites — integrate DBPedia (WP), etc; q about dependencies on their proprietary sw
* side skype chat discussing problems with rich text editors that mangle output, same problem for many systems


Today we have a grab bag of standard Web components. Semantic Wikis should '''not''' be thought of as another element. The list of blogs, CMSs, calendars, etc, etc can all be rolled up into a semantic wiki, with re-use of information throughout - add a query and view into your blog posting, add events to any document.
== Mashup of LexWiki and WebProtege for collaborative ontology authoring - Guoqian Jiang ==


Of course, other systems have and are gaining semantic features. But standard sites today are 'admin' managed. 'Users' on wiki sites also expect to participate more. They can create or augment data types and add their own views. They can use their own front ends to work with data. In fact, browsers tomorrow are expected to be more interactive and rely on server processing less - a server can just provide raw data, the application can be in the browser.
* Guoqian Jiang @MayoClinic Lexwiki collab ontology dev ('propose' tab), curate, integrity; SMW to scale/distrib experts, hierch probs


This yields other benefits. Today many sites don't pay much attention to accessibility - use of sites by people with reduced vision, for example. On a well designed site with good structure and cues, a person with disabilities can be greatly enabled, perhaps more so than people who just read a page from top to bottom. But on poorly designed sites, it can become extremely tedious or impossible to access data. Well structured data using formats like RDF can allow alternative front ends for special uses to be easily created, regardless of the competency of the source agency.


[[Category:SemWeb]]
==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}}
Retrieved from "https://asiancanadianwiki.org/w/Special:MobileDiff/3296"