Merge branch 'devel'

Author: michalvasko

CMakeLists.txt

@@ -58,7 +58,7 @@ master branch. If you want the latest code from the devel branch, install `libya
 ```
 $ mkdir build; cd build
 $ cmake ..
-$ make 
+$ make
 # make install
 ```
 
@@ -125,6 +125,26 @@ The directory path can be also changed runtime via environment variable, e.g.:
 $ LIBYANG_EXTENSIONS_PLUGINS_DIR=`pwd`/my/relative/path yanglint
 ```
 
+#### Optimizations
+
+Whenever the latest revision of a schema is supposed to be loaded (import without specific revision),
+it is performed in the standard way, the first time. By default, every other time when the latest
+revision of the same schema is needed, the one initially loaded is reused. If you know this can cause
+problems meaning the latest available revision of a schema can change during operation, you can force
+libyang to always search for the schema anew by:
+
+```
+$ cmake -DENABLE_LATEST_REVISIONS=OFF ..
+```
+
+Also, it can be efficient to store certain information about schemas that is generated during parsing
+so that it does not need to be generated every time the schema is used, but it will consume some
+additional space. You can enable this cache with:
+
+```
+$ cmake -DENABLE_CACHE=ON ..
+```
+
 ### CMake Notes
 
 Note that, with CMake, if you want to change the compiler or its options after
@@ -158,7 +178,7 @@ libyang project includes features rich tool called `yanglint(1)` for validation
 and conversion of the schemas and YANG modeled data. The source codes are
 located at [`/tools/lint`](./tools/lint) and can be used to explore how an
 application is supposed to use the libyang library. `yanglint(1)` binary as
-well as its man page are installed together with the library itself. 
+well as its man page are installed together with the library itself.
 
 There is also [README](./tools/lint/examples/README.md) describing some examples of
 using `yanglint`.

README.md

@@ -0,0 +1,119 @@
+module ietf-datastores {
+  yang-version 1.1;
+  namespace "urn:ietf:params:xml:ns:yang:ietf-datastores";
+  prefix ds;
+
+  organization
+    "IETF Network Modeling (NETMOD) Working Group";
+
+  contact
+    "WG Web:   <https://datatracker.ietf.org/wg/netmod/>
+
+     WG List:  <mailto:[email protected]>
+
+     Author:   Martin Bjorklund
+               <mailto:[email protected]>
+
+     Author:   Juergen Schoenwaelder
+               <mailto:[email protected]>
+
+     Author:   Phil Shafer
+               <mailto:[email protected]>
+
+     Author:   Kent Watsen
+               <mailto:[email protected]>
+
+     Author:   Rob Wilton
+               <[email protected]>";
+
+  description
+    "This YANG module defines two sets of identities for datastores.
+     The first identifies the datastores themselves, the second
+     identifies datastore properties.
+
+     Copyright (c) 2017 IETF Trust and the persons identified as
+     authors of the code.  All rights reserved.
+
+     Redistribution and use in source and binary forms, with or
+     without modification, is permitted pursuant to, and subject to
+     the license terms contained in, the Simplified BSD License set
+     forth in Section 4.c of the IETF Trust's Legal Provisions
+     Relating to IETF Documents
+     (http://trustee.ietf.org/license-info).
+
+     This version of this YANG module is part of RFC XXXX
+     (http://www.rfc-editor.org/info/rfcxxxx); see the RFC itself
+     for full legal notices.";
+
+  revision 2017-08-17 {
+    description
+      "Initial revision.";
+    reference
+      "RFC XXXX: Network Management Datastore Architecture";
+  }
+
+  /*
+   * Identities
+   */
+
+  identity datastore {
+    description
+     "Abstract base identity for datastore identities.";
+  }
+
+  identity conventional {
+    base datastore;
+    description
+     "Abstract base identity for conventional configuration
+      datastores.";
+  }
+
+  identity running {
+    base conventional;
+    description
+     "The running configuration datastore.";
+  }
+
+  identity candidate {
+    base conventional;
+    description
+     "The candidate configuration datastore.";
+  }
+
+  identity startup {
+    base conventional;
+    description
+     "The startup configuration datastore.";
+  }
+
+  identity intended {
+    base conventional;
+    description
+     "The intended configuration datastore.";
+  }
+
+  identity dynamic {
+    base datastore;
+    description
+     "Abstract base identity for dynamic configuration datastores.";
+  }
+
+  identity operational {
+    base datastore;
+    description
+     "The operational state datastore.";
+  }
+
+  /*
+   * Type definitions
+   */
+
+  typedef datastore-ref {
+    type identityref {
+      base datastore;
+    }
+    description
+      "A datastore identity reference.";
+  }
+
+}