Overview of this How To Guide
Status of this document: Working Draft
This document is open for feedback, please post questions and comments in the forum at the bottom of this page. You will need a login to post in the forum.
- Entry Points
- Case Studies
- Principles of Interoperability
- Building a Business Case
- Using Publicly Available Tools
This section is an outline of all the sections in this How To Guide. Click on a heading below to jump directly to that section.
ISO 15926 itself has been around since the early 1990s. Its predecessor standards and organizations were around many years before that. A great deal has already been written. To help you with your research, this section lists the more important repositories.
In its most basic form, ISO 15926 has already been used many times, while in its complete form it is still in development and pilot testing. This section describes a number of these instances showing:
- Background of the project.
- Different usage scenarios based on different maturity starting points.
- The original justification of ISO 15926
- What ISO 15926 accomplished.
Before you can understand how to implement ISO 15926, you must understand a few principles. For instance, the typical computer programmer approach to interoperability is to learn as much as possible from each system that is a member of the exchange, in order to get the code as tight as possible, and to exploit any available idiosyncrasies. But this is exactly opposite to the approach of ISO 15926. The more you know about partner systems, the more inflexible your information exchange is. Instead, you need to devise an information exchange system that does not require any knowledge at all of any of the partners to the exchange.
This section will give you some ideas on how to look for the value of ISO 15926.
In a nutshell, you first start by closely examining the interconnecting network of software at your organization. Get to know all of the information that has to move, and what each data value represents.
Second, choose a data flow to make ISO 15926-complient. Perhaps there is already a data flow; perhaps not.
Third, use the publicly-available tools to map your terms to the ISO 15926 classes.
This section describes the publicly-available
- Using the RDS/WIP (RDL Façade)
- TC184 Classes
- POSC/CAESER RDS
- Compliance Doc
- Mapping Methodology
File and XML exchange technologies and other API's as well as iRING / OWL / SparQL Are you a developer or a user - you will have quite different needs here ?
- Dictionary Mapping
- Practice Files
- Creating a Mapping Spreadsheet
- Mapping to ISO 15926-4 using the RDS/WIP
- Dealing with all the class choices in the RDS/WIP
- Resolving Differences with Business Partners
- Using Templates