This superfamily includes sialidases enzymes. Several viruses use sialic acid as a cell surface receptor for host invasion. These viruses then have cell surface neuraminidase enzymes to cleave sialic acid from cell surface proteins allowing them to leave the host cell after replication. This superfamily are composed of six beta-sheets that form a six-fold beta-propeller structure. Many members of this superfamily contain BNR sequence motifs Pfam:PF02012.
This clan contains 11 families and the total number of domains in the clan is 9072. The clan was built by A Bateman.
- Taylor G;, Curr Opin Struct Biol. 1996;6:830-837.: Sialidases: structures, biological significance and therapeutic potential. PUBMED:8994884 EPMC:8994884
This clan contains the following 11 member families:BNR BNR_2 BNR_3 BNR_4 BNR_6 End_beta_barrel End_beta_propel HN Neur PSII_BNR Sortilin-Vps10
External database links
Below is a listing of the unique domain organisations or architectures from this clan. More...
The graphic that is shown by default represents the longest sequence with a given architecture. Each row contains the following information:
- the number of sequences which exhibit this architecture
a textual description of the architecture, e.g. Gla, EGF x 2, Trypsin.
This example describes an architecture with one
Gladomain, followed by two consecutive
EGFdomains, and finally a single
- a link to the page in the Pfam site showing information about the sequence that the graphic describes
- the UniProt description of the protein sequence
- the number of residues in the sequence
- the Pfam graphic itself.
Note that you can see the family page for a particular domain by
clicking on the graphic. You can also choose to see all sequences which
have a given architecture by clicking on the
in each row.
Finally, because some families can be found in a very large number of architectures, we load only the first fifty architectures by default. If you want to see more architectures, click the button at the bottom of the page to load the next set.
Loading domain graphics...
The table below shows the number of occurrences of each domain throughout the sequence database. More...
In brackets beside each number is the percentage of the total number of sequence hits for the clan that are represented by this domain. The rightmost column provides a link to the alignments tab for each domain. Finally, the last row in the table provides a link to the HTML representation of the alignment for the seed alignments for all members of this clan.
Please note: the clan alignment can be extremely large and the resulting HTML file is often too large to be rendered by web-browsers. Please consider downloading the alignment (by right-clicking the link) rather than viewing it in your browser.
|Pfam family||Num. domains||Alignment|
|Sortilin-Vps10 (PF15902)||2675 (29.5%)||View|
|BNR_2 (PF13088)||2189 (24.1%)||View|
|BNR_3 (PF13859)||1733 (19.1%)||View|
|PSII_BNR (PF14870)||1426 (15.7%)||View|
|BNR (PF02012)||482 (5.3%)||View|
|BNR_4 (PF15892)||448 (4.9%)||View|
|BNR_6 (PF15899)||104 (1.1%)||View|
|HN (PF00423)||7 (0.1%)||View|
|Neur (PF00064)||6 (0.1%)||View|
|End_beta_propel (PF12217)||1 (0.0%)||View|
|End_beta_barrel (PF12195)||1 (0.0%)||View|
|Total: 11||Total: 9072||Clan alignment|
Please note: Clan alignments can be very large and can cause problems for some browsers. Read the note above before viewing.
This diagram shows the relationships between members of this clan. More...
Relationships between families in a clan are determined using HHsearch. Families are deemed to be closely related if their E-value is less than 10-3 and these relationships are shown with a solid line. Less closely related family pairs, with an E-value of between 10-3 and 10-1, are shown with a dashed line.
The E-value for each pair of closely or partially related families is shown next to the line linking the families. You can see the information regarding a Pfam family by clicking on the family box.
This tree shows the occurrence of the domains in this clan across different species. More...
For all of the domain matches in a full alignment we count the number of domains that are found on all sequences in the alignment. This total is shown in the purple box.
We also count the number of unique sequences on which each domain is found, which is shown in green. Note that a domain may appear multiple times on the same sequence, leading to the difference between these two numbers.
Finally, we group sequences from the same organism according to the NCBI code that is assigned by UniProt, allowing us to count the number of distinct sequences on which the domain is found. This value is shown in the pink boxes.
We use the NCBI species tree to group organisms according to their taxonomy and this forms the structure of the displayed tree. Note that in some cases the trees are too large (have too many nodes) to allow us to build an interactive tree, but in most cases you can still view the tree in a plain text, non-interactive representation.
You can use the tree controls to manipulate how the interactive tree is displayed:
- show/hide the summary boxes
- expand/collapse the tree or expand it to a given depth
- select a sub-tree or a set of species within the tree and view them graphically or as an alignment
- save a plain text representation of the tree
There are 24 interactions for this clan. More...
We determine these interactions using iPfam, which considers the interactions between residues in three-dimensional protein structures and maps those interactions back to Pfam families. You can find more information about the iPfam algorithm in journal article that accompanies the website.
For those sequences which have a structure in the Protein DataBank, we use the mapping between UniProt, PDB and Pfam coordinate systems from the MSD group, to allow us to map Pfam domains onto UniProt three-dimensional structures. The table below shows the mapping between the Pfam families in this clan, the corresponding UniProt entries, and the region of the three-dimensional structures that are available for that sequence.
Loading structure mapping...