<?xml version="1.0" encoding="UTF-8"?>
<item xmlns="http://omeka.org/schemas/omeka-xml/v5" itemId="2178" public="1" featured="0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://omeka.org/schemas/omeka-xml/v5 http://omeka.org/schemas/omeka-xml/v5/omeka-xml-5-0.xsd" uri="https://www.socictopen.socict.org/items/show/2178?output=omeka-xml" accessDate="2026-04-17T05:05:09+00:00">
  <fileContainer>
    <file fileId="2178">
      <src>https://www.socictopen.socict.org/files/original/3012bd3733b086aabeb7fd9c4641e065.pdf</src>
      <authentication>583cf5a2c1947e337c37609c928ac89b</authentication>
    </file>
  </fileContainer>
  <collection collectionId="1">
    <elementSetContainer>
      <elementSet elementSetId="1">
        <name>Dublin Core</name>
        <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
        <elementContainer>
          <element elementId="50">
            <name>Title</name>
            <description>A name given to the resource</description>
            <elementTextContainer>
              <elementText elementTextId="1">
                <text>Coronavirus</text>
              </elementText>
            </elementTextContainer>
          </element>
          <element elementId="41">
            <name>Description</name>
            <description>An account of the resource</description>
            <elementTextContainer>
              <elementText elementTextId="2">
                <text>Dominio científico: Coronavirus</text>
              </elementText>
            </elementTextContainer>
          </element>
        </elementContainer>
      </elementSet>
    </elementSetContainer>
  </collection>
  <itemType itemTypeId="1">
    <name>Text</name>
    <description>A resource consisting primarily of words for reading. Examples include books, letters, dissertations, poems, newspapers, articles, archives of mailing lists. Note that facsimiles or images of texts are still of the genre Text.</description>
  </itemType>
  <elementSetContainer>
    <elementSet elementSetId="1">
      <name>Dublin Core</name>
      <description>The Dublin Core metadata element set is common to all Omeka records, including items, files, and collections. For more information see, http://dublincore.org/documents/dces/.</description>
      <elementContainer>
        <element elementId="50">
          <name>Title</name>
          <description>A name given to the resource</description>
          <elementTextContainer>
            <elementText elementTextId="20937">
              <text>The SARS Coronavirus S Glycoprotein Receptor Binding Domain: Fine Mapping and Functional Characterization</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="39">
          <name>Creator</name>
          <description>An entity primarily responsible for making the resource</description>
          <elementTextContainer>
            <elementText elementTextId="20938">
              <text>Xiao-xiao Dong, Prabakaran Ponraj, Chakraborti Samitabh, Dimitrov Dimiter S</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="41">
          <name>Description</name>
          <description>An account of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="20939">
              <text>Abstract The entry of the SARS coronavirus (SCV) into cells is initiated by binding of its spike envelope glycoprotein (S) to a receptor, ACE2. We and others identified the receptor-binding domain (RBD) by using S fragments of various lengths but all including the amino acid residue 318 and two other potential glycosylation sites. To further characterize the role of glycosylation and identify residues important for its function as an interacting partner of ACE2, we have cloned, expressed and characterized various soluble fragments of S containing RBD, and mutated all potential glycosylation sites and 32 other residues. The shortest of these fragments still able to bind the receptor ACE2 did not include residue 318 (which is a potential glycosylation site), but started at residue 319, and has only two potential glycosylation sites (residues 330 and 357). Mutation of each of these sites to either alanine or glutamine, as well as mutation of residue 318 to alanine in longer fragments resulted in the same decrease of molecular weight (by approximately 3 kDa) suggesting that all glycosylation sites are functional. Simultaneous mutation of all glycosylation sites resulted in lack of expression suggesting that at least one glycosylation site (any of the three) is required for expression. Glycosylation did not affect binding to ACE2. Alanine scanning mutagenesis of the fragment S319–518 resulted in the identification of ten residues (K390, R426, D429, T431, I455, N473, F483, Q492, Y494, R495) that significantly reduced binding to ACE2, and one residue (D393) that appears to increase binding. Mutation of residue T431 reduced binding by about 2-fold, and mutation of the other eight residues – by more than 10-fold. Analysis of these data and the mapping of these mutations on the recently determined crystal structure of a fragment containing the RBD complexed to ACE2 (Li, F, Li, W, Farzan, M, and Harrison, S. C., submitted) suggested the existence of two hot spots on the S RBD surface, R426 and N473, which are likely to contribute significant portion of the binding energy. The finding that most of the mutations (23 out of 34 including glycosylation sites) do not affect the RBD binding function indicates possible mechanisms for evasion of immune responses.</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="40">
          <name>Date</name>
          <description>A point or period of time associated with an event in the lifecycle of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="20940">
              <text>2005</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="43">
          <name>Identifier</name>
          <description>An unambiguous reference to the resource within a given context</description>
          <elementTextContainer>
            <elementText elementTextId="20941">
              <text>DOI: 10.1186/1743-422X-2-73</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="48">
          <name>Source</name>
          <description>A related resource from which the described resource is derived</description>
          <elementTextContainer>
            <elementText elementTextId="20942">
              <text>Virology Journal</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="45">
          <name>Publisher</name>
          <description>An entity responsible for making the resource available</description>
          <elementTextContainer>
            <elementText elementTextId="20943">
              <text>BMC</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="38">
          <name>Coverage</name>
          <description>The spatial or temporal topic of the resource, the spatial applicability of the resource, or the jurisdiction under which the resource is relevant</description>
          <elementTextContainer>
            <elementText elementTextId="20944">
              <text>Infectious and parasitic diseases</text>
            </elementText>
          </elementTextContainer>
        </element>
        <element elementId="44">
          <name>Language</name>
          <description>A language of the resource</description>
          <elementTextContainer>
            <elementText elementTextId="20945">
              <text>EN</text>
            </elementText>
          </elementTextContainer>
        </element>
      </elementContainer>
    </elementSet>
  </elementSetContainer>
</item>
