From OntologPSMW

Revision as of 04:39, 9 January 2016 by KennethBaclawski (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search
[ ]


A Glimpse into the Future of SemanticWiki's     (1)

For SemanticWiki mini-series Session-6: The Future of Semantic Trends, Challenges and Outlook (Panel Discussion)     (1A)

As part of the preparation for the concluding session of the SemanticWiki mini-series program, we are inviting all our panelists to share with us their vision of what the future of semantic wikis would be like.     (1A1)

All organizers, chairs and speakers from previous sessions are invited to each deliver short statements regarding the future of semantic wikis as they each see it (2 min. each). Those who plan to make short statements are requested to add their 3 to 6 bullets here (or send them in via email to the session co-chairs with a copy to <>) before the end-of-day Friday 2009.02.27     (1A2)

Key bullets of speakers' short statements     (1C)

Sample statements: (template)     (1C1)

utilizing wikis; and half of them will be (what we would recognize as) semantic wikis.     (1C6)

Please enumerate your 3 to 6 thoughts on how you see the Future of Semantic Wikis, in terms of Trends, Challenges and Outlook.     (1C7)

... read this if it's your first time editing the Ontolog wiki. =ppy     (1C8)

These thoughts will be presented in 2-minutes lightning talks at the SemanticWiki mini-series session-6 event     (1C9)

    • technologies from semantic wikis will merge into collaborative Web 2.0 (3.0?) apps like Google Docs     (1C12A)
    • nobody will use wiki text syntax any more. WYSIWYG HTML editing or semantic forms or something else will be the GUI for editing/annotating     (1C12B)
    • still a challenge: adequately mapping knowledge with complex structures onto the page-granular wiki architecture, where the page is the base unit of editing, versioning, linking, search     (1C12C)
    • still a challenge (not really been addressed in recent years AFAIK): more expressive reasoning vs. maintaining consistency     (1C12D)
    • Semantic wikis provide an enormous potential to serve communities of casual users as mash up application providing unified view on business-related artifacts. We foresee the following challenges on the way to this vision:     (1C13A)
      • Improve usability of schema level operations (e.g. wizzard to build a representation of the artifact "customer complaint")     (1C13A1)
      • Improve ways to include artifacts from legacy systems into the wiki (e.g. drag and drop of documents, bugzilla bug reports etc)     (1C13A2)
      • Learn about usability and ease-of-use from commercial (enterprise) wikis such as Confluence or Deki Wiki     (1C13A3)
    • Semantic Wikis are a special case of the more general category of Model-driven Web Applications, for which established methodologies exist;     (1C15A)
    • Future (semantic) web applications will have wiki characteristics, notably, end-user contributed data AND schemas;     (1C15B)
    • The current (semantic) wikis architectures are not appropriate to support full-fledged applications; more general architectures will be used.     (1C15C)
    • ��Ontology�� as it is used today serves (at least) two distinct roles:     (1C19A)
    • 1. A collection of shared definitions:     (1C19B)
    • --- When I (we) say ��X��, we mean...     (1C19C)
    • --- If you��ve got A, B, C then you��ve got an ��X��     (1C19D)
    • 2. A distributed collection of knowledge     (1C19E)
    • --- ��X�� might cause ��Y��.     (1C19F)
    • --- ��X�� usually is associated with ��T��     (1C19G)
    • A primary role of Wiki (however we define it) has always been role 2     (1C19I)
    • Semantic Wiki allows islands of knowledge to become networks of knowledge, by allowing links across definitions... if we have shared knowledge of those definitions. (O4W)     (1C19J)
    • The jury is still out when it comes to the applicability of Semantic Wiki on role (1). We have seem some promising efforts on W4O, and, clearly, Semantic Wiki can play a critical role in evaluating, critiquing and gathering collective knowledge for role 1, but the OOR still seems to be something that goes well beyond ��wiki�� space when it comes to organizing, validating and dissemination.     (1C19K)
    • Application and solutions are still fragmented - we need more mix and match, both on content AND tools     (1C19L)
    • 1. Community buy-in: we need to convince the users (e.g., neuroscientists and life scientists) that semantic wiki can help their work     (1C23A)
    • 2. If we have DBPedia as the semantic web interface to Wikipedia, how can we create a more powerful interface between semantic web and semantic wiki?     (1C23B)
    • 3. Can semantic wiki help bridge web 2.0 and web 3.0?     (1C23C)
  • Mark Musen - regarding "what is a semantic wiki?"     (1C28)
    • [One possible issue] is that there are folks who are ascribing a religious aura to the term "semantic wiki." People in the community are focusing on the "wiki" moniker, rather than on the underlying functionality that has been implemented. It has become an article of faith that, if developers are using the term "wiki", then the software is, ipso facto, easy to use. If they are using the term "semantic wiki", then not only is the software easy to use, but also by definition the software "solves" the problems of knowledge representation. I have heard of representatives of funding agencies that are uninterested in any Web 2.0 technology unless it is a "wiki", since "wiki" has become synonymous with usability.     (1C28A)
    • I am not suggesting that the "semantic wiki" community needs to draw lines in the sand, but I am concerned that the term "semantic wiki" is becoming an overloaded buzzword that often drives unrealistic expectations. I agree that the community should be inclusive, but I wonder whether the term "wiki" is no longer helpful. I'm having a lot of d��j�� vu from the days when the phrase "expert system" became so problematic for the knowledge-based systems community.     (1C28B)

(application-specific data structures, reasoning, constraint checking, etc.)     (1C30)

also between other sites/tools/web services)     (1C32)

    • semantic wikis as user programmed environments for applications (business, public and other domains)     (1C40A)
    • programmed in the same way as the wiki pages are edited     (1C40B)
    • different models and languages need to be studied to support that (such as composition by meshup, lightweight domain specific languages and so on)     (1C40C)
    • The semantic wiki (in its enlarged scope) as the HCI (human-computer interaction) interface of choice     (1C42A)
    • Wikis, Semantic Wiki and even the Semanitc Web to disappear into the mainstream, to be recognized by users and the media as web x.0     (1C42B)
    • Impact: Semantic Wiki as the enabler of collective human intelligence - I am constantly reminded of Doug Engelbart's NLS (oNLine System), and his notions of OHS (Open Hyperdocument System), DKR (Dynamic Knowledge Repository) and [[CollectiveIQ]] . . . finally, after decades, they are coming close to becoming a reality     (1C42C)
    • a word of caution: if we give up on "open" - open read/write access, open content, open source technology; essentially open collaboration & open knowledge - as many applications may opt for, we are giving up on a huge portion of the power and benefit that a wiki (as it was originally conceived) is able to bring us.     (1C42D)
  • Rudi Studer - Some Decisions to Be Made (by Us)     (1C44)
    • "More Power!" vs. "Keep it simple!" (a classical conflict, continued)     (1C44A)
      • SemanticWiki users do ask for more expressivity     (1C44A1)
      • SemanticWiki users do complain about ease of use     (1C44A2)
      • Semantic Tech offers so many new features     (1C44A3)
      • Approach 1: Invent new interface metaphors (this is more than just implementing impressive GUIs; e.g. use "concepts", "rules", "inheritance" not "logical formulas", "axioms", "ontologies"; new ideas wanted!)     (1C44A4)
      • Approach 2: Separate concerns in modeling (not all users are equal: clarify different editing roles; provide filtered "views" on knowledge; modularize)     (1C44A5)
      • Further Approaches?     (1C44A6)
    • What about the world beyond wikis? (yes, there is one)     (1C44B)
      • Most SemanticWiki's offer some data exchange     (1C44B1)
      • Few SemanticWiki's actually exchange any data     (1C44B2)
      • Semantics should enable knowledge exchange     (1C44B3)
      • Approach 1: Conquer the Desktop (much data still is offline; build connections to exchange knowledge with relevant tools; often tool-by-tool basis)     (1C44B4)
      • Approach 2: Conquer the Web (every wiki is an island; how to integrate data across sites? Integrating wikis with other web services?)     (1C44B5)
      • Further Approaches?     (1C44B6)
    • What becomes of the "Wiki Way"? (times are a-changin' ...)     (1C44C)
      • Wikis were "defined" as CMS that are quick, simple, collaborative but hardly any concrete feature is common to all "wikis"     (1C44C1)
      • Semantic Wikis are Wikis that "use" semantics     (1C44C2)
      • "Definitions" of other CMS types hardly better     (1C44C3)
      • Are these categories really useful?     (1C44C4)
      • What content management do we want to use tomorrow?     (1C44C5)
      • Semantic wikis as the basis for guiding new systems for managing knowledge     (1C44C6)

is able to access and understand it immediately, and is able to learn how the content can be extended and changed within very short time.     (1C50)

semantic technologies and that follow the principles of wikis. They will build upon the research we are doing today on semantic wikis. However, these web applications will probably not call themselves "semantic wikis".     (1C52)

Additional pertinent thoughts: (all are welcome!)     (1C56)

... please enter your thougths below (kindly identify yourself and date your entry.)     (1C56A)

This page has been migrated from the OntologWiki - Click here for original page     (1C56C)