Version 13 (modified by gordonrachar, 14 years ago) |
---|
TracNav menu
- Back to Avalon Collaboration Page
-
Introduction
- Overview
- Entry Points to Learning About ISO 15926
- Case Studies
- Principles of Interoperability
- Building a Business Case
-
Using ISO 15926 Tools
- Discovering the Right Class
- TC 184 SC 4 WG 3
- Using the RDS/WIP (RDL Façade)
- POSC/CAESER RDS
-
Tutorials
- Mapping to ISO 15926-4
- Using Templates
- Diagnostic Page
Introduction to Implementing 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
- Entry Points
- Case Studies
- Principles of Interoperability
- How to Use ISO15926 Tasks, Procedures, and Resources
- Technologies
- Tools (for different tasks)
- Software Applications (appropriate to the scenario)
- How to Build a Business Case
- Next
Entry Points
- Introductory Slide Set
- Primer / knowledge of ISO15926 itself
- Existing RDL-WIP content / sources.
- The iRING Reference Data Architecture
- Etc ...
- Other References and Resources
- A comprehensive list of entry points and learning material
Case Studies
Descriptions of projects where ISO 15926 was implemented.
Principles of Interoperability
Before you can understand how to implement ISO 15926, you must understand a few principles. For instance, the typical computer programmer approach to interoperabitlity 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, exploiting any available idiosyncracies. 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.
How to Use ISO15926 Tasks, Procedures, and Resources
Common - independent of scenario Specific to each scenario
Content
Your business content Your business process use of that content (relevant to the scenario) Prioritizing different kinds of content (doesn't make any sense to try to represent all of it in 15926)
Mapping your content to 15926 content
(According to priorities and the compliance level appropriate to your business situation and the particular scenario) (Modelling & Templates etc only by reference as necessary - these are really under the hood - wrong to attempt to describe these in this document)
Technologies
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 ?
Tools (for different tasks)
.
.
Software Applications (appropriate to the scenario)
.
.
How to Build a Business Case
Different usage scenarios, different maturity starting points. What 15926 does for you in those cases, how is 15926 use justified. (References only to background existing principles, history, model standard development projects ...) (The different scenarios are most important, because what you need to do, and what you should expect to achieve are quite different.)
Next
Attachments
- IDS-ADI-Resources-Introduction.ppt (2.0 MB) - added by gordonrachar 14 years ago.
-
HistoryISO15926.JPG
(71.9 kB) - added by gordonrachar
13 years ago.
History of ISO 15926