This is an old version of this document, from version 0.9 of the Open511 spec. You should probably visit the current version of our documentation.

Change log

(Please refer to the commit history for detailed change log)

DateDescription
Dec 6th, 2012Initial version
Jan 9th, 2013
  • Add timezone at jurisdiction level
  • Use snake case (underscored) for compound word in field names
  • Change event filtering for the status field
  • Add in_effect_on filtering parameter for events
  • Add bbox filtering parameter for events.
Feb 4th, 2013
  • Add crowdsourcing feature (report resource)
  • Improve severity filtering to include greater than/lesser than filtering
  • Define geography filtering parameter, including the need to support POST requests.
  • Include tolerance filtering parameter when a point or linestring is used.
  • Remove license conditions and generic license in the jurisdiction resource.
  • Add link to "road" resource in the event resource.
  • Change attachments structure using atom links.
  • Add restriction structure. Units are fixed for each type of restriction.
  • Specify how specific_date should be formatted.
Apr 29th, 2013
  • Remove the ability to filter events by polygon and the ability to POST geography filters (events).
  • Precise when to use x-www-form and multiple/form-data to post a report (events).
  • Limit supported authentication options to "api key" and removed the need to support HTTP Basic (Guidelines).
  • Specify the requirements for cross-domain requests: CORS and JSONP (Guidelines).
  • Specify how implementors can add custom fields in the data structure (Guidelines).
  • Add new ressource region and add the region data structure in the event structure (region and event).
  • Define a new resource, jurisdiction geography, to contain the boundaries of a jurisdiction jurisdiction geometry and jurisdiction
  • Add field id at the jurisdiction level and use this field to field events by jurisdiction. (jurisdiction)
May 13th, 2013
  • Rename region into area
May 22nd, 2013
  • Release the specification as version 0.9
June 5th, 2013
  • Allow multi event_subtype values in an event
June 12th, 2013
  • Remove limit parameter from pagination output
  • Rename days_of_week to days, and use a nested-element structure rather than a space-separated list, for consistency and easier serialization rules
  • Description field is optional on event
  • Clarify that supported_versions is a subelement of service on discovery resource
July 18th, 2013
  • Bring link tag into main namespace
  • Rename area_name and area_id tags to name and id
  • Add id to event
  • Specify that the in_effect_on filter may be provided either timezone-aware or naive timestamps
  • Added guidelines on GML geographies
July 31st, 2013
  • Change severity to use string values.
  • Accept comma-separated lists for OR queries on several event filters.
  • Recommend HTTP Basic in auth guidelines
  • Document limit querystring parameter
Sept 13th, 2013
  • Change schedule structure, adding a schedules container
  • Move timezone from schedule to the top level of the event
  • Rename road_name to name
  • Remove lane_status element
  • Add state, lanes_open, and lanes_closed elements to road
Oct 1st, 2013
  • Change service_type in discovery resource to a link
  • Simplify content-type and version negotiation
  • Change XML and JSON container structures
  • Update event_subtype and impacted_system value lists
Oct 25th, 2013
  • Add error handling section to Guidelines document
Nov 6th, 2013
  • Allow areas that don't map to GeoNames
May 7, 2014
  • Clarify that the in_effect_on filter on events should never return archived events
May 14, 2014
  • Document static/simple version of events resource