[[TracNav(TracNav/ISO15926Primer)]] = Other Resources for Learning About 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 ![WikiStart#Contactpoints need a login] to post in the forum. ---- [[PageOutline(2-4,Contents,inline)]] ---- == Abstract == As of this writing, summer 2009, there is no one place a prospective user can go to get a definitive curriculum to follow to learn all there is to know about ISO 15926. This is partly because it uses existing technology developed for the Semantic Web, and partly because it is still in its infancy. What follows here is a collection of resources that describe the individual pieces that together make up ISO 15926. ---- == RDS/WIP Browsers == The classes that make up Part 4, the dictionary of ISO 15926, are stored in what is called the RDS/WIP (Reference Data System/Work In Progress.) To search the classes you use an RDS/WIP browser. For more information about RDS/WIP: * http://rdswip.ids-adi.org/presentation/overview/index.html * https://www.posccaesar.org/wiki/RdsWipProject This second link contains links to a great deal of information on how the RDS/WIP is implemented. There are a number of browsers for the RDS/WIP: === rdlfaçade === The RDS/WIP Search, otherwise known as the "RDL Façade" was created during the early development of ISO 15926. * http://rdl.rdlfacade.org For instructions on how to use the browser: * [wiki:ISO15926Primer_OtherResources_RDLFacade Using the RDL Façade] === POSC Caesar Part 4 Browser === POSC Caesar has its own library of reference data presented in the form of spreadsheets: * http://rds.posccaesar.org/2008/05/XML/ISO-15926-4_2007/ POSC Caesar has developed a browser for ISO 15926-4 reference data: * http://193.212.132.108/apps/rdsclient.html (You will need a login to use this but can login as a guest.) Some instructions on using the POSC browser: * http://15926.org/home/tiki-index.php?page=Tutorial+ISO+15926+part+4 === DNV Reference Data Browser === Det Norske Veritas (DNV) has also created its own browser: * http://projects.dnv.com/reference_data/RD7Browser/browser.aspx?id=part4:RDS415124 ---- == Camelot Download Page == The Camelot project was a proof-of-concept demonstrated in mid 2009. It demonstrated several data flows that used the full ISO 15926 specification. Its deliverable was open source software called iRING 1.0. Since it is open source it is free for anyone to use without royalties. * http://iring.ids-adi.org/repository/org/ids-adi/camelot/index.html ---- == Business Interfaces Definition Guide (BIDG) == The BIDG is becoming the basis for determining the future developement of the classes that make up Part 4 and the templates that make up Part 7. It is worth reading to understand the direction the developement of ISO 15926 will take. It is issued in two parts: * Part 1 is currently known as [http://fire.nist.gov/bfrlpubs/build05/art037.html Capital Facilities Information Handover Guide Part 1]. It was reissued in 2006 by FIATECH and NIST. * Part 2 is divided again into two editions; one for general buildings, and one for process plants: * [http://fire.nist.gov/bfrlpubs/build07/art015.html General Buildings Information Handover Guide] by NIST and others * Process Plant Information Handover Guide, by FIATECH, ccurrently under development. The Business Interfaces Definition Guide was formerly known as the ''Process'' ''Industries'' ''Data'' ''Handover'' ''Guide''. It was issued in two parts by EPISTLE in the late 1990's. * [http://www.btinternet.com/~Chris.Angus/epistle/specifications/handover/guide1.pdf Part 1] consistes of guidelines for establishing the requirements for the exchange of facilities information between engineering contractors and owner/operators. * [http://www.btinternet.com/~Chris.Angus/epistle/specifications/handover/guide2.pdf Part 2] consists of guidelines for the types and formats of handover information. ---- == ISO 15926 Development Documents == === ISO 15927-7 Template Specification === The diagrams on this page will give you a glimpse of the level of detail involved in developing ISO 15926 templates. * http://www.rdlfacade.org/files/iso15926-7/ts/0096.htm === Template Methodology === This page is the beginning of several pages on methodology for developing templates. * https://www.posccaesar.org/wiki/IdsAdiTemplateMethodology === Characterization Methodology === Any existing schema can be "characterized", or transformed into an ISO 15926 schema. The easiest way to do this is to use Templates. This page is the beginning of instructions on how to do this. * https://www.posccaesar.org/wiki/TemplateCharacterization Look for links to two documents: * ISO15926 Methodology Specification for Dataset Template Characterization. (Word document.) * ISO15926 Workbook for Public Template Definitions and their Business Selection Logic. (Excel Spreadsheet.) === Compliance Guide === ISO 15926 does not have to be implemented all at once. There are several axes of compliance and several steps on each axis. The Compliance Guide is both a sort of road map to full implementation, and a rough measuer of the level of compliance of an ISO 15926 implementation. The following page discusses Compliance and has a link to the Compliance Specification: * https://www.posccaesar.org/wiki/IdsAdiComplianceSpecification Look for this link: '''current working version of The Compliance Specification ''' == Information Modeling Resources == Information modeling is the core of ISO 15926. Most people won't have to know anything about it, but a "lucky few" will get to go all the way down the rabbit hole. For instance, elsewhere in this Primer we have used the metaphor of heavier than air flight. Most of us use flight by phoning our travel agent to book a trip. But a few people (they probably also describe themselves as the "lucky few") actually know areonautical engineering and know ''why'' airplanes fly. The barriers to digital interoperability are no longer hardware and technology, but rather information modeling. To truly develop ubiquitous digital interoperabiltity, we will need robust information models that describe plant objects and the relationships between them, from their inception, through operation, to demobilization. This provides a distinct growth opportunity for plant engineers who understand that ''information'' about plant objects is as valuable as the objects themselves. When we have a large knowledge base, classified accurately, we will be able to exchange worthwhile information without human involvement in each transfer. If you would like to become one of the "lucky few", here are some publications to get you started. The bad news is that the notation and terminology of information modeling can be daunting to newcomers. The author's suggestion is "Keep Reading!" Eventually it will start to make sense. === The Archives of Dr. Matthew West === Dr. West has a long history with Shell's Information Management department, and as a developer of parts of ISO 15926. He has posted many of his publications on his website: * http://www.matthew-west.org.uk/publications.html There is a wealth of information here for those introducing themselves to information modeling. I'd start part way down the list and work up. * Replaceable Parts: A Four Dimensional Analysis (2003) * Developing Shell’s Downstream Data Model based on ISO 15926 (2006) * An Introduction to 4 Dimensionalism in Data Modelling (2007) * Developing Shell’s Downstream Data Model based on ISO 15926 (2007) * Levels of reality in ISO 15926 and Shell's Downstream Data Model (2007) * Roles: A Four-Dimensional Analysis (2008) * Ontology Meets Business (2009) * 4 Dimensional Data Modelling: An Ontological Approach (2009) === Modeling Guide #1 === ... === Modeling Guide #2 === ... ---- == Infrastructure Technology == === XML === ... === RDF === Resource Description Framework is a way of storing information about information (that is, metadata) in what are called triplestores. The ISO 15926 is a large triplestore. * http://www.w3.org/TR/REC-rdf-syntax/ * http://www.w3.org/RDF/ === OWL === Web Ontology Language is a language for creating ontologies. ISO 15926 uses OWL to represent information. * http://www.w3.org/2004/OWL/ A W3C introduction which contains links to a language guide * http://www.w3.org/TR/owl-features/ W3C Overview === SPARQL === SPARQL, pronounced "sparkle", is a query language designed to be used with RDF triple stores. The ISO 15926 RDS/WIP uses SPARQL. * http://jena.sourceforge.net/ARQ/Tutorial/ A short Tutorial. * http://www.w3.org/2001/sw/DataAccess/ This contains some interesting links. === Gellish === Gellish (originally derived from General Engineering Language) is a language in which information can be expressed in a manner that is computer readable. It is used to make the ISO 15926-7 templates. References Wikipedia http://sourceforge.net/project/showfiles.php?group_id=28353 Gellish - A Product Modeling Language == Next == * [wiki:ISO15926Primer_OtherResources_RDLFacade Using the RDL Façade] ---- [[ViewTopic(ISO15926Primer_OtherResources)]]