Proposal for edits to the revised charter

[chris-little]

@cportele stadnards -> standards Also, I would prefer OGC API Standards specify Web based capabilities which are typically based on polling for collection resource updates (new or changed or deleted features/records, coverages, maps, etc.). Depending on a collection's temporal resolution or frequency of updates, an event-driven / Publish-Subscribe architecture provides a timely, efficient and low latency approach for delivery of data updates. to read something like: OGC API Standards specify Web based capabilities which are typically based on polling for collection resource updates (new or changed or deleted features/records, coverages, maps, data, etc.). Depending on a collection's temporal resolution or frequency of updates or size, an event-driven / Publish-Subscribe architecture provides a timely, efficient and low latency approach for delivery of data updates or notifications.

[cportele]

@chris-little - Thanks. I have fix the typo and added two of your three changes. I have not added "data", because it is a generic term and not a resource type in the OGC API standards.