| Gliffy | ||
|---|---|---|
|
This resource model is proposed for this project. Additional notes:
...
(5) Enums are passed as the English text of their values.
(6) Unlicensed user raff, please check to make sure key/value pairs can be handled in both JSON and XML. See (8) and (9) below.
Second thoughts
(7) I'm thinking that rather than being subclass handlers, all 3 definitions and all 3 requests should be first-class resources. They would each contain all the current superclass fields (except Type) plus their own private fields. That way, we could at some later point incorporate their subclasses (e.g. AgeCohortDefinition, EncounterDatasetDefinition, PeriodIndicatorReportDefinition) into the model so they can be CRUDed through the REST interface.
...