Replies: 1 comment
-
As mentioned by @Fabalab and @GCHQDeveloper42 we should consider rules for inferring |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Improve the mapping of HQDM to RDF. This mapping is currently ad-hoc and there may be ways to improve it. This task will investigate the options and propose a way forward, assessing the impact on existing code and models.
kind_of_X
intordfs:subClassOf X
. (See rule below) See Kinds as rdfs:subClassOf #198party
will not returnperson
ororganization
entities, but they are returned when inference rules are used.A member_of_kind B
thenA rdf:type B
A rdf:type B
andB rdf:type hqdm:class
thenA member_of_kind B
A rdf:type kind_of_X
thenA rdfs:subClassOf X
(needs a rule instance for each kind_of_X)A rdfs:subClassOf X
thenA rdf:type kind_of_X
(also needs a rule instance for each kind_of_X).A rdfs:subClassOf B
thenA has_superclass B
.A has_superclass B
thenA rdfs:subClassOf B
.spatio_temporal_extent S is part_of_possible_world P
thenparts of S are part_of_possible_world P
.A member_of B
thenB rdf:type rdfs:Class
.C is a classification of A as a member of B
thenA member_of B
.A member_of B
then∃C: C is a classification of A as a member of B
.A has_superclass B
then∃S: S is a specialization such that A specialises B
S is a specialization such that A specialises B
thenA has_superclass B
.The main purpose of these rules is to unify the two different extension mechanisms provided for extending HQDM - sub-typing and by creating 'kinds'. In theory if these rules are used then one form of extension mechanism can be inferred from the other.
Beta Was this translation helpful? Give feedback.
All reactions