atlas-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Radley <>
Subject Re: Current use cases for POST /entities
Date Wed, 14 Sep 2016 07:43:46 GMT
Yes I agree this is reasonable to not send information supplied by the 
sender in the create response. If there are multiple objects being created 
we need to return a list of containing the new guids 
ResournceProvider.createResources already returns lists of guids already  
- we would need to ensure that the order was the same as the request, it 
might be worth adding a name (ideally fully qualified name) with the guid 
for readability and to aid debugging. If there are contained objects that 
are created with guids, it would be worth returning a response which 
contains the nested object structure, but only containing the guids (and 
name) in the object bodies.
With the guids, we could return other useful information like  the last 
update date and created date. It might be that we introduce a start date 
which could also gain the creation date by default. My suggestion would be 
to put this sort of response information in a named json object that used 
by creates , updates , deletes, gets and is consistently used by all 
objects (types, terms , tags entities etc). I would like that this sort of 
information should go in a top level object (I notice interface 
ResourceDefinition does not contain this information). 
   all the best, David Radley. 

From:   Shwetha Shivalingamurthy <>
To:     "" <>
Date:   14/09/2016 06:13
Subject:        Re: Current use cases for POST /entities

We can remove the definition, but I think we should return the guids.

The location in the response header contains the guid. But we should find
a way of returning all the guids created - probably list of locations?

When you change the create API, make sure to change even the update and
delete APIs.


On 14/09/16, 3:46 AM, "Suma Shivaprasad" <>

>On Mon, Sep 12, 2016 at 9:22 PM, Apoorv Naik <>
>> Is anyone relying on the definition object within the response of a
>> entity call ? If not, let¹s remove it from the response as it can be
>> inferred from the request body itself and the only useful piece seems
>>to be
>> the GUIDs.

Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message