Actions
Question #1682
closed
SKOS broad match
Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
2022-04-04
Estimated time:
Description
Next to close and exact match, I would be very beneficial if we also implement https://www.w3.org/2009/08/skos-reference/skos.html#broadMatch SKOS broad Match as a selection for reference systems entries.
This would allow linking narrower types to a broader one if there is no matching close or exaxt match.
We would need this e.g. for the ARIADNE Plus Aggregation.
Thanks in Advance!
Updated by Stefan Eichert about 2 years ago
Would this work:
INSERT INTO model.entity (cidoc_class_code, name, openatlas_class_name, description) VALUES ('E55', 'broad match', 'type', 'is used to state a hierarchical mapping link between two conceptual resources in different concept schemes');
INSERT INTO model.link (property_code, range_id, domain_id) VALUES
('P127', (SELECT id FROM model.entity WHERE name = 'External reference match'), (SELECT id FROM model.entity WHERE name='broad match'));
Updated by Alexander Watzinger about 2 years ago
Sorry but the discussion about extending our used SKOS terms is now spawning over multiple issues, see #1674. We definitely should meet about this.
Updated by Bernhard Koschiček-Krombholz almost 2 years ago
- Tracker changed from Feature to Question
- Status changed from New to Closed
Discussed in the developer meeting, we closed this question since we already have this indirectly with our type hierarchy.
Actions