Changes

Jump to navigation Jump to search
Line 21: Line 21:     
== Product read API ==
 
== Product read API ==
 +
 +
=== call ===
 +
 +
=== result json ===
 +
* The json seems to have two user groups: OFF itself and end users (apps). Can the json be split in two section that correspond to these groups as well? Not sure whether this is a good approach.
 +
* The json can be more structured, so that it is more readible for a viewer, but also from an parsing interpreting point of view. I.e. everything that corresponds to packaging goes together.
 +
* Improved field-names, which clearly reflect the origin or processing of the data. This should reduce the number of questions around field s and their interpretation.
    
== Product write API ==
 
== Product write API ==
3,393

edits

Navigation menu