RDF/XMLNTriplesTurtleShow queryShare
SubjectPredicateObject
http://purl.uniprot.org/citations/26519531http://www.w3.org/1999/02/22-rdf-syntax-ns#typehttp://purl.uniprot.org/core/Journal_Citation
http://purl.uniprot.org/citations/26519531http://www.w3.org/2000/01/rdf-schema#comment"The transporter associated with Ag processing (TAP) translocates proteasomally derived cytosolic peptides into the endoplasmic reticulum. TAP is a central component of the peptide-loading complex (PLC), to which tapasin (TPN) recruits MHC class I (MHC I) and accessory chaperones. The PLC functions to facilitate and optimize MHC I-mediated Ag presentation. The heterodimeric peptide transporter consists of two homologous subunits, TAP1 and TAP2, each of which contains an N-terminal domain (N-domain) in addition to a conserved transmembrane (TM) core segment. Each N-domain binds to the TM region of a single TPN molecule, which recruits one MHC I molecule to TAP1 and/or TAP2. Although both N-domains act as TPN-docking sites, various studies suggest a functional asymmetry within the PLC resulting in greater significance of the TAP2/TPN interaction for MHC loading. In this study, we demonstrate that the leucine-rich hydrophobic sequence stretches (with the central leucine residues L20 and L66) in the first and second TM helix of TAP2 form a functional unit acting as a docking site for optimal TPN/MHC I recruitment, whereas three distinct highly conserved arginine and/or aspartate residues inside or flanking these TM helices are dispensable. Moreover, we show that the physical interaction between TAP2 and TPN is disrupted by benzene, a compound known to interfere with hydrophobic interactions, such as those between pairing leucine zippers. No such effects were observed for the TAP1/TAP2 interaction or the complex formation between TPN and MHC I. We propose that TAP/TPN complex formation is driven by hydrophobic interactions via leucine zipper-like motifs."xsd:string
http://purl.uniprot.org/citations/26519531http://purl.org/dc/terms/identifier"doi:10.4049/jimmunol.1500246"xsd:string
http://purl.uniprot.org/citations/26519531http://purl.uniprot.org/core/author"Leonhardt R.M."xsd:string
http://purl.uniprot.org/citations/26519531http://purl.uniprot.org/core/author"Knittler M.R."xsd:string
http://purl.uniprot.org/citations/26519531http://purl.uniprot.org/core/author"Rufer E."xsd:string
http://purl.uniprot.org/citations/26519531http://purl.uniprot.org/core/author"Kagebein D."xsd:string
http://purl.uniprot.org/citations/26519531http://purl.uniprot.org/core/date"2015"xsd:gYear
http://purl.uniprot.org/citations/26519531http://purl.uniprot.org/core/name"J Immunol"xsd:string
http://purl.uniprot.org/citations/26519531http://purl.uniprot.org/core/pages"5482-5494"xsd:string
http://purl.uniprot.org/citations/26519531http://purl.uniprot.org/core/title"Hydrophobic Interactions Are Key To Drive the Association of Tapasin with Peptide Transporter Subunit TAP2."xsd:string
http://purl.uniprot.org/citations/26519531http://purl.uniprot.org/core/volume"195"xsd:string
http://purl.uniprot.org/citations/26519531http://www.w3.org/2004/02/skos/core#exactMatchhttp://purl.uniprot.org/pubmed/26519531
http://purl.uniprot.org/citations/26519531http://xmlns.com/foaf/0.1/primaryTopicOfhttps://pubmed.ncbi.nlm.nih.gov/26519531
http://purl.uniprot.org/uniprot/#_A0A0A0MSV9-mappedCitation-26519531http://www.w3.org/1999/02/22-rdf-syntax-ns#objecthttp://purl.uniprot.org/citations/26519531
http://purl.uniprot.org/uniprot/#_A0A0A0MT98-mappedCitation-26519531http://www.w3.org/1999/02/22-rdf-syntax-ns#objecthttp://purl.uniprot.org/citations/26519531
http://purl.uniprot.org/uniprot/#_A0A024RCT1-mappedCitation-26519531http://www.w3.org/1999/02/22-rdf-syntax-ns#objecthttp://purl.uniprot.org/citations/26519531
http://purl.uniprot.org/uniprot/#_Q15547-mappedCitation-26519531http://www.w3.org/1999/02/22-rdf-syntax-ns#objecthttp://purl.uniprot.org/citations/26519531
http://purl.uniprot.org/uniprot/#_A0A1V0E419-mappedCitation-26519531http://www.w3.org/1999/02/22-rdf-syntax-ns#objecthttp://purl.uniprot.org/citations/26519531
http://purl.uniprot.org/uniprot/#_A0A1U9X8L5-mappedCitation-26519531http://www.w3.org/1999/02/22-rdf-syntax-ns#objecthttp://purl.uniprot.org/citations/26519531
http://purl.uniprot.org/uniprot/#_A0A1V0E3X6-mappedCitation-26519531http://www.w3.org/1999/02/22-rdf-syntax-ns#objecthttp://purl.uniprot.org/citations/26519531
http://purl.uniprot.org/uniprot/#_A0A1V0E3Z3-mappedCitation-26519531http://www.w3.org/1999/02/22-rdf-syntax-ns#objecthttp://purl.uniprot.org/citations/26519531
http://purl.uniprot.org/uniprot/#_A0A1V0E403-mappedCitation-26519531http://www.w3.org/1999/02/22-rdf-syntax-ns#objecthttp://purl.uniprot.org/citations/26519531
http://purl.uniprot.org/uniprot/#_A0A1V0E415-mappedCitation-26519531http://www.w3.org/1999/02/22-rdf-syntax-ns#objecthttp://purl.uniprot.org/citations/26519531
http://purl.uniprot.org/uniprot/#_B6VNV2-mappedCitation-26519531http://www.w3.org/1999/02/22-rdf-syntax-ns#objecthttp://purl.uniprot.org/citations/26519531