kempersc/glam
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
glam/schemas/20251121/linkml/modules/classes/ServiceArea.yaml
kempersc 6c3fa6b5a3 Remove deprecated slots and add new slot definitions for enhanced data modeling 
- Deleted obsolete slot definitions for work_location and workshop_space.
- Introduced new TaxonName class to represent scientific taxonomic names with detailed attributes.
- Archived existing slots related to surname_prefix, target_name, taxon_name, terminal_count, text_region_count, title, title_proper, total_chapter, total_characters_extracted, total_connections_extracted, track_name, transcript_format, traveling_venue, type_label, type_status, typical_responsibility, unesco_domain, unesco_inscription_year, unesco_list_status, uniform_title, unit_name, used_by_custodian, uv_filtered_required, valid_from_geo, valid_to_geo, validation_status, variant_of_name, verification_date, viability_status, within_auxiliary_place, and within_place.
- Updated slot descriptions and structures to improve clarity and compliance with standards.
2026-01-15 11:42:35 +01:00

182 lines
9.9 KiB
YAML
Raw Blame History

id: https://nde.nl/ontology/hc/class/ServiceArea
name: service_area_class
title: ServiceArea Class
prefixes:
schema: http://schema.org/
tooi: https://identifier.overheid.nl/tooi/def/ont/
geosparql: http://www.opengis.net/ont/geosparql#
dcterms: http://purl.org/dc/terms/
org: http://www.w3.org/ns/org#
prov: http://www.w3.org/ns/prov#
rico: https://www.ica.org/standards/RiC/ontology#
imports:
- linkml:types
- ../metadata
- ./GeoSpatialPlace
- ./CustodianLegalStatus
- ./Country
- ./Subregion
- ./Settlement
- ./TimeSpan
- ../enums/ServiceAreaTypeEnum
- ../slots/temporal_extent
- ../slots/served_by
- ../slots/covers_country
- ../slots/contains_or_contained_covers_settlement
- ../slots/cover_or_covered_subregion
- ../slots/halc_adm1_code
- ../slots/halc_adm2_name
- ../slots/has_boundary
- ../slots/is_historical_boundary
- ../slots/service_area_description
- ../slots/service_area_id
- ../slots/service_area_name
- ../slots/service_area_type
- ../slots/source_dataset
- ../slots/specificity_annotation
- ../slots/template_specificity
- ./SpecificityAnnotation
- ./TemplateSpecificityScores
classes:
ServiceArea:
class_uri: schema:AdministrativeArea
description: "Geographic area served by a heritage custodian institution.\n\n**Dutch Term**: \"Werkgebied\" - the operational\
\ territory of an archive,\nlibrary, or museum where they provide services and collect materials.\n\n**CRITICAL DISTINCTION:\
\ ServiceArea vs Jurisdiction**\n\nServiceArea and Jurisdiction are fundamentally different concepts:\n\n| Aspect |\
\ ServiceArea | Jurisdiction |\n|--------|-------------|--------------|\n| **Definition** | Geographic area where a\
\ SPECIFIC custodian operates (\"werkgebied\") | Geographic area where specific LAWS AND POLICIES apply |\n| **Scope**\
\ | Operational territory | Legal framework scope |\n| **Sharing** | UNIQUE to each custodian | SHARED by multiple custodians\
\ operating under same legal framework |\n| **Example** | Each municipal archive has its own municipality as service\
\ area | Dutch national law creates a jurisdiction for all municipal archives in NL |\n\n**Key Example**:\n\nA national\
\ law (e.g., Archiefwet) creates a JURISDICTION covering the entire Netherlands.\nALL Dutch municipal archives operate\
\ within this SAME jurisdiction - they share it!\nBut each municipal archive has a DIFFERENT ServiceArea (werkgebied)\
\ - typically\ntheir own municipality or region.\n\n- Noord-Hollands Archief: ServiceArea = Haarlem + surrounding municipalities,\
\ Jurisdiction = NL (Dutch national law)\n- Gemeentearchief Amsterdam: ServiceArea = Amsterdam municipality, Jurisdiction\
\ = NL (same!)\n- Regionaal Archief Tilburg: ServiceArea = Tilburg region, Jurisdiction = NL (same!)\n\nAll three have\
\ DIFFERENT service areas but share the SAME jurisdiction.\n\n**Purpose**:\n\nServiceArea captures the geographic jurisdiction/coverage\
\ of heritage institutions:\n\n1. **Archives**: The municipalities whose records they manage\n - Provincial archives\
\ cover entire province\n - Regional archives cover specific municipalities\n - Municipal archives cover single\
\ city\n\n2. **Libraries**: The service district for lending/access\n - Public libraries serve defined municipalities\n\
\ - Academic libraries may have national scope\n\n3. **Museums**: Geographic scope of collection mandate\n - Regional\
\ museums collect from specific area\n - National museums have country-wide scope\n\n| Ontology | Class/Property |\
\ Usage |\n|----------|----------------|-------|\n| **Schema.org** | `schema:areaServed` | Primary property linking\
\ Organization → ServiceArea |\n| **Schema.org** | `schema:AdministrativeArea` | Class for geographic regions under\
\ jurisdiction |\n| **TOOI** | `tooi:BestuurlijkeRuimte` | Dutch government pattern for administrative spaces |\n| **TOOI**\
\ | `tooi:JuridischeRuimte` | Operational/effect area of legal instruments |\n| **GeoSPARQL** | `geosparql:Feature`\
\ | Geospatial representation base class |\n| **W3C Org** | `org:hasSite` | Related concept for organizational presence\
\ |\n\n**Relationship to Other Classes**:\n\n```\nCustodianLegalStatus --schema:areaServed--> ServiceArea\n \
\ |\n ├──> GeoSpatialPlace (boundary\
\ polygon)\n ├──> Country (covered country)\n \
\ ├──> Subregion (covered provinces)\n └──> Settlement\
\ (covered cities)\n```\n\n**Historical vs Current Boundaries**:\n\nService areas may change over time due to:\n- Municipal\
\ mergers (gemeentelijke herindeling)\n- Archive reorganizations\n- Administrative boundary changes\n\nUse `is_historical_boundary:\
\ true` and `temporal_extent` to track historical areas.\n\n**Display Styling**:\n\n| Boundary Type | Border Color |\
\ Fill Color | Opacity |\n|---------------|--------------|------------|---------|\n| Current | Blue (#3498db) | Blue\
\ (#3498db) | 20% |\n| Historical | Brown (#8b4513) | Goldenrod (#daa520) | 20% |\n\n**Example - Noord-Hollands Archief**:\n\
\nThe NHA serves multiple municipalities in Noord-Holland province.\nBefore the 2001 merger, Gemeentearchief Haarlem\
\ and Rijksarchief Noord-Holland\nhad separate service areas. After merger, the combined service area includes\nboth\
\ the city and provincial scope.\n"
exact_mappings:
- schema:AdministrativeArea
close_mappings:
- tooi:BestuurlijkeRuimte
- tooi:JuridischeRuimte
- geosparql:Feature
related_mappings:
- schema:Place
- dcterms:Location
- rico:Place
slots:
- covers_country
- contains_or_contained_covers_settlement
- cover_or_covered_subregion
- halc_adm1_code
- halc_adm2_name
- has_boundary
- is_historical_boundary
- served_by
- service_area_description
- service_area_id
- service_area_name
- service_area_type
- source_dataset
- specificity_annotation
- template_specificity
- temporal_extent
slot_usage:
service_area_id:
identifier: true
required: true
examples:
- value: https://nde.nl/ontology/hc/servicearea/nha-werkgebied
- value: https://nde.nl/ontology/hc/servicearea/vianen-historical-1500
service_area_name:
required: true
service_area_type:
required: false
comments:
- Represents the geographic SERVICE AREA ('werkgebied') of a heritage custodian
- UNIQUE to each custodian - each archive/library/museum has its own service area
- NOT to be confused with Jurisdiction, which is the legal framework scope SHARED by multiple custodians
- 'Example: All Dutch municipal archives share the same Jurisdiction (NL/Archiefwet) but each has a DIFFERENT ServiceArea'
- 'ServiceArea answers: ''Which geographic area does this specific custodian serve?'''
- 'Jurisdiction answers: ''Under which legal framework does this entity operate?'''
- Links to GeoSpatialPlace for actual boundary polygons
- Supports historical boundaries via is_historical_boundary and temporal_extent
- HALC fields (halc_adm1_code, halc_adm2_name) enable historical boundary lookups
- 'Display styling: current=blue, historical=brown/goldenrod'
- Archives use werkgebied to define which municipalities they serve
- Museums may have service areas indicating collection geographic scope
see_also:
- https://schema.org/areaServed
- https://schema.org/AdministrativeArea
- https://identifier.overheid.nl/tooi/def/ont/
- http://www.opengis.net/ont/geosparql
examples:
- value:
service_area_id: https://nde.nl/ontology/hc/servicearea/nha-werkgebied
service_area_name: Noord-Hollands Archief Werkgebied
service_area_description: Service area covering Haarlem and surrounding municipalities in Noord-Holland province
service_area_type: REGIONAL
covers_country:
alpha_2: NL
cover_or_covered_subregion:
- iso_3166_2_code: NL-NH
name: Noord-Holland
contains_or_contained_covers_settlement:
- geonames_id: 2755003
name: Haarlem
- geonames_id: 2754669
name: Heemskerk
has_boundary:
- geospatial_id: https://nde.nl/ontology/hc/geo/nha-boundary
geometry_type: MULTIPOLYGON
geometry_wkt: MULTIPOLYGON(((4.5 52.2, 5.0 52.2, 5.0 52.5, 4.5 52.5, 4.5 52.2)))
temporal_extent: # was: valid_from_geo
begin_of_the_begin: '2001-01-01'
is_historical_boundary: false
served_by: https://nde.nl/ontology/hc/legal/noord-hollands-archief
description: Current service area for Noord-Hollands Archief
- value:
service_area_id: https://nde.nl/ontology/hc/servicearea/vianen-historical-1500
service_area_name: Graafschap Vianen (Historical)
service_area_description: Historical territory of the County of Vianen, circa 1500
service_area_type: HISTORICAL
covers_country:
alpha_2: NL
has_boundary:
- geospatial_id: https://nde.nl/ontology/hc/geo/vianen-1500
geometry_type: POLYGON
source_dataset: HALC
temporal_extent: # was: valid_from_geo + valid_to_geo
begin_of_the_begin: '1500-01-01'
end_of_the_end: '1795-01-01'
is_historical_boundary: true
temporal_extent:
begin_of_the_begin: '1500-01-01'
end_of_the_end: '1795-01-01'
halc_adm1_code: VI
halc_adm2_name: Vianen
served_by: https://nde.nl/ontology/hc/legal/gemeentearchief-vianen
source_dataset: HALC Historical Boundaries 1500
description: Historical service area for Gemeentearchief Vianen based on 1500 territory
Reference in a new issue View git blame Copy permalink