Naming Conventions for IdP Extensions

[Daniel Lutz]

Are there some naming conventions for IdP extensions for names of properties, beans,
cookies and storage contexts, to avoid conflicts with existing or future names
used by the IdP core?

I've read https://wiki.shibboleth.net/confluence/display/DEV/Java+Coding+Conventions,
but this covers Java in general and doesn't cover these types of identifiers, and I
didn't found another page covering this.

To my knowledge, extensions shouldn't use the prefixes "idp." and "shibboleth." for properties
and beans, respectively, as these are reserved for the IdP core.

Are there recommended rules how to name properties, beans, cookies and storage contexts
in IdP extensions? (Or how not to name them?)

Would it make sense to list such rules on the page
https://wiki.shibboleth.net/confluence/display/IDP30/BuildingExtensions ?
(At least it should say that "idp." and "shibboleth." should not be used.)


- Daniel