Inconsistent Type Declarations

[ankonyeni]

define.yaml is inconsistent in how it declares string types: some slots use explicit range: string, while others omit range and rely on the implicit string default. This makes it unclear whether missing ranges are intentional or accidental.

Examples

With explicit range:

resourceType:
  description: Type of resource
  range: string

Without range:

protocol:
  description: Protocol used by the service (e.g., HTTPS, FTP)

Question

Should we treat missing ranges as intentionally string, require explicit range: string everywhere, or remove all range: string declarations and set default_range: string at the schema level for consistency?