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 fcd1c21c63 Add aliases and enhance slot definitions across various modules 
- Added new aliases for existing slots to improve clarity and usability, including:
  - has_deadline: has_embargo_end_date
  - has_extent: has_extent_text
  - has_fonds: has_fond
  - has_laboratory: conservation_lab
  - has_language: has_iso_code639_1, has_iso_code639_3
  - has_legal_basis: legal_basis
  - has_light_exposure: max_light_lux
  - has_measurement_unit: has_unit
  - has_note: has_custodian_observation
  - has_occupation: occupation
  - has_operating_hours: has_operating_hours
  - has_position: position
  - has_quantity: has_artwork_count, link_count
  - has_roadmap: review_date
  - has_skill: skill
  - has_speaker: speaker_label
  - has_specification: specification_url
  - has_statement: rights_statement_url, rights_statement
  - has_type: custodian_only
  - has_user_category: serves_visitors_only
  - hold_record_set: record_count
  - identified_by: has_index_number
  - in_period: has_period
  - in_place: has_place
  - in_series: has_series
  - measure: has_measurement
  - measured_on: measurement_date
  - organized_by: has_organizer
  - originate_from: has_origin
  - part_of: suborganization_of
  - published_on: has_publication_date
  - receive_investment: has_investment
  - related_to: connection_heritage_type
  - require: preservation_requirement
  - safeguarded_by: current_keeper, record_holder_note
  - state: states_or_stated
  - take_comission: takes_or_took_comission
  - take_place_at: takes_or_took_place_at
  - transmit_through: transmits_or_transmitted_through
  - warrant: warrants_or_warranted

- Introduced a new slot definition for evaluated_through to capture evaluation methodologies and review statuses.
2026-02-14 14:41:49 +01:00

142 lines
9.1 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
- ../enums/ServiceAreaTypeEnum
- ../metadata
- ../slots/contain_covers_settlement
- ../slots/cover_geographic_subdivision
- ../slots/cover_country
- ../slots/identified_by
- ../slots/has_label
- ../slots/has_score
- ../slots/has_boundary
- ../slots/provided_by
- ../slots/has_description
- ../slots/has_type
- ../slots/has_provenance
- ../slots/temporal_extent
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 \u2192 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 \u251C\u2500\u2500> GeoSpatialPlace (boundary polygon)\n \u251C\u2500\u2500> Country (covered country)\n \u251C\u2500\u2500> Subregion (covered provinces)\n \u2514\u2500\u2500> 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:
- cover_country
- contain_covers_settlement
- cover_geographic_subdivision
- identified_by
- has_label
- has_boundary
- provided_by
- has_description
- identified_by
- has_label
- has_type
- has_provenance
- has_score
- temporal_extent
slot_usage:
identified_by:
range: HALCAdm1Code
inlined: true
has_label:
range: HALCAdm2Name
inlined: true
identified_by:
identifier: true
required: true
examples:
- value: https://nde.nl/ontology/hc/servicearea/nha-werkgebied
- value: https://nde.nl/ontology/hc/servicearea/vianen-historical-1500
has_label:
required: true
has_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
cover_country:
alpha_2: NL
cover_geographic_subdivision:
- iso_3166_2_code: NL-NH
name: Noord-Holland
contain_covers_settlement:
- geonames_id: 2755003
name: Haarlem
- geonames_id: 2754669
name: Heemskerk
- geospatial_id: https://nde.nl/ontology/hc/geo/nha-boundary
geometric_extent:
- has_format:
has_value: MULTIPOLYGON(((4.5 52.2, 5.0 52.2, 5.0 52.5, 4.5 52.5, 4.5 52.2)))
has_type:
has_label: MULTIPOLYGON
temporal_extent:
begin_of_the_begin: '2001-01-01'
is_historical_boundary: false
served_by: https://nde.nl/ontology/hc/legal/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
cover_country:
alpha_2: NL
is_historical_boundary: true
temporal_extent:
begin_of_the_begin: '1500-01-01'
end_of_the_end: '1795-01-01'
identified_by:
identified_by: VI
has_label:
has_label: Vianen
served_by: https://nde.nl/ontology/hc/legal/gemeentearchief-vianen
source_dataset: HALC Historical Boundaries 1500
annotations:
specificity_score: 0.1
specificity_rationale: Generic utility class/slot created during migration
custodian_types: "['*']"
Reference in a new issue View git blame Copy permalink