Return-Path: Delivered-To: apmail-incubator-stanbol-commits-archive@minotaur.apache.org Received: (qmail 98472 invoked from network); 1 Mar 2011 17:14:01 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 1 Mar 2011 17:14:01 -0000 Received: (qmail 67640 invoked by uid 500); 1 Mar 2011 17:14:01 -0000 Delivered-To: apmail-incubator-stanbol-commits-archive@incubator.apache.org Received: (qmail 67529 invoked by uid 500); 1 Mar 2011 17:14:00 -0000 Mailing-List: contact stanbol-commits-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: stanbol-dev@incubator.apache.org Delivered-To: mailing list stanbol-commits@incubator.apache.org Received: (qmail 67388 invoked by uid 99); 1 Mar 2011 17:14:00 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 01 Mar 2011 17:14:00 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED,T_RP_MATCHES_RCVD X-Spam-Check-By: apache.org Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 01 Mar 2011 17:13:58 +0000 Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116]) by hel.zones.apache.org (Postfix) with ESMTP id EBEC949E78 for ; Tue, 1 Mar 2011 17:13:36 +0000 (UTC) Date: Tue, 1 Mar 2011 17:13:36 +0000 (UTC) From: "Enrico Daga (JIRA)" To: stanbol-commits@incubator.apache.org Message-ID: <1973359867.5457.1298999616963.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] Created: (STANBOL-107) semantic description of the engines MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org semantic description of the engines ----------------------------------- Key: STANBOL-107 URL: https://issues.apache.org/jira/browse/STANBOL-107 Project: Stanbol Issue Type: New Feature Components: Enhancer Reporter: Enrico Daga Priority: Minor It would be nice to find a way to let engines declare which is the contribution they are going to provide. I see at least the following kinds of enhancements: 1) tagging: detect keywords, entities, concepts "within" the content 2) categorization/classification: locate the content in a conceptual place within a given framework. For example an engine could state that the document has "Secon World War" as primary topic, or "Theatre" in the framework of DBPedia categories, or state that is an E-mail, or a News, in the framework of the CMS document types; 3) metadata: the engine extracts metadata from within the content. For instance it returns the PDF metadata in RDF using the dublin core vocabulary 4) embedded knowledge: the source document is a rich HTML (with RDFa, Microformats) or it is a structured file (why not an RDF file, say a FOAF profile?) then, the enhancement engine should also say HOW it contributes in terms of vocabulary elements 1) Does the engine add annotation roles? 2) Does it add entity types? 3) Which metadata fields it will return? This could be done with an RDF description stating which are the terms the engine will introduce in relation to the ones of the Stanbol Enhancement base ontology (STANBOL-52). This is also related to STANBOL-3. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira