Hello @devin @davidraznick !
The HSDS schema includes metadata for each object. But is this strictly necessary to include in the response for the API endpoints (e.g. services, service_at_locations, etc.) to be HSDS-compliant? Considering the deeply nested structure of an endpoint like /services (which includes other objects like organization, phones, service_areas, etc.), how frequently each object could be updated, and the field-level granularity of metadata, this would add an impractical amount of data for each service object returned.