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
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
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_Xintordfs:subClassOf X. (See rule below) See Kinds as rdfs:subClassOf #198partywill not returnpersonororganizationentities, but they are returned when inference rules are used.A member_of_kind BthenA rdf:type BA rdf:type BandB rdf:type hqdm:classthenA member_of_kind BA rdf:type kind_of_XthenA rdfs:subClassOf X(needs a rule instance for each kind_of_X)A rdfs:subClassOf XthenA rdf:type kind_of_X(also needs a rule instance for each kind_of_X).A rdfs:subClassOf BthenA has_superclass B.A has_superclass BthenA rdfs:subClassOf B.spatio_temporal_extent S is part_of_possible_world Pthenparts of S are part_of_possible_world P.A member_of BthenB rdf:type rdfs:Class.C is a classification of A as a member of BthenA member_of B.A member_of Bthen∃C: C is a classification of A as a member of B.A has_superclass Bthen∃S: S is a specialization such that A specialises BS is a specialization such that A specialises BthenA 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