Rise

From semanticweb.org

• Homepage RISE-Homepage
• Platform: Anywiki, here LAMP + Sekt Integration Platform
  • SIP works von Data repository
  • There is another implementation of RISE Wiki with TRAC RISE LSA+Tag
• Paper: Self-organized Reuse of Software Engineering Knowledge supported by Semantic Wikis

We have two installations, based on different technologies. Here, the installation on the RISE homepage - based on CBR - is mentioned.

Contents 1 Wikitology: The underlying idea 2 Evaluation 2.1 Main wiki characteristics 2.2 Standard project info (align with sourceforge attributes) 2.3 Standard wiki features 3 User Features 3.1 Formalization

[edit] Wikitology: The underlying idea

The guiding idea of RIS is the "Wikitology", i.e., that the Wiki is the physical representation of the ontology with pages as concepts and links as relations (an idea of Ralph Traphoener, reported in Decker, Ras et al., 2005; Decker, Rech et al., 2005) The practical implementation of this Wikitology is as follows: The ontology used by the community is edited via the Wiki itself. A set of naming conventions is used to determine automatically the actual ontology from the Wiki content. For example, document templates may start with “DocType”. This naming convention allows a user to add new document templates just by creating a new document starting with DocType (an alternative to this convention would be to use namespaces). Since those templates contain a reference to themselves, an instance of this template is automatically linked to the template. In addition, domain-ontology independent information like the document type or the date of creation is derived from the Wiki and included into the ontology. These conventions and automatic determination of meta-data can be seen as an easily remindable, implicit meta-ontology.

[edit] Evaluation

[edit] Main wiki characteristics

Is the wiki web-based or a (standalone) desktop application?

• Web-based

What communities (type/size) is the wiki intended for?

• Primary target group: People in the software process, in particular Software Developers, but also documentation specialists, support and

[edit] Standard project info (align with sourceforge attributes)

What is the wiki engine's software license?

• Currently, proprietary / commercial.
• The Sekt Integration Platform - containing relevant parts of the software used in here - will be released in december under a Freeware license (i.e. no open source for the core!)

What programming language is it written in?

• Java (Server Pages, J2EE)

What status is the project in? (project maturity)

• Prototype

What is the estimated size of the developer community?

• 10 (IESE + people at one of the application partners)

What is the estimated size of the installation base?

• 1 Installations (@ customer)

[edit] Standard wiki features

== Description Scheme:

• Name
  • Short description
  • Rationale (also for additional users
  • Scale, Possible Values, Explanation

[edit] User Features

• • Editing: Basic
  • Markup Syntax: JSP Wiki style
  • Access Rights: User Group
  • Attachments: Yes
  • Versioning: Diff, Rollback
  • Navigation Support: Backlinks
  • Plugins: Yes, MASE as underlying offer several plugins
  • Further Features: None

• Developer Features
  • Backend: File based and Database
  • Versioning 4 Devs: File based and Database
  • XML-RPC Ready: Read Only (Since based on JSP Wiki)
  • Extensions Mechanism: Plugin

[edit] Formalization

Are semantics (triples/whatever) separated from or included in the wiki markup?

• Included (marked with {} for named links and metadata.
• Ontology extraction on the instance level is also done based on pages name.
• Example: instances (documents) of templates (concepts) start with the name of the template.
  • Example: Actor_RegularUser is derived from the template Actor

Is the end user supported when formalizing content/adding annotations in some way? autocompletion/proposal generation/schema or consistency checking

• No! (So use metadata / additional information sparingly!

What representation language is used? (RDF/OWL/...)

• Orenge Knowledge Models (proprietary, but documented format, export to RDF possible via SIP

Is there versioning support for the formalized content?

• Ontology is created (on the instance level) every night, old version are overwritten!

Is there provenance (Herkunft) support for the formalized content? (get formalized contents/triples tagged with its author?)

• No!

What things can get formalized?

• Metadata, links, templates

Is there support for typing pages/category system/page tagging?

• No!

Is there support for typing links?

• No!

What ontology support does the wiki provide?

•  ????

Is there support for loading/saving ontologies?

• No! -> Created based on rules

Can ontologies be created/changed from within the wiki?

• Somehow: When you add templates based on naming conventions

Is there any reasoning support?

• CBR (If this counts as reasoning)

Is the instance data required to comply with the ontologies?

• No

How can semantic information be exploited?

• For navigation and consistency checks

Is there simple querying support? (search for all triples with a certain subject, predicate, object)

• Yes,

Is there advanced querying support? (free, complex queries) Is there any real user interface for expressing advanced queries?

• Show similar pages based on curren content and context

Is there any special visualization?

• Hyperbolic tree / topic map

Is there any way to render pages from formalized content? No!