- RDS/WIP Introduction
- Models, Data & Meta-Data
- Paths to Interoperability
- Automated Mapping
- Thought and Language
- Coarse to Fine
- Fine to Coarse
- Template Methodologies
- Choice of System
- RDS/WIP Sample Queries
- RDS/WIP Staging Diagrams
- RDS/WIP 1.0 Plan
- RDS/WIP 1.0 Testing
- RDS/WIP 1.0 Process
- RDS/WIP 1.0 Inventory
- RDS/WIP 2.0 Plan
- RDS/WIP ID Generator
- RDS/WIP Domain Proposal
- RDS/WIP Requirements Table
- RDS/WIP Use Case: Discrete Editing
- RDS/WIP Use Case: CSV Upload
- RDS/WIP 1.0 General Use Cases
- RDS/WIP 2.0 General Use Cases
- RDS/WIP ISO 15926 Template Definitions
- RDS/WIP OWL/RDF Definition
- RDS/WIP OWL/RDF Project Plan
- RDS/WIP Forums
- RDS/WIP Use Case: Bulk Upload
- ISO 15926 Primer
- ISO15926 Standard Structure
- IDS-ADI Coordination Structure
- IDS-ADI Infrastructure
- The AVALON Project
- Core Modelers Projects
- Core Implementers Projects
- Core Compliance Project
- Core Methodology Project
- IDS-ADI Matrix Master (login)
- IDS-ADI Matrix 1,2,3 activity
- IDS-ADI Matrix 4 activity
- IDS-ADI Matrix 8 activity
- IDS-ADI Part3 Harmonization
- IDS-ADI BIDG (aka Handover Guide)
- IDS-ADI Proteus Project
Project planning, resourcing and scheduling information for the RDS/WIP.
The RDS/WIP 2.0 is a plan to fold the functionality of the three databases in the RDS/WIP 1.0 (detailed below) into a single triplestore. The idea behind this is to eliminate redundancy and complexity, primarily to rein in the costs of development, deployment and maintenance.
The RDS/WIP 2.0 is an unratified plan at this stage - it exists as a concept without any official resourcing or agreement.
Some specific requirements for the 2.0 release:
- Bulk Upload Feature - The redesigned RDS/WIP will incorporate a bulk upload feature. The requirements of this feature are discussed at http://15926.org/home/tiki-index.php?page=ImportingRDLQuantity
There is a table covering the unimplemented requirements for both the RDS/WIP 1.0 and 2.0 on the RdsWipRequirementsTable page.
The RdsWipTwoPlan page covers initial thoughts about the goals, general design and resourcing of the new service.
The current RDS/WIP is available via a number of different access methods.
- The thin-client launch page is here
- SPARQL endpoints are listed here
Please note that the SPARQL endpoints and their contents are purely experimental.
While this RDS/WIP is currently available, it is not "fully deployed" in that the endpoints do not yet match the allocated endpoints and there are some deployment modifications required to get reasonable performance from the triplestore.
There is no bulk or automated upload feature planned for RDS/WIP 1.0.
The RDS/WIP 1.0 is a complex deployment consisting of three separate databases:
- Brutus - the RDS implemented as an EXPRESS database.
- Tarcus - a relational representation of classes and templates from Brutus in SQL Server, with a .NET based thin-client front-end.
- An un-named triplestore that represents the Tarcus as OWL/RDF using PHP, PECL, ADODB and RAP componentry over a SQL Server database.
Tarcus is accessible via a thin client, whereas the triplestore is accessible via the SPARQL service endpoints.
The RdsWipOnePlan page covers some discussion about additional short term measures to bring the 1.0 service to the level where it meets our external obligations.
Julian Bourne is currently acting as the project lead for the RDS/WIP.