Appearance
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 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:
| Field | Source / Predicate | Description | Example |
|---|---|---|---|
| Voorkeursterm | term.name / skos:prefLabel | Official preferred term | Pand |
| Definitie | term.description / skos:definition | Formal concept definition | Kleinste zelfstandig toegankelijke bouwkundige eenheid. |
| Toelichting | term.additionalInformation / skos:scopeNote | Contextual notes | Geldt niet voor tijdelijke bouwwerken. |
| Uitleg | xFields.nlsbb_uitleg / rdfs:comment | Plain-language explanation for non-experts | Een echt gebouw met een dak en muren. |
| Synoniemen | term.synonyms / skos:altLabel | Alternative terms | Bouwwerk, Gebouweenheid |
| Zoekterm | xFields.nlsbb_zoekterm / skos:hiddenLabel | Search keywords or common spelling variants | woning, bedrijfspand |
| Voorbeeld | xFields.nlsbb_voorbeeld / skos:example | Practical example | Een eengezinswoning of een kantoorgebouw. |
| Bron | xFields.nlsbb_bron / dcterms:source | Bibliographic or legal citation (URL or text) | https://wetten.overheid.nl/BWBR0024779 |
| Exacte overeenkomst | xFields.nlsbb_exactMatch / skos:exactMatch | URI of exact matching concept in an external scheme | https://schema.org/Building |
| Nauwe overeenkomst | xFields.nlsbb_closeMatch / skos:closeMatch | URI of closely related concept in an external scheme | https://schema.org/Place |
| Status | xFields.nlsbb_status / adms:status | Lifecycle state | Vastgesteld |
| Persistent URI | xFields.nlsbb_uri | Explicit persistent URI | https://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:broaderandskos:narrower, plus ISO 25964isothes:broaderGenericandisothes:narrowerGeneric.
Partitief (Part-Whole)
- Labels:
Partitief (is onderdeel van)orPartitief (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:broaderPartitiveandisothes:narrowerPartitive, along withskos:broaderandskos:narrower.
Associatief (Related)
- Label:
Gerelateerd - Appearance: Purple line.
- Semantics: Symmetric semantic connection between two concepts.
- Export: Emitted as symmetric
skos:relatedin both directions.
4. Lifecycle Status (ADMS)
Use the Status dropdown on concepts to indicate their lifecycle stage:
| Status Value | Meaning | Exported ADMS URI |
|---|---|---|
| Concept | Draft / In development | http://purl.org/adms/status/UnderDevelopment |
| Voorgesteld | Proposed for review | http://purl.org/adms/status/UnderDevelopment |
| Vastgesteld | Formally approved / valid | http://purl.org/adms/status/Completed |
| Vervallen | Deprecated / historical | http://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.
- Configuring Base URI: In , replace the default
termboard.comnamespace with your organization's domain URI (e.g.https://organisatie.nl/id/begrip/). Termboard will remember this base URI for future exports. - Freezing URIs: In the export dialog, click Freeze Generated URIs to Concepts. This populates each concept's
nlsbb_urifield with its current full URI. - Once frozen, renaming a term label will never change its published URI.
6. Exporting to Turtle (.ttl)
To export your begrippenkader:
- Open .
- 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
- Output Format:
- Expand Preview to inspect the generated Turtle document.
- Verify the concept statistics at the bottom of the dialog.
- Click Export to download your
<model-name>.ttlfile.
Export Output Structure
The exported Turtle file contains:
- Standard namespace prefixes (
skos,isothes,adms,dcterms,rdfs). - A
skos:ConceptSchemerepresenting the begrippenkader with title, creator, and modification date. - All concepts declared as
skos:Conceptreferencing the scheme viaskos:inScheme. - Top-level concepts automatically identified and linked via
skos:hasTopConceptandskos:topConceptOf. - All semantic relationships mapped to SKOS and ISO 25964 properties.
- All status states mapped to ADMS URIs.