Mailing-List: contact stanbol-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: stanbol-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of suatgonul@gmail.com
 designates 209.85.214.47 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:user-agent:mime-version:to:subject
         :content-type:content-transfer-encoding;
        b=PRMLyvE+ntSymVpsq9ZnWT4pCjA08BiKV/UMk7dixdnnLl1KGWTTJDXmTn24mFpw+p
         X+XGHE1nTuxfgcO/+ZMUSqzKi1JQCiE816ryNdVQ7ZBnpl7/BBsQWQ/Of2KhR+It3bcl
         5mKsVgZev2SHbkOgoqJNQgRF2SWii2dQYZ1ig=
Message-ID: <4DE5E1FF.2020909@gmail.com>
Date: Wed, 01 Jun 2011 09:53:51 +0300
From: Suat Gonul <suatgonul@gmail.com>
User-Agent: Thunderbird 2.0.0.24 (X11/20100623)
MIME-Version: 1.0
To: stanbol-dev@incubator.apache.org
Subject: Contenthub structure
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Hi everbody,

After discussing with Rupert yesterday, we have come up with a basic 
design for the Contenthub component.

It will provide two main RESTful interface to:

1) Upload (register) content and metadata (Available in current 
implementation)
2) Search for registered content

There would be Indexing Engines for (1) and Search Engines for (2). The 
Contenthub implementation would then implement Indexing Engines to store 
the enhancements in a triple store and Search Engines to search 
enhancements and content items in triple store.

There is also an already started implementation for the search part in 
google code base of IKS project at [1]. It will be integrated to the 
Contenthub component.

What do you think?


Best,
Suat

[1] 
http://code.google.com/p/iks-project/source/browse/sandbox/#sandbox%2Fsearch