RDF/XMLNTriplesTurtleShow queryShare
SubjectPredicateObject
http://purl.uniprot.org/citations/26758079http://www.w3.org/1999/02/22-rdf-syntax-ns#typehttp://purl.uniprot.org/core/Journal_Citation
http://purl.uniprot.org/citations/26758079http://www.w3.org/2000/01/rdf-schema#comment"Defining permissive and non-permissive mismatches for transplantation is a demanding challenge. Single mismatches at amino acid (AA) position 156 of human leucocyte antigen (HLA) class I have been described to alter the peptide motif, repertoire, or mode of peptide loading through differential interaction with the peptide-loading complex. Hence, a single mismatch can tip the balance and trigger an immunological reaction. HLA-B*35 subtypes have been described to evade the loading complex, 156 mismatch distinguishing B*35:01 and B*35:08 changes the binding groove sufficiently to alter the sequence features of the selected peptide repertoire. To understand the functional influences of residue 156 in B*35 variants, we analyzed the peptide binding profiles of HLA-B*35:01(156Leu), B*35:08(156Arg) and B*35:62(156Trp). The glycoprotein tapasin represents a target for immune evasions and functions within the multimeric peptide-loading complex to stabilize empty class I molecules and promote acquisition of high-affinity peptides. All three B*35 subtypes showed a tapasin-independent mode of peptide acquisition. HLA-B*35-restricted peptides of low- and high-binding affinities were recovered in the presence and absence of tapasin and subsequently sequenced utilizing mass spectrometry. The peptides derived from B*35 variants differ substantially in their features dependent on their mode of recruitment; all peptides were preferentially anchored by Pro at p2 and Tyr, Phe, Leu, or Lys at pΩ. However, the Trp at residue 156 altered the p2 motif to an Ala and restricted the pΩ to a Trp. Our results highlight the importance of understanding the impact of key micropolymorphism and how a single AA mismatch orchestrates the neighboring AAs."xsd:string
http://purl.uniprot.org/citations/26758079http://purl.org/dc/terms/identifier"doi:10.1007/s00251-015-0896-4"xsd:string
http://purl.uniprot.org/citations/26758079http://purl.uniprot.org/core/author"Blasczyk R."xsd:string
http://purl.uniprot.org/citations/26758079http://purl.uniprot.org/core/author"Huyton T."xsd:string
http://purl.uniprot.org/citations/26758079http://purl.uniprot.org/core/author"Bade-Doeding C."xsd:string
http://purl.uniprot.org/citations/26758079http://purl.uniprot.org/core/author"Celik A.A."xsd:string
http://purl.uniprot.org/citations/26758079http://purl.uniprot.org/core/author"Kunze-Schumacher H."xsd:string
http://purl.uniprot.org/citations/26758079http://purl.uniprot.org/core/author"Manandhar T."xsd:string
http://purl.uniprot.org/citations/26758079http://purl.uniprot.org/core/date"2016"xsd:gYear
http://purl.uniprot.org/citations/26758079http://purl.uniprot.org/core/name"Immunogenetics"xsd:string
http://purl.uniprot.org/citations/26758079http://purl.uniprot.org/core/pages"247-260"xsd:string
http://purl.uniprot.org/citations/26758079http://purl.uniprot.org/core/title"Understanding the obstacle of incompatibility at residue 156 within HLA-B*35 subtypes."xsd:string
http://purl.uniprot.org/citations/26758079http://purl.uniprot.org/core/volume"68"xsd:string
http://purl.uniprot.org/citations/26758079http://www.w3.org/2004/02/skos/core#exactMatchhttp://purl.uniprot.org/pubmed/26758079
http://purl.uniprot.org/citations/26758079http://xmlns.com/foaf/0.1/primaryTopicOfhttps://pubmed.ncbi.nlm.nih.gov/26758079
http://purl.uniprot.org/uniprot/#_A0A0A7C552-mappedCitation-26758079http://www.w3.org/1999/02/22-rdf-syntax-ns#objecthttp://purl.uniprot.org/citations/26758079
http://purl.uniprot.org/uniprot/#_A0A0E3DC98-mappedCitation-26758079http://www.w3.org/1999/02/22-rdf-syntax-ns#objecthttp://purl.uniprot.org/citations/26758079
http://purl.uniprot.org/uniprot/#_A0A0E3DCA0-mappedCitation-26758079http://www.w3.org/1999/02/22-rdf-syntax-ns#objecthttp://purl.uniprot.org/citations/26758079
http://purl.uniprot.org/uniprot/#_A0A0E3DCA1-mappedCitation-26758079http://www.w3.org/1999/02/22-rdf-syntax-ns#objecthttp://purl.uniprot.org/citations/26758079
http://purl.uniprot.org/uniprot/#_A0A068B107-mappedCitation-26758079http://www.w3.org/1999/02/22-rdf-syntax-ns#objecthttp://purl.uniprot.org/citations/26758079
http://purl.uniprot.org/uniprot/#_A0A068B112-mappedCitation-26758079http://www.w3.org/1999/02/22-rdf-syntax-ns#objecthttp://purl.uniprot.org/citations/26758079
http://purl.uniprot.org/uniprot/#_A0A068B116-mappedCitation-26758079http://www.w3.org/1999/02/22-rdf-syntax-ns#objecthttp://purl.uniprot.org/citations/26758079
http://purl.uniprot.org/uniprot/#_A0A068B2J5-mappedCitation-26758079http://www.w3.org/1999/02/22-rdf-syntax-ns#objecthttp://purl.uniprot.org/citations/26758079
http://purl.uniprot.org/uniprot/#_A0A068B2Z1-mappedCitation-26758079http://www.w3.org/1999/02/22-rdf-syntax-ns#objecthttp://purl.uniprot.org/citations/26758079