Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support type 'namedComplex' #33

Closed
jvwong opened this issue Jun 27, 2023 · 1 comment
Closed

Support type 'namedComplex' #33

jvwong opened this issue Jun 27, 2023 · 1 comment

Comments

@jvwong
Copy link
Member

jvwong commented Jun 27, 2023

Support in converter

Support an incoming factoid model entity type namedComplex that represents a complex. This differs from a factoid model entity type complex in that it has no components, and thus can be treated as a 'black-box'.

In factoid, namedComplex will have a FamPlex identifier. This can be used in an Xref (bp:UnificationXref) attached directly to it.

Alternative - Factoid converts namedComplex to complex

Could convert the namedComplex in Factoid to a regular complex in the outgoing BioPAX template. In this way, the BioPAX converter need only support black-box complexes with no components. An xref would still be available for tagging the complex instance with a UnificationXref.

Details

  • Google Doc 'Factoid binary interaction types' updates

Related to:

@jvwong
Copy link
Member Author

jvwong commented Jun 28, 2023

Using the alternative solution: Do the necessary conversion to a regular complex in factoid.

@jvwong jvwong closed this as completed Jun 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant