aboutsummaryrefslogtreecommitdiff
path: root/features
diff options
context:
space:
mode:
authorPjotr Prins2023-03-19 14:23:34 +0100
committerPjotr Prins2023-03-19 14:23:34 +0100
commit3417b300492288a35dab6a70209176dbfad50f35 (patch)
tree933acb21fb46d6eb6c1b9399f9f6d0d6dbd59904 /features
parente5b0845d2e737e503e56b42fa6d1f20ef289fdf1 (diff)
downloadgn-docs-3417b300492288a35dab6a70209176dbfad50f35.tar.gz
Bringing in relationships to GN data
Diffstat (limited to 'features')
-rw-r--r--features/data-structures.md37
1 files changed, 37 insertions, 0 deletions
diff --git a/features/data-structures.md b/features/data-structures.md
index 8c9f820..380a775 100644
--- a/features/data-structures.md
+++ b/features/data-structures.md
@@ -152,3 +152,40 @@ groups).
However, it would be cool to compare differences in gene expression in
the liver of BXD mice, HXD rats, and GTEx humans as a function of sex
and age.
+
+## RDF and relationship databases
+
+Naming is hard. Properties might have been more descriptive than attributes. But is
+a publication or a cage name a property or attribute for individual
+mouse? Not really. RDFS has vocabulary for such
+
+=> https://www.sti-innsbruck.at/sites/default/files/courses/fileadmin/documents/semweb13-14/SW-Lecture7.pdf
+
+I think, rather than bringing it in its one term we should be using relationships. So a publication would be a property of trait and therefore of group.
+
+* publication belongs to trait
+* individual partOf trait
+
+That way publications are connected to individual mouse.
+
+* trait belongs to group
+
+That way publications are connected to group
+
+That also makes the ownership path clear. Publications are handled at the trait level, not at the group level. This makes the discussion around how attributes are handled *much* clearer. Meanwhile
+
+* individual partOf epoch
+* status partOf individual
+
+Status is also arbitrary. Here status might be individualLocation or
+something more descriptive. I.e.
+
+* individual hasLocation location
+
+But it is also clear that the 'status' attribute is handled at the individual level and not at the group level. Maybe I get this wrong, but then we can decide at what level 'status' belongs for editing. Right?
+
+Anyway, you can see I am talking relationships that are descriptive and can be parsed by AI. Also this brings out where today's attributes belong.
+
+Anything enumerable can be used as a covariate, that includes location, handler etc.
+
+The RRID is a strain level property that we display as if it is an individual level property.