Remove ImportResolutionMode.OPENCONFIG_SEMVER

[yangtools.git] / parser / yang-parser-rfc7950 / src / test / resources / openconfig-version / yin-input / basic-import / openconfig-extensions@2016-01-29.yin

diff --git a/parser/yang-parser-rfc7950/src/test/resources/openconfig-version/yin-input/basic-import/openconfig-extensions@2016-01-29.yin b/parser/yang-parser-rfc7950/src/test/resources/openconfig-version/yin-input/basic-import/openconfig-extensions@2016-01-29.yin
deleted file mode 100644 (file)
index e93a5a7..0000000
--- a/parser/yang-parser-rfc7950/src/test/resources/openconfig-version/yin-input/basic-import/openconfig-extensions@2016-01-29.yin
+++ /dev/null
@@ -1,97 +0,0 @@
-<?xml version="1.0" encoding="UTF-8"?>
-<module xmlns="urn:ietf:params:xml:ns:yang:yin:1" xmlns:oc-ext="http://openconfig.net/yang/openconfig-ext"
-        name="openconfig-extensions">
-    <yang-version value="1"></yang-version>
-    <namespace uri="http://openconfig.net/yang/openconfig-ext"></namespace>
-    <prefix value="oc-ext"></prefix>
-    <organization>
-        <text>OpenConfig working group</text>
-    </organization>
-    <contact>
-        <text>OpenConfig working group www.openconfig.net</text>
-    </contact>
-    <description>
-        <text>
-            This module provides extensions to the YANG language to allow
-            OpenConfig specific functionality and meta-data to be defined.
-        </text>
-    </description>
-    <revision date="2017-01-29">
-        <description>
-            <text>Added extension for annotating encrypted values.</text>
-        </description>
-        <reference>
-            <text>TBD</text>
-        </reference>
-    </revision>
-    <revision date="2015-10-09">
-        <description>
-            <text>Initial OpenConfig public release</text>
-        </description>
-        <reference>
-            <text>TBD</text>
-        </reference>
-    </revision>
-    <revision date="2015-10-05">
-        <description>
-            <text>Initial revision</text>
-        </description>
-        <reference>
-            <text>TBD</text>
-        </reference>
-    </revision>
-    <oc-ext:openconfig-version semver="0.0.1"></oc-ext:openconfig-version>
-    <extension name="openconfig-version">
-        <argument name="semver">
-            <yin-element value="false"></yin-element>
-        </argument>
-        <status value="current"></status>
-        <description>
-            <text>The OpenConfig version number for the module. This is
-                expressed as a semantic version number of the form:
-                x.y.z
-                where:
-                * x corresponds to the major version,
-                * y corresponds to a minor version,
-                * z corresponds to a patch version.
-                This version corresponds to the model file within which it is
-                defined, and does not cover the whole set of OpenConfig models.
-                Where several modules are used to build up a single block of
-                functionality, the same module version is specified across each
-                file that makes up the module.
-
-                A major version number of 0 indicates that this model is still
-                in development (whether within OpenConfig or with industry
-                partners), and is potentially subject to change.
-
-                Following a release of major version 1, all modules will
-                increment major revision number where backwards incompatible
-                changes to the model are made.
-
-                The minor version is changed when features are added to the
-                model that do not impact current clients use of the model.
-
-                The patch-level version is incremented when non-feature changes
-                (such as bugfixes or clarifications to human-readable
-                descriptions that do not impact model functionality) are made
-                that maintain backwards compatibility.
-
-                The version number is stored in the module meta-data.
-            </text>
-        </description>
-    </extension>
-    <extension name="openconfig-encrypted-value">
-        <description>
-            <text>
-                This extension provides an annotation on schema nodes to
-                indicate that the corresponding value should be stored and
-                reported in encrypted form.
-                Clients reading the configuration or applied configuration
-                for the node should expect to receive only the encrypted value.
-                This annotation may be used on nodes such as secure passwords
-                in which the device never reports a cleartext value, even
-                if the input is provided as cleartext.
-            </text>
-        </description>
-    </extension>
-</module>
\ No newline at end of file