— VickySchneider (@MVickySchneider) March 7, 2017
Justin and Gos attended the BioSchemas kick-off meeting at Hinxton this week. As well as giving a short talk about InterMine (the slides are on FigShare), Justin managed to jot down a few thoughts about the event:
The aim of the Bioschemas schema is to come up with simple metadata that can be embedded in webpages (JSON-LD, RDFa, etc.) to make it easier to find data. For instance, suppose you wanted datasets that concerned the effect of a certain drug. At the moment, if you search in Google for that drug name, you will find relevant datasets, but also possibly datasets that happen to use that drug as part of their protocol and more things besides.
But if you can embed a schema which names the subject of the dataset in a structured way (e.g. puts an ontology term URL in a dataset.subject field) then you can pull up more relevant data.
However, there is a strong concern with keeping such markup as light as possible so that people aren’t put off annotating their datasets. Hence, a notional rule that there should only be 6 properties per class (e.g. just name, description, url, keywords, variableMeasured, creator.name for dataset).
As such, bioschemas won’t be replacing any of the existing ‘heavyweight’ schemas (DATS, DataCite’s model, OMICSdi model, our own InterMine data model), as it’s not meant to be used as an internal data model.
- Bioschemas is about getting properties into schema.org (as supported by Google, Bing, Yahoo, etc.). However, schema.org is a big bag of potential metadata with few constraints (no cardinality, for instance!). It’s up to Bioschemas to come up with constraints for our purposes, especially on generic metadata such as DataSet and DataCatalog.
- Bioschemas is also largely about general areas at the moment (datasets, data sources, etc.) though there is some specific work on protein annotations and samples. But not, for instance, on genes and proteins at this stage (though presumably protein annotations would need some metadata for proteins….)
- Things are at an early stage – the next year will (hopefully) see some Bioschemas definitions. There is still debate about exactly what it can be used for beyond search. For instance, we (InterMine) may be able to use them to improve our data integration process if all sources start embedding common metadata in their download files as well as on webpages.
- Bioschemas is more than schema work. The initiative covers topics such as identifiers, citation, metrics and tools too (which will be relevant to us in the future). We can get value from these other areas too – for instance there was discussion of a standard way of providing notification that a data source (uniprot, etc.) had updated, which would be very useful to us in building mines that automatically update. There was also talk of having metadata that specifies when a data source changes its format – another thing that would be tremendously useful for us.
- The presentations were interesting and the group friendly. InterMine seemed to be well received. The group doesn’t have a many actual data consumers and integrators, so I think that we can make a valuable contribution from that perspective.