poseidon-framework / poseidon3-schema Goto Github PK

Ideally we'd want a CI workflow that also checks our example together with the schemas.

We will host the file terms.rdf on our website, but we'd like to keep it in this repo, since it's a core part of the schema definition and therefore needs to be in the core development repo.

Is there some way to automatically copy it over to the github.io repo every time it's changed?

To talk about metagenomics integration into schema.

Subtables

Request upstream fields (dnaSequencing or library level)

It might be better for general linked data application of our vocabulary file (terms.rdf.json) would also be provided in XML (file ending .rdf). This can be automatically rendered nicely in Firefox and seems to be more standard. So I think we should write a short script to convert, and than have Travis convert it automatically within this repo, and then push the xml one instead of the json one to the website.

Currently the README assumes 'archaeogenetics' is human-individual specific, however this is a narrow view of what it covers. Archaeogenetics can also be applied to a wider range of genetic data (zooarchaeology, artefact DNA etc.).

I would suggest to be more explicit in two possible ways:

1. Specific specifically in the README that the framework is designed for human DNA (or at least first of the schema)
2. Add an additional field specifying what organism or 'host' the DNA is derived or associated with.

Another example(s):

• maybe in the future (complete speculation) one would want to associate individuals with animal bone artefacts and see whether certain populations of animals were used for different social status individuals.
• associating certain types of animal with diet or clothes as with Ötzi (https://doi.org/10.1016/j.cub.2018.05.067, or https://doi.org/10.1038/srep31279)