Getting Started with ISO 15926

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.

---

Contents

1. Abstract
2. ISO 15926 Roadmap
3. Get Familiar with ISO 15926
4. Build a Business Case
5. Identify a Scope
6. Identify the Roles
7. Training
8. Gather Application Information
9. RDS/WIP
10. See What Existing Models Are Available
11. Set up a Sandbox to Test
12. Map Internal Applications to ISO 15926
13. Use the Ontology Browser

Abstract

[Enter abstract]

---

The purpose of this section is to give you a roadmap for implementing ISO 15926 at your organization. Of necesity, the roadmap will not be a single direct route to a single end-point, like a route map from your travel agent showing the shortest route from your house to the beach where you plan to take your next vacation.

Figure 1 - Shortest Route to the Beach

Instead, this section is more like a roadmap of the country you live in showing many roads, many beachers, and in fact many good vacation spots on the wat to the beach in case you don't want to go all the way the first year. This means that you can start with limited goals, or a demonstration project, to, say, map two interacting applications together useing ISO 15926 part 4 (15926-4). Later on you can work up to a full 15926-7 façade.

Figure 2 - A More Interesting Route to the Beach

A direct route gets you there faster, but sometimes the longer route is more interesting.

ISO 15926 Roadmap

Figure 3 - ISO 15926 Roadmap

...

...

...

Get Familiar with ISO 15926

Read the Primer!

(Well, actually, you're already reading it. But in case you linked directly to this page, start at the beginning. Poke the "Primer" link in the big green box.)

It is important to understand that ISO 15926 is a fundamenatally different approach to making machines be able to talk to each other and convey meaning. In the past we've viewed machine-to-machine communication as a technology problem, building more powerful processers, or writing more artful code. But we ran into the wall of not knowing how to handle the information. ISO 15926 sidesteps the powerful chips and Machiavellian code and focuses on modeling information.

Build a Business Case

...

...

Identify a Scope

...

Links to old examples ...

Identify the Roles

• Business Person (a.k.a. Subject Matter Expert)
• Information Modler
• Application Configuration
• Project Manager

Training

Information Modeler

• ISO 15926 methodology for information modeling

Applications Configurator

• Set up web services
• Storage for triplestores
• Configuraing I-Ring components

Subject Matter Expert

• Overview training

Gather Application Information

Dig into each application

Document the schema - catalogue what's there.

• Do this for the information that has to move, not necessarily everything

Cover any special requiresments. For instance, uncover any relationships that have to be maintained. Understand them all.

RDS/WIP

Understand the purpose of RDS/WIP.

Look at the classes that are there

Look at the types and subtypes

To know how deep to model, match the legacy ststem. For instance, to move an instrument list you may only need the class of instruments, not every subtype. It depends on how the legacy system at each end holds them. But the legacy system at each end may not be at the same level. While one application may only use the base class, the other may you subclasses.

Most of the steps will be the same as they would have been without ISO 15926, you will just be modeling the information to ISO 15926 standards.

See What Existing Models Are Available

...

...

Set up a Sandbox to Test

...

...

Map Internal Applications to ISO 15926

...

...

Use the Ontology Browser

Use the ontologoy Browser to examine content to see if the mapping is correct.

...

...

---

Discussion

You have no rights to see this discussion.