{"id":1616,"date":"2018-10-25T14:50:19","date_gmt":"2018-10-25T14:50:19","guid":{"rendered":"https:\/\/wetransform.eu\/?post_type=news-and-events&p=1616"},"modified":"2022-07-28T08:23:54","modified_gmt":"2022-07-28T08:23:54","slug":"metadata-tools-haleconnect","status":"publish","type":"news-and-events","link":"https:\/\/wetransform.to\/de\/neuigkeiten-veranstaltungen\/metadata-tools-haleconnect\/","title":{"rendered":"Metadata Tools in hale\u00bbconnect: Profile Management and Automated Metadata Generation"},"content":{"rendered":"

A few months back, we described how you can setup hale\u00bbconnect<\/a> to fully automate metadata generation, re-use and validation. In the past months, we have worked together with a reference customer, the LGL Baden-W\u00fcrttemberg, to extend the metadata tools in hale\u00bbconnect substantially. LGL Baden-W\u00fcrttemberg is one of 16 state-level cadastral, mapping and spatial planning authorities in Germany and maintains the state spatial data infrastructure.<\/p>\n

The Problem<\/h2>\n

The problem that the LGL approached us with is one that we have seen many times already: there is a specific metadata profile, but both in terms of process and tools, the maintenance and implementation of this profile requires a lot of extra effort. The LGL used a massive Excel Table with more than 400 rows to describe their profile. This Excel table conflated profile rules from different levels (ISO, INSPIRE, national, and local), which all needed to be updated and kept in sync.<\/p>\n

\"Excel
\nExcel table containing LGL Baden-W\u00fcrttemberg requirements.<\/strong> The excel table contains rules from ISO, INSPIRE, national and local schemas.<\/p>\n

In implementation of the profile, there were often ambiguities or different interpretations of certain aspects of the profile. Furthermore, the documentation was a bit unwieldy and hard to read for most people outside the immediate circle of editors.<\/p>\n

Thus, LGL reached out to us to understand how they could improve on this situation. Wetransform originally conducted a UML and Metadata workshop to explore whether developing the profile in a UML Tool such as Enterprise Architect would make sense. However, some aspects such as a nice differential documentation and the generation of an executable test suite directly from the profile proved to be quite hard.<\/p>\n

Thus, in early 2018, LGL asked wetransform to develop a toolset that would support the creation of a fully formal profile definition of the ISO metadata schemas. This toolset would enable the definition of profiles on any XML-based schema, be it the CSW 2.0.2 Application Profile ISO 1.0.0 or a GML Application Schema.<\/p>\n

The Solution<\/h2>\n

There were several key requirements that the profile toolset should resolve:<\/p>\n

    \n
  1. Definition of type and property constraints (e.g. on cardinality, allowed content and allowed property types.)<\/li>\n
  2. Definition of consistency constraints (e.g. \u201cIf A exists, B must also exist<\/em>\u201d) and other advanced validation rules.<\/li>\n
  3. Addition of documentation via tagged values.<\/li>\n
  4. Automated generation of printable documentation.<\/li>\n
  5. Automated generation of differential documentation.<\/li>\n
  6. Automated generation of Executable Testsuites (ETS) for the INSPIRE Reference Validator (ETF.)<\/li>\n
  7. Automated generation of example XML instance documents for the profile.<\/li>\n
  8. Be easy to use for people without in-depth knowledge in technologies such as XML, XML Schema, Schematron and ETF.<\/li>\n<\/ol>\n

    <\/p>\n

    To fulfil these, we developed a formal model that could capture all the required information, as well as a set of editing functions that extend the existing schema modelling tools in hale connect. The formal profile contains type and property constraints, consistency constraints and tagged values:<\/p>\n

    \"Formal
    \nFormal profile model diagram.<\/strong> The diagram displays the formal profile model developed by wetransform.<\/p>\n

    To create a profile, you first have to create a schema using any of the methods supported in hale connect. For creating a metadata profile, use either the ISO 19139 preset or the CSW 2.0.2 Application Profile ISO 1.0.0 preset.<\/p>\n

    After this step, you have to create a profile of that schema. This is also done through the \u201cCreate new Schema\u201d process, using the \u201cCreate Profile\u201d option. When the profile has been created (which takes up to 30 seconds), you can go to the Feature Types section and start applying type and property constraints.<\/p>\n

    \"Type
    \nType level constraints.<\/strong> The toggle switch can be used to make a type mandatory.<\/p>\n

    To make a single type mandatory, you can just toggle it in the type header. Making it mandatory means that an object of this type has to occur at least once in any document. This is particularly useful in GML Feature Collection, where you want to state which types of objects have to be present.<\/p>\n

    Most of the constraints are set using the Edit Mode, which you can access through the Pen icon in the type header. Clicking this icon brings you to a powerful editor, where you can set a number of constraints:<\/p>\n

      \n
    • Content Required: If not already true, you can set this to true to make sure that the given property always has to have content. The semantics of this constraint are equivalent to setting the nillable<\/em> flag to false.<\/li>\n
    • Minimum Cardinality: The minimum number of times this property needs to occur in any given type. It needs to be higher than the one defined in the schema, but lower or equal than the value given for maximum cardinality.<\/li>\n
    • Maximum Cardinality: The maximum number of times this property needs to occur in any given type. It needs to be lower than the one defined in the schema, but higher or equal than the value given for minimum cardinality.<\/li>\n
    • Allowed Values: In this field you can define an enumeration of the actually allowed values. If the property uses an enumeration or code list, you will be able to activate or deactivate options from that enumeration or codelist.<\/li>\n
    • Allowed Types: If this field uses a Choice, Substitution Group or Union, you can limit the allowed types by deactivating options.<\/li>\n<\/ul>\n

      In addition, you can add any number of tagged values to each property. You can use any keys you want, but some control specific behavior:<\/p>\n

        \n
      • label-testcase: Label for this test case in the ETF Testsuite<\/code><\/li>\n
      • description-testcase: Description for this test case in the ETF Testsuite<\/code><\/li>\n
      • module-id: ID of the TestModule<\/code> group to which the test case generated for this property will be added<\/li>\n
      • example: Content to be used for the generation of XML sample files. If the property is a complex element, setting this value to "true" leads to the element being generated.<\/li>\n<\/ul>\n

        \"Consistency
        \nConsistency constraint editor:<\/strong> Consistency constraints are added to schema elements.<\/p>\n

        The second big block of functionality is to be found in the \u201cConsistency Conditions\u201d section of the profile. When you go there, you will be able to define various sets of rules, such as:<\/p>\n

          \n
        • If A exists, B must\/must not exist<\/li>\n
        • If A has value \u201cX\u201d, B must have value \u201cY\u201d<\/li>\n<\/ul>\n

          You can combine any number of such rules through logical operators (AND, OR, XOR). To each Consistency Condition, you can add a label and a description, as well as tagged values.<\/p>\n

          \"Generated
          \nGenerated documentation example.<\/strong> Profile documentation can be printed easily.<\/p>\n

          When you want to review your profile at any time, the differential documentation is a handy feature, especially in big schemas like the ISO 19139 schema. It hides all elements (types and properties) for which no change or addition was made in the profile, resulting in a compact, well-readable format.<\/p>\n

          Either the full profile or the differential documentation can be printed to any device, specifically to PDF. This enables you to get a document that you can send around to any user.<\/p>\n

          By going to the \u201cFiles\u201d section of the profile, you can also export sample XML instance documents for your profile.<\/p>\n