-
Notifications
You must be signed in to change notification settings - Fork 0
post composition annotation
Page to write about the post composition of annotations for data in supplemental .ttl files.
I had been experimenting with post com-positionally creating annotations, for example for the global_chlorophyll_a.csv
dataset, when annotating a data column about haptophyta chlorophyll a, instead of making a new class for haptophyta chlorophyll a, I made a blank node by which to annotate the column. The blank node works and is parsed into the conjunctive graph in a python script.
#HaptophytaChlA column is about an owl class which is a subclass of chlorophyll a and is part of some Coccolithale
file:HaptophytaChlA obo:IAO_0000136 _:b4 .
_:b4 rdf:type owl:Class ;
rdfs:subClassOf obo:CHEBI_18230,
[obo:BFO_0000050 obo:NCBITaxon_418917] .
which is parsed into the datastore graph and expressed in ttl as:
ns1:global_chlorophyll_a.csvHaptophytaChlA rdfs:label "Haptophyta Chl A" ;
obo:IAO_0000136 [ a owl:Class ;
rdfs:subClassOf [ obo:BFO_0000050 obo:NCBITaxon_418917 ],
obo:CHEBI_18230 ] ;
ns2:rfc4180columnPosition 7 .
See the end of the log from this day: 28.11.17.
###//TODO: I need to check if I can query for a data about this column using the blank node annotation.
What I'd like to do is post-compositionally annotate classes to be in the same format as is done by owl to add annotation properties to it's classes. This way querying against ontology and querying post-compositionally annotated data can be done in the same way, which makes my scripts more standard and powerful.