Skip to content

Add structured information to causal JSON format #12

@cthoyt

Description

@cthoyt
{
  "causalStatement": [
    {
      "source": {
        "identifier": "http://purl.obolibrary.org/obo/CHEBI_17489",
        "name": "3',5'-cyclic AMP",
        "biologicalActivity": {
          "identifier": "http://purl.obolibrary.org/obo/GO_0034237",
          "name": "protein kinase A regulatory subunit binding"
        }
      },
      "effect": {
        "identifier": "http://purl.obolibrary.org/obo/MI_2236",
        "name": "up-regulates activity",
        "effectCompartment": {
          "identifier": "http://purl.obolibrary.org/obo/GO_0005737",
          "name": "cytoplasm"
        }
      },
...

The fact that we're in JSON makes me want to have much more structured information. I would request you rename a couple fields that actually aren't descriptive, and add a few.

  • what's currently called identifier would better be called purl
  • add a field in each entry called prefix that says from what namespace the entity is (see Use standardized prefixes when possible #11)
  • add a field in each entry called identifier that actually points to the database identifier

In practice, the snippet from above would become:

{
  "causalStatement": [
    {
      "source": {
        "purl": "http://purl.obolibrary.org/obo/CHEBI_17489",
        "prefix": "chebi",
        "identifier": "17489",
        "name": "3',5'-cyclic AMP",
        "biologicalActivity": {
          "purl": "http://purl.obolibrary.org/obo/GO_0034237",
          "prefix": "go",
          "identifier": "0034237",
          "name": "protein kinase A regulatory subunit binding"
        }
      },
      "effect": {
        "purl": "http://purl.obolibrary.org/obo/MI_2236",
        "prefix": "mi",
        "identifier": "2236",
        "name": "up-regulates activity",
        "effectCompartment": {
          "purl": "http://purl.obolibrary.org/obo/GO_0005737",
          "prefix": "go",
          "identifier": "0005737",
          "name": "cytoplasm"
        }
      },
...

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions