Reference Data Services

1. Reference Data Services Status and plans for the RDS and the RDL Tore Christiansen, Information Quality Management Høvik, November 28, 2006

2. Project results The RDS project has delivered: • The Reference Data System (RDS) including - • A Browser version (for exploring and studying the RDL) • An Editor version (for extending and maintaining the RDL) • A Database that represents all of ISO 15926-2 • A set of Import/Export facilities (CSV, P28 XML, P21 Express) • An updated Reference Data Library (RDL) with - • Standard (ISO 15926-4) term and definitions used in oil, gas & process industry • Represented as reference classes and relations • Covering the complete POSC/Caesar RDL • Active participation in standardization efforts - • ISO 15926 POSC/Caesar wrt. ISO and W3C • ISO 10303-239 PLCS wrt. ISO and OASIS Version

3. RDL status The RDL available in the RDS consists of - • Almost all relevant POSC/Caesar RDL classes have been migratedfrom snapshot E (Julius database) to ISO 15926-2 model (in the RDS) • Proposed ISO 15926-4 Core Set (to be approved): 10.000 classes • Major parts of the 35.000 classes defined by POSC/Caesar projects • ISO 15926-4 issue resolution ongoing • All relevant ISO 10303-239 PLCS classes are ready for import • Including update of specialization hierarchy and classification wrt. DEX’es • Requires mapping/updating of meta-data (from Dublin Core to ISO 11179) Version

4. The RDS can be used for global information exchange http://rds.posccaesar.com Version

5. Search for classes Classes matching search criteria Directory of classes Class meta-data ”Subclass relationships” ”Superclass relationships” Editor for adding and modifying classes and relationships Format for exporting and importing classes and relationships RDS functionality Version

6. RDS user documentation Concepts Components How to guides Version

7. RDS system documentation Data models Web services Express queries Installation and back-up procedures in progress Version

8. Presentation Application RDSServer RDS architecture overview WS Server Version

9. Remaining RDS development item • The project has not (yet) received functionality for long transactions and stop points • Disables rolling back unwanted additions and erroneous work • Required for editing production data • Dependent on new version of the EDM Server • Forfeit this functionality in exchange for additional server licenses • Allows new and more flexible operational regime • Same total cost to the project • With option for changing back to the original deliveryonce the missing functionality is in place • Or adding it to the current delivery at substantially reduced price Version

10. RDS implementation The operational set-up will consist of – • One Production RDS Server for browsing (only) by any number of anonymous users hosted on DMZ 107 (http://193.212.132.107/apps/rdsclient.html) • One Staging RDS Server for merging input (5 named users with login/password and editor privileges)hosted on DMZ 108 (http://193.212.132.108/apps/rdsclient.html) • Up to 10 standalone RDS Applications for creating new RDL Classes & Relationships as input to the Staging Serverhosted on end-user machines • As we gain more experience, this scheme may be modified or replaced by creating new information directly on the Staging Server • As we gain more usage, this set-up may be augmented and extendedby adding additional servers for new industry sectors Version

11. RDS/RDL access and information resources http://rds.posccaesar.com/info Version

12. Information Query Question Solution Semantic web reference data services Reference data RDS Internet WS WS Extranet Intranet Rep App People and applications Version

13. Related work to integrate the RDS • Web Services server 4 RDS • Multi-RDL Web Service client demo • RDL Meta-data Web Service client demo • RDL Meta-data 4 XML-documents demo • RDS API for import/export to tabular format • RDS 2 OWL translation (and OWL 2 RDS) • ISO 15926-4 OWL representations (Lite, DL and Full) • Document storage and linking from RDS • Using Reference Data to address the needs of the ADI and IDS projects IDS project financing DNV internal financing Financing to be decided Version

14. Web Service Demo client for Reference Data definitions Version

15. Annotation of standard terms in Data Sheets Version

16. Continued semantic development • Import and export product information in OWL and other XML files • Generate end-user reports using XSLT, and data sheets using XSchema • Perform reasoning on information models using SWRL and reasoners • Define interface to databases holding real-time data instances • Query and inspect instance data using SPARQL and reasoners • Add RDL classes from ISO 10303-239 PLCS • Develop web services interface to other data sources (e.g., PLCS RDS server) • Connect information content (text, figures and pictures) to RDL classes • Integrate smarter search algorithms to find relevant content about RDL classes Version

17. Create (create and store) Reference Data Transform (import and export) Reference Data Improve (correct and extend) Reference Data Reference Data Management System (RDMS) Version

18. Plans for additional development • Annotation of standard terms in Data Sheets • Annotation of company-specific terms in Data Sheets • W3C Oil and Gas Interest Group (ideas from Eric Miller, W3C) • DND Semantic Interest Group (visit from Ivan Herman, W3C) • Improve the quality of the ontology (OBO and Barry Smith) • Proposal for developing a collaborative semantic application scenario • Structuring and storage of Project Data and Documentation • Logging and reporting of users and usage • Development of business models for Reference Data Services • Management of reference data for specific purposes and projects Version

19. Version