Mailing-List: contact jena-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jena-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: local policy)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Apple Message framework v1082)
Subject: Re: Lucene/Solr and Jena
From: Damian Steer <d.steer@bristol.ac.uk>
In-Reply-To: <0B7BBDC3-866A-4662-A111-965941C72DE2@bris.ac.uk>
Date: Wed, 9 Feb 2011 14:24:17 +0000
Content-Transfer-Encoding: quoted-printable
Message-Id: <D05CC8F1-2E2B-4841-BBD5-77C60E5D2BFD@bris.ac.uk>
References: <AANLkTikO1kkW6Lois8YTXy5ETtncgNGuKp-6q0LA78VR@mail.gmail.com>
 <0B7BBDC3-866A-4662-A111-965941C72DE2@bris.ac.uk>
To: jena-dev@incubator.apache.org

Apologies, I guess attachments get stripped. Textified doc below.

Damian

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D


SolrStore Project


2/1/2011
Independent Study
CSC-9020-001


Team Members:  	Frank Tanz,=20
Bharti Gupta
Bala Krishna Chitneni


=0CProject Charter
SolrStore

Project Title: SolrStore
Date: February 1, 2011

Project Start Date: February 1, 2011		Projected Finish Date: =
April 30, 2011

Project Manager: Frank Tanz			E-mail: =
frank.tanz@villanova.edu


Project Justification:=20
Currently, the Jena API provides persistent storage of RDF data using =
relational database models such as MySQL, Oracle and Microsoft SQL =
Server.  These relational databases are convenient for storage but =
suboptimal for the storage and access model present in the Semantic Web. =
=20

Project Objective:=20
The focus of this project is to extend the Jena API with the ability to =
persist graphs/models using a non-Relational Database Model.=20

Approach:
We intend to use and leverage the Lucene/Solr engine which was created =
by Doug Cutting of Google. This will allow us to step beyond the =
non-polynomial algorithms which combine search and semantic access.  We =
also intend to use and leverage Cloud Computing as it provides a =
targeted opportunity for large scale storage and access in a fault =
tolerant a load balanced way.

Project Scope (Characteristics and Requirements):
Project team members will join the Open Jena project team as =
contributors.
Configuration management will be handled utilizing the implementation of =
Subversion within Sorurceforge.net.
All software material for the project will be managed and stored within =
the project=92s repository within Sourceforge.net.
The ability to persist Semantic Web content in the cloud.
The ability to retrieve Semantic Web content from the cloud.
The ability to provide fault tolerance and failover within the cloud for =
Semantic Web content.

Project Deliverables:
High level abstract design.
Detail design demonstrating how the Jena API will hook into both Solr =
and Lucene models.
Source code and objects for the Open Jena SolrStore implementation.
Individual Final Report prepared by Frank Tanz
Individual Final Report prepared by Bharti Gupta
Individual Final Report prepared by Bala Krishna Chitneni


Stakeholder Roles and Responsibilities:

Name	Role	Responsibilities
Frank Tanz	Project Manager/Developer/Lead Jena Expert	Design, =
Development, Project Management, and Testing
Bharti Gupta	Developer/Lead Lucene Expert	Design, Development, =
Documentation, and Testing
Bala Krishna Chitneni	Develper/Lead Solr Expert	Design, =
Development, Documentation, and Testing
Scott Streit	Project Advisor	Project Requirements, Project Guidance, =
Project Signoff
Vijay Geholt	Project Co-Advisor	Project Requirements, Project =
Guidance, Project Signoff

=0CProject Schedule:

Milestone	Start Date	Target Due Date
Set up project on SourceForge and assign team access to the project.	=
2/1/11	2/8/2011
Setup team client development environments.	=09
Setup team server development environments	=09
Set up subversion file structure	=09
Create work breakdown schedule	=09
Finalize abstract design 	=09
Finalize detail design	=09
Achieve Semantic Web persistence =96 local via Lucene	=09
Achieve Semantic Web retrieval =96 local via Lucene	=09
Achieve Semantic Web persistence =96 cloud via Solr	=09
Achieve Semantic Web retrieval =96 cloud via Solr	=09
Final Reports =96 Initial Draft	=09
Final Reports =96 Final Version	=09

Communication Plan:

The team agreed to communicate via email, sourceforge.net, as often as =
needed.
The team agreed to meet each Thursday afternoon face to face at 5:00 PM =
prior to the start of evening classes.
 The team agreed to participate in conference calls and Skype as needed.
The team agreed to adhere to all committed dates on the project schedule =
and the work breakdown schedule.=20
Each Thursday, each team member will provide a progress status report to =
the Project Manager and Co-Advisors via email.

Risk Management:

Area of Risk	Severity	Mitigation Plan
TBD	=09
	=09


Project Success Criteria:=20
The project=92s Co-Advisors accept the deliverables.=