On 18/07/13 12:27, Reshmi Raji wrote:
Hi,
Abstract :
*User interface to select any resource from either a list of all triples in
a graph, or from the results of a SPARQL query(result table).
*An IDE for input query - syntax highlighting, automatic indentation, and
easy commenting out of selected lines of text.
* Display how long queries have been executing, and allow the user to
cancel queries that may be taking too long.
*Fuseki Management:
There are many tasks here that would be great. Expose JVM properties via
JMX in a nice UI. Things like CPU/Memory usage, disk space remaining, etc.
Allow initiation of back-up tasks. Allow the user to download a snapshot of
the repository.
Yes - that's what JENA-420 says. I'd add the ability to add and remove
datasets from a running server (needs both UI and server side changes).
http://community.apache.org/mentoringprogramme-icfoss-pilot.html
gives a project proposal framework of
WHAT - HOW - WHEN
There needs to be more detail of the WHAT (JENA-420 lists possibilities
- it's not a prescriptive list - try dividing it up into user tasks, for
different kinds of user like query writers and systems admins).
You then need to give the HOW, from studying the Fuseki codebase and
looking at what it currently offers.
The WHEN should be a plan for the duration of ICFOSS, describing tasks
needed to achieve some or all of WHAT, and giving a timeline of what
will delivered when. Note especially the mid-way evaluation.
If you also look at the material about Google Summer of Code, which this
is based on, there is advice on what makes a good project proposal.
Andy
