From IKS Project
RICK stands for Reference Infrastructure for Content and Knowledge.
Reference Infrastructure:RICK provides an infrastructure to manage referenced Sites. RICK comes with out of the box support for commonly used protocols such as Linked Data but also allows extensions to work with sites that do not support standards. RICK allows the use of local caches. Such caches can store some/all information of referenced sites and are typically used if one needs to work offline, to increase query performance or to support queries that would not be possible/feasible by directly using the services provided by the referenced site.
RICK provides RESTful services to work with Entities used by a CMS. This includes services to
- import entities: Import Entities from referenced Sites and to configure which properties should be imported. If necessary, define several mappings to merge information originating from different referenced sites.
- manage entities: RICK defines states for both imported entities and entity mappings. The proposed state allows to add entities to the entity hub even if there would be a need for some kind of approval before they can be used for daily operations. The active state is used for entities that are approved by the organization. In addition it is possible to mark entities as deprecated or removed. Default states are configurable per referenced site (e.g. entities imported form geonames.org are automatically approved - state:active)
- work with entities: Search for Entities based on name and language, type, value ranges ... This provides suggestions for entities while typing. Looks up Entities for Tags and/or URLs. Retrieves information for Entities mentioned in content managed by the CMS. Gets the knowledge needed to enable [Dynamic Semantic Publishing].
- single access point: RICK allows to query for and to retrieve entities defined by any of the referenced sites. Developers need not to understand the different services, query languages and data formats. RICK provides a single access point and query language to work with all of them. Typically such functionality is important for semantic lifting of content (see FISE), but might be also interesting for manually tagging of content if users are allowed to suggest/import new Entities from any of the referenced sites.
- Installation of the Rick
- RestFull Service API of the Rick
- Rick Software Documentation
- Indexing Utilities (for creating full caches of referenced sites
- File:IKS-community-workshop-stanbol-entity.pdf (December 2010): This Presentation gives an overview about RICK (renamed to "stanbol.entityhub").
Specially Supported Referenced Sites
- dbPedia.org: For more information see configuration of Referenced Site, because dbPedia is used there as Example.
- geonames.org: There is a special tool that creates a full index based on the data base dumps. This index can than be used to use geonames.org with the Rick. The this page for details.
- This article describes the Motivation for RICK and links to several interesting articles.
- The specification of the Symbol Service provides the definition for terms such as Entity, Symbol, Representation and also gives Examples what it means to re-use Web-Resources for Content Management. The specification of the Symbol Service at the end of the Document is a little bit outdated and need to be replaces with the Documentation of the actual implementation of RICK.
- The source code of the first alpha version of Rick is available here [http://code.google.com/p/iks-project/source/browse/#svn/sandbox/rick