glam/frontend/public/schemas/20251121/linkml/modules/classes/ResearchSourceData.yaml
kempersc 1fb924c412 feat: add ontology mappings to LinkML schema and enhance entity resolution
Schema enhancements (443 files):
- Add class_uri with proper ontology references (schema:, prov:, skos:, rico:)
- Add close_mappings, related_mappings per Rule 50 convention
- Replace stub hc: slot_uri with standard predicates (dcterms:identifier, skos:prefLabel)
- Improve descriptions with ontology mapping rationale
- Add prefixes blocks to all schema modules

Entity Resolution improvements:
- Add entity_resolution module with email semantics parsing
- Enhance build_entity_resolution.py with email-based matching signals
- Extend Entity Review API with filtering by signal types and count
- Add candidates caching and indexing for performance
- Add ReviewLoginPage component

New rules and documentation:
- Add Rule 51: No Hallucinated Ontology References
- Add .opencode/rules/no-hallucinated-ontology-references.md
- Add .opencode/rules/slot-ontology-mapping-reference.md
- Add adms.ttl and dqv.ttl ontology files

Frontend ontology support:
- Add RiC-O_1-1.rdf and schemaorg.owl to public/ontology
2026-01-13 13:51:02 +01:00

85 lines
2.7 KiB
YAML

# ResearchSourceData - Structured data from a research source
# Extracted from custodian_source.yaml per Rule 38 (modular schema files)
# Extraction date: 2026-01-08
id: https://nde.nl/ontology/hc/classes/ResearchSourceData
name: ResearchSourceData
title: ResearchSourceData
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:
ResearchSourceData:
description: >-
Structured data from WHOIS research sources including domain registrant
information (name, address, city, state, country, postal code),
organization, contact details (email, phone), and domain lifecycle
dates (creation, update, expiration, registration). Used for
institutional identity verification.
Ontology mapping rationale:
- class_uri is prov:Entity because this is structured data extracted
from a WHOIS research source with provenance implications
- close_mappings includes schema:Organization as the data primarily
describes organizational registrant information
- related_mappings includes prov:PrimarySource as WHOIS is an
authoritative data source
class_uri: prov:Entity
close_mappings:
- schema:Organization
related_mappings:
- prov:PrimarySource
attributes:
registrant_name:
range: string
description: WHOIS registrant name
registrant_address:
range: string
description: WHOIS registrant address
registrant_city:
range: string
description: WHOIS registrant city
registrant_state:
range: string
description: WHOIS registrant state/province
registrant_country:
range: string
description: WHOIS registrant country
registrant_postal_code:
range: string
description: WHOIS registrant postal code
organization:
range: string
description: Organization name
email:
range: string
description: Contact email
phone:
range: string
description: Contact phone
creation_date:
range: string
description: Domain creation date
updated_date:
range: string
description: Domain updated date
expiration_date:
range: string
description: Domain expiration date
domain_registered:
range: string
description: Domain registration date
registry:
range: string
description: Domain registrar name