glam/schemas/20251121/linkml/modules/classes/RejectedGoogleMapsData.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

35 lines
1.3 KiB
YAML

id: https://nde.nl/ontology/hc/classes/RejectedGoogleMapsData
name: RejectedGoogleMapsData
title: RejectedGoogleMapsData
prefixes:
linkml: https://w3id.org/linkml/
hc: https://nde.nl/ontology/hc/
schema: http://schema.org/
prov: http://www.w3.org/ns/prov#
xsd: http://www.w3.org/2001/XMLSchema#
imports:
- linkml:types
default_range: string
classes:
RejectedGoogleMapsData:
description: "Rejected Google Maps data preserved for audit trail, documenting\
\ place data that was fetched but rejected due to validation failures (e.g.,\
\ country mismatch). Includes place ID, name, address, coordinates, expected\
\ vs returned country, and timestamps.\nOntology mapping rationale: - class_uri\
\ is prov:Entity because this is data preserved for\n audit purposes with full\
\ provenance\n- close_mappings includes prov:InvalidatedEntity as this data\
\ was\n explicitly rejected/invalidated\n- related_mappings includes schema:Place\
\ as the underlying data\n describes a geographic place"
class_uri: prov:Entity
close_mappings:
- prov:InvalidatedEntity
related_mappings:
- schema:Place
annotations:
specificity_score: 0.1
specificity_rationale: Generic utility class/slot created during migration
custodian_types: '[''*'']'
slots:
- name
- latitude
- longitude