RDF/XMLNTriplesTurtleShow queryShare
SubjectPredicateObject
http://purl.uniprot.org/citations/21418451http://www.w3.org/1999/02/22-rdf-syntax-ns#typehttp://purl.uniprot.org/core/Journal_Citation
http://purl.uniprot.org/citations/21418451http://www.w3.org/2000/01/rdf-schema#comment"Taspase1 is a threonine protease suspected to process (patho)biologically relevant nuclear and cytoplasmic substrates, such as the mixed lineage leukemia protein. However, neither the mechanisms regulating Taspase1's intracellular localization nor their functional consequences are known. Analysis of endogenous and ectopically expressed Taspase1 detected the protease predominantly in the nucleus accumulating at the nucleolus. Microinjection and ectopic expression studies identified an evolutionarily conserved bipartite nuclear import signal (NLS) (amino acids (197) KRNKRKLELA ERVDTDFMQLKKRR(220) ) interacting with importin-α. Notably, an NLS-mutated, import-deficient Taspase1 was biologically inactive. Although the NLS conferred nuclear transport already of the proenzyme, Taspase1's nucleolar localization required its autoproteolytic processing, triggering its interaction with the nucleolar shuttle protein nucleophosmin. In contrast, (auto)catalytically inactive Taspase1 mutants neither accumulated at the nucleolus nor bound nucleophosmin. Active nuclear import and interaction with nucleophosmin was found to be required for the formation of proteolytically active Taspase1 ensuring to efficiently process its nuclear targets. Intriguingly, coexpression of pathological nucleophosmin variants increased the amount of cytoplasmic Taspase1. Hence, Taspase1 appears to exploit the nuclear export activity of nucleophosmin to gain transient access to the cytoplasm required to also cleave its cytoplasmic substrates. Collectively, we here describe a hitherto unknown mechanism regulating the biological activity of this protease."xsd:string
http://purl.uniprot.org/citations/21418451http://purl.org/dc/terms/identifier"doi:10.1111/j.1600-0854.2011.01191.x"xsd:string
http://purl.uniprot.org/citations/21418451http://purl.uniprot.org/core/author"Schneider G."xsd:string
http://purl.uniprot.org/citations/21418451http://purl.uniprot.org/core/author"Bier C."xsd:string
http://purl.uniprot.org/citations/21418451http://purl.uniprot.org/core/author"Docter D."xsd:string
http://purl.uniprot.org/citations/21418451http://purl.uniprot.org/core/author"Knauer S.K."xsd:string
http://purl.uniprot.org/citations/21418451http://purl.uniprot.org/core/author"Stauber R.H."xsd:string
http://purl.uniprot.org/citations/21418451http://purl.uniprot.org/core/author"Kramer O.H."xsd:string
http://purl.uniprot.org/citations/21418451http://purl.uniprot.org/core/date"2011"xsd:gYear
http://purl.uniprot.org/citations/21418451http://purl.uniprot.org/core/name"Traffic"xsd:string
http://purl.uniprot.org/citations/21418451http://purl.uniprot.org/core/pages"703-714"xsd:string
http://purl.uniprot.org/citations/21418451http://purl.uniprot.org/core/title"The importin-alpha/nucleophosmin switch controls taspase1 protease function."xsd:string
http://purl.uniprot.org/citations/21418451http://purl.uniprot.org/core/volume"12"xsd:string
http://purl.uniprot.org/citations/21418451http://www.w3.org/2004/02/skos/core#exactMatchhttp://purl.uniprot.org/pubmed/21418451
http://purl.uniprot.org/citations/21418451http://xmlns.com/foaf/0.1/primaryTopicOfhttps://pubmed.ncbi.nlm.nih.gov/21418451
http://purl.uniprot.org/uniprot/#_A0A140VJQ2-mappedCitation-21418451http://www.w3.org/1999/02/22-rdf-syntax-ns#objecthttp://purl.uniprot.org/citations/21418451
http://purl.uniprot.org/uniprot/#_A0A0S2Z491-mappedCitation-21418451http://www.w3.org/1999/02/22-rdf-syntax-ns#objecthttp://purl.uniprot.org/citations/21418451
http://purl.uniprot.org/uniprot/#_A0A0S2Z4G7-mappedCitation-21418451http://www.w3.org/1999/02/22-rdf-syntax-ns#objecthttp://purl.uniprot.org/citations/21418451
http://purl.uniprot.org/uniprot/#_A8K7D9-mappedCitation-21418451http://www.w3.org/1999/02/22-rdf-syntax-ns#objecthttp://purl.uniprot.org/citations/21418451
http://purl.uniprot.org/uniprot/#_A4ZU86-mappedCitation-21418451http://www.w3.org/1999/02/22-rdf-syntax-ns#objecthttp://purl.uniprot.org/citations/21418451
http://purl.uniprot.org/uniprot/#_B1PHD4-mappedCitation-21418451http://www.w3.org/1999/02/22-rdf-syntax-ns#objecthttp://purl.uniprot.org/citations/21418451
http://purl.uniprot.org/uniprot/#_P52292-mappedCitation-21418451http://www.w3.org/1999/02/22-rdf-syntax-ns#objecthttp://purl.uniprot.org/citations/21418451
http://purl.uniprot.org/uniprot/#_Q7Z726-mappedCitation-21418451http://www.w3.org/1999/02/22-rdf-syntax-ns#objecthttp://purl.uniprot.org/citations/21418451
http://purl.uniprot.org/uniprot/#_P06748-mappedCitation-21418451http://www.w3.org/1999/02/22-rdf-syntax-ns#objecthttp://purl.uniprot.org/citations/21418451