FISE Use Cases
From IKS Project
Note The use cases described in this section are not all fully implemented yet! For each use case you will get the future vision and the current state of development. The current state is becomes visible through our online demo server.
Contents |
Stateless REST analysis
Vision
- Clients POST content to FISE enhancement engines and get back the enhanced content.
- The interface allows the caller to submit content to the FISE engines and get the resulting enhancements formatted as RDF at once without storing anything on the server-side.
- The content to analyze should be sent in a POST request with the mimetype specified in the Content-type header. The response will hold the RDF enhancement serialized in the format specified in the Accept header.
Current State
- See /engines end point of FISE at our online demo powered by NUXEO.
Content registration
Vision
- Clients make a POST request to FISE, including content as a payload, and optional additional metadata using the FISE schema (to be defined).
- FISE analyzes content, finds out which enhancements apply, and creates requests for enhancements in an internal queue.
- FISE returns a unique ID for the document ("ContentID") that client uses later to retrieve info about this piece of content.
Current State
- See /store end point of FISE at our online demo powered by NUXEO.
Get enhanced content
Vision
- Client makes a GET request to FISE on the URL of the content ID.
- FISE returns meta-data that includes process info (like any pending enhancement requests) and the content of enhancements
Current State
- See /store end point of FISE at our online demo powered by NUXEO.
Query enhanced content
Vision
- A GET request on a SPARQL endpoint executes a query in the FISE store, and returns data with the same schema as in the "get enhanced content" use case.
Current State
- See /sparql end point of FISE at our online demo powered by NUXEO.
