> > I'm kind of agreeing here that fixing IRIs is perhaps too extreme. These > can be frozen, thawed, modified and replaced as more data improves their > information value and genes and their products get better described. > Properties, what they belong to, do need to be fixed. But I also see that > one needs to identify the right IRIs and stick to them to move forwards in > a snapshot kind of way...imho. > I think this sounds right. "Fix" in this sense simply means "choose and publish," but that will not be a one-time event. It'll be an iterative process that results from community discussion and consensus. What is published will be constantly evolving. And users will of course be free to use any other terms and/or IRIs in addition to the ones in the Bioschemas context. If users need to refer to a snapshot of the Bioschemas context, maybe they could reference the git commit hash or at least the first 8 characters of it. For example, you will always get version "c66c76dd" (the first 8 characters of the git commit SHA-1 hash) from this IRI: https://cdn.rawgit.com/BioSchemas/bioschemas.github. io/c66c76dd/Protein/context.jsonld, and we could do something similar, perhaps in the format "http://bioschemas.org/context.jsonld?sha1=c66c76dd".
Received on Wednesday, 15 November 2017 21:36:02 UTC