Redirect sequence access to different schema

Hi all,

I'm trying to inject some behavior via rules between an application and a table schema, preferably without modifying
eitherof them. Using views, I'm able to have a query that is run with one schema as the search_path to actually run
againsta table in a different schema. Is that also possible for sequences somehow? I tried creating a view like so: 

create view myseq as select * from other_schema.foo_id_seq;

but when I run "select nextval('myseq');" I get an error saying that myseq "is not a sequence". What other options are
there?

Best Regards
Magnus Reftel