Describe the feature or improvement you are requesting
The definitions under ./specification/base/typespec/common should be refactored into separate definitions organized by feature area, instead of keeping them grouped in a shared common location.
This would improve ownership and maintainability by making it clearer which models belong to which API surface, and it would reduce coupling across unrelated feature areas.
Additional context
Today, ./specification/base/typespec/common mixes definitions that are used by different feature areas. Splitting these into feature-specific definition files/directories would create a cleaner separation of concerns and make future changes easier to reason about.
This issue is specifically about reorganizing the TypeSpec definitions so that shared/common definitions are minimized and feature-area boundaries are clearer.
Describe the feature or improvement you are requesting
The definitions under
./specification/base/typespec/commonshould be refactored into separate definitions organized by feature area, instead of keeping them grouped in a shared common location.This would improve ownership and maintainability by making it clearer which models belong to which API surface, and it would reduce coupling across unrelated feature areas.
Additional context
Today,
./specification/base/typespec/commonmixes definitions that are used by different feature areas. Splitting these into feature-specific definition files/directories would create a cleaner separation of concerns and make future changes easier to reason about.This issue is specifically about reorganizing the TypeSpec definitions so that shared/common definitions are minimized and feature-area boundaries are clearer.