home.social

#curies — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #curies, aggregated by home.social.

  1. New blog post about how to represent BiomarkerKB (biomarkerkb.org) in @bioregistry

    📖 cthoyt.com/2025/08/22/bioregis

    Also useful for anyone else running a database in the life/natural sciences who might want to make it more findable and FAIR - please get in touch!

    #PIDs #semanticweb #linkedopendata #linkeddata #bioregistry #curies #fair #fairdata #researchdatamanagement #rdm

  2. New blog post about how to represent BiomarkerKB (biomarkerkb.org) in @bioregistry

    📖 cthoyt.com/2025/08/22/bioregis

    Also useful for anyone else running a database in the life/natural sciences who might want to make it more findable and FAIR - please get in touch!

    #PIDs #semanticweb #linkedopendata #linkeddata #bioregistry #curies #fair #fairdata #researchdatamanagement #rdm

  3. New blog post about how to represent BiomarkerKB (biomarkerkb.org) in @bioregistry

    📖 cthoyt.com/2025/08/22/bioregis

    Also useful for anyone else running a database in the life/natural sciences who might want to make it more findable and FAIR - please get in touch!

    #PIDs #semanticweb #linkedopendata #linkeddata #bioregistry #curies #fair #fairdata #researchdatamanagement #rdm

  4. New blog post about how to represent BiomarkerKB (biomarkerkb.org) in @bioregistry

    📖 cthoyt.com/2025/08/22/bioregis

    Also useful for anyone else running a database in the life/natural sciences who might want to make it more findable and FAIR - please get in touch!

    #PIDs #semanticweb #linkedopendata #linkeddata #bioregistry #curies #fair #fairdata #researchdatamanagement #rdm

  5. The only sane way to deal with #CURIEs in code: Expand as early as possible and contract as late as possible.

    Expand CURIEs in the input layer, as soon as you got the data from the outside world. Contract them in the output layer, just before you send the data back to the outside world.

    Between the two, let your code be a CURIE-free zone, where the only identifiers are opaque full-length IRIs.

    Life is too short to spend it dealing with CURIEs more than what’s absolutely necessary.

  6. The only sane way to deal with #CURIEs in code: Expand as early as possible and contract as late as possible.

    Expand CURIEs in the input layer, as soon as you got the data from the outside world. Contract them in the output layer, just before you send the data back to the outside world.

    Between the two, let your code be a CURIE-free zone, where the only identifiers are opaque full-length IRIs.

    Life is too short to spend it dealing with CURIEs more than what’s absolutely necessary.

  7. The only sane way to deal with #CURIEs in code: Expand as early as possible and contract as late as possible.

    Expand CURIEs in the input layer, as soon as you got the data from the outside world. Contract them in the output layer, just before you send the data back to the outside world.

    Between the two, let your code be a CURIE-free zone, where the only identifiers are opaque full-length IRIs.

    Life is too short to spend it dealing with CURIEs more than what’s absolutely necessary.

  8. I re-implemented the Name-to-Things (N2T) ARK resolver using the `curies` Python package and wrote an explanation of how I did it here: cthoyt.com/2023/04/11/n2t-ark-

    Code available here: github.com/cthoyt/n2t-ark-reso

    #arks #pids #semanticweb #curies #uris

  9. I re-implemented the Name-to-Things (N2T) ARK resolver using the `curies` Python package and wrote an explanation of how I did it here: cthoyt.com/2023/04/11/n2t-ark-

    Code available here: github.com/cthoyt/n2t-ark-reso

    #arks #pids #semanticweb #curies #uris

  10. I re-implemented the Name-to-Things (N2T) ARK resolver using the `curies` Python package and wrote an explanation of how I did it here: cthoyt.com/2023/04/11/n2t-ark-

    Code available here: github.com/cthoyt/n2t-ark-reso

    #arks #pids #semanticweb #curies #uris

  11. I re-implemented the Name-to-Things (N2T) ARK resolver using the `curies` Python package and wrote an explanation of how I did it here: cthoyt.com/2023/04/11/n2t-ark-

    Code available here: github.com/cthoyt/n2t-ark-reso

    #arks #pids #semanticweb #curies #uris

  12. I re-implemented the Name-to-Things (N2T) ARK resolver using the `curies` Python package and wrote an explanation of how I did it here: cthoyt.com/2023/04/11/n2t-ark-

    Code available here: github.com/cthoyt/n2t-ark-reso

    #arks #pids #semanticweb #curies #uris