loading...| Preferred Name | Interaction | |
| Synonyms |
|
|
| Definitions |
Definition: A biological relationship between two or more entities. Rationale: BioPAX interactions are atomic from modeling perspective, i.e. it is not possible to define sub-interactions. For representing non-atomic continuants with explicit subevents, pathway class should be used. Interactions does not have to be temporally atomic though, for example genetic interactions cover a large span of time. Usage: Interaction is a highly abstract class and in almost all cases it is more appropriate to use subclasses of interaction. It is partially possible to define generic reactions by using generic participants. A more comprehensive method is planned for BioPAX L4 for covering all generic cases like oxidization of a generic alcohol. Synonyms: Process, relationship, event. Examples: protein-protein interaction, biochemical reaction, enzyme catalysis Definition: A biological relationship between two or more entities. Rationale: In BioPAX, interactions are atomic from a database modeling perspective, i.e. interactions can not be decomposed into sub-interactions. When representing non-atomic continuants with explicit subevents the pathway class should be used instead. Interactions are not necessarily temporally atomic, for example genetic interactions cover a large span of time. Interactions as a formal concept is a continuant, it retains its identitiy regardless of time, or any differences in specific states or properties. Usage: Interaction is a highly abstract class and in almost all cases it is more appropriate to use one of the subclasses of interaction. It is partially possible to define generic reactions by using generic participants. A more comprehensive method is planned for BioPAX L4 for covering all generic cases like oxidization of a generic alcohol. Synonyms: Process, relationship, event. Examples: protein-protein interaction, biochemical reaction, enzyme catalysis |
|
| ID |
http://www.biopax.org/release/biopax-level3.owl#Interaction |
|
| comment |
Definition: A biological relationship between two or more entities. Rationale: BioPAX interactions are atomic from modeling perspective, i.e. it is not possible to define sub-interactions. For representing non-atomic continuants with explicit subevents, pathway class should be used. Interactions does not have to be temporally atomic though, for example genetic interactions cover a large span of time. Usage: Interaction is a highly abstract class and in almost all cases it is more appropriate to use subclasses of interaction. It is partially possible to define generic reactions by using generic participants. A more comprehensive method is planned for BioPAX L4 for covering all generic cases like oxidization of a generic alcohol. Synonyms: Process, relationship, event. Examples: protein-protein interaction, biochemical reaction, enzyme catalysis Definition: A biological relationship between two or more entities. Rationale: In BioPAX, interactions are atomic from a database modeling perspective, i.e. interactions can not be decomposed into sub-interactions. When representing non-atomic continuants with explicit subevents the pathway class should be used instead. Interactions are not necessarily temporally atomic, for example genetic interactions cover a large span of time. Interactions as a formal concept is a continuant, it retains its identitiy regardless of time, or any differences in specific states or properties. Usage: Interaction is a highly abstract class and in almost all cases it is more appropriate to use one of the subclasses of interaction. It is partially possible to define generic reactions by using generic participants. A more comprehensive method is planned for BioPAX L4 for covering all generic cases like oxidization of a generic alcohol. Synonyms: Process, relationship, event. Examples: protein-protein interaction, biochemical reaction, enzyme catalysis |
|
| prefixIRI |
bp:Interaction Interaction |
|
| prefLabel |
Interaction |
|
| disjointWith |
http://www.biopax.org/release/biopax-level3.owl#PhysicalEntity |
|
| subClassOf |