API Traversal
-------------

The system represents the reference of an entity in the system as
`Hypermedia as the Engine of Application State <http://en.wikipedia.org/wiki/HATEOAS>`_ (HATEOS).
Each reference position is represented by an object pair pkid and href.

A client integrates with |VOSS-4-UC| entirely through hypermedia dynamically provided
by the |VOSS-4-UC| application and does not need any prior knowledge about how to interact
with the system other than a generic understanding of hypermedia. This means that
no `WADL <http://en.wikipedia.org/wiki/Web_Application_Description_Language>`_
is provided. This also means that the client and |VOSS-4-UC| can be decoupled in
a way that allows |VOSS-4-UC| to evolve independently.

A client enters the |VOSS-4-UC| through a simple fixed URL. All future actions the client
may take are discovered within resource representations returned from the server

The detailed URL tree endpoint information is available in the relevant 
API Reference Guides for the core and features.

This response emulates the HierarchyNode list response, and utilizes the parent
and children in the meta references section of the response, as discussed in
Meta Data References.



.. |VOSS-4-UC| replace:: VOSS-4-UC
.. |Unified CM| replace:: Unified CM