RDS Information Page
This information page will present information about the status on the Reference Data Systems that will be useful for users and interested parties, and includes current and planned changes to the systems.
No new messages. Systems are running as expected.
We are currently working on:
defaultRdsId & RDS-WIP
Recover as many of the RDS-WIP mappings as possible Review recovery process Create defaultRdsIds based on RDS-WIP and RDS numbers according to the JORD ID spec The focus for January will be on step 1. The process is to look through previous OWL exports from Brutus (the old Reference Data Service) to find out what the RDS-WIP mapping file was actually pointing too and then tracing this up through the exports searching by id or by designation. A computer program has been created to automate this process. The result will be a matrix showing the trace through the files.
More backup files have been retrieved. The software will be updated to run on more of these files.
The focus for this effort is on reference data classes (things with designations).
Update 12th of March 2014.
Recovery process is done. Result of the automated process can be found here.
The following have been analysed by hand (here).
And a list of the RDL items that now have multiple RDS WIP IDs after the recovery process (here).
Work has concluded and finished results are available on: http://data.posccaesar.org/rdl
Below is a list of planned changes for the existing content and systems:
As per the JORD ID Spec, all URI's will be human-readable where possible. These changes will only be reflected in the new namespaces. owl:sameAs or owl:Equivalent properties will be used to link back to the previous version.
The new namespaces http://data.posccaesar.org/..../ are planned implemented.
New namespaces has been implemented for data.posccaesar.org/rdl/
New Hosting Provider
We are planning on setting up the endpoints through a new hosting provider (Amazon). This change will be based on the current infrastructure and components, and some improvements to the setup.
Running on new servers with the main server in Amsterdam and the backup server in New York.
Proposed changes (additions and improvements) of content need to be verified. An automated solution that handles RDF data and uses SPARQL to generate a verification report will be made available.