Semantic Mediawiki Spring 2010 conference: Difference between revisions
Jump to navigation
Jump to search
(espace) |
No edit summary |
||
| Line 2: | Line 2: | ||
* at Spring #SMWCon 2010 | * at Spring #SMWCon 2010 | ||
* First challenge for smw: visibility | * First challenge for smw: visibility | ||
* Second challenge for smw: communication ... duplicate effort | * Second challenge for smw: communication ... duplicate effort | ||
| Line 7: | Line 8: | ||
* Third challenge, less important, funding ... too much money can hurt a project | * Third challenge, less important, funding ... too much money can hurt a project | ||
* "Semantic" is an abused word, use alternatives.. platform.. bur semantic will be the breakthrough? | * "Semantic" is an abused word, use alternatives.. platform.. bur semantic will be the breakthrough? | ||
* @karger - many tools are wrong, developers 'guessing' - smw lets users emerge their data/structure, see more tools like smw | * @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 | * Philip of @Ontoprise plan fine access controls; rich editor w annotations, queries; social/dashboard; wikibooks; facet browse, rules | ||
* @Ontoprise dev'ing linked open data #LOD between sites — integrate DBPedia (WP), etc; q about dependencies on their proprietary sw | * @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 | * side skype chat discussing problems with rich text editors that mangle output, same problem for many systems | ||
* Guoqian Jiang @MayoClinic Lexwiki collab ontology dev ('propose' tab), curate, integrity; SMW to scale/distrib experts, hierch probs | * Guoqian Jiang @MayoClinic Lexwiki collab ontology dev ('propose' tab), curate, integrity; SMW to scale/distrib experts, hierch probs | ||
* Jie Bao SMW usability (map.rpi.edu, data.gov) UI trumps low level abilities; forms limited; page model restrictive; devs prefer dev | * 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 | * RDF model 'deeply right' for flexbl DB. Fixes: small cadre dev semantics, most use; inline triples; support mult POV; SMW != RDF | ||
* Timothy Quievryn SMW impact on @wikia (mostly entertainment); Forms great advance, biggest wikis use it; soon all, dynamic games? | * Timothy Quievryn SMW impact on @wikia (mostly entertainment); Forms great advance, biggest wikis use it; soon all, dynamic games? | ||
* Jesse Wang connects SMW to MS Office for user workflow, usability: uses MS SMartTags. Browse values, easy Outlook export nonfree | * Jesse Wang connects SMW to MS Office for user workflow, usability: uses MS SMartTags. Browse values, easy Outlook export nonfree | ||
* Clarence Dillon @DeptofDefense Flexible, purposive SMW use: mil takes 5 years to roll out; hesitate to collab. | * Clarence Dillon @DeptofDefense Flexible, purposive SMW use: mil takes 5 years to roll out; hesitate to collab. | ||
* "Power corrupts; PowerPoint corrupts absolutely" | * "Power corrupts; PowerPoint corrupts absolutely" | ||
| Line 21: | Line 29: | ||
* social networking critical. remote data, vocabularies. encouraging not using Office at all, directly in wiki. wikipatterns | * 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" | * avoid noisy data w forms, "nobody above Major/above 35 uses it" (with exceptions) intel. comm. "learn to collab or lose job" | ||
* @karger SIMILE, Exhibit, Dido: structured data in embedded novel interfaces for everyone in author society — lenses, views, facets | * @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] | * @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 | * 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 | * Dido inline view/data editor — no need to learn schemas, "Make the data look the way you want" separate representation from backend | ||
* Yaron Koren @wikiworks Next steps for Semantic Forms better integrated; easier SMW class maint; sep model/view, device UIs; use XML? | * 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 | * wiki markup vs xml, issues moving away from wiki model to create richer, simpler UIs, markup too complicated: a crossroads | ||
* No great answers for n-ary data in SMW — no rich page editing, problems with page model? | * No great answers for n-ary data in SMW — no rich page editing, problems with page model? | ||
{{Blikied|May 23, 2010}} | {{Blikied|May 23, 2010}} | ||
Revision as of 22:06, 29 May 2010
I attended http://semantic-mediawiki.org/wiki/Spring_2010_SMWCon at the MIT CSAIL Lab in sunny Boston. Here are my Twitter microblog comments, my talk is at Encouraging Semantic Mediawiki use with non technical people.
- at Spring #SMWCon 2010
- First challenge for smw: visibility
- 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.. bur semantic will be the breakthrough?
- @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
- @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
- Guoqian Jiang @MayoClinic Lexwiki collab ontology dev ('propose' tab), curate, integrity; SMW to scale/distrib experts, hierch probs
- 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
- Timothy Quievryn SMW impact on @wikia (mostly entertainment); Forms great advance, biggest wikis use it; soon all, dynamic games?
- Jesse Wang connects SMW to MS Office for user workflow, usability: uses MS SMartTags. Browse values, easy Outlook export nonfree
- 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"
- @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" 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
- 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
- No great answers for n-ary data in SMW — no rich page editing, problems with page model?