glam/schemas/20251121/linkml/modules/classes/Jurisdiction.yaml
kempersc fc405445c6 Refactor and update schema definitions
- Removed obsolete slots: `has_or_had_custodian_observation`, `provider`, and `specificity_annotation`.
- Updated `has_or_had_score` slot to use `SpecificityScore` class and modified its description and examples.
- Added new slots: `end_seconds`, `end_time`, `has_archive_path`, `has_or_had_custodian_name`, `protocol_name`, and `protocol_version`.
- Introduced a script `check_annotation_types.py` to validate the presence and structure of `custodian_types` in YAML files.
- Added a script `update_specificity.py` to automate updates related to `SpecificityAnnotation` to `SpecificityScore`.
2026-02-01 19:55:38 +01:00

76 lines
6 KiB
YAML

id: https://nde.nl/ontology/hc/class/jurisdiction
name: jurisdiction
title: Jurisdiction Class
prefixes:
linkml: https://w3id.org/linkml/
hc: https://nde.nl/ontology/hc/
gleif_base: https://www.gleif.org/ontology/Base/
lcc_cr: https://www.omg.org/spec/LCC/Countries/CountryRepresentation/
schema: http://schema.org/
imports:
- linkml:types
- ../enums/JurisdictionTypeEnum
- ../enums/LegalSystemTypeEnum
- ../metadata
- ../slots/country
- ../slots/has_or_had_code
- ../slots/has_or_had_description
- ../slots/has_or_had_geographic_subdivision
- ../slots/has_or_had_identifier
- ../slots/has_or_had_score
- ../slots/jurisdiction_id
- ../slots/jurisdiction_type
- ../slots/legal_system_type
- ../slots/settlement
classes:
Jurisdiction:
class_uri: lcc_cr:GeographicRegion
description: "A distinct area subject to a government and set of laws.\n\n**CRITICAL DISTINCTION: Jurisdiction vs ServiceArea**\n\nJurisdiction and ServiceArea are fundamentally different concepts:\n\n| Aspect | Jurisdiction | ServiceArea |\n|--------|--------------|-------------|\n| **Definition** | Geographic area where specific LAWS AND POLICIES apply | Geographic area where a SPECIFIC custodian operates (\"werkgebied\") |\n| **Scope** | Legal framework scope | Operational territory |\n| **Sharing** | SHARED by multiple custodians operating under same legal framework | UNIQUE to each custodian |\n| **Example** | Dutch national law creates a jurisdiction for all municipal archives in NL | Each municipal archive has its own municipality as service area |\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: Jurisdiction = NL (Dutch national law), ServiceArea = Haarlem + surrounding municipalities\n- Gemeentearchief Amsterdam: Jurisdiction = NL (same!), ServiceArea = Amsterdam municipality\n- Regionaal Archief Tilburg: Jurisdiction = NL (same!), ServiceArea = Tilburg region\n\nAll three share the SAME jurisdiction but have DIFFERENT service areas.\n\n**Purpose of Jurisdiction**:\n\nJurisdictions define the LEGAL scope of registration authorities and trade registers.\nUnlike pure geographic classes (Country, Subregion, Settlement), Jurisdiction captures\nthe legal framework applicable to organizations - which laws govern their registration,\ndissolution, governance, and archival obligations.\n\n**Ontology Alignment:**\n\n- lcc_cr:GeographicRegion - OMG Languages Countries and Codes (used by GLEIF)\n- gleif_base:hasLegalJurisdiction - links entities to their jurisdiction of registration\n\
- gleif_base:hasCoverageArea - geographic scope of registration authorities\n\n**Types of Jurisdiction:**\n\n1. **National Jurisdiction**: Entire country (e.g., Netherlands, Japan)\n - Maps to Country class\n - Most common for trade registers\n\n2. **Subnational Jurisdiction**: State, province, region (e.g., Bavaria, New York)\n - Maps to Subregion class\n - Common for federal systems (USA, Germany, Canada, Australia)\n\n3. **Municipal Jurisdiction**: City-level (e.g., City of London, Hong Kong)\n - Maps to Settlement class\n - For city-states and special administrative regions\n\n4. **Supranational Jurisdiction**: Multi-country (e.g., European Union, OHADA)\n - Represented via supranational identifier\n - Relevant for EU-wide legal forms (SE, SCE, EEIG)\n\n**GLEIF Integration:**\n\nThis class aligns with GLEIF ontology concepts:\n- gleif_base:hasLegalJurisdiction - jurisdiction where entity is registered\n- gleif_base:hasCoverageArea - geographic scope of registration\
\ authority\n\n**Examples:**\n\n- Netherlands (national): authority=KvK, covers all NL legal entities\n- Bavaria (subnational): Handelsregister M\xFCnchen, covers Bavarian businesses\n- Hong Kong (special region): Companies Registry, covers HK companies\n- European Union (supranational): European Company (SE) registration\n\nSee also:\n- TradeRegister: Business registers operating within a jurisdiction\n- RegistrationAuthority: Organizations maintaining registers\n- LegalForm: Legal forms valid within specific jurisdictions\n- **ServiceArea**: The operational territory (\"werkgebied\") of a specific custodian - NOT to be confused with Jurisdiction!\n"
exact_mappings:
- lcc_cr:GeographicRegion
close_mappings:
- schema:AdministrativeArea
related_mappings:
- gleif_base:hasLegalJurisdiction
- gleif_base:hasCoverageArea
slots:
- country
- has_or_had_description
- has_or_had_identifier
- jurisdiction_id
- jurisdiction_type
- legal_system_type
- settlement
- has_or_had_geographic_subdivision
- has_or_had_code
- has_or_had_score
slot_usage:
jurisdiction_id:
identifier: true
required: true
jurisdiction_type:
required: true
country:
required: false
has_or_had_geographic_subdivision:
required: false
settlement:
required: false
has_or_had_code:
required: false
comments:
- Jurisdiction is the geographic area where specific LAWS AND POLICIES apply
- SHARED by multiple custodians operating under the same legal framework
- 'Example: All Dutch municipal archives share the same NL jurisdiction (Archiefwet applies to all)'
- NOT to be confused with ServiceArea, which is the operational territory ('werkgebied') UNIQUE to each custodian
- 'Jurisdiction answers: ''Under which legal framework does this entity operate?'''
- 'ServiceArea answers: ''Which geographic area does this specific custodian serve?'''
see_also:
- https://www.gleif.org/en/about-lei/code-lists/registration-authorities-list
annotations:
specificity_score: 0.1
specificity_rationale: Generic utility class/slot created during migration
custodian_types: "['*']"