Version 2 (modified by margs, 15 years ago)


SandBox no. 4

This is just a test. This text is collected from ISO15926Primer_Glossary for testing purposes.


There are a great many glossaries available, as well as on-line dictionaries and, of course, Wikipedia. A particularly detailed Glossary is right here: STEPDEX: Glossary of Data Management Terms

Another glossary is on the USPI website, Look for Glossary_jun99.doc.

The following is terms that are particularly interesting to ISO 15926 enquirerers. They are not in alphabetical order, but are in groups.

RDF (Resource Description Framework)

If you dig deeper under the hood of ISO 15926 you will soon run into this term because it is the means of storing the Part 4 definitions.

Wikipedia says that Resource Description Framework is a set of specifications originally designed as a metadata data model. (But if you are like the author, this doesn't help at all, so we will deconstruct the definition.)


  • Metatdata is data about data. For instance, one piece of metadata about the ISO 15926 Primer is that it was written on the POSC/Caesar's wiki website.

Data Model

  • A data model is an abstract model that describes how data is represented and accessed.


  • Abstraction is a process of generalizing about something to reduce the information content about an object to only those attributes you are interested in. A typical abstraction is the answer "7600 Glover Road" to the question "Where do you live?" You might live in a beautiful split level house with a wonderful view of the ocean framed by huge 100 year old pine trees but your questioner only wants to know where to have a package delivered. (On the other hand, yours could be a very ordinary house on a very ordinary road, but the city just wants your land for a freeway bypass and the friendly bulldozer operator needs to know where you live.)


Putting it all together, then, RDF is:

  • instructions on how to represent
  • just the bits of data you are interested in
  • that describes certain other bits of data
  • then access it easily

(Whew! I bet you thought that was going to be difficult!)

In particular, RDF makes statements about things, which it calls Resources, in the form of Subject-Predicate-Object expressions known as Triple Stores.

Subject-Predicate-Object Triple Stores

"The ISO 15926 Primer was written on the POSC/Caesar wiki" might be stored in the RDF as the triple:

  • the subject: ISO 15926 Primer
  • the predicate: was written on
  • the object: POSC/Caesar wiki

The each term in the subject-predicate-object may be explicitly named, as in the example above, or they could be in the form of a URI, a Uniform Resource Identifier.

Uniform Resource Identifier

You can think of a Uniform Resource Identifier as a website for a piece of information. This allows the same resource to be reliably referenced many times. So instead of writing the Subject-Predicate-Object triple as above, it could be rendered as:

And in fact we could carry this further by defining somewhere on the Internet the exact meaning of the phrase was written on, and put its URI in the predicate.

More Information about RDF

A good place to start if you want to know more about RDF is the RDF Primer written by the W3C. Be warned, it is not for the feint of heart. But if you can wade through it you will start to see what we mean when we say that "Everything, in the end, is reference data."

RDL ( Resource Description Library)


RDS/WIP (Reference Data System / Working, In Progress)

The RDS/WIP is several things:

  • a library of reference data for ISO 15926
  • a means of publishing core ISO 15926 definitions
  • a platform for developing new ISO 15926 definitions
  • a workspace for harmonizing other standards with ISO 15926 (or each other)

Anyone can search the RDS/WIP and find terms, much like in a dictionary. Accredited users can add information to the RDS/WIP.


Pronounced "sparkle"

Conservation of Complexity

You cannot eliminate complexity. You can move it from one place to another, but it will always be there somewhere. This is used to talk about how we deal with complex Plant information. We can deal with it manually, piece-by-piece, as we have been, or we can encapsulate it with ISO 15926 and let machines deal with it.

This is related to the Law of Conservation of Energy, which says that you can neither create or destroy energy, all you can do is change it from one form to another.


Hiding complexity from users who really don't want to know any more.

AEX (Automating Equipment Information Exchange)

The Automating Equipment Information Exchange (AEX) project is developing, demonstrating and deploying eXtensible Markup Language (XML) specifications to automate information exchange for the design, procurement, delivery, operation and maintenance of engineered equipment.

AEX – The natural collaboration between AEX and IDS-ADI is via the Matrix/SIG’s teams.

About PCA
Reference Data Services