The OBO file contains e.g.
xref: BEL:"9-1-1 Complex"
The standard for CURIEs is not very clear, but this is probably not conformant. Certainly this is rejected by the OBO parser pronto. Moreover this can't be resolved by bioregistry.io, see e.g : https://bioregistry.io/reference/bel:/9-1-1%20Complex.
I suggest that you change these, e.g. by URL-encoding to BEL:9-1-1%Complex.
(Probably not conformant; the RFC for CURIEs references the RFC for IRIs, but actually the full range of permitted characters allowed by the IRI RFC would be unusual and probably rejected by most CURIE processing software. Nevertheless, spaces are excluded.)
Thank you for FamPlex. Like you, we find many mentions of gene families and complexes that cannot be linked to HGNC families, so we are excited to evaluate it.
The OBO file contains e.g.
The standard for CURIEs is not very clear, but this is probably not conformant. Certainly this is rejected by the OBO parser pronto. Moreover this can't be resolved by bioregistry.io, see e.g : https://bioregistry.io/reference/bel:/9-1-1%20Complex.
I suggest that you change these, e.g. by URL-encoding to
BEL:9-1-1%Complex.(Probably not conformant; the RFC for CURIEs references the RFC for IRIs, but actually the full range of permitted characters allowed by the IRI RFC would be unusual and probably rejected by most CURIE processing software. Nevertheless, spaces are excluded.)
Thank you for FamPlex. Like you, we find many mentions of gene families and complexes that cannot be linked to HGNC families, so we are excited to evaluate it.