IDS-ADI Infrastructure Status

The breadth and depth of ISO 15926 makes for considerable infrastructure requirements, ranging from special interest groups around engineering disciplines, to training provision and software services running on the Internet.

This page itemizes these deliverables as undertaken by IDS-ADI and provides each with a status report, responsible party and in some cases links to other on-line information.

SIGs

TBD

Training

TBD

Introductory Collateral

Status: some business and engineering collateral available

Next Release: no date set

Engineering Lead: none chosen

Business Lead: Jeff Bonnell

Technical Lead: Julian Bourne

Overview

Business, technical and engineering users all require focused introductory collateral. Some of this collateral exists but is not necessarily easy to find or collected all in one place. Some of this collateral is at a far too detailed or abstracted level to be generally useful to someone first coming into contact with the standard.

Report

There is substantial engineering collateral available in different forms, from power point presentations to web sites. This material addresses the underlying need for ISO 15926 as a neutral model and definitional space (reference data library); and it also addresses how to go about (methodology). What may be missing is a guide for the kind of engineer who deals in concrete things, not in abstract concepts; and secondly for the kind of engineer who has the right sort of outlook to bridge the gap between the concrete and the less totally abstract, but is not interested in the completely abstract.

Some of the high level engineering collateral targeted at explaining the need for ISO 15926 can be repurposed for business; and there is some existing collateral under the FIATECH ADI project site addressing business and technical at a (very) high level. Jeff Bonnell has volunteered to lead the initiative in providing a more complete business view of the standard.

Technical introductory collateral targeted at implementation is thoroughly scant at this stage: there is a need to provide almost a "path" or "plan" to integrated ISO 15926 into vendor tools in a meaningful way. Julian Bourne has volunteered to lead that initiative.

RDS/WIP

Status: somewhat operational

Next Release: manually operational, end of June 2008

Following Release: fully operational, no date set

Lead: Julian Bourne

Overview

The RDS/WIP project provides the software and Internet-accessible services for publishing both the standard and contributions to its associated reference data library. There are two exposed forms of this data: one is intended for machines, expressed in OWL/RDF and delivered via SPARQL; the other is intended for humans and is presented using HTML in a web browser.

Report

The existing deployment is only partially operational: it does not reach the necessary mark in aspects such as performance and standards conformance and is missing machine-driven mechanisms for submitting new contributions. Also, its internal structure is far too rigid and requires a great deal of coordination between different parties to effect change.

The next stage (RDS/WIP 1.0) will be to move that solution to a more robust and faster technical framework, dropping the support for direct editing in the interim, but adding much more flexible support for incorporating bulk contributions, with some administrator intervention.

The following stage (RDS/WIP 2.0) will be to provide a completely automated path to incorporate bulk contributions and the administration features needed to manage that; along with recreating a direct editing feature for ISO 15926 data only.

The main advantage of the revised platform, apart from performance and conformance, is that it will allow any RDF to be published, which leaves a great deal of flexibility in structure and representation - allowing the structures and representation to change quickly and without much need for coordination. It also provides a lower barrier to entry when starting a collaborative project to harmonize standards against one another. These features are inherent in the architecture and to the technology choices and will be available from the outset of RDS WIP 1.0.