Join GitHub today
GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
Already on GitHub? Sign in to your account
Distribute iMicrobe sample descriptions as RDF #318
Comments
|
For the distribution, I'll follow the globi model whereby we create a new repo for each dataset, see also https://github.com/cmungall/biocaddie-gym/ |
ramonawalls
commented
May 9, 2016
|
"decide on RO props for biome, material and feature" Note that MIXS (now available as RDF) has properties for biome, material, and feature. Their properties are just http://www.w3.org/1999/02/22-rdf-syntax-ns#Property, so we would still probably want to make RO properties. This is a bigger issue we have defined for BCO, in terms of translating Darwin Core properties into OWL (BiodiversityOntologies/bco#10) See: Note that mixs hasn't quite got the mappings right, as it says: <rdf:Description rdf:about="http://gensc.org/ns/mixs/env_biome"> which can't be true b/c mixs terms are propoerties (@pyilmaz @tucotuco - I will file an issue). |
ramonawalls
commented
May 9, 2016
|
Github doesn't like to display rdf as code. See pyilmaz/mixs#1 |
|
Understood. Are the domains always samples or some kind of material entity? The RO object properties would be labeled more like verb phrase, e.g.
But strictly speaking the sample isn't located in, so there would need to be an intermediate derived from Might be easier to work back from the triples, something like this?
Where E would either be a blank node or a skolemized term |
ramonawalls
commented
May 11, 2016
|
The imicrobe-lib archive is now licensed under a GPLv3 LICENSE |
|
On 11 May 2016, at 13:49, Ramona Walls wrote:
The imicrobe-lib archive is now licensed under a GPLv3 LICENSE
Although it's not clear what this means for data, if this were software
then anything linking to it would have to be GPL, it's viral
GPL defines linking in software terms (e.g. static vs dynamic). Not
clear how that applies to linked data. Probably not at all, I recommend
CC-BY/CC-0
|
ramonawalls
commented
May 11, 2016
|
I added a statement to the license doc that the code on the repo (which is most of the content) is GPLv3 but the data in the docs folder is CC0. See https://github.com/hurwitzlab/imicrobe-lib/blob/master/LICENSE |
biomeAs we're dealing with a I wouldn't use a relation like At this stage, the MIxS community probably just want to state what the broad ecosystemic context is (right @pyilmaz?). If we could have a material entity to system relation like This system/component thinking will be very useful for SDGIO too. featureIn this case, I think the triple approach works well. The sample isn't Note that F can be any material entity, as ENVO's materialS
This looks reasonable. Also, there also may be more than one feature determining the E. We could also more closely link the S to the $material in question. I spoke to @pyilmaz about this some time back and there's nothing preventing more than one class being used in any field.
I've mixed in some cardinality to the RDF for brevity: these would just expand to their own distinct triples.
Never come across a non-material one yet. |
cmungall commentedMay 9, 2016
•
edited by ramonawalls
Source:
https://raw.githubusercontent.com/hurwitzlab/imicrobe-lib/master/docs/mapping_files/CameraMetadata_ENVO_working_copy.csv