anchor.diff:  
   Typically, each project will require a set of different content types. Together they can be considered the content model of your project. Staying with the example of a product catalogue website: a product, product category, product image, and product manual each represent a separate content type. In Gentics Mesh, a *schema* is used to define such content types in terms of a couple of standard fields (e.g. ```uuid```, ```name```, ```description```, ```version```, etc.) and an arbitrary number of custom fields (e.g., ```string```, ```number```, ```HTML```, ```date```, ```binary```, ```list```, ```node```, ```micronode```, ```boolean```). You can think of a schema as a blueprint for new content items.  
   
  -TIP: Using the ```container``` property, a schema can be configured to allow for hierarchically structuring nodes. Nodes based on a such a schema may contain child nodes. This is the basis for building http://getmesh.io/docs/beta/#_contenttrees[content trees] in Gentics Mesh and leveraging the power of automatic http://getmesh.io/docs/beta/#_navigation[navigation menus], http://getmesh.io/docs/beta/#_breadcrumbs[breadcrumbs] and http://getmesh.io/docs/beta/#_prettyurls[pretty URLs].
  +TIP: Using the ```container``` property, a schema can be configured to allow for hierarchically structuring nodes. Nodes based on a such a schema may contain child nodes. This is the basis for building link:features.html#_contenttrees[content trees] in Gentics Mesh and leveraging the power of automatic link:features.html#_navigation[navigation menus], link:features.html#_breadcrumbs[breadcrumbs] and link:features.html#_prettyurls[pretty URLs].
   
   === API end points
   
  
positive.code: Gentics Mesh *users* can be physical persons or client apps interacting with elements in Gentics Mesh. Both have a user object counterpart in Gentics Mesh. 
  This user object has a standard set of properties, e.g.```firstname```, ```lastname```, ```username```, and ```emailAddress``` , which can be extended by referencing a custom user object. The property ```nodeReference``` is used for storing additional user-related data, thus allowing for extensible user profiles. 
  
  In order to be able to store and retrieve content, a user needs to authenticate using one of the available http://getmesh.io/docs/beta/#_authentication[authentication] mechanisms. 
  
  === API end points
  
  
negative.code: | Delete the schema with the given uuid.
  | ```DELETE /api/v1/schema/:schemaUuid```
  
  | Apply the provided changes on the latest version of the schema and link:features.html#_schema_microschema_migration[migrate] all nodes which are based on the schema.
  | ```POST /api/v1/schema/:schemaUuid/changes```
  
  | Compare the given schema with the stored schema and create a changeset for link:features.html#_schema_microschema_migration[migration]. 
  | ```POST /api/v1/schema/:schemaUuid/diff```
  
  |======
  