Charles Tapley Hoyt
Charles Tapley Hoyt
I would strongly oppose "doi:xx.yyyy/zzzzzz"^^xsd:string as it is effectively representing a URI as a string, and since we're in the semantic web context, I would much rather represent a URI...
I saw that. It doesn’t do what I want, and I don’t like how it does it. With this kind of stuff I would much rather rebuild it from scratch.
If you can point me to your contribution guidelines, I'd be happy to add something like this myself and send a PR.
For example, which file should I edit? Is there a release process? Or should I make the same change in multiple artifacts?
Also, it appears that [is encoded in (SWO:0000741)](https://www.ebi.ac.uk/ols/ontologies/swo/properties?iri=http%3A%2F%2Fwww.ebi.ac.uk%2Fefo%2Fswo%2FSWO_0000741) has been previously used for doing this kind of thing, but this doesn't have an obvious label nor does it have specific...
Thanks so much for the feedback! Ping me if/when you're ready for me to get involved.
stringifying a NAN from pandas isn't the right solution - this would introduce incorrect characters. This might have already been fixed in cc2f27b
@cmungall @JervenBolleman is there any possibility the SIB can host me for a week or two to work on this coordination / we can work together to get project funding...
Conversion code: https://github.com/pyobo/pyobo/blob/main/src/pyobo/sources/slm.py Artifacts: https://github.com/biopragmatics/obo-db-ingest/tree/main/export/swisslipid PyOBO will always follow the Bioregistry standard, so if you want to talk about changing the prefix we can do a discussion on the tracker...
CC @sartweedie