Renamed IKeyedTopicViewModel to ICoreTopicViewModel

With the introduction of `ContentType` (9bc0d00), the new name is more fitting. In addition, this is more consistent with our familiar phrasing of "core attributes" to refer to `Id`, `Key`, `ContentType`, and `Parent`. (Though we don't need `Id` or `Parent` here, as they're rarely needed in view models.)

Author: JeremyCaney

OnTopic.ViewModels/TopicViewModel.cs

@@ -22,7 +22,7 @@ namespace OnTopic.ViewModels {
   ///   default implementations that can be used directly, used as base classes, or overwritten at the presentation level. They
   ///   are supplied for convenience to model factory default settings for out-of-the-box content types.
   /// </remarks>
-  public record TopicViewModel: ITopicViewModel, IKeyedTopicViewModel, IAssociatedTopicBindingModel, ITopicBindingModel {
+  public record TopicViewModel: ITopicViewModel, ICoreTopicViewModel, IAssociatedTopicBindingModel, ITopicBindingModel {
 
     /*==========================================================================================================================
     | ID

OnTopic/Models/IKeyedTopicViewModel.cs OnTopic/Models/ICoreTopicViewModel.csOnTopic/Models/IKeyedTopicViewModel.cs renamed to OnTopic/Models/ICoreTopicViewModel.cs

@@ -12,18 +12,24 @@
 namespace OnTopic.Models {
 
   /*============================================================================================================================
-  | INTERFACE: KEYED TOPIC VIEW MODEL
+  | INTERFACE: CORE TOPIC VIEW MODEL
   \---------------------------------------------------------------------------------------------------------------------------*/
   /// <summary>
-  ///   Ensures that a model maintains, at minimum, a <see cref="Key"/> property, necessary to support e.g. a <see cref="
-  ///   KeyedCollection{TKey, TValue}"/>.
+  ///   Ensures that a model maintains, at minimum, a <see cref="Key"/> and <see cref="ContentType"/> property, which are
+  ///   expected of all <see cref="Topic"/>s.
   /// </summary>
   /// <remarks>
-  ///   It is not required that topic view models implement the <see cref="IKeyedTopicViewModel"/> interface for the <see cref="
-  ///   TopicMappingService"/> to correctly identify and map <see cref="Topic"/>s to topic view models. That said, the interface
-  ///   does ensure that those view models can be keyed, which is useful for, especially, child collections.
+  ///   <para>
+  ///     This is necessary to support e.g. a <see cref="KeyedCollection{TKey, TValue}"/>, while also allowing it to filter by
+  ///     <see cref="ContentType"/>—a common requirement for topic (view model) collections.
+  ///   </para>
+  ///   <para>
+  ///     It is not required that topic view models implement the <see cref="ICoreTopicViewModel"/> interface for the <see cref=
+  ///     "TopicMappingService"/> to correctly identify and map <see cref="Topic"/>s to topic view models. That said, the
+  ///     interface does ensure that those view models can be keyed, which is useful for, especially, child collections.
+  ///   </para>
   /// </remarks>
-  public interface IKeyedTopicViewModel {
+  public interface ICoreTopicViewModel {
 
     /*==========================================================================================================================
     | PROPERTY: KEY

OnTopic/Models/ITopicBindingModel.cs

@@ -17,7 +17,7 @@ namespace OnTopic.Models {
   ///   It is strictly required that topic binding models implement the <see cref="ITopicBindingModel"/> interface for the
   ///   default <see cref="ReverseTopicMappingService"/> to correctly identify and map a binding model to a <see cref="Topic"/>.
   /// </remarks>
-  public interface ITopicBindingModel: IKeyedTopicViewModel {
+  public interface ITopicBindingModel: ICoreTopicViewModel {
 
 
   } //Class

OnTopic/Models/ITopicViewModel.cs

@@ -30,7 +30,7 @@ namespace OnTopic.Models {
   ///     layer and any supporting libraries.
   ///   </para>
   /// </remarks>
-  public interface ITopicViewModel: IKeyedTopicViewModel, IAssociatedTopicBindingModel, ITopicBindingModel {
+  public interface ITopicViewModel: ICoreTopicViewModel, IAssociatedTopicBindingModel, ITopicBindingModel {
 
     /*==========================================================================================================================
     | PROPERTY: ID
@@ -59,7 +59,7 @@ public interface ITopicViewModel: IKeyedTopicViewModel, IAssociatedTopicBindingM
     /// <remarks>
     ///   This value can be set via the query string (via the <c>TopicViewResultExecutor</c> class), via the Accepts header
     ///   (also via the <c>TopicViewResultExecutor</c> class), on the topic itself (via this property), or via the <see cref="
-    ///   IKeyedTopicViewModel.ContentType"/>. By default, it will be set to the name of the <see cref="IKeyedTopicViewModel.
+    ///   ICoreTopicViewModel.ContentType"/>. By default, it will be set to the name of the <see cref="ICoreTopicViewModel.
     ///   ContentType"/>; e.g., if the Content Type is <c>Page</c>, then the view will be <c>Page</c>. This will cause the <c>
     ///   TopicViewResultExecutor</c> to look for a view at, for instance, <c>/Views/Page/Page.cshtml</c>.
     /// </remarks>
@@ -81,7 +81,7 @@ public interface ITopicViewModel: IKeyedTopicViewModel, IAssociatedTopicBindingM
     ///   Gets or sets the Title attribute, which represents the friendly name of the topic.
     /// </summary>
     /// <remarks>
-    ///   While the <see cref="IKeyedTopicViewModel.Key"/> may not contain, for instance, spaces or symbols, there are no
+    ///   While the <see cref="ICoreTopicViewModel.Key"/> may not contain, for instance, spaces or symbols, there are no
     ///   restrictions on what characters can be used in the title. For this reason, it provides the default public value for
     ///   referencing topics.
     /// </remarks>