manifoldcf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karl Wright (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CONNECTORS-1181) Apache Stanbol Transformation Connector
Date Fri, 12 Feb 2016 07:49:18 GMT

    [ https://issues.apache.org/jira/browse/CONNECTORS-1181?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15144228#comment-15144228
] 

Karl Wright commented on CONNECTORS-1181:
-----------------------------------------

Hi [~dileepaj],

Usually the way the CLA works is the following:

- The granting organization owns the code privately and holds the copyright;
- The granting organization wishes to relicense the code for use and distribution by the Apache
Software Foundation;
- The granting organization fills out the CLA, and provides the granted code as a zip or tar
to Apache, who sets up a project and licenses the code under the Apache 2 license, provided
that the project has been accepted into the Apache Incubator first.

If Zaizi has already open-sourced the code through another means, and made it available under
the Apache 2 license, there is no need for Zaizi to fill out a CLA with Apache.  As soon as
the code is made publicly available with Apache 2 license headers, effectively Zaizi has done
that.  Even if this open-sourcing was done incorrectly, that is without the knowledge or legal
approval of the appropriate officers of Zaizi, the code still exists in the open source realm
and cannot readily be "un-open-sourced".

For the connector and client project, my understanding is that these have resided, freely
available, with appropriate open-source headers in GitHub for quite some time.  If that's
the case, I do not think a CLA grant is needed.  But if you want to make the client an Apache
project, you would need to approach the Apache Incubator, make your case for it, and have
a vote held.  Alternatively, we could decide to include the code as part of the Stanbol connector
in the MCF project, but then it would not be available separately for other potential users.

Hope this helps.


> Apache Stanbol Transformation Connector
> ---------------------------------------
>
>                 Key: CONNECTORS-1181
>                 URL: https://issues.apache.org/jira/browse/CONNECTORS-1181
>             Project: ManifoldCF
>          Issue Type: Wish
>    Affects Versions: ManifoldCF 1.8.2, ManifoldCF 2.0.2
>            Reporter: Rafa Haro
>            Assignee: Rafa Haro
>            Priority: Minor
>              Labels: connect, transformation
>             Fix For: ManifoldCF 2.4
>
>
> Apache Stanbol (https://stanbol.apache.org/) provides a set of reusable components for
semantic content management. One of this component is the Enhancer (https://stanbol.apache.org/docs/trunk/components/enhancer/)
which allows to extract features and semantic metadata from textual content like entities/concepts
from domain ontologies, named entities and so on.
> Apache Stanbol provides an easy-to-use REST API. The main idea behind this transformation
connector would be to enrich the Repository Document's (string) content with a configured
Stanbol processing chain. The Transformation Connector would allow the user to configure the
metadata that will be extracted from the Enhancer result for including it as RD's metadata
> This behavior come to somehow replace the functionality of the old Apache Stanbol CMS
Adapter (https://stanbol.apache.org/docs/trunk/components/cmsadapter/) and ContentHub (https://stanbol.apache.org/docs/trunk/components/contenthub/)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message