Pelagios Project Plan Part 6: Projected Timeline, Workplan & Overall Project Methodology
Pelagios is divided into three work packages (WP), centred on the three stated outputs of the project: core ontology development; application of that ontology to the project partners’ sample datasets, and documentation of the process; and development of web resources to trial and show the value of the ontology for users.
WP1 Ontology Specification – LUCERO, Southampton ACRG, Pleiades
WP1 has three key elements:
1. First, to develop a core ontology for (ancient) place references (COPR) with help from the partners. This involves:
· Gathering from the project partners sample dataset ontologies that describe references to places in their documents, identifying common elements, and evaluating their robustness
· Constructing a core ontology that can be applicable for all the different datasets represented by the partners (text, database, map), and then testing its implementation with a SPARQL demonstrator
2. Second, to hold a two-day workshop on developing a core ontology for linking open geodata. This involves:
· Disseminating around the project partners and workshop invitees the proposed ontology as well as abstracts from all the speakers
· Hosting a one-day workshop that is open to all members of the community* with three sessions dedicated to: 1) Issues of referencing ancient and contemporary places online; 2) Lightweight ontology approaches; 3) Methods for generating, publishing and consuming compliant data. Each session will consist of several short (15 min) papers followed by half an hour of open discussion.
· Hosting a project meeting on the day following the workshop, which will be devoted to incorporating feedback from the community and then deciding upon the core pelagios ontology that will be used by each of the project partners
3. Lastly, to publish the COPR in RDF (hosted by Pleiades)
*For more information about the community workshop, including registration details, please visit: http://pelagios.eventbrite.com/
WP2 Documentation of Uniform Resource Identifiers (URI) Mapping and RDF publication – GAP, Perseus, SPQR, Arachne, DME
WP2 is divided into 5 parallel streams (A-E) according to the different document types hosted by each of the partners. Each stream will:
i) Detail the process by which local place references are aligned with Pleiades URIs and COPR-compliant RDF is generated and hosted
ii) Make recommendations for document-type extensions to COPR
· Stream A: GAP will document processes related to narrative free texts
· Stream B: Perseus will document processes related to XML-encoded freetext (In Kind)
· Stream C: SPQR will document processes related to fragmentary free texts
· Stream D: Arachne will document processes related to database records
· Stream E: DME will document processes related to rasterized maps
WP3 Development of Web services and tools to facilitate consumption – DME
This last WP trials and develops the various web-applications to which the ontology may be put. This includes:
· Developing a Representational State Transfer (REST) webservice to output COPR-compliant RDF in alternative output formats, e.g. Keyhole Markup Language (KML), GeoJSON
· Developing a suite of three web visualization tools: a map view, a table view, and an ‘ordered’ view (for chronological or narrative timelines)
· Incorporating further feedback from each partners’ user groups in order to permit agile development of the ontology webresources
The Pelagios GANTT chart (01 February 2011 – 31 October 2011)
Most project meetings take place via skype:
· A monthly meeting comprising of the PI, Co-I and one representative from each of the partners is established for checking progress, identifying and resolving common issues, planning for the forthcoming month’s activities, ensuring aims are met, and disseminating the project outcomes.
· In the run-up to the workshop, a smaller group comprising of the PI, Co-I one representative from the development partners meet to discuss the ontology development.
· The PI and Co-I meet once a month with their JISC PM, David Flanders, to ensure that the project is on target.
The project uses a google group email for more regular, bi-weekly communication:
· This email group keeps partners informed of deadlines and to-dos.
· It also hosts discussion of work flows, issues and methodologies. All communication is archived for the benefit of the broader community.
In addition, the PI and Co-I will make one visit to each partner during the ontology application process. Rapid-iteration Agile methods will be used for software development.