anchor.diff:  
   |======
   
  -=== Query Parameters
  -
  -==== Paging Parameters
  -
  -include::examples/tables/PagingParametersImpl.adoc[]
  -
  -==== Role Permission Parameters
  -
  -include::examples/tables/RolePermissionParametersImpl.adoc[]
  -
  -==== Node Parameters
  -
  -Parameters which affect the optional returned user ```nodeReference``` property.
  -
  -include::examples/tables/NodeParametersImpl.adoc[]
  -
  -include::examples/tables/VersioningParametersImpl.adoc[]
  -
  -==== User Parameters
  -
  -include::examples/tables/UserParametersImpl.adoc[]
  -
   === Response Sample
   
   [source,json]
  
positive.code: 
  == Node
  
  Content items in Gentics Mesh are called *nodes* and represent the main structural building blocks for your content. A node is a specific piece of content within your project. The type of a node is always defined by the assigned schema. For example in product catalogue website you would create content types like product, product categories, product images, and product manuals.
  
  NOTE: In Gentics Mesh every content item is a node, there is no separate concept for media assets such as images, videos, and documents. Instead content types for them can be defined individually giving you the freedom to store any metadata with your assets. For your convenience Gentics Mesh is shipped with four default schemas - _image_, _video_, _audio_ and _document_ to be customized to your needs and liking!
  
  Nodes can be hierarchically structured if the schema is allowing this. They can be tagged by any number of tags. Furthermore, nodes can be translated into other languages, thus supporting multiple locales.
  
  NOTE: It is important to understand that a node is just a container for language variants. These language variants will store your fields. You can query individual language variants by appending the ```?lang``` query parameter. The ```language``` json property within an update or create request will be used to identify which language variant should be created or updated.
  
  === API endpoints
  [options="header",cols="2*"]
  
negative.code: | link:++raml#groups__groupUuid__users__userUuid__delete++[```DELETE /api/v1/group/:groupUuid/users/:userUuid```]
  |======
  
  === Response Sample
  
  [source,json]
  