First sketch at Open311 endpoint
Open311 attributes for Service Definition

http://wiki.open311.org/GeoReport_v2#GET_Service_Definition
Open311 Spark encoding conventions for xml/json
Service Definition output schema
Service Definition input validation
Move Rx schema into separate module
extract spark tests
doc tweak
POST service request validation
Better handling of invalid service code
More POST validation tests
Refactor POST input validation
POST output validation
stubbed ::Request class, refactored tests
Post requests
extral JSON and XML outputters to 'has'
Refactor to Result->success/error
Make jurisdiction_id required if appropriate
Open311 schema checking for comma separated data

e.g. status, service_request_id etc., which are documented
like "can be declared multiple times, comma delimited"

As the comma-separated data may be of specific (string-like)
types, we allow the type to be declared like:

    {
        type => '/open311/comma',
        contents => '/open311/status',
    }

We could also simply pass '//str' or similar.

We also accept a 'trim' parameter to remove leading/trailing
whitespace before checking value.
Open311 endpoint validator for datetime