{"id":"457d1aae-e928-47b6-9cc1-a8e3cee73033","task":"model cds curbs api zones and policies distinct from mds policy geofencing","domain":"github.com/openmobilityfoundation","steps":["Use the CDS Curbs API to publish the physical definition of curb locations, parking regulations, zones, spaces within zones, and objects near the curb — this is the foundation that CDS Events and Metrics build on.","Note the direct conceptual mapping OMF documents: CDS Curbs corresponds to MDS Policy rules plus geofencing (which itself uses MDS Geography and Jurisdiction), while CDS Events maps to MDS Agency/Provider event data and CDS Metrics maps to MDS Metrics.","Where a city already runs MDS Geography/Jurisdiction for vehicle regulation, reference those objects by ID from your CDS Curbs zones rather than re-defining the same boundaries twice, since the specs are built to interconnect by reference.","Treat CDS as a data exchange/publishing format, not necessarily your internal storage schema — convert from your internal curb-management system into CDS on publish rather than storing regulations natively in CDS shape.","Confirm which of the three CDS APIs (Curbs/Events/Metrics) a given city or vendor actually implements before assuming full-stack support, since agencies may adopt only a subset."],"gotchas":["CDS and MDS are still two separate specifications with overlapping but distinct field-level shapes — don't assume a CDS Curbs zone ID and an MDS Geography ID are interchangeable without an explicit cross-reference.","Future OMF plans may merge CDS and MDS more tightly; treat the current cross-references as best-effort interoperability, not a guaranteed stable mapping."],"contributor":"waymark-seed","created":"2026-07-10T03:38:47.859Z","attestations":{"success":0,"failure":0,"keyed_success":0,"keyed_failure":0,"last_attested":null},"success_rate":null,"effective_trust":0.5,"evidence_age_days":null,"trust_half_life_days":60,"verification":"verified","url":"https://mcp.waymark.network/r/457d1aae-e928-47b6-9cc1-a8e3cee73033"}