FiseDesign
From IKS Project
Contents |
Overview
- Clients can register content with FISE, by POSTing the URL of a piece of content to FISE. In the first prototype we simplify this by including the content in the POST payload.
- When content is registered, FISE creates 0 to N requests for content enhancement, and adds them to an internal queue.
- The FISE enhancement engine processes those requests, and can use various semantic enhancement engines (configured as plugins) to obtain additional meta-data, extracted entities, etc. from the content.
- This additional meta-data is stored internally by FISE.
- Once a piece of content is registered, FISE returns a unique ID for it.
- Clients can then use this ID to retrieve the FISE representation of the piece of content, which includes process info (any pending requests for enhancements for example) and enhancements provided by the external engines and identified according to which engine provided a particular enhancement.
Use cases
The use case have moved to FISE Use Cases page.
FISE components
This is the initial design of the FISE software components, as discussed on 2010/03/29. This has evolved since, see the services API package (including javadoc/package.html) for the current design: http://iks-project.googlecode.com/svn/sandbox/fise/trunk/generic/servicesapi/src/main/java/eu/iksproject/fise/servicesapi/
Content Registration Hook
Manages the content POST operations - just a thin layer on the framework's RESTful interface.
Content Analyzer
Creates requests for enhancement by analyzing the incoming content, and queues them in the Enhancement Engine for asynchronous execution.
Enhancement Engine
Manages the queue of enhancements requests.
To execute a request, selects an adapter for each external engine that it needs to talk to, asks that engine to enhance the content and stores the results in the FISE store.
Content Renderer
Formats the results of querying the FISE store, either to get data of a single content item or several.
