Currently, Annotation may be single-class or it may have many annotation classes contained within a single annotation feature class. The former is fine but the latter is not when you consider the following:
- Annotation with multiple subclasses is not supported for feature services.
- If you publish them despite the incompatibility warnings, the performance will be poor
- If you publish to Enterprise, the ArcGIS Server will log thousands of errors about the incompatible layers every day.
- There is no real advantage to having all that anno jammed into one feature class versus having individual single-class annotation features within a feature dataset.
- They are harder to deal with in many ETL and/or sharing situations than single-class features are.
- Holistically, the ESRI data formats should work well, throughout the ecosystem, not just in Pro.
So the Idea is to to deprecate multi-class annotation feature classes entirely and perpetuate only single-class annotation, ensuring the anno feature classes are supported throughout the whole ecosystem. (A rare idea to simplify something, rather than add something more)
