We recently added the ability to reference the annotation applied to model element by specifying the element followed by "@" and the fully qualified name of the annotation.

As described in reviewing the application of the change, we chose "@" in applying the change primarily because it allowed the client to more easily differentiate whether the applied cast was to a type or an annotation term.

However, by using "@" instead of "/", as originally proposed, we lost the ability to identify the different segments of the expression by splitting on "/". Referencing the applied annotation really is properly a different segment and should be separated by "@".

SO the proposal is to restore the "/" to rightly indicate a separate path segment, but to keep the "@" as a prefix to the annotation in order to more easily differentiate it as an annotation term.