Binary interactions
Last modified January 12, 2012
This section provides information about binary protein-protein interactions. The data presented in this section are a quality-filtered subset of binary interactions automatically derived from the IntAct database. It is updated on a monthly basis. Each binary interaction is displayed on a separate line.
We report the name of the interacting protein in the ‘With’ column along with the UniProtKB accession number of the interacting protein in the ‘Entry’ column. The latter may be the identifier of a specific isoform which participates in the interaction. The ’#Exp’ column indicates the number of experiments in the IntAct database which support the interaction, while the ‘IntAct’ column contains the IntAct database accession numbers of the two interacting proteins. Specific information regarding the interaction may be present in the ‘Notes’ column.
Examples: Q9V3W6, O61491, Q02821
Homotypic interactions are indicated by the presence of the qualifier ‘itself’ in the ‘With’ column.
Example: Q64279
If different isoforms of the protein described in the entry have been shown to interact with the same target protein, different IntAct accession numbers are present in this sections.
Example: See the interaction of Q8N2H9 with P51617
Homotypic interactions are are indicated by the presence of the qualifier ‘itself’ in the ‘With’ column.
Example: Q64279
If different isoforms of the protein described in the entry have been shown to interact with the same target protein, different IntAct accession numbers are present in this sections.
Example: See the interaction of Q8N2H9 with P51617
Homotypic interactions are listed before heteromeric interactions, which are sorted alphanumerically based on their ‘identifier’.
The sentence ‘From a different organism’ in the ‘Notes’ column indicates that the interacting proteins are derived from different species. This may be due either to the experimental design or may reflect a pathogen-host interaction.
Example: O00165
UniProtKB ‘Binary interactions’ are automatically derived from the IntAct database, but represent only a subset of the binary interactions found in IntAct. The complete IntAct set can accessed using the link in the ‘Cross-references’ section.
Example: P51617