http://purl.uniprot.org/citations/17007944 | http://www.w3.org/1999/02/22-rdf-syntax-ns#type | http://purl.uniprot.org/core/Journal_Citation |
http://purl.uniprot.org/citations/17007944 | http://www.w3.org/2000/01/rdf-schema#comment | "Originally, the peroxisomal targeting signal 1 (PTS1) was defined as a tripeptide at the C-terminus of proteins prone to be imported into the peroxisomal matrix. The corresponding receptor PEX5 initiates the translocation of proteins by identifying potential substrates via their C-termini and trapping PTS1s through remodeling of its TPR domain. Thorough studies on the interaction between PEX5 and PTS1 as well as sequence-analytic tools revealed the influence of amino acid residues further upstream of the ultimate tripeptide. Altogether, PTS1s should be defined as dodecamer sequences at the C-terminal ends of proteins. These sequences accommodate physical contacts with both the surface and the binding cavity of PEX5 and ensure accessibility of the extreme C-terminus. Knowledge-based approaches in applied Bioinformatics provide reliable tools to accurately predict the peroxisomal location of proteins not yet determined experimentally."xsd:string |
http://purl.uniprot.org/citations/17007944 | http://purl.org/dc/terms/identifier | "doi:10.1016/j.bbamcr.2006.08.022"xsd:string |
http://purl.uniprot.org/citations/17007944 | http://purl.uniprot.org/core/author | "Hartig A."xsd:string |
http://purl.uniprot.org/citations/17007944 | http://purl.uniprot.org/core/author | "Brocard C."xsd:string |
http://purl.uniprot.org/citations/17007944 | http://purl.uniprot.org/core/date | "2006"xsd:gYear |
http://purl.uniprot.org/citations/17007944 | http://purl.uniprot.org/core/name | "Biochim Biophys Acta"xsd:string |
http://purl.uniprot.org/citations/17007944 | http://purl.uniprot.org/core/pages | "1565-1573"xsd:string |
http://purl.uniprot.org/citations/17007944 | http://purl.uniprot.org/core/title | "Peroxisome targeting signal 1: is it really a simple tripeptide?"xsd:string |
http://purl.uniprot.org/citations/17007944 | http://purl.uniprot.org/core/volume | "1763"xsd:string |
http://purl.uniprot.org/citations/17007944 | http://www.w3.org/2004/02/skos/core#exactMatch | http://purl.uniprot.org/pubmed/17007944 |
http://purl.uniprot.org/citations/17007944 | http://xmlns.com/foaf/0.1/primaryTopicOf | https://pubmed.ncbi.nlm.nih.gov/17007944 |
http://purl.uniprot.org/uniprot/#_P0C024-mappedCitation-17007944 | http://www.w3.org/1999/02/22-rdf-syntax-ns#object | http://purl.uniprot.org/citations/17007944 |
http://purl.uniprot.org/uniprot/#_Q15067-mappedCitation-17007944 | http://www.w3.org/1999/02/22-rdf-syntax-ns#object | http://purl.uniprot.org/citations/17007944 |
http://purl.uniprot.org/uniprot/#_A8MXV4-mappedCitation-17007944 | http://www.w3.org/1999/02/22-rdf-syntax-ns#object | http://purl.uniprot.org/citations/17007944 |
http://purl.uniprot.org/uniprot/#_O14734-mappedCitation-17007944 | http://www.w3.org/1999/02/22-rdf-syntax-ns#object | http://purl.uniprot.org/citations/17007944 |
http://purl.uniprot.org/uniprot/#_O15228-mappedCitation-17007944 | http://www.w3.org/1999/02/22-rdf-syntax-ns#object | http://purl.uniprot.org/citations/17007944 |
http://purl.uniprot.org/uniprot/#_O15254-mappedCitation-17007944 | http://www.w3.org/1999/02/22-rdf-syntax-ns#object | http://purl.uniprot.org/citations/17007944 |
http://purl.uniprot.org/uniprot/#_P21549-mappedCitation-17007944 | http://www.w3.org/1999/02/22-rdf-syntax-ns#object | http://purl.uniprot.org/citations/17007944 |
http://purl.uniprot.org/uniprot/#_P39210-mappedCitation-17007944 | http://www.w3.org/1999/02/22-rdf-syntax-ns#object | http://purl.uniprot.org/citations/17007944 |
http://purl.uniprot.org/uniprot/#_Q13011-mappedCitation-17007944 | http://www.w3.org/1999/02/22-rdf-syntax-ns#object | http://purl.uniprot.org/citations/17007944 |
http://purl.uniprot.org/uniprot/#_Q14032-mappedCitation-17007944 | http://www.w3.org/1999/02/22-rdf-syntax-ns#object | http://purl.uniprot.org/citations/17007944 |
http://purl.uniprot.org/uniprot/#_O75874-mappedCitation-17007944 | http://www.w3.org/1999/02/22-rdf-syntax-ns#object | http://purl.uniprot.org/citations/17007944 |
http://purl.uniprot.org/uniprot/#_P14920-mappedCitation-17007944 | http://www.w3.org/1999/02/22-rdf-syntax-ns#object | http://purl.uniprot.org/citations/17007944 |
http://purl.uniprot.org/uniprot/#_P43155-mappedCitation-17007944 | http://www.w3.org/1999/02/22-rdf-syntax-ns#object | http://purl.uniprot.org/citations/17007944 |