Open311.org Draft Spec - Revision history

Philipashlock: Reverted edits by Absh1us (Talk) to last version by Phil.ashlock.us

2010-09-30T20:22:26Z

Reverted edits by Absh1us (Talk) to last version by Phil.ashlock.us

2010-08-26T13:16:15Z

‎Case Studies

2010-04-16T17:51:26Z

2010-02-23T17:09:21Z

‎System Architecture

2010-02-11T18:05:01Z

‎System Architecture

2009-12-15T02:20:50Z

‎System Architecture

2009-11-25T22:58:45Z

2009-11-23T21:25:11Z

2009-11-09T20:21:27Z

2009-11-02T23:18:52Z

@@ Line 18: / Line 18: @@
 * [http://octolabs.pbworks.com/Open-311-API-v2-Documentation Washington DC API v2 draft]
 * [http://docs.google.com/View?id=dc8k3dxw_45gcnhm4dp SeeClickFix API draft]
-*[http://www.wa-liability-insurance.com/ Liability Insurance Washington]
 == Terminology ==

@@ Line 18: / Line 18: @@
 * [http://octolabs.pbworks.com/Open-311-API-v2-Documentation Washington DC API v2 draft]
 * [http://docs.google.com/View?id=dc8k3dxw_45gcnhm4dp SeeClickFix API draft]
+*[http://www.wa-liability-insurance.com/ Liability Insurance Washington]
 == Terminology ==

← Older revision		Revision as of 17:51, 16 April 2010
Line 91:		Line 91:

	[[Image:311-flowchart.png]]		[[Image:311-flowchart.png]]
−
−	~~== Example API Calls & Responses ==~~
−
−	~~I've been sketching out possible JSON calls and responses on this page's [http://wiki.open311.org/Talk:Open311.org_Draft_Spec Talk page].~~

← Older revision		Revision as of 17:09, 23 February 2010
Line 82:		Line 82:

	== System Architecture ==		== System Architecture ==
		+	Please note that this illustrates a proposal and does not represent the current API specs being implemented in Washington D.C. or San Francisco.

	# Service request (SR) data and location are entered from open311 app. App requests SR jurisdiction API URI from [[GeoWeb DNS]] (if not already cached).		# Service request (SR) data and location are entered from open311 app. App requests SR jurisdiction API URI from [[GeoWeb DNS]] (if not already cached).

@@ Line 87: / Line 87: @@
 # A generic SR (core schema) is sent to the jurisdiction API
 # If successful, check if the app and jurisdiction supports extensions for additional details. If so, additional details for the identified SR type are requested (sr_type.get)
-# Additional details are sent to the jurisdiction from any app at a later date.
+# Additional details are sent to the jurisdiction by any app and any person (not necessarily the original reporter) at a later date.
 [[Image:311-flowchart.png]]

@@ Line 83: / Line 83: @@
 == System Architecture ==
-# Service request (SR) data and location are entered from open311 app. App requests SR jurisdiction API URI from Geo DNS (if not already cached).
+# Service request (SR) data and location are entered from open311 app. App requests SR jurisdiction API URI from [[GeoWeb DNS]] (if not already cached).
 # The jurisdiction API URI is returned (eg http://api.nyc.gov/311). If no URI is found, default to an adhoc SR service (an equivalent of FixMyStreet or SeeClickFix)
 # A generic SR (core schema) is sent to the jurisdiction API
@@ Line 90: / Line 90: @@
 [[Image:311-flowchart.png]]
 == Example API Calls & Responses ==
 I've been sketching out possible JSON calls and responses on this page's [http://wiki.open311.org/Talk:Open311.org_Draft_Spec Talk page].

@@ Line 1: / Line 1: @@
 == Abstract ==
@@ Line 50: / Line 13: @@
 It is expected that multiple versions of the Open311 API will exist and interoperate concurrently. The spec is designed to allow service providers of different versions to be able to communicate together.
@@ Line 76: / Line 44: @@
      Example: 37.40320,-121.977521

← Older revision		Revision as of 20:21, 9 November 2009
Line 1:		Line 1:
	You can use syntax highlighting to help display a schema, eg JSON. See the [[Help:Editing]] for more information. Content pulled from working doc: http://etherpad.com/Gg1kfcXQR3		You can use syntax highlighting to help display a schema, eg JSON. See the [[Help:Editing]] for more information. Content pulled from working doc: http://etherpad.com/Gg1kfcXQR3
		+
		+	I've been sketching out possible JSON calls and responses on this page's [http://wiki.open311.org/Talk:Open311.org_Draft_Spec Talk page].

	'''Service Request'''		'''Service Request'''

@@ Line 4: / Line 4: @@
 <pre class="brush:jscript">
 -id (alpha-numeric)
--status ("open","closed","more info", "in progress")
+-status ("submitted", "incomplete", "rejected", "open", "assigned", "closed","more info", "in progress")
 -location (location type)
 -data feed URL (atom feed subscription)