...
External Resources
https://wiki.onap.org/display/DW/Data+Representation
https://wiki.onap.org/display/DW/Interface+style
Open Issues/Decisions
# | Description | Details | Decisions |
|---|---|---|---|
| 1 | Should the java interface take in one (JSON) objects(like REST interface) or a few individual fields in a signature? | Mapping the request body to an object | |
| 2 | Input streams or files? | Toine has a preference for input stream. | Use input stream. |
| 3 | API uses (generated) ID's or customer provided names | Using ID would mean client has to get/cache ID's all the time. Maybe the Java API should use names like the REST API does. anchors & nodes - may need ID Create methods should return the objects created. Should throw an exception if it already exists. All ID's generated should be in the response. If we return it we also need methods to use the ID. If we update the java API to use ID, we should also update the rest API. Create methods will be void. Create methods could return false if already exists. | |
| 4 | Should a user be able to update/override/delete a dataspace, module, module set? (of the same revision) | Business logic to check on create if it already exists. If it exists we do not create it. |
CPS provides the following interfaces:
...