style="FONT-SIZE: 10pt">The public interface of a base class should provide a
rich set of functionality for the consumer of that class. However,
customizers of that class often want to implement the fewest methods possible to
provide that rich set of functionality to the consumer. To meet this goal,
provide a set of non-virtual or final public methods that call through to a
single (or very small set of) protected (family) method with the “Core” suffix
that provides implementations for such a method.

size=1>Annotation (BradA): Notice in a few parts of
the Framework v1.0 we used the suffix “Impl” for this convention. In
retrospect “Core” is more common and is not an abbreviation, so we choice to
standardize on it.

I would prefer "Internal". I want to provide some reasoning behind it:
1. The cumulative for “protected” and “private” is exactly internal. A user cannot invoke the internal methods
2. The term “Core” is overloaded. It also can be used in other contexts and have other meanings not akin to the implementation pattern.

In addition to the suffixes Implementation and Self I have seen Real and Work.

Actually, there is a huge difference between protected and private members… They are not in the same class… protected members can be called by basicly anyone, all you have to do is subclass the class.. Internal members can only be called from types in the same assembly.