0 Replies Latest reply on Jan 17, 2018 3:46 PM by stroebeljc RSS
    stroebeljc Explorer

    Why does the v2 RestAPI wadl use references in many places where it actually provides the object?

    I noticed that many of the type definitions in the v2 rest wadl use References in their definitions, even though they often provide the object when queried.  For example, when getting a DataItemValue, the wadl indicates that a DataItemReference is returned, which is correct.  However, it appears that for performance and convenience, the DataItem object itself is also included.  The same DataItemValue includes an AssetReference, but does not provide the Asset object, which also makes sense as far as interface design goes.


    There are many other examples.  My question is, can the WADL be updated to properly reflect the structures being provided so that we don't have to make assumptions or just "know" what information is actually being provided by the interface?