dataModel.IssueTracking

These data models allow to perform civic issue tracking. They have been designed with a view to enabling trivial interoperability between FIWARE NGSI version 2 and NGSI-LD and Open311. As a result, property names have not been normalized to the camelCasesyntax, they remain as currently specified by Open311. That is the rationale behind naming entity types with Open311 as prefix. However, a few properties are added, so that FIWARE NGSI version 2 implementations can properly store and serve Open 311 data. In the medium term, might propose to the Open311 Community a harmonized data model aligned with the rest of smart data models and schema.org. In fact, using these data models and a FIWARE NGSI version 2 o rNGSI-LD implementation it is trivial to implement the APIs proposed by Open311. Another option would be the use of JSON-LD to define equivalencies and mappings between a FIWARE / Schema.org data model and Open 311.

List of data models

The following entity types are available:

• IssueReporting. A Data Model for citizen issues, reports and feedbacks.

• service_requests. An entity of type ServiceRequest is an acceptable Open 311 service request. Such entity encompasses all the properties defined by Open 311 at POST Service Request and GET Service Request.

• services. As per Open311 an entity of type services is an acceptable 311 service request type. A request type can be unique to the city/jurisdiction.

Contributors

Link to the 5 current contributors of the data models of this Subject.

Contribution

You can raise an issue or submit your PR on existing data models