Stanbol
  1. Stanbol
  2. STANBOL-268

Configurable processing chains for enhancement

    Details

    • Type: New Feature New Feature
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 0.12.0
    • Component/s: Enhancer
    • Labels:
      None

      Description

      Depending on the application client need, a same Stanbol instance could provide different processing chain.

      At least, two types of processing chain could be useful :

      • The first one - fast - with just one or two "essentials" engines, provide entities to the users in (near) "real time"
      • The second one - slower -with a lot of engines, provided a detailed analysis, and computations that help for classification, summary, detailed enhancements, etc... and are displayed to the user later or when reopen document.

      Another types of chains can be useful depending on the type or the source of document (e.g. engine A is not useful for mail and picture, but relevant for scientific paper)

      Depending on the chain configuration, the endpoint could be sync or Async (see STANBOL-263), in a push or pull mode.

        Issue Links

          Activity

          Hide
          Florent ANDRE added a comment -

          Send by Fabian Christ on stanbol-dev ML :

          yes we discussed such chains a while ago and they are definitely on
          the roadmap. If I remember correctly, the idea was to have different
          chains at different URLs.

          /engines/fastchain
          /engines/mytestchain
          ...

          something like that

          Show
          Florent ANDRE added a comment - Send by Fabian Christ on stanbol-dev ML : yes we discussed such chains a while ago and they are definitely on the roadmap. If I remember correctly, the idea was to have different chains at different URLs. /engines/fastchain /engines/mytestchain ... something like that
          Hide
          Florent ANDRE added a comment -

          May Apache Camel, with this"Entreprise Integration Pattern" [1], may help to build routes for processing chains.

          A possibility to also building tuple space collaboration is something to consider (idea description here : http://www.mail-archive.com/stanbol-dev@incubator.apache.org/msg01138.html)

          [1] : http://camel.apache.org/enterprise-integration-patterns.html

          Show
          Florent ANDRE added a comment - May Apache Camel, with this"Entreprise Integration Pattern" [1] , may help to build routes for processing chains. A possibility to also building tuple space collaboration is something to consider (idea description here : http://www.mail-archive.com/stanbol-dev@incubator.apache.org/msg01138.html ) [1] : http://camel.apache.org/enterprise-integration-patterns.html
          Hide
          Rupert Westenthaler added a comment -

          EnhancementChains (see STANBOL-431, and [1]) do solve the principle problem of allowing different enhancement configurations as described here.

          However Enhancement-Workflows defined by using enterporise-integration-patterns are not covered by the current EnhancementChains.

          I see strong evidence that one needs both

          • Enhancement-Chains as something that helps to configure the Stanbol Enhancer (semantic lifting layer) - different semantic lifting workflows
          • Enhancement-workflows as something that integrates semantic lifting with the business layer - esases the integration of semantic lifting with the enterprise.

          So my proposal would be to further work on Enhancement-Workfows as integration pattern of Apache Stanbol with the entierpise.

          WDYT
          Rupert

          [1] http://incubator.apache.org/stanbol/docs/trunk/enhancer/chains/

          Show
          Rupert Westenthaler added a comment - EnhancementChains (see STANBOL-431 , and [1] ) do solve the principle problem of allowing different enhancement configurations as described here. However Enhancement-Workflows defined by using enterporise-integration-patterns are not covered by the current EnhancementChains. I see strong evidence that one needs both Enhancement-Chains as something that helps to configure the Stanbol Enhancer (semantic lifting layer) - different semantic lifting workflows Enhancement-workflows as something that integrates semantic lifting with the business layer - esases the integration of semantic lifting with the enterprise. So my proposal would be to further work on Enhancement-Workfows as integration pattern of Apache Stanbol with the entierpise. WDYT Rupert [1] http://incubator.apache.org/stanbol/docs/trunk/enhancer/chains/
          Hide
          Florent ANDRE added a comment -

          Solve this issue as #STANBOL-1008 is more focused on "Enhancements Workflow"

          Show
          Florent ANDRE added a comment - Solve this issue as # STANBOL-1008 is more focused on "Enhancements Workflow"

            People

            • Assignee:
              Unassigned
              Reporter:
              Florent ANDRE
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development