To do
- There are some nodes in %NODE_DETAILS% that do not have longitude or latitude parameters.
- www.ucu.edu.ar, sunysb.edu, buitms.seecs.edu.pk, www.nren.nasa.gov, rzserv2.gsi.de, gluino.phys.unm.edu, and ouhep1.nhn.ou.edu
- Find a way to set up prefixes programmatically.
- Verify security of Sesame Server. Do I need to set up User/Password?
Aggregation
- Resolve in the Ontology the aggregated data for countries, continents, and groups.
- Store the aggregated data generated by Pingtable(by country, continent, or group).
- Think about storing or not aggregated data generated by the project.
About Schools
- Search about Lucene+Sparql to increase and enhance the results for querying over School Names.
- Edit the ontology to include data about Schools.
- Store school data into the RDF storage.
- Search data sets about schools other than DBPedia.
Doing
- Working on storing PingER measurement data into the RDF storage. (June 21)
- Testing Open RDF Sesame as a triple storage.
Done
- Geographic data about a sample of PingER monitored and monitoring nodes (the %NODE_DETAILS) is already inserted in the RDF storage (hence using our ontology) and is query-able using our own Sparql Endpoint. (June 20)
Could do
- Create a package under the package 'general' to write the ontology. Create constant classes for each prefix. Then, when programming, instead of writing strings for each statement, you would refer to the constants created. For example, create a class called GNONT with a constant called NAME. Then, when programming you would use GNONT.NAME.
- The method pinger.rest.HttpGetter.getJsonGeonames can be optimized. There is a test that verifies if the geonames username has been overused hence blocked. If it is, try another username. There could be a priority scheduling policy; a Map with priorities could be used to implement. The username that was able to be used would receive higher priority than blocked usernames.