4.2. Tooling for creating AFD-definitions

AOS is part of a suite of support tools developed by SIVI to facilitate working with AFD Schemas, collectively known as AFD Online.
Alongside AOS, AFD Online encompasses tools such as AFD 1.0 Online, AFD 2.0 Online, Validate, Certify and Register.

SIVI has introduced the ‘AFD Online Samenstellen’ (AOS, AFD Online Composing) tool, to aid in the implementation of the AFD definition Standard. This tool enables the creation of AFD-definitions in a standardized manner. Currently, the tool offers:

• XML Schema and XPath validation rules for AFD 1.0-definitions.
• JSON Schema and JMESPath validation rules for AFD 2.0-definitions.
  

Baselines

Users initiating the composition of an AFD-definition in AOS begin by selecting a baseline. Baselines are based on an AFD structure and contain a subset of entities and attributes within AFD, applicable to a certain domain (e.g. motor vehicle or income). SIVI preselects the entities and attributes that are part of a certain baseline, simplifying the user experience by presenting only relevant data elements and reducing the likelihood of errors. Baselines for AFD 1.0 and AFD 2.0 are distinct, reflecting the differing setups of their respective data catalogs.

AFD 1.0 baselines are based on the message types in AFD 1.0 (e.g. contract message (contractbericht)) and consist of (AFD 1.0) entities and attributes already defined with specific data types and format restrictions (e.g., alphanumeric fields of 20 positions)
AFD 2.0 baselines, on the other hand, are based on AFD structures (e.g. policyStructure), entities, entityTypes and attributes, following JSON data types without format restrictions (e.g. string or integer).

Baselines are categorized by:

• SIVI Community (e.g. AFD or AFD 2.0)
• Message structure (e.g. Contractdocument or policyStructure )
• Domain (e.g. ‘Aansprakelijkheid’ (liability) or General)
  

Examples of baselines include:

• AFD, Contractdocument, Motorrijtuigen
• AFD 2.0, policyStructure, motorVehicle
• AFD 2.0, claimStructure, General
  

Upon request, SIVI can create new baselines: particularly if a user seeks to develop an AFD-definition based on a structure or a domain, not yet covered by existing frameworks.
Baselines are not available for download, but can be obtained upon request in XML Schema (AFD 1.0) or JSON Schema (AFD 2.0) format.

Functions

The AFD-definition Standard is based on the premise of processing a set of data within specific functions. Examples of these functions include:

• Registering a policy
• Requesting a premium
• Providing a set of acceptance rules upon request
  

AOS is structured in a similar manner. An AFD-definition is created for a product or service based on the requested functions. Within a single AFD-definition, it’s possible to define functions associated with a product or service. Each function within an AFD-definition is allocated its own (partial) AFD-definition. For instance, consider the product “Gemak Verzekerd”, which is a motor vehicle insurance comprising functions such as ‘newContract_request’ and ‘newContract_response’. The AFD-definition for the ‘Gemak Verzekerdl’ product then contains two partial AFD definitions: one for ‘newContract_request’ and one for ‘newContract_response’. Further details regarding AFD-definition files are provided in the Collection of AFD definition files section.