Modeling for Edition Based Redefinition in Oracle 11Gr2 and beyond.

I'm looking for hints, tips, gottcha's for using PD to model for Edition based redefinition in Oracle 11g r2.

Just starting to explore the technology and it's impact on how we model in PD.

Unfortunately I'm still on PD version 16.1.0.3821 EBF13

[EDIT] Just thought I add some clarity. What I'm really looking for is how do I manage having for example views with the same name but representing different editions of the underlying structure? Do I use branching in the repository? Does later versions of PD allow objects with the same name but different "editions"?

thanks

Tim

Message was edited by: Timothy Graham