RDF/XMLNTriplesTurtleShow queryShare
SubjectPredicateObject
http://purl.uniprot.org/citations/22923333http://www.w3.org/1999/02/22-rdf-syntax-ns#typehttp://purl.uniprot.org/core/Journal_Citation
http://purl.uniprot.org/citations/22923333http://www.w3.org/2000/01/rdf-schema#comment"The loading of antigen-derived peptides onto MHC class I molecules for presentation to cytotoxic T cells is a key process in adaptive immune defense. Loading of MHC I is achieved by a sophisticated machinery, the peptide-loading complex (PLC), which is organized around the transporter associated with antigen processing (TAP) with the help of several auxiliary proteins. As an essential adapter protein recruiting MHC I molecules to TAP, tapasin catalyzes peptide loading of MHC I. However, the exact stoichiometry and basic molecular architecture of TAP and tapasin within the PLC remains elusive. Here, we demonstrate that two tapasin molecules are assembled in the PLC, with one tapasin bound to each TAP subunit. However, one tapasin molecule bound either to TAP1 or TAP2 is sufficient for efficient MHC I antigen presentation. By specifically blocking the interaction between tapasin-MHC I complexes and the translocation complex TAP, the MHC I surface expression is impaired to the same extent as with soluble tapasin. Thus, the proximity of the peptide supplier TAP to the acceptor MHC I is crucial for antigen processing. In summary, the human PLC consists maximally of 2× tapasin-ERp57/MHC I per TAP complex, but one tapasin-ERp57/MHC I in the PLC is essential and sufficient for antigen processing."xsd:string
http://purl.uniprot.org/citations/22923333http://purl.org/dc/terms/identifier"doi:10.1096/fj.12-217489"xsd:string
http://purl.uniprot.org/citations/22923333http://purl.uniprot.org/core/author"Tampe R."xsd:string
http://purl.uniprot.org/citations/22923333http://purl.uniprot.org/core/author"Baldauf C."xsd:string
http://purl.uniprot.org/citations/22923333http://purl.uniprot.org/core/author"Hulpke S."xsd:string
http://purl.uniprot.org/citations/22923333http://purl.uniprot.org/core/date"2012"xsd:gYear
http://purl.uniprot.org/citations/22923333http://purl.uniprot.org/core/name"FASEB J"xsd:string
http://purl.uniprot.org/citations/22923333http://purl.uniprot.org/core/pages"5071-5080"xsd:string
http://purl.uniprot.org/citations/22923333http://purl.uniprot.org/core/title"Molecular architecture of the MHC I peptide-loading complex: one tapasin molecule is essential and sufficient for antigen processing."xsd:string
http://purl.uniprot.org/citations/22923333http://purl.uniprot.org/core/volume"26"xsd:string
http://purl.uniprot.org/citations/22923333http://www.w3.org/2004/02/skos/core#exactMatchhttp://purl.uniprot.org/pubmed/22923333
http://purl.uniprot.org/citations/22923333http://xmlns.com/foaf/0.1/primaryTopicOfhttps://pubmed.ncbi.nlm.nih.gov/22923333
http://purl.uniprot.org/uniprot/#_A0A0A7C543-mappedCitation-22923333http://www.w3.org/1999/02/22-rdf-syntax-ns#objecthttp://purl.uniprot.org/citations/22923333
http://purl.uniprot.org/uniprot/#_A0A0A7C548-mappedCitation-22923333http://www.w3.org/1999/02/22-rdf-syntax-ns#objecthttp://purl.uniprot.org/citations/22923333
http://purl.uniprot.org/uniprot/#_A0A0A7C549-mappedCitation-22923333http://www.w3.org/1999/02/22-rdf-syntax-ns#objecthttp://purl.uniprot.org/citations/22923333
http://purl.uniprot.org/uniprot/#_A0A0A7C551-mappedCitation-22923333http://www.w3.org/1999/02/22-rdf-syntax-ns#objecthttp://purl.uniprot.org/citations/22923333
http://purl.uniprot.org/uniprot/#_A0A0A7C552-mappedCitation-22923333http://www.w3.org/1999/02/22-rdf-syntax-ns#objecthttp://purl.uniprot.org/citations/22923333
http://purl.uniprot.org/uniprot/#_A0A0A7C553-mappedCitation-22923333http://www.w3.org/1999/02/22-rdf-syntax-ns#objecthttp://purl.uniprot.org/citations/22923333
http://purl.uniprot.org/uniprot/#_A0A0E3DC98-mappedCitation-22923333http://www.w3.org/1999/02/22-rdf-syntax-ns#objecthttp://purl.uniprot.org/citations/22923333
http://purl.uniprot.org/uniprot/#_A0A0E3DCA0-mappedCitation-22923333http://www.w3.org/1999/02/22-rdf-syntax-ns#objecthttp://purl.uniprot.org/citations/22923333
http://purl.uniprot.org/uniprot/#_A0A0E3DCA1-mappedCitation-22923333http://www.w3.org/1999/02/22-rdf-syntax-ns#objecthttp://purl.uniprot.org/citations/22923333
http://purl.uniprot.org/uniprot/#_A0A0G2R0N3-mappedCitation-22923333http://www.w3.org/1999/02/22-rdf-syntax-ns#objecthttp://purl.uniprot.org/citations/22923333
http://purl.uniprot.org/uniprot/#_A0A0G2R0N4-mappedCitation-22923333http://www.w3.org/1999/02/22-rdf-syntax-ns#objecthttp://purl.uniprot.org/citations/22923333
http://purl.uniprot.org/uniprot/#_A0A068B107-mappedCitation-22923333http://www.w3.org/1999/02/22-rdf-syntax-ns#objecthttp://purl.uniprot.org/citations/22923333