Skip to content

Modeling NL-SBB Begrippenkaders and Turtle Export ​

This guide explains how to model domain concept schemes according to the Nederlandse Standaard voor het Beschrijven van Begrippen (NL-SBB) and export them as standards-compliant Turtle (.ttl) files in Termboard.

What is NL-SBB? ​

NL-SBB is the official Dutch government standard for describing concepts, taxonomies, and thesauri, maintained by Geonovum. It is formally listed as Verplicht ("Pas toe of leg uit") on the Forum Standaardisatie list for public sector organizations (Kadaster, DSO, municipalities, provinces, ministries).

Termboard provides an end-to-end visual workflow for NL-SBB:

  • A dedicated NL-SBB Domain Profile with Dutch terminology and standardized metadata attributes.
  • Native semantic relations adhering to SKOS and ISO 25964 (isothes).
  • Standardized lifecycle states mapped to ADMS status URIs.
  • Persistent URI locking adhering to the Nederlandse URI-strategie.
  • One-click export to RDF Turtle (.ttl).

1. Activating the NL-SBB Domain Profile ​

To work with NL-SBB, switch your document to the NL-SBB profile.

From the Top Menu Bar ​

Click on the profile dropdown in the top navigation bar and select NL-SBB (Begrippenkader).

In Document Properties ​

Alternatively, open File > Document Properties and change Domain Profile to NL-SBB (Begrippenkader).

When the profile is activated, Termboard automatically seeds the required NL-SBB metadata fields into your document.


2. Term Types and Metadata ​

In the NL-SBB profile, nodes represent concepts:

  • Begrip (skos:Concept): Standard domain concept.
  • Begrip (abstract) (skos:Concept): Abstract or high-level concept.
  • Collectie (skos:Collection): Visual compound group used to cluster related concepts.

NL-SBB Concept Attributes ​

Each concept has access to standard Termboard properties plus dedicated NL-SBB extra fields in the Term Sidebar:

FieldSource / PredicateDescriptionExample
Voorkeurstermterm.name / skos:prefLabelOfficial preferred termPand
Definitieterm.description / skos:definitionFormal concept definitionKleinste zelfstandig toegankelijke bouwkundige eenheid.
Toelichtingterm.additionalInformation / skos:scopeNoteContextual notesGeldt niet voor tijdelijke bouwwerken.
UitlegxFields.nlsbb_uitleg / rdfs:commentPlain-language explanation for non-expertsEen echt gebouw met een dak en muren.
Synoniementerm.synonyms / skos:altLabelAlternative termsBouwwerk, Gebouweenheid
ZoektermxFields.nlsbb_zoekterm / skos:hiddenLabelSearch keywords or common spelling variantswoning, bedrijfspand
VoorbeeldxFields.nlsbb_voorbeeld / skos:examplePractical exampleEen eengezinswoning of een kantoorgebouw.
BronxFields.nlsbb_bron / dcterms:sourceBibliographic or legal citation (URL or text)https://wetten.overheid.nl/BWBR0024779
Exacte overeenkomstxFields.nlsbb_exactMatch / skos:exactMatchURI of exact matching concept in an external schemehttps://schema.org/Building
Nauwe overeenkomstxFields.nlsbb_closeMatch / skos:closeMatchURI of closely related concept in an external schemehttps://schema.org/Place
StatusxFields.nlsbb_status / adms:statusLifecycle stateVastgesteld
Persistent URIxFields.nlsbb_uriExplicit persistent URIhttps://organisatie.nl/id/begrip/pand

3. Modeling Semantic Relations ​

NL-SBB defines specific relation types with strict semantics:

Generiek (Generalization / Is-a) ​

  • Label: Generiek (is een soort)
  • Appearance: Solid blue line with triangle arrow.
  • Semantics: Connect child concept (source) to parent concept (target).
  • Export: Emitted as skos:broader and skos:narrower, plus ISO 25964 isothes:broaderGeneric and isothes:narrowerGeneric.

Partitief (Part-Whole) ​

  • Labels: Partitief (is onderdeel van) or Partitief (maakt deel uit van)
  • Appearance: Red/green line with diamond arrow.
  • Semantics: Connect whole concept (source) to constituent part (target).
  • Export: Emitted as ISO 25964 isothes:broaderPartitive and isothes:narrowerPartitive, along with skos:broader and skos:narrower.
  • Label: Gerelateerd
  • Appearance: Purple line.
  • Semantics: Symmetric semantic connection between two concepts.
  • Export: Emitted as symmetric skos:related in both directions.

4. Lifecycle Status (ADMS) ​

Use the Status dropdown on concepts to indicate their lifecycle stage:

Status ValueMeaningExported ADMS URI
ConceptDraft / In developmenthttp://purl.org/adms/status/UnderDevelopment
VoorgesteldProposed for reviewhttp://purl.org/adms/status/UnderDevelopment
VastgesteldFormally approved / validhttp://purl.org/adms/status/Completed
VervallenDeprecated / historicalhttp://purl.org/adms/status/Deprecated

5. Persistent URIs & The Dutch URI Strategy ​

Under the Dutch Government URI Strategy (NEN 3610), concept URIs must remain stable over time and not change if a term is renamed.

  1. Configuring Base URI: In File > Export > OWL Ontology, replace the default termboard.com namespace with your organization's domain URI (e.g. https://organisatie.nl/id/begrip/). Termboard will remember this base URI for future exports.
  2. Freezing URIs: In the export dialog, click Freeze Generated URIs to Concepts. This populates each concept's nlsbb_uri field with its current full URI.
  3. Once frozen, renaming a term label will never change its published URI.

6. Exporting to Turtle (.ttl) ​

To export your begrippenkader:

  1. Open File > Export > OWL Ontology.
  2. When the NL-SBB profile is active, the dialog automatically defaults to:
    • Output Format: Turtle (.ttl)
    • Vocabulary Style: NL-SBB (Geonovum SKOS-AP-NL, Turtle)
    • Language Tag: nl
  3. Expand Preview to inspect the generated Turtle document.
  4. Verify the concept statistics at the bottom of the dialog.
  5. Click Export to download your <model-name>.ttl file.

Export Output Structure ​

The exported Turtle file contains:

  • Standard namespace prefixes (skos, isothes, adms, dcterms, rdfs).
  • A skos:ConceptScheme representing the begrippenkader with title, creator, and modification date.
  • All concepts declared as skos:Concept referencing the scheme via skos:inScheme.
  • Top-level concepts automatically identified and linked via skos:hasTopConcept and skos:topConceptOf.
  • All semantic relationships mapped to SKOS and ISO 25964 properties.
  • All status states mapped to ADMS URIs.