RESQML Editor/Validator Tool. User guide

Transcription

1 RESQML Editor/Validator Tool User Guide For RESQML v2.0.1 RESQML Overview The RESQML standard facilitates data exchange among the many software applications used along the E&P subsurface workflow, which helps promote interoperability and data integrity among these applications and improve workflow efficiency and flexibility. Tool Version v1.0 Abstract The RESQML Editor/Validator software tool was created so that people can explore, edit and validate RESQML data objects and EPC files the container file used to gather related RESQML data objects for exchange among software packages. There is also a Command Line Validator, which may be integrated with RESQML-enabled software, for example, to run automatically when RESQML data is imported. This guide explains how to download, install, and use these tools and provides reference material on various functions. Prepared by Geosiris and Energistics Date published 28 June 2017 Document type Keywords: User guide standards, energy, data, information, process, reservoir model, shared earth model, validator tool

2 Document Information DOCUMENT VERSION 1.0 Date 28 June 2017 Language U.S. English Usage, Intellectual Property Rights, and Copyright This document was developed using the Energistics Standards Procedures. These procedures help implement Energistics requirements for consensus building and openness. Questions concerning the meaning of the contents of this document or comments about the standards procedures may be sent to Energistics at The material described in this document was developed by and is the intellectual property of Energistics. Energistics develops material for open, public use so that the material is accessible and can be of maximum value to everyone. Use of the material in this document is governed by the Energistics Intellectual Property Policy document and the Product Licensing Agreement, both of which can be found on the Energistics website, All Energistics published materials are freely available for public comment and use. Anyone may copy and share the materials but must always acknowledge Energistics as the source. No one may restrict use or dissemination of Energistics materials in any way. Trademarks Energistics, WITSML, PRODML, RESQML, Upstream Standards. Bottom Line Results., The Energy Standards Resource Centre and their logos are trademarks or registered trademarks of Energistics in the United States. Access, receipt, and/or use of these documents and all Energistics materials are generally available to the public and are specifically governed by the Energistics Product Licensing Agreement ( Other company, product, or service names may be trademarks or service marks of others. Tool: v1.0/doc: v June 2017 Page 2 of 43

3 Tool Version Doc Version Amendment History Date Comment By June 2017 First release of the tools and user guide. Geosiris and Energistics Tool: v1.0/doc: v June 2017 Page 3 of 43

4 Table of Contents 1 Introduction Audience, Purpose, and Scope Why do We Need a Validator Tool? Benefits of the Editor/Validator Tool Background: Overview of RESQML and How it Works What is RESQML? Some Key Technologies and Their Purpose How the Editor/Validator Works Technology Basic Process: What the Editor/Validator Does (and cannot do) Resource Set Installing and Running the Editor/Validator Download and Install the Tool Overview of the Main Interactive Tool Window Synchronizing Views Validate an EPC File Examine and Update Your Files Basic Example Advanced Creation Functions References: Views Table View Graph View Resource Set and Resource Set List Views Properties View Log View References: Menus and Commands File Menu File->New File->Open EPC File->Save Epc File->Open a Resqml Resource File->Open File File -> Close Resqml resource File->Close All Resources File-> Save a Resqml Resource File-> Save a RESQML Resource as File-> Save All Resources File-> Exit Edit Menu Navigate Menu Show View Menu Validate Menu Validate -> Validate Syntactic Consistency Validate -> Validate EPC Relationships Validate -> Create Validation Sequence of Business Rules Validate -> Validate EPC with Business Rules Business Rules Overview of the Approach Tool: v1.0/doc: v June 2017 Page 4 of 43

5 5.2 Types of RESQML Business Rules and How they Work Business Rules Descriptions and Explanations Category A: BRT1.xml: Semantic constraints validation of relationships between top-level objects Category A: BRT2: Semantic constraints validation of relationships between top level objects including Enum value checking Category A: BRT3: Semantic consistency of attributes between top level objects that are linked by data object reference relationships Category B: BRT4: Numeric constraints validation between attributes belonging to the same top level object (validation on XML content only) Category B: BRT5: Numeric constraints validation between attributes belonging to different top Level objects (validation on XML content only) Category C: BRT7: The dimensions of the HDF5 array of a property must correspond to the Ni, Nj, Nk dimensions declared in the supporting IJK grid representation Command Line Validator Download and Install the Tool How to Launch the Command Line Validator Tool How to Compose the Validation File used by the Command Line Tool Example Validation File Tool: v1.0/doc: v June 2017 Page 5 of 43

6 1 Introduction RESQML is Energistics data-exchange standard for data used in earth and reservoir modeling workflows, which are complex and varied. RESQML was designed by the industry to be comprehensive and flexible so that it can handle the inherent complexity and variety of these workflows and related data. As a result, RESQML data sets can be large and complex. The RESQML Editor/Validator software tool (Editor/Validator) was designed to help information technology (IT) and geology, geoscience and engineering (GG&E) professionals quickly and easily explore, validate and edit RESQML data sets before importing them into their RESQML-enabled GG&E software applications. NOTE: The Editor/Validator is designed to check consistency of objects to the RESQML schemas/model. It is NOT designed to validate the characteristic functions of geo-modeling software. For example, its objective is not to validate geometrical consistency between two entities (such as, checking whether one is located in a higher geometric position than the other). This guide explains how to download, install and use the Editor/Validator for RESQML v2.0.1 files. Command Line Validator. There is also a Command Line Validator (CL Validator), which developers can implement in RESQML-enabled software, for example, to run automatically when RESQML data is imported. For information about download and installation of the CL Validator, see Chapter 6. Sections 1.2 (background on RESQML) and 1.5 (how validation works) also pertain to the CL Validator, as does Chapter 5, Business Rules. 1.1 Audience, Purpose, and Scope This user guide: Is intended for IT and GG&E professionals who work or support the development of earth and reservoir models and exchange data between RESQML-enabled software applications used in that process. Explains the benefits of and how to use the RESQML Editor/Validator software tool (Editor/Validator), which supports v2.0.1 of RESQML. Assumes the audience is familiar with RESQML v2.0.1 and its basic purpose and function. However, for context, a high-level overview of RESQML is provided Documentation Conventions Though no special text formatting used, all chapter and section numbers are hyperlinks. The table of content is also hyperlinked. 1.2 Why do We Need a Validator Tool? RESQML is a set of 80+ data objects specified as XML schemas (XSD files), which define the many data objects used in subsurface workflows. To specify the relationships between these objects, RESQML uses a mechanism specially designed by Energistics called a data object reference (DOR). In many cases, RESQML also specifies related business rules, which are required to define specific conditions that must be met to further ensure valid relationships and correct models. In the case of a simple XSD design, developers can use traditional tools (such as XML spy or GSoap) to explore their models and validate their content types versus XSD schemas. However, these tools do not work with the DOR and RESQML business rules, so a new tool had to be developed: this new tool is this RESQML Editor/Validator and the Command Line Validator. For more details about the RESQML design and how the Editor/Validator works, see Sections 1.4 and 1.5. Tool: v1.0/doc: v June 2017 Page 6 of 43

7 1.3 Benefits of the Editor/Validator Tool The RESQML v2.0.1 Editor/Validator tool: Provides a way for you to quickly and easily validate RESQML data contained in an Energistics Packaging Conventions (EPC) file, thereby ensuring its integrity before you begin using the data in a software application/technical workflow. Ensures the integrity and validity of the: Top-level RESQML data objects contained in an EPC file. - Relationships between these RESQML data objects. Provides an automated way to validate RESQML business rules. Delivers interactive exploration and editing capabilities that let you work with your RESQML data (XML and HDF5) to resolve issues or (for advanced users) to create files for examples and testing. 1.4 Background: Overview of RESQML and How it Works This section is a high-level overview of RESQML to provide context for why the Editor/Validator is needed and how it works What is RESQML? RESQML is an XML- and HDF5-based data-exchange standard that facilitates reliable, automated exchange of data among software packages used in subsurface workflows. RESQML consists of a set of XML schemas (XSD files) and other standards-based technology, which developers implement into software packages. RESQML-enabled software can read and write the standard format, essentially allowing these applications to exchange (or transfer or import/export) data from one software application to another Some Key Technologies and Their Purpose UML and XML RESQML was first created as a consistent UML data model, developed using Enterprise Architect as the data modeling tool. The RESQML UML model is composed of objects and the relationships between them, such as inheritance, containment, and reference. From the UML model, an automated process generates XSD files (XML schemas), which software developers use to produce software classes to read/write RESQML data objects in their software applications. With this approach (UML model to generate schemas), we see that though RESQML is first and foremost a data-exchange standard, it also has an underlying data model. This data model provides benefits over other data-exchange standards that simply define objects for example, it is a comprehensive visual model showing objects and their context, which allows IT professionals and GG&E end users to work together to better specify requirements. However, it also adds some complexity for implementing RESQML HDF5 and Top-Level Objects The schemas are produced as a set of discrete data objects (for example, faults, horizons, grids, etc.). XML is used to define the basic data object (typically the metadata, such as name, location, UUID, etc.). The numeric data associated with a data object is formatted using HDF5, a binary file format that is more efficient than XML for storing numeric data. Most RESQML data objects are referred to in the Energistics community as top-level objects (TLO). By definition, a TLO inherits from the same abstract data object, and therefore has set of common Tool: v1.0/doc: v June 2017 Page 7 of 43

8 characteristics; for example: each instance of a data object is uniquely identified by a UUID and has a common set of required metadata (date created, last modified, by whom/what software, etc.) Data Object References and Partial Transfers The relationships between the XML data objects are specified using XML conventions (e.g., inheritance, etc.) and a specially designed mechanism called a data object reference (DOR), which allows data objects to indicate other data object(s) that it references and the nature of the relationship (for example, interprets, represents, or supports) The data object reference is also a key mechanism (along with UUIDs) that allows what RESQML calls a partial transfer (or partial model update). For example: on an initial transfer Software A may transfer all data objects in a model and the relationships between those objects to Software B. Subsequently, if one object in the model changes, Software A only needs to transfer to Software B: the updated object and the references to the other objects (that have not change). Software B then knows which objects comprise the model, can make changes to the updated object, and can fetch the previously transferred objects to render the complete, updated model Business Rules For consistency and coherency of the model, RESQML also includes textually and numerically defined business rules between XML instances. For example: The first count attribute of a Grid2DPatch contained in an ObjGrid2DRepresentation must be less than or equal to the attribute inlinecount of the grid2dpatch.fastests axiscount of the same ObjGrid2DRepresentation. Typically, business rules can be verified using Object Constraint Language (OCL). However, OCL expressions can only focus on one context object (in RESQML, at TLO). In RESQML, rules often require multiple contexts; for example: for XML objects with corresponding arrays of data in HDF5, it is sometimes necessary to correlate the metadata in the XML object with the dimensions of the arrays in HDF5. (The Editor/Validator does use OCL, but other considerations had to be used to address the situations that OCL cannot handle.) For more information about business rules, see Chapter EPC to Group Objects into a Single Package For a reliable, streamlined transfer of data, all objects that comprise a model (or set of data to be transferred) are contained in an EPC file (sometimes called package), which is essentially a zip file. The EPC file also specifies the relationships between the data objects it contains, based on DORs, in both directions (source to target and target to source). The Energistics Packaging Conventions (EPC) is an implementation of the Open Packaging Conventions (OPC), a commonly used container file technology standard supported by two international standards organizations. If the XML data objects have associated HDF5 data, that data is referenced from within the EPC file to an HDF5 file stored externally to the EPC file. The files are associated by naming convention, for example: my_earth_model.epc and my_earth_model.h How the Editor/Validator Works This section provide a brief overview of the Editor/Validator s underlying technology and an overview of what the tool does and how it works to validate RESQML data Technology The tool was developed using the Eclipse Modeling Framework (EMF) and Object Constraint Language (OCL), and integrates a viewer for the HDF5 data, which may be associated with RESQML data objects. It has a GUI that lets you interact with the data as you edit and validate your model. Tool: v1.0/doc: v June 2017 Page 8 of 43

9 Eclipse Modeling Framework (EMF) This tool is based on the IBM ECLIPSE development environment. It uses modeling-driven technology to set its internal data model and the design of the tool has been improved through testing and actual use. The ECLIPSE development environment allows the use of the EMF to automatically generate two concurrent Java data models: One model from the published XSD expression of the model One model from the published UML expression of the model EMF supports the definition of structural meta-models and the subsequent use of models conforming to these meta-models. EMF also supports the generation of Java code to represent the meta-models. Additional Java code can be provided to add behavior to the structural meta-models Generic and Specific Functions The user interface (UI) of the Editor/Validator is a specialization of a generic user interface provided by EMF to validate the syntactic conformity of an XML instance versus an individual XSD (XML schema). The out-of-the-box UI provides many generic functions (e.g., opening, closing, creating and saving files) that are useful in the context of working with and validating RESQML; more information on them is available in the EMF documentation.. Additionally, to meet specific requirements of RESQML, we have enhanced the generic functions and added some new specific functions Object Constraint Language The Editor/Validator Tool also uses the Object Constraint Language (OCL). OCL is a standard, compatible with EMF, and allows business rules to be specified in textual language that non-developers can also understand. For more information on implementing business rules, see Chapter 5. OCL provides a modeling language that allows the behavior to be embedded within the structural metamodels or provided as a complement to those meta-models. As a modeling language, OCL understands the models. For this reason, the OCL code is much more compact than the equivalent Java. OCL code can be statically checked, whereas the corresponding Java code often uses reflection and cannot be checked in this way. Eclipse OCL is an implementation of the OMG OCL 2.4 specification for use with Encore and UML meta-models (see The OCL specification is defined by the OMG. It originally evolved as part of UML where it is used for the detailed mathematical aspects that are not appropriate for graphical exposition. OCL 2.0 was split off from UML 2.0 in recognition of its greater utility File Handling The Editor/Validator is intended to be used in the context of one (and only one) RESQML EPC file. The tool has no concurrency access control on EPC files, and the use case in which two instances of the Editor/Validator are importing the same EPC file is not managed. When you open (import) an EPC file from the Editor/Validator, the tool unzips the contents of the EPC, creates a new directory (in the same location and with the same name as your EPC file), and stores the unzipped files (the content of your EPC file) in that directory. The tool then uses those files to build working models in memory to perform its various analyses. As you use the exploration and editing features, changes are made in working memory. You can chose to save these changes to disk. However, if you do not save the changes, when you exit the tool, all working models are deleted. Tool: v1.0/doc: v June 2017 Page 9 of 43

10 1.5.2 Basic Process: What the Editor/Validator Does (and cannot do) This section gives an overview of how the Editor/Validator works and its capabilities. For detailed instructions on how to: Install the tool, see Section 2.1. Use the tool, see Section Read and Check EPC File Content, Validate Conformance to Schema and Relationships When you open an EPC file in the tool, it unzips the contents of the EPC file, uses the contents to build working models in memory, and then automatically begins the validation process. An EPC file contains RESQML top-level objects (TLO) (XML instances) plus some relationships expressed as data object references (DOR). When reading an EPC file, the Editor/Validator first verifies the syntactic validity of these instances by checking their conformance with the published RESQML v2.0.1 XSD schemas. In a second step, the tool checks relationships between objects. Specifically it uses the information in the _rels file in the EPC file to ensure that both parts of each DOR are captured correctly: one from the source to the target object and the other from the target to the source object. The tool also checks each object to ensure that UUIDs are consistent, basically the same, in the DOR and the corresponding entry in the _rels file. Because relationships between the XML objects are expressed as DORs, the tool cannot further validate the semantics of the model using only the XSD schemas. To address this challenge, the tool also uses the EPC content to create a UML model, where the expression of the relationship between the TLOs is properly defined. To do this transformation, the tool transfers all the attributes (e.g. int, string, enum, etc.) but not the DORs. Instead, the tool restores the native TLO relations (the ones defined in the UML expression of the RESQML model), which results in a new instance of the EPC package expressed in the structure of the UML model. From this UML model, you can then perform a semantic validation using business rules; see Sections and below and Chapter Explore and Edit the EPC File Using Tool Views After the initial reading and validation by the tool, you can then use it to interactively explore and edit the in-memory model of your EPC file. The tool provides several views that work together, which are further explained in Chapter 3. This multiple-view capability was provided by applying an EMF-generation mechanism to the published XSD schema, and using graphical tools such as ZEST ( and a specific HDF Viewer for browsing the numeric values. For an overview of Editor/Validator Views, see Chapter Validate the Semantic and/or Numeric Consistency of References and Attributes (Business Rules) Use the tool to explore and validate the semantic and numeric consistency of references and attributes. The tool does this validation using the UML model it creates from your EPC file and a set of business rules from the RESQML model, which you must specify for the validator. The Editor/Validator uses OCL constraints to describe the necessary validation operations. OCL provides a modeling language that allows the behavior to be embedded within the structural meta-models or provided as a complement to those meta-models. As a modeling language, OCL understands the models. Before you can use the tool to do this type of validation, you must: Define the business rules (as specified in the RESQML model) in OCL (for more information see, Chapter 5). Tool: v1.0/doc: v June 2017 Page 10 of 43

11 Specify the set of rules and the order in which you want the tool to validate them (for more information, see Sections 2.3 and 4.5). An example of validation is to verify a business rule that states two instances should have a semantic consistence in their enumerations (enums). In this case, the tool checks that two different TLOs (which are independent instances) each has the same enum value. For example, the tool checks that an ObjHorizonInterpretation interprets an ObjGeneticBoundaryFeature with a geneticboundarykind that has a value of horizon (BRT4) Validate Array Dimensions RESQML has important business rules to ensure the consistency between array dimensions specified in an XML object and the array dimensions in a corresponding HDF5 file. For example, consider the case of the numeric validation that needs to be done between an attribute and the size of the corresponding HDF5 array, both defined in the same TLO. We must check that in the case of a Grid2dRepresentation defined with Point3dZValueArray-based geometry, the Grid2dPatch SlowestAxisCount and FastestAxisCount are consistent with associated array dimensions in the associated HDF5 file. OCL has a lot of advantages but it is not fit for acquiring values by using external libraries. To do this type of validation, the tool first gets the HDF5 Group path in the context object and then uses the HDF5 library to get the corresponding array and to obtain its dimensions (NI, NJ). Then, by using an OCL expression template, the tool composes a new local OCL expression incorporating the NI, NJ value as numeric values, so that it can compare them with the values recorded as SlowestAxisCount and FastestAxis Count in the XML objects. The tool is then able to process, at run time, this new local OCL expression, which was previously incomplete. 1.6 Resource Set All Energistics standards and related resources are freely available for download from the Energistics website. The following table lists the resources that are available for the Editor/Validator tool for RESQML v2.0.1 and provides a link to RESQML v2.0.1 resources (schemas, documentation, etc.) Resource/Document Description 1. RESQML Editor/Validator Tool Download the tool from here: /Resqml_v2.0.1_Editor_Validator_v2.zip 2. RESQML Command Line Tool Download the tool from here: /Resqml_v2.0.1_Validator_Command_Line_v1.zip 3. RESQML Editor/Validator Tool User Guide (this document) This guide includes instructions for both the Editor/Validator tool and the Command Line Validator. Download the tool and documentation from here: SQML_Editor_Validator_User_Guide_v1.0_Doc_v1.0.pdf. 4. Example files. Several example files are available to help show how the tool is supposed to work. The examples are described in this user guide. Download the example files from here: mples.zip 5. RESQML v2.0.1 resources Download all resources (schemas, documentation, etc.) for RESQML v2.0.1 here: Tool: v1.0/doc: v June 2017 Page 11 of 43

12 2 Installing and Running the Editor/Validator This chapter explains how to download and install the tool, and provides: a brief overview of the main program window, a simple procedure for how to use the tool to validate an EPC file, and additional information on how to examine and edit your data. 2.1 Download and Install the Tool For links to download available resources (tools, user guide, example files, etc.) see Section 1.6. The zip file for the tool contains the program (for Windows 7, 32 and 64 bits). To install the tool: 1. Choose the directory on your computer where you want to install the tool. To avoid problems if you are not the administrator of your computer, do not chose c:/programfiles. Recommendation: Download to your user directory, e.g., c:/user/myname/myresqmltools. 2. Move the downloaded zip file to that location and unzip it there. The unzipped file has the directory organization shown in Figure 2-1 Figure 2-1: The directory organization of the ZIP file that you download to install the RESQML v2.0.1 Editor/Validator tool. 3. To run the tool, double-click: This executable launches the Interactive Editor/Validator and a specific HDF5 viewer, which has been integrated with the Editor/Validator. When you launch the tool, it looks like Figure 2-2. Tool: v1.0/doc: v June 2017 Page 12 of 43

13 2.2 Overview of the Main Interactive Tool Window This interactive tool is composed of a system of menus and different views (which are shown in Figure 4-1, page 28) and explained briefly in the table below the figure. For more information: About the views, see Chapter 3. About menus and commands, see Chapter 4.. Figure 2-2: The main window when you first launch the Editor/Validator tool. View What it displays For more information, see Section: Table Graph Resource Set/Resource Set List Log Properties A tabular list of all top-level objects (TLO) in the in-memory model of an EPC file. For each object it shows, content type, title and UUID. A graphical representation of objects in the in-memory model of an EPC file, showing references, hierarchy, etc. Displays the details of a TLO in the in-memory model of the EPC file. To display the data for an object, in Table View, double click on the object. A Resource window opens for each object, where you can drill down on the hierarchy of data that comprises the object. The Resource View allows multiple TLOs to be open (each in a separate window) and keeps a list of open resources so you can manage them. Displays results data from the validation functions. If you run multiple validations, the results are appended to the log. Displays property data for the resource that is selected in the Resource View. You can examine and edit properties Tool: v1.0/doc: v June 2017 Page 13 of 43

14 2.2.1 Synchronizing Views To synchronize edits in one view across all views or your model, use CTRL+S. You can also choose to save to disk either a complete EPC file or one or more individual RESQML resources (TLOs). For more information, see Section Validate an EPC File The Editor/Validator is intended to be used in the context of one (and only one) RESQML EPC file. The tool has no concurrency access control on EPC files, and the use case in which two instances of the Editor/Validator are importing the same EPC file is not managed. This section provides a simple procedure for validating RESQML objects in an EPC file. However, there are many ways you can use this validation tool, depending on your specific workflow. To validate an EPC file, perform the following steps: 1. Open the EPC file by choosing File->Open EPC. When the tool opens the EPC file, it automatically generates two concurrent Java data models: one model from the published XSD expression of the model - one model from the published UML expression of the model The tool automatically validates the syntactic consistency of the objects and the relationships of the objects in the in-memory XSD model of the EPC file. The results, including any errors, from the validation are displayed in the Log View. 2. Specify the set and sequence of business rules that want to use to validate your EPC file by choosing Validate->Create Validation Sequence. You must create business rules (outside of this tool) using Object Constraint Language (OCL). For information on how to develop business rules (see Chapter 5). After you create the business rules, in Editor/Validate you must select the rules and specify the sequence in which they must be executed. For more information see, Section Validate the model using your business rules by choosing Validate->Validate EPC with Business Rules. The tool validates the in-memory UML model of your EPC file for the business rules you specified in the sequence you specified. Tool: v1.0/doc: v June 2017 Page 14 of 43

15 2.4 Examine and Update Your Files This section contains step-by-step instructions for a basic and an advanced examples Basic Example The Resource Set View shows the details of a single TLO instance in your EPC model. You can have multiple Resource View windows open at one time. Figure 2-3 shows the Resource View and some of the most useful functions for examining and updating your data. Figure 2-3: Resource Set List View. When you click on a resource (anywhere in the resource hierarchy), the Properties View shows the editable properties (attributes and enumerations) for the selected resource. Each time you select a different resource, the Properties View shows the values for the selected resource (i.e., the tool displays only one property view; it does not support multiple property windows). You can modify these attributes, and, if your modifications meet the constraints defined in the XSD schema, then you can save it in your in-memory working model with CRTL+S. Examples of edits you can do and constraints shown in Figure 2-3: For Surface Role Enum, the tool only accepts map or pick, so the tool presents only these 2 options. If a numeric value to enter must be a non-negative integer then the tool prevents you from entering negative values. Tool: v1.0/doc: v June 2017 Page 15 of 43

16 Now, you can examine (and update, if you want) the attributes and enums of any TLO. Select the object by clicking on it; related attributes and enums are displayed in the Properties View, where you can edit them. Figure 2-4 shows the Local Depth3D CRS attached to a triangulated surface. Figure 2-4: Local CRS attached to a triangulated surface. To execute a specific activity on an XSD element, select it and right-click it. The tool displays available options for that object; Figure 2-5 shows available functions both generic (e.g., Cut, Copy, Delete, Validate, Load Resource, Refresh, Show Properties View) and specific (e.g., Open HDF View and New Child (which is a create Resource function)) functions. Figure 2-5: Right-click on an XSD element to display a context-sensitive menu. To view numeric values in an HDF5 file (Figure 2-6): Select the object, right-click and chose Open HDF View. The tool opens the HDF5 Viewer (the one packaged with the Editor/Validator tool) and displays the numerical data for the selected object (Figure Tool: v1.0/doc: v June 2017 Page 16 of 43

17 2-7). For more information on how to use the HDF5 viewer, see Figure 2-6: The Editor/Validator includes a modified version of an HDF5 file viewer that can be launched to display the numeric data of a specific object by selecting the object, right-clicking and choosing Open HDF View. Tool: v1.0/doc: v June 2017 Page 17 of 43

18 Figure 2-7: The tool displays the numeric content in an HDF5 viewer package with the Editor/Validator. When your edits have been validated and you are satisfied with the results, you can save the EPC file or one or more individual RESQML resources; for more information, see Section Advanced Creation Functions NOTE: This section is for users who are very experienced (experts) with RESQML v2.0.1 models. These tasks are most likely for developers who want to create test cases. Using the Editor/Validator you can create EPC files from scratch for metadata only. That is you can create an EPC file with TLOs that have no HDF data (such as features and interpretations) or to build new organizations using existing TLOs. Here is a basic procedure to create a new EPC file and populate it with TLOs. 1. Choose File->New->Epc Model (Figure 2-8). The tool presents the dialog shown in Figure 2-8 where you can specify a directory, model type, and XML encoding. Tool: v1.0/doc: v June 2017 Page 18 of 43

19 Figure 2-8: You can create an EPC file and add objects to it. For advanced users only, usually for purpose of testing. 2. To create a new genetic boundary feature in this EPC file, choose New->Resqmlv2 Model (Figure 2-9). The tool displays a dialog where you can specify a file name and location and choose the type of RESQML data object (for this example, genetic boundary feature). Figure 2-9: After you create an EPC file, you can create new objects to add to it. Tool: v1.0/doc: v June 2017 Page 19 of 43

20 3. To complete the information for the new object you added, right-click, choose new child, and the type of metadata that you want to add. Figure 2-10 shows the available metadata options for a genetic boundary feature. For example you could choose to add a Citation XSD element and title the object MyNewGeneticBoundary (Figure 2-11). Figure 2-10: To add metadata for an object, right-click and choose New Child and select from the available metadata options. Figure 2-11: Using the Citation element you can title the new TLO instance MyNewGeneticBoundary. To create a new horizon interpretation and associate to the MyNewGeneticBoundary by data object reference (DOR), follow these steps: 1. Create a New RESQML Object of type Horizon Interpretation. Tool: v1.0/doc: v June 2017 Page 20 of 43

21 Figure 2-12: Create a New RESQML Object of type Horizon Interpretation. 2. Add a citation object to the new Horizon Interpretation. Figure 2-13: Add a citation object to the new Horizon Interpretation 3. Reference the interpreted feature (MyNewGeneticBoundary) by its UUID (Figure 2-14). In this sequence, the Editor/Validator carefully selects the TLO that can be linked by relationships defined in the UML Schema. For example in Figure 2-14, only features are proposed as possible choices. Tool: v1.0/doc: v June 2017 Page 21 of 43

22 Figure 2-14: When specifying relationships to a new object in an EPC file, the Editor/Validator limits available choices based on definitions in the data object schema (XSD file). Figure 2-15 shows the resulting Graph View for this EPC file and object relationships. Using this same basic method, you can continue to add TLOs and define relationships between them to build up a complex structural organization interpretation that incorporates contact interpretations and complex stratigraphic columns. Work like this can be useful to set up complex tests and control the consistency of complex EPC files. Tool: v1.0/doc: v June 2017 Page 22 of 43

23 Figure 2-15: Graph View for this EPC file and the object relationships. Tool: v1.0/doc: v June 2017 Page 23 of 43

24 3 References: Views This chapter lists and explains the views in the Editor/Validator. REMINDER: Generic functions are standard to ECLIPSE EMF. Specific functions are those created specifically for RESQML. The views discussed in this chapter are different views of the EPC file that you imported (in-memory model). Changes made in one view do NOT automatically update in another view. To synchronize edits in one view across all views or your model, use CTRL+S. You can also choose to save to disk either a complete EPC file or one or more individual RESQML resources (TLOs). For more information, see Section Table View This is a generic function with some specific enhancements. When you open an EPC file using File->Open EPC, the tool presents the information in Table View, which lists the TLOs, and for each TLO, its content type, title and UUID (Figure 3-1). (For more information on content types, see the Energistics Packaging Conventions Specification (EPC Spec). Figure 3-1: When you open an EPC file, the tool displays the TLOs in Table View. When you select a TLO (row of table (Line N 3 above) the Resource Set view displays that object s associate resources. The objects are ordered by content type and the Line N column indicates its position (for easier reference) in the EPC file. This Line N does not change (even if you sort the file by other attributes). Table View has a couple of ways to help you locate a particular object: Search by the first characters of a UUID using the search box (just above the table). Click on any of the column headings to sort by that column. Tool: v1.0/doc: v June 2017 Page 24 of 43

25 To display the details of an object in this table, double-click it. The tool opens a tab and displays the object details in the Resource Set View. Each time you double-click an object in the table, the tool opens a corresponding tab with that objects details in the Resource Set View. You can also capture a value to copy to another field using CTRL+C. To synchronize views, use CRTL+S. 3.2 Graph View This is a specific function developed using ZEST ( a standard development tool provided with ECLIPSE EMF. Graph View helps you to visualize and understand the relationships between the TLOs in your EPC model. This is a graphical interface that you can detach (e.g., move the window independently of the main tool window) to interact between the different views. Use commands on the Navigate menu to show/hide objects in Graph view. For example, if you open ALWYN-Testing.epc, the Graph View looks something like Figure 3-2. Figure 3-2: Graph View of example file ALWYN-Testing.epc. If you double click on the organization feature JLL, you can see an interpretation (Earth Model Interpretation: sismage) and the link interprets appears. Then double click on this interpretation feature, and you can see the representation linked (Grid Representation: Grid 3D) and the link represents appears. Then you double click on this representation feature, and you can see the Depth CRS attached and the various Properties linked (Properties: BulkVolume, SWAT, PORO, NTG, PERMX) and the links supports appear. The software does its best to present these TLOs on screen. If you don t like the layout, you can move objects to make the image more readable. Tool: v1.0/doc: v June 2017 Page 25 of 43

26 Every time you double-click on an object you display its details in a tab in the Resource View or deploy the graph of the relationships between this TLO and the others. To synchronize views, press CRTL+S. To choose the TLO types to be visualized, use the File/Navigate command. 3.3 Resource Set and Resource Set List Views The Resource Set View is a generic view with a number of specific enhancements. When you double-click on a TLO in the Table View or in the Graph View, the tool opens a tab and displays that object in the Resource Set View. In the Resource Set View, you can click on objects to expand the hierarchy and drill down in the object. When you click on an object in the hierarchy, its enumerations and attributes are displayed in the Properties View (Figure 3-3). The tool supports having multiple resource tabs open at one time; the tool includes a Resource Set List to help you view and manage the open resource tabs (Figure 3-3). NOTE: All the updates done in this Resource Set View and in the associated Properties View are temporary and not automatically propagated to other views or saved. To synchronize views, use CTRL+S; to save, use the available save resource options (for more information, see Chapter 4). You can display a list of all open resources. If you select a resource here its properties are displayed here. Figure 3-3: When you double-click on an object in the table, its details are displayed on the Resource Set View. If multiple resource tabs are open, the tool displays a list to help you manage the tabs/resources. 3.4 Properties View Displays the properties for a selected resource (RESQML TLO) (see Figure 3-3 above). You can edit the properties but any edits must conform to the constraints specified in the XML schema for that object and property. For example, if a property has enumerated values specified in the schema, the tool displays only those values for you to choose. Tool: v1.0/doc: v June 2017 Page 26 of 43

27 3.5 Log View When the Editor/Validator performs any validation tasks on an EPC file, the results and errors are displayed in the Log View. The tool also stores these results in a log file whose name is based on the EPC file that you opened. For example, if you opened MyEPC.epc, then the log file is named MyEPC.log. If multiple validations are run, the new results are appended to the log view and file. Tool: v1.0/doc: v June 2017 Page 27 of 43

28 4 References: Menus and Commands This chapter lists and explains all menus and each ones respective commands. It identifies menus and commands as generic to the EMF environment or specific functions developed for RESQML and EPC files. 4.1 File Menu The File menu has both generic and specific functions. Reminder: When you open an EPC file, the tool creates an in-memory model based on the contents of that EPC file. Save functions are related to storing any changes you may have made that in-memory model to disk. CTRL + S synchronizes the tool s various views of the model. Figure 4-1: The Editor/Validator File menu is used to open, create and save EPC files, their associated HDF5 file, and RESQML resources File->New This is a generic function that lets you generate an object from a list of classes. For example, we can create: A CommonV2Model (instance of an EPC external part Reference) An EPC file (a new container of instances) A ResqmlV2Model instance using 46 available top-level classes. The other options are EMF generic options not used in with RESQML/EPC, but which could be used, for example, if you import some complementary XSD descriptions File->Open EPC This is a specific function that lets you open an EPC File with its associated HDF5 file. When you choose Open EPC, the tool opens a directory window to choose an EPC file such as MyEPC.epc. If the same directory also has an HDF5 file with the same name as the EPC (e.g., MyEPC.h5) the system makes the connection between these files. If no HDF5 with the same name exists, the tool proposes another HDF5 file to associate with the EPC. When you import a file, the system examines the EPC relationships and the syntactic conformity of all the top level objects (TLOs) included in the EPC content and displays errors (if any) in the Log View and stores them in a log file named MyEPC.log in the same directory as the file MyEPC.epc. Tool: v1.0/doc: v June 2017 Page 28 of 43

29 Even if the file MyEPC.epc is not correct, the tool loads it with syntactic errors and you can edit and correct the information File->Save Epc This is a specific function that lets you save an EPC file with the same name or with another name (e.g., MynewEPC.epc). A related HDF5 file is not modified/exported during this operation File->Open a Resqml Resource This is a generic function that allows you to work on a specific instance out of its EPC context. In this case, you can only verify the syntactic conformity of this instance. This function can be used to look at the metadata of a specific TLO File->Open File Generic function that opens (or imports) a file. It is not useful for our needs. The following functions are only active if an EPC file was already imported and some Resources transferred in to the Resource view File -> Close Resqml resource Generic function to close the resource active in the Resource Set View (see below: Resource View) and Close All resources actives in the File->Close All Resources Generic function to close all the resources present in the Resource Set List View. The following save commands are useful generic functions to save all results when you edit resources. When the user edit one resource, this resource is updated only in the front end views on which the edits were applied. To actually push the information into the persistent memory of the application the user must save its changes. If the save functions are active, it means that there are some resource s updates which are not already be pushed to the internal memory of the application. As soon as these save functions are applied any the updates are recorded and the EPC can be fully exported. NOTE: CTRL+S saves changes done in the Resource and/or Property Views and saves all changes to the Editor/Validator persistent memory File-> Save a Resqml Resource Generic function that saves the updates done to the current resource in the Resource Set View to all the other views and into the persistent instance of the data model in memory File-> Save a RESQML Resource as Generic function that exports the current resource in the Resource Set view in an XML file File-> Save All Resources Generic function that propagates the updates done in the resources present in the Resource Set List (see below) to all the other views and the persistent instance of the data model in memory File-> Exit This is a generic function to exit/close the tool. If you did not save your previous changes, the Editor//Validator prompts you to save any edits. Tool: v1.0/doc: v June 2017 Page 29 of 43

30 Figure 4-2: Resource Set View and Resource Set list View enhancement and message send when some resource are not saved. 4.2 Edit Menu Displays generic editing functions and their keyboard shortcuts. Figure 4-3: Edit menu commands and keyboard shortcuts. 4.3 Navigate Menu The Navigate menu has only specific functions, which are filters applied to TLOs displayed in the Graph View. Figure 4-4: Navigate menu functions. These are all specific functions applied to the TLOs displayed in Graph View. Tool: v1.0/doc: v June 2017 Page 30 of 43

31 4.4 Show View Menu The Show View menu has only specific functions. If you accidentally close any of the four views (Table, Graph, Log or Properties), use these commands to open the view. You can arrange views in the tool interface. Figure 4-5: Show View menu commands. 4.5 Validate Menu The Validate menu has specific functions only. Some of these functions are launched automatically when you open/import an EPC file. However, if you do corrections or edits to your EPC model, or if you create a new one, you can then use these commands to re-run the validation on demand. You must explicitly choose and execute commands related to creating and validating business rules (they never run automatically). Figure 4-6: The Validate menu commands Validate -> Validate Syntactic Consistency Validates the syntactic consistency of each TLO in an EPC file (also done automatically when you open an EPC file). Results of this operation are displayed in Log View and in a log file that has the same name and is stored in the same directory as the EPC file being validate. For example, if you are validating a file named MyEPC.epc, the log file is MyEPC.log. You can also perform this function on one resource (e.g., a single RESQL TLO instance): from Resource Set View; simply right-click the object and select the Validate command. So for example, if you open an EPC file and one of the RESQML resources has an error (as noted in your log file), you can then edit/correct the resource, then have the tool validate only that object (to ensure your edits have corrected any previous problems Validate -> Validate EPC Relationships Validates the relationships between all TLOs in in EPC file (also done automatically when you open an EPC file). Like the previous command, results and errors are displayed in log file with the same name stored in the same directory as the EPC file. Run this function from the Properties View. Use this function after you have edited the contents of an EPC file. Tool: v1.0/doc: v June 2017 Page 31 of 43

32 4.5.3 Validate -> Create Validation Sequence of Business Rules Use this function to gather previously defined business rules into the sequence that you want the tool to validate them. After you create and save this list, then you can launch the validation (Validate-> Validate EPC with Business Rules, see Section ) You must develop RESQML business rules (which are specified in the RESQML Technical Reference Guide v2.0.1 (also in the RESQML UML model)) using OCL as described in Chapter 5. NOTE: For more information about OCL, see download.eclipse.org/ocl/doc/5.0.0/ocl.pdf. The official specification of the standard is available at When you choose this command, the Tool displays the dialog shown in Figure 4-7. Navigate to the directory where you have stored your business rules; the tool displays available business rules in the left column. From the left column, select the rule(s) you want and use the arrow button to copy them to the right column. Use the up and down arrows to specify the sequence in which you want the rules to be validate. When you are satisfied with the list, you can save it. Figure 4-7: You must specify the business rules that want to use and the sequence in which you want the tool to validate these rules. How to write the actually business rules (which are specified in RESQML) is explained in a separate document, as referenced above Validate -> Validate EPC with Business Rules Use this function to validate a sequence of business rules for a specific EPC file. The business rules must have been previously defined; see Section To validate a particular EPC file, follow these steps: 1. Open the file you want to validate. 2. Choose Validate -> Validate EPC with Business Rules. The Editor/Validator displays the dialog shown in Figure Navigate to the directory where your business rules are stored. Do one of the following: Select the business rules and specify the sequence in which you want the validator. - Open a file where you previously saved a sequence of business rules. Tool: v1.0/doc: v June 2017 Page 32 of 43

33 4. Choose the Validate button. The results of the validation are displayed in the Log View and are added to a log file with same name as the EPC file (e.g., MyEPC.epc and MyEPC.log) and in the same directory. The log file lists the TLOs (by UUID) and their respective business rule violations. Use the Table View to explore and edit the objects so that they conform to the business rules. Rerun the business rule validation to validate your corrections. Each time the tool validates a model, the results are appended to the log. Figure 4-8: When you choose the Validate with Business Rules command, the tool displays a dialog where you can select the business rules and the sequence OR select a file where you have previously stored the sequence that you want the validator to use. Tool: v1.0/doc: v June 2017 Page 33 of 43

34 5 Business Rules Both the Editor/Validator Tool and Command Line (CL) Validator use business rules, which are described in plain text in the RESQML v2.0.1 Technical Usage Guide and expressed for use in the tools with the Object Constraint Language (OCL). Both tools use the Eclipse OCL implementation of the OMG OCL 2.4 specification for use with UML meta-models. For more information about OCL, see For information on the syntax of the expressions, see OCL Tutorials documents like This chapter explains the business rules (BRs) used in the tools and provides some guidance on how to implement them (syntactic details are provided in the OCL resources listed above). It also provides and explains some examples of the BRs defined in RESQML. For an overview of how the tool works and how business rules are applied, see Section NOTE: RESQML uses the terms writer ( export ) and reader ( import ) to refer to the software packages involved in a data exchange. 5.1 Overview of the Approach The ability to implement business rules in the validator tools provides organizations with flexibility to accommodate the particular needs of their workflows, without having to hard code the rules in software. Organizations: Must specify and observe the BRs defined in the RESQML documentation. May: Specify additional internal-use-only rules within their own organizations and workflows. Propose new BRs to be incorporated into the RESQML standard. Indeed, as part of continued development of RESQML, the SIG may add new BRs (which will be noted in change management documentation included with a new version of any Energistics standard). To propose new BRs to be added to RESQML, use Energistics typical work channels such as JIRA or BaseCamp or contact an Energistics staff member. Proposals for new BRs should also include two example EPC files to help clearly illustrate the BR and its intent: 1) An EPC file that correctly supports the BR (i.e., will achieve a True result from the Tool and 2) An EPC file that violates the BR (i.e., will achieve a False result from the Tool). Use OCL to define constraints that must be respected by instances of data objects contained in an Energistics Packing Conventions (EPC) file. This definition is done by expressing these constraints using the OCL syntax in a BRT*.xml file. Here s how the validator tools (Editor/Validator or CL Tool) work: First it reads an EPC file and does a first check on the conformance of the instances to the XML schemas (provided by Energistics). Next the tool checks the consistency of the data object reference (DOR) relationships, and finally it loads the objects into memory. While the objects themselves are based on the top level object (TLO) XML files defined by the Energistics schemas, the model loaded into memory is actually based on the UML model (from which Energistics produces the XML schemas). The tool then does a second pass where it reads in sequence the XML files containing the BRs (each file contains one BR). For each business rule, the tool inspects each instance (<source object>) corresponding to a specific class (<classname>) and checks the constraint(s) defined by an <expression>. The response of the tool can be true (the object conforms to the BRs) or false. If it is false, the tool produces a log file describing the errors, which is stored in the same directory as the EPC file. Developers Tool: v1.0/doc: v June 2017 Page 34 of 43

35 who want to automate RESQML software exchanges (using the CL Tool), can use the logs to guide their work OCL is used to formally describe the BRs defined in free plain text in the RESQML v2.0.1 Technical Reference Guide which cannot be constrained by the XSD schema. You can also define some additional BRs that must be followed by a group of users to ensure that the reader can understand correctly, without misunderstanding, what the writer wants to express. If you want to define more constraints to be added officially as part of the RESQML standard, you can describe them in free plain text (using JIRA as a support to communicate to the SIGs for example) and ask Energistics to write the corresponding BRs in OCL. To help ensure clear understanding of a new BR and how it is intended to work, when proposing a new BR, you should also include two example EPC files: one that supports the new BR (test results = True) and one that violates the new BR (test results = False). The advantage of this approach is that additional BRs can be specified and expressed as simple XML files without additional development. The Editor/Validator and the Command Line validator can read, understand, and execute all the necessary checking without any change in the code, independently of any developer. 5.2 Types of RESQML Business Rules and How they Work The business rules defined in the RESQML v2.0.1 Technical Reference Guide can be categorized as follows: Category A: Semantic consistency of attributes inside one top level object (TLO) and between attributes belonging to different TLOs that are linked by data object reference (DOR) relationships. Example BRT1, BRT2, and BRT3; see Sections 5.3.1, 5.3.2, Category B: Numeric consistency between two numeric attributes depending on the same TLO (BRT5) or depending on two different but related TLOs (BRT5). See Sections and Category C: Numeric consistency between numeric values of TLO attributes and dimensions of arrays in related Hdf5proxy/HdfGroup or even between the dimensions of arrays attached to two different TLOs. See BRT7 in Section Categories A and B are challenging because the tool needs to explore the instances of a model that was exploded (from one global UML model to many individual XSD schemas, and the relationships in the schemas are not as clearly specified as in the UML model). With multiple schemas, OCL is not easy to apply. This is why, when the tool imports an EPC file, it reads the file.xml of the TLOs and automatically reconstructs the in-memory model according to the UML model; once in memory the OCL constraints can be applied on the entire EPC file/model. Category C is even more challenging. In fact there is no OCL engine to import numerical values and check dimensions of arrays only expressed in HDF5 files, so the Editor/Validator had to be designed to address this. To do this, on a first pass reading the EPC, the Editor/Validator transfers the number of dimensions (DimensionCount) and the sizeperdimension of each array to the HdfDataset Object with its PathinHdfFile. Using this strategy, each instance of the EPC file deployed in the EA UML model having a relationship to an array in the HDF5 file is informed of the size of the arrays and then, all the OCL constraints involving these values can be checked. Having recorded these values, it is now possible to add any business rules in OCL that can validate the quality of the semantic and numeric attributes of any EPC instance. Tool: v1.0/doc: v June 2017 Page 35 of 43

36 5.3 Business Rules: Descriptions and Explanations Construct business rules as OCL constraints; these rules are then used by the interactive Editor/Validator or the Command Line Validator to validate an EPC file and its contents. To help you understand and implement business rules, the download for the tool includes an example file of several business rules (BRT) that represent the three main categories of BRs used by RESQML v Six of these business rules are explained here Category A: BRT1.xml: Semantic constraints validation of relationships between top-level objects This business rule checks that a FaultInterpretation interprets a TectonicBoundaryFeature. This business rule is not expressed in plain text in the RESQML v2.0.1 Technical Reference Guide document, but it is implicit and must be explicitly stated and checked by a business rule. In RESQML v2.0.1, we have no way in the model to declare that a FaultInterpretation MUST interpret a TectonicBoundaryFeature. The relationships are defined between more abstract concepts like FeatureInterpretation and GeologicalFeature. But the writer MUST not write that a FaultInterpretation interprets a geneticboundaryfeature. In fact, the RESQML v2.0.1 model is a very permissive model which allows users, with the data object reference (DOR) mechanism, to inadvertently associate any interpretation object to any feature object. Applying this business rule on an EPC file checks this relationship; for any given EPC file, we explore each FaultInterpretation and check to make sure they are effectively associated to a TectonicBoundaryFeature. This condition should be checked to ensure that the EPC file is valid. The SourceObject considered here has the class name resqmlv2.objfaultinterpretation. The following expression should be True : All instances (which are defined by self) of an interpreted feature should respect this rule: oclistypeof(t: Type): Boolean is true if the type of self and t: (in this case TectonicBoundaryFeature ) are the same. Such an expression can be written with the same type of rule for the source object: resqmlv2.objhorizoninterpretation. Tool: v1.0/doc: v June 2017 Page 36 of 43

37 5.3.2 Category A: BRT2: Semantic constraints validation of relationships between top level objects including Enum value checking This example checks that an ObjEarthModelInterpretation interprets an ObjOrganizationFeature with an organizationkind of earthmodel. As discussed above, it is not possible to constrain an EarthModelInterpretation to interpret specifically an OrganizationFeature. So a business rule in the RESQML v2.0.1 Technical Reference Guide specifies that, in this case, the OrganizationFeature should have an OrganizationKind of value earthmodel (instead of fluid, stratigraphic or structural). The SourceObject considered here has the class name resqmlv2.objfaultinterpretation. Both points in the following expression should be True : All instances (which are defined by self) of an interpreted feature should respect this rule: oclistypeof(t: Type): Boolean is true if the type of self and t: (in this case OrganizationFeature ) are the same. All instances (which are defined by self) of this OrganizationKind has earth model for value of the ENUM : OrganizationKind Tool: v1.0/doc: v June 2017 Page 37 of 43

38 5.3.3 Category A: BRT3: Semantic consistency of attributes between top level objects that are linked by data object reference relationships This example checks that all individual interpretations (faults and horizons) used to constitute a StructuralOrganizationInterpretation have the same domain declaration in all these objects: StructuralOrganizationInterpretation, FaultInterpretation, and HorizonInterpretation. The Editor/Validator begins examining all instances of StructuralOrganizationInterpretation and for each of these instances, both these conditions must be true: For the Fault Interpretation(s) part: With the instruction: self.faults launched on StructuralOrganizationInterpretation, the tool will find all the instances of Fault Interpretations linked by the relationship: faults (0,*). It will store the result of its query in the variable e. Then, for each of these FaultInterpretations, the tool will find the value recorded in its domain attribute and compare it to the value recorded of the domain attribute of the StructuralOrganizationInterpretation instance chosen. For the Horizon Interpretation part: With the instruction: self.horizons launched on StructuralOrganizationInterpretation, the tool will find all the instances of HorizonInterpretationIndex linked by the relationship: Horizons (0,*). It will store the result of its query in the variable hindex. Then, with the instruction: for all hindex, it will find all instances linked by hindex.horizon. For each of the instances of the corresponding HorizonInterpretation, it will find the value of the domain attribute. - The last check is the same as for the faults: The tool will compare it to the value recorded of the domain attribute of the StructuralOrganizationInterpretation instance chosen. If all the results are true, the EPC passes the validation test. Tool: v1.0/doc: v June 2017 Page 38 of 43

39 5.3.4 Category B: BRT4: Numeric constraints validation between attributes belonging to the same top level object (validation on XML content only) This example checks that in the case of an ObjGrid2dRepresentation related to a SeismicLatticeFeature, the values of grid2dpatch.slowestaxiscount and grid2dpatch.fastestaxiscount are consistent with the grid2dpatch.geometry.points.offset arrays size. The checking is applied on every Grid2dRepresentation. In RESQML v2.0.1, we can associate a Grid2dRepresentation to an interpretation of a seismiclatticefeature. This is done defining an origin (Point3DLatticeArray.origin) and a vector by (Point3DOffset.Offset) in each direction. As we associate this lattice to a Grid2dRepresentation, we have to define two vectors and the Spacing.count will be the number of interval(s) in each direction. At the end, this number MUST be equal to the number of Point-1 for each direction. In the 2D GridPatch, the number of points in each direction will be the lowestaxiscount and the fastestaxiscount. We start by exploring all Grid2dRepresentations and check if they represent a seismic lattice feature. If we find such a construction, then we start to explore the first relationship Offset of the point3dlattice Array. This relationship is given a sequence of two elements, both of which must be true: The first one corresponds to an array (of type double constant array) and for this constantarray, the Spacing.count must be equal to the Grid2dPatch. SlowestAxiscount -1. This is because the value of the SlowestAxiscount of the tested Grid2dRepresentation is the number of points in the I direction of this Gri2dPatchRepresentation. The second one corresponds to an array (of type double constant array) and for this constantarray, the Spacing.count must be equal to the Grid2dPatch. FastestAxiscount -1. This is because the value of the FastestAxiscount of the tested Grid2dRepresentation is the number of points in the J direction of this Gri2dPatchRepresentation. If all the results are true, the EPC passes the validation test Tool: v1.0/doc: v June 2017 Page 39 of 43