private static SemVer getSemanticVersion(final StatementContext statement, final String sourceName) {
final List<StatementContext> subStatements = statement.statement();
String semVerString = null;
- final String semVerStmtName = SupportedExtensionsMapping.SEMANTIC_VERSION.getStatementName().getLocalName();
+ final String semVerStmtName = SupportedExtensionsMapping.OPENCONFIG_VERSION.getStatementName().getLocalName();
for (final StatementContext subStatement : subStatements) {
final String subStatementName = Utils.trimPrefix(subStatement.keyword().getText());
if (semVerStmtName.equals(subStatementName)) {
.builder(YangStmtMapping.IMPORT)
.addMandatory(YangStmtMapping.PREFIX)
.addOptional(YangStmtMapping.REVISION_DATE)
- .addOptional(SupportedExtensionsMapping.SEMANTIC_VERSION)
+ .addOptional(SupportedExtensionsMapping.OPENCONFIG_VERSION)
.build();
public ImportStatementDefinition() {
.addAny(YangStmtMapping.TYPEDEF)
.addAny(YangStmtMapping.USES)
.addOptional(YangStmtMapping.YANG_VERSION)
- .addOptional(SupportedExtensionsMapping.SEMANTIC_VERSION)
+ .addOptional(SupportedExtensionsMapping.OPENCONFIG_VERSION)
.build();
public ModuleStatementSupport() {
import org.opendaylight.yangtools.yang.parser.spi.meta.AbstractStatementSupport;
import org.opendaylight.yangtools.yang.parser.spi.meta.SemanticVersionNamespace;
import org.opendaylight.yangtools.yang.parser.spi.meta.StmtContext;
-import org.opendaylight.yangtools.yang.parser.stmt.rfc6020.effective.SemanticVersionEffectiveStatementImpl;
+import org.opendaylight.yangtools.yang.parser.stmt.rfc6020.effective.OpenconfigVersionEffectiveStatementImpl;
@Beta
-public final class SemanticVersionStatementImpl extends AbstractDeclaredStatement<SemVer> implements
+public final class OpenconfigVersionStatementImpl extends AbstractDeclaredStatement<SemVer> implements
UnknownStatement<SemVer> {
private static final SubstatementValidator SUBSTATEMENT_VALIDATOR = SubstatementValidator.builder(
- SupportedExtensionsMapping.SEMANTIC_VERSION).build();
+ SupportedExtensionsMapping.OPENCONFIG_VERSION).build();
- SemanticVersionStatementImpl(
+ OpenconfigVersionStatementImpl(
final StmtContext<SemVer, UnknownStatement<SemVer>, ?> context) {
super(context);
}
- public static class SemanticVersionSupport
+ public static class OpenconfigVersionSupport
extends
AbstractStatementSupport<SemVer, UnknownStatement<SemVer>, EffectiveStatement<SemVer, UnknownStatement<SemVer>>> {
- public SemanticVersionSupport() {
- super(SupportedExtensionsMapping.SEMANTIC_VERSION);
+ public OpenconfigVersionSupport() {
+ super(SupportedExtensionsMapping.OPENCONFIG_VERSION);
}
@Override
@Override
public UnknownStatement<SemVer> createDeclared(
final StmtContext<SemVer, UnknownStatement<SemVer>, ?> ctx) {
- return new SemanticVersionStatementImpl(ctx);
+ return new OpenconfigVersionStatementImpl(ctx);
}
@Override
public EffectiveStatement<SemVer, UnknownStatement<SemVer>> createEffective(
final StmtContext<SemVer, UnknownStatement<SemVer>, EffectiveStatement<SemVer, UnknownStatement<SemVer>>> ctx) {
- return new SemanticVersionEffectiveStatementImpl(ctx);
+ return new OpenconfigVersionEffectiveStatementImpl(ctx);
}
@Override
import org.opendaylight.yangtools.yang.model.api.meta.EffectiveStatement;
import org.opendaylight.yangtools.yang.model.api.meta.StatementDefinition;
import org.opendaylight.yangtools.yang.parser.stmt.rfc6020.effective.AnyxmlSchemaLocationEffectiveStatementImpl;
-import org.opendaylight.yangtools.yang.parser.stmt.rfc6020.effective.SemanticVersionEffectiveStatementImpl;
+import org.opendaylight.yangtools.yang.parser.stmt.rfc6020.effective.OpenconfigVersionEffectiveStatementImpl;
@Beta
public enum SupportedExtensionsMapping implements StatementDefinition {
ANYXML_SCHEMA_LOCATION("urn:opendaylight:yang:extension:yang-ext", "2013-07-09",
AnyxmlSchemaLocationStatementImpl.class, AnyxmlSchemaLocationEffectiveStatementImpl.class,
"anyxml-schema-location", "target-node", false),
- SEMANTIC_VERSION("urn:opendaylight:yang:extension:semantic-version", "2016-02-02",
- SemanticVersionStatementImpl.class, SemanticVersionEffectiveStatementImpl.class,
- "semantic-version", "semantic-version", false);
+ OPENCONFIG_VERSION("http://openconfig.net/yang/openconfig-ext",
+ OpenconfigVersionStatementImpl.class, OpenconfigVersionEffectiveStatementImpl.class,
+ "openconfig-version", "semver", false);
private final Class<? extends DeclaredStatement<?>> type;
private final Class<? extends EffectiveStatement<?, ?>> effectiveType;
.addSupport(sourceLocal(BelongsToModuleContext.class))
.addSupport(sourceLocal(QNameToStatementDefinition.class))
.addSupport(sourceLocal(BelongsToPrefixToModuleName.class))
- .addSupport(new SemanticVersionStatementImpl.SemanticVersionSupport())
+ .addSupport(new OpenconfigVersionStatementImpl.OpenconfigVersionSupport())
.addSupport(global(SemanticVersionNamespace.class))
.addSupport(global(SemanticVersionModuleNamespace.class))
.addSupport(sourceLocal(ImpPrefixToSemVerModuleIdentifier.class))
final YangVersionEffectiveStatementImpl yangVersionStmt = firstEffective(YangVersionEffectiveStatementImpl.class);
this.yangVersion = (yangVersionStmt == null) ? YangVersion.VERSION_1 : yangVersionStmt.argument();
- final SemanticVersionEffectiveStatementImpl semanticVersionStmt = firstEffective(SemanticVersionEffectiveStatementImpl.class);
+ final OpenconfigVersionEffectiveStatementImpl semanticVersionStmt =
+ firstEffective(OpenconfigVersionEffectiveStatementImpl.class);
this.semanticVersion = (semanticVersionStmt == null) ? DEFAULT_SEMANTIC_VERSION : semanticVersionStmt.argument();
final OrganizationEffectiveStatementImpl organizationStmt = firstEffective(OrganizationEffectiveStatementImpl.class);
import org.opendaylight.yangtools.yang.parser.spi.meta.StmtContext;
@Beta
-public final class SemanticVersionEffectiveStatementImpl extends
+public final class OpenconfigVersionEffectiveStatementImpl extends
UnknownEffectiveStatementBase<SemVer> {
private final SchemaPath path;
- public SemanticVersionEffectiveStatementImpl(
+ public OpenconfigVersionEffectiveStatementImpl(
final StmtContext<SemVer, UnknownStatement<SemVer>, ?> ctx) {
super(ctx);
path = ctx.getParentContext().getSchemaPath().get().createChild(getNodeType());
if (getClass() != obj.getClass()) {
return false;
}
- SemanticVersionEffectiveStatementImpl other = (SemanticVersionEffectiveStatementImpl) obj;
+ OpenconfigVersionEffectiveStatementImpl other = (OpenconfigVersionEffectiveStatementImpl) obj;
if (!Objects.equals(path, other.path)) {
return false;
}
.builder(YangStmtMapping.IMPORT)
.addMandatory(YangStmtMapping.PREFIX)
.addOptional(YangStmtMapping.REVISION_DATE)
- .addOptional(SupportedExtensionsMapping.SEMANTIC_VERSION)
+ .addOptional(SupportedExtensionsMapping.OPENCONFIG_VERSION)
.addOptional(YangStmtMapping.DESCRIPTION)
.addOptional(YangStmtMapping.REFERENCE)
.build();
.addAny(YangStmtMapping.TYPEDEF)
.addAny(YangStmtMapping.USES)
.addMandatory(YangStmtMapping.YANG_VERSION)
- .addOptional(SupportedExtensionsMapping.SEMANTIC_VERSION)
+ .addOptional(SupportedExtensionsMapping.OPENCONFIG_VERSION)
.build();
@Override
import org.opendaylight.yangtools.yang.parser.util.ASTSchemaSource;
import org.opendaylight.yangtools.yang.parser.util.TextToASTTransformer;
-public class SemVerSharedSchemaRepositoryTest {
+public class OpenconfigVerSharedSchemaRepositoryTest {
@Test
public void testSemVerSharedSchemaRepository() throws Exception {
final SharedSchemaRepository sharedSchemaRepository = new SharedSchemaRepository(
- "sem-ver-shared-schema-repo-test");
+ "openconfig-ver-shared-schema-repo-test");
final SettableSchemaProvider<ASTSchemaSource> bar = getImmediateYangSourceProviderFromResource(
- "/semantic-version/semver-shared-schema-repository/bar@2016-01-01.yang");
+ "/openconfig-version/openconfigver-shared-schema-repository/bar@2016-01-01.yang");
bar.register(sharedSchemaRepository);
bar.setResult();
final SettableSchemaProvider<ASTSchemaSource> foo = getImmediateYangSourceProviderFromResource(
- "/semantic-version/semver-shared-schema-repository/foo.yang");
+ "/openconfig-version/openconfigver-shared-schema-repository/foo.yang");
foo.register(sharedSchemaRepository);
foo.setResult();
final SettableSchemaProvider<ASTSchemaSource> semVer = getImmediateYangSourceProviderFromResource(
- "/semantic-version/semver-shared-schema-repository/semantic-version.yang");
+ "/openconfig-version/openconfigver-shared-schema-repository/openconfig-extensions.yang");
semVer.register(sharedSchemaRepository);
semVer.setResult();
final SharedSchemaRepository sharedSchemaRepository = new SharedSchemaRepository("shared-schema-repo-test");
final SettableSchemaProvider<ASTSchemaSource> bar = getImmediateYangSourceProviderFromResource(
- "/semantic-version/shared-schema-repository/bar@2016-01-01.yang");
+ "/openconfig-version/shared-schema-repository/bar@2016-01-01.yang");
bar.register(sharedSchemaRepository);
bar.setResult();
final SettableSchemaProvider<ASTSchemaSource> foo = getImmediateYangSourceProviderFromResource(
- "/semantic-version/shared-schema-repository/foo.yang");
+ "/openconfig-version/shared-schema-repository/foo.yang");
foo.register(sharedSchemaRepository);
foo.setResult();
final SettableSchemaProvider<ASTSchemaSource> semVer = getImmediateYangSourceProviderFromResource(
- "/semantic-version/shared-schema-repository/semantic-version.yang");
+ "/openconfig-version/shared-schema-repository/openconfig-extensions.yang");
semVer.register(sharedSchemaRepository);
semVer.setResult();
* terms of the Eclipse Public License v1.0 which accompanies this distribution,
* and is available at http://www.eclipse.org/legal/epl-v10.html
*/
-package org.opendaylight.yangtools.yang.stmt.semver;
+package org.opendaylight.yangtools.yang.stmt.openconfigver;
import static org.junit.Assert.assertEquals;
import static org.junit.Assert.assertNotNull;
import org.opendaylight.yangtools.yang.parser.spi.meta.ReactorException;
import org.opendaylight.yangtools.yang.stmt.StmtTestUtils;
-public class SemanticVersionBorderCaseTest {
+public class OpenconfigVersionBorderCaseTest {
@Test
public void borderCaseValidMajorTest() throws Exception {
- SchemaContext context = StmtTestUtils.parseYangSources("/semantic-version/border-case/border-case-valid-major",
+ SchemaContext context = StmtTestUtils.parseYangSources("/openconfig-version/border-case/border-case-valid-major",
StatementParserMode.SEMVER_MODE);
assertNotNull(context);
Module foo = context.findModuleByNamespace(new URI("foo")).iterator().next();
- Module semVer = context.findModuleByNamespace(new URI("urn:opendaylight:yang:extension:semantic-version"))
+ Module semVer = context.findModuleByNamespace(new URI("http://openconfig.net/yang/openconfig-ext"))
.iterator().next();
assertEquals(SemVer.valueOf("0.0.1"), semVer.getSemanticVersion());
@Test
public void borderCaseValidMinorTest() throws Exception {
- SchemaContext context = StmtTestUtils.parseYangSources("/semantic-version/border-case/border-case-valid-minor",
+ SchemaContext context = StmtTestUtils.parseYangSources("/openconfig-version/border-case/border-case-valid-minor",
StatementParserMode.SEMVER_MODE);
assertNotNull(context);
Module foo = context.findModuleByNamespace(new URI("foo")).iterator().next();
- Module semVer = context.findModuleByNamespace(new URI("urn:opendaylight:yang:extension:semantic-version"))
+ Module semVer = context.findModuleByNamespace(new URI("http://openconfig.net/yang/openconfig-ext"))
.iterator().next();
assertEquals(SemVer.valueOf("0.0.1"), semVer.getSemanticVersion());
@Test
public void borderCaseValidPatchTest() throws Exception {
- SchemaContext context = StmtTestUtils.parseYangSources("/semantic-version/border-case/border-case-valid-patch",
+ SchemaContext context = StmtTestUtils.parseYangSources("/openconfig-version/border-case/border-case-valid-patch",
StatementParserMode.SEMVER_MODE);
assertNotNull(context);
Module foo = context.findModuleByNamespace(new URI("foo")).iterator().next();
- Module semVer = context.findModuleByNamespace(new URI("urn:opendaylight:yang:extension:semantic-version"))
+ Module semVer = context.findModuleByNamespace(new URI("http://openconfig.net/yang/openconfig-ext"))
.iterator().next();
assertEquals(SemVer.valueOf("0.0.1"), semVer.getSemanticVersion());
@Test
public void borderCaseInvalidMajorTest() throws Exception {
try {
- StmtTestUtils.parseYangSources("/semantic-version/border-case/border-case-invalid-major",
+ StmtTestUtils.parseYangSources("/openconfig-version/border-case/border-case-invalid-major",
StatementParserMode.SEMVER_MODE);
- fail("Test should fail due to invalid semantic version");
+ fail("Test should fail due to invalid openconfig version");
} catch (ReactorException e) {
assertTrue(e.getCause().getMessage()
.startsWith("Unable to find module compatible with requested import [bar(5.5.5)]."));
@Test
public void borderCaseInvalidMinorTest() throws Exception {
try {
- StmtTestUtils.parseYangSources("/semantic-version/border-case/border-case-invalid-minor",
+ StmtTestUtils.parseYangSources("/openconfig-version/border-case/border-case-invalid-minor",
StatementParserMode.SEMVER_MODE);
- fail("Test should fail due to invalid semantic version");
+ fail("Test should fail due to invalid openconfig version");
} catch (ReactorException e) {
assertTrue(e.getCause().getMessage()
.startsWith("Unable to find module compatible with requested import [bar(5.5.5)]."));
@Test
public void borderCaseInvalidPatchTest() throws Exception {
try {
- StmtTestUtils.parseYangSources("/semantic-version/border-case/border-case-invalid-patch",
+ StmtTestUtils.parseYangSources("/openconfig-version/border-case/border-case-invalid-patch",
StatementParserMode.SEMVER_MODE);
- fail("Test should fail due to invalid semantic version");
+ fail("Test should fail due to invalid openconfig version");
} catch (ReactorException e) {
assertTrue(e.getCause().getMessage()
.startsWith("Unable to find module compatible with requested import [bar(5.5.5)]."));
* terms of the Eclipse Public License v1.0 which accompanies this distribution,
* and is available at http://www.eclipse.org/legal/epl-v10.html
*/
-package org.opendaylight.yangtools.yang.stmt.semver;
+package org.opendaylight.yangtools.yang.stmt.openconfigver;
import static org.junit.Assert.assertEquals;
import static org.junit.Assert.assertNotNull;
import org.opendaylight.yangtools.yang.model.util.SchemaContextUtil;
import org.opendaylight.yangtools.yang.stmt.StmtTestUtils;
-public class SemanticVersionComplexTest {
+public class OpenconfigVersionComplexTest {
@Test
public void complexTest1() throws Exception {
- final SchemaContext context = StmtTestUtils.parseYangSources("/semantic-version/complex/complex-1",
+ final SchemaContext context = StmtTestUtils.parseYangSources("/openconfig-version/complex/complex-1",
StatementParserMode.SEMVER_MODE);
verifySchemaContextTest1(context);
}
@Test
public void complexTest1Yang1_1() throws Exception {
- final SchemaContext context = StmtTestUtils.parseYangSources("/rfc7950/semantic-version/complex-1",
+ final SchemaContext context = StmtTestUtils.parseYangSources("/rfc7950/openconfig-version/complex-1",
StatementParserMode.SEMVER_MODE);
verifySchemaContextTest1(context);
}
final Module foo = context.findModuleByNamespace(URI.create("foo")).iterator().next();
final Module semVer = context.findModuleByNamespace(
- URI.create("urn:opendaylight:yang:extension:semantic-version")).iterator().next();
+ URI.create("http://openconfig.net/yang/openconfig-ext")).iterator().next();
// check module versions
assertEquals(SemVer.valueOf("1.3.95"), semVer.getSemanticVersion());
@Test
public void complexTest2() throws Exception {
- final SchemaContext context = StmtTestUtils.parseYangSources("/semantic-version/complex/complex-2",
+ final SchemaContext context = StmtTestUtils.parseYangSources("/openconfig-version/complex/complex-2",
StatementParserMode.SEMVER_MODE);
verifySchemaContextTest2(context);
}
@Test
public void complexTest2Yang1_1() throws Exception {
- final SchemaContext context = StmtTestUtils.parseYangSources("/rfc7950/semantic-version/complex-2",
+ final SchemaContext context = StmtTestUtils.parseYangSources("/rfc7950/openconfig-version/complex-2",
StatementParserMode.SEMVER_MODE);
verifySchemaContextTest2(context);
}
final Module foo = context.findModuleByNamespace(URI.create("foo")).iterator().next();
final Module semVer = context.findModuleByNamespace(URI.create(
- "urn:opendaylight:yang:extension:semantic-version")).iterator().next();
+ "http://openconfig.net/yang/openconfig-ext")).iterator().next();
// check module versions
assertEquals(SemVer.valueOf("2.5.50"), semVer.getSemanticVersion());
* terms of the Eclipse Public License v1.0 which accompanies this distribution,
* and is available at http://www.eclipse.org/legal/epl-v10.html
*/
-package org.opendaylight.yangtools.yang.stmt.semver;
+package org.opendaylight.yangtools.yang.stmt.openconfigver;
import static org.junit.Assert.assertEquals;
import static org.junit.Assert.assertNotNull;
import org.opendaylight.yangtools.yang.parser.spi.meta.ReactorException;
import org.opendaylight.yangtools.yang.stmt.StmtTestUtils;
-public class SemanticVersionDefaultsTest {
+public class OpenconfigVersionDefaultsTest {
@Test
public void defaultsTest() throws Exception {
- SchemaContext context = StmtTestUtils.parseYangSources("/semantic-version/defaults/defaults",
+ SchemaContext context = StmtTestUtils.parseYangSources("/openconfig-version/defaults/defaults",
StatementParserMode.SEMVER_MODE);
assertNotNull(context);
@Test
public void defaultMajorValidTest() throws Exception {
- SchemaContext context = StmtTestUtils.parseYangSources("/semantic-version/defaults/default-major-valid",
+ SchemaContext context = StmtTestUtils.parseYangSources("/openconfig-version/defaults/default-major-valid",
StatementParserMode.SEMVER_MODE);
assertNotNull(context);
@Test
public void defaultMajorInvalidTest() throws Exception {
try {
- StmtTestUtils.parseYangSources("/semantic-version/defaults/default-major-invalid",
+ StmtTestUtils.parseYangSources("/openconfig-version/defaults/default-major-invalid",
StatementParserMode.SEMVER_MODE);
- fail("Test should fail due to invalid semantic version");
+ fail("Test should fail due to invalid openconfig version");
} catch (ReactorException e) {
assertTrue(e.getCause().getMessage()
.startsWith("Unable to find module compatible with requested import [bar(0.0.0)]."));
* terms of the Eclipse Public License v1.0 which accompanies this distribution,
* and is available at http://www.eclipse.org/legal/epl-v10.html
*/
-package org.opendaylight.yangtools.yang.stmt.semver;
+package org.opendaylight.yangtools.yang.stmt.openconfigver;
import static org.junit.Assert.assertEquals;
import static org.junit.Assert.assertNotNull;
import org.opendaylight.yangtools.yang.model.repo.api.StatementParserMode;
import org.opendaylight.yangtools.yang.stmt.StmtTestUtils;
-public class SemanticVersionIgnoringRevisionTest {
+public class OpenconfigVersionIgnoringRevisionTest {
@Test
public void ignoringRevisionTest() throws Exception {
- SchemaContext context = StmtTestUtils.parseYangSources("/semantic-version/ignoring-revision",
+ SchemaContext context = StmtTestUtils.parseYangSources("/openconfig-version/ignoring-revision",
StatementParserMode.SEMVER_MODE);
assertNotNull(context);
Module foo = context.findModuleByNamespace(new URI("foo")).iterator().next();
Module bar = context.findModuleByNamespace(new URI("bar")).iterator().next();
- Module semVer = context.findModuleByNamespace(new URI("urn:opendaylight:yang:extension:semantic-version"))
+ Module semVer = context.findModuleByNamespace(new URI("http://openconfig.net/yang/openconfig-ext"))
.iterator().next();
assertEquals(SemVer.valueOf("0.0.1"), semVer.getSemanticVersion());
@Test
public void ignoringRevision2Test() throws Exception {
- SchemaContext context = StmtTestUtils.parseYangSources("/semantic-version/ignoring-revision-2",
+ SchemaContext context = StmtTestUtils.parseYangSources("/openconfig-version/ignoring-revision-2",
StatementParserMode.SEMVER_MODE);
assertNotNull(context);
Module foo = context.findModuleByNamespace(new URI("foo")).iterator().next();
- Module semVer = context.findModuleByNamespace(new URI("urn:opendaylight:yang:extension:semantic-version"))
+ Module semVer = context.findModuleByNamespace(new URI("http://openconfig.net/yang/openconfig-ext"))
.iterator().next();
Module bar = StmtTestUtils.findImportedModule(context, foo, "bar");
* terms of the Eclipse Public License v1.0 which accompanies this distribution,
* and is available at http://www.eclipse.org/legal/epl-v10.html
*/
-package org.opendaylight.yangtools.yang.stmt.semver;
+package org.opendaylight.yangtools.yang.stmt.openconfigver;
import static org.junit.Assert.assertEquals;
import static org.junit.Assert.assertNotNull;
import org.opendaylight.yangtools.yang.parser.spi.meta.ReactorException;
import org.opendaylight.yangtools.yang.stmt.StmtTestUtils;
-public class SemanticVersionImportTest {
+public class OpenconfigVersionImportTest {
@Test
public void importValidTest() throws Exception {
- SchemaContext context = StmtTestUtils.parseYangSources("/semantic-version/import/import-valid",
+ SchemaContext context = StmtTestUtils.parseYangSources("/openconfig-version/import/import-valid",
StatementParserMode.SEMVER_MODE);
assertNotNull(context);
- Module semVer = context.findModuleByNamespace(new URI("urn:opendaylight:yang:extension:semantic-version"))
+ Module semVer = context.findModuleByNamespace(new URI("http://openconfig.net/yang/openconfig-ext"))
.iterator().next();
assertEquals(SemVer.valueOf("1.0.0"), semVer.getSemanticVersion());
@Test
public void importInvalidDeprecatedTest1() throws Exception {
try {
- StmtTestUtils.parseYangSources("/semantic-version/import/import-invalid-deprecated-1",
+ StmtTestUtils.parseYangSources("/openconfig-version/import/import-invalid-deprecated-1",
StatementParserMode.SEMVER_MODE);
- fail("Test should fail due to invalid import of semantic-version module");
+ fail("Test should fail due to invalid import of openconfig-version module");
} catch (ReactorException e) {
assertTrue(e.getCause().getMessage().startsWith(
- "Unable to find module compatible with requested import " + "[semantic-version(1.0.0)]."));
+ "Unable to find module compatible with requested import " + "[openconfig-extensions(1.0.0)]."));
}
}
@Test
public void importInvalidDeprecatedTest2() throws Exception {
try {
- StmtTestUtils.parseYangSources("/semantic-version/import/import-invalid-deprecated-2",
+ StmtTestUtils.parseYangSources("/openconfig-version/import/import-invalid-deprecated-2",
StatementParserMode.SEMVER_MODE);
- fail("Test should fail due to invalid import of semantic-version module");
+ fail("Test should fail due to invalid import of openconfig-version module");
} catch (ReactorException e) {
assertTrue(e.getCause().getMessage().startsWith(
- "Unable to find module compatible with requested import " + "[semantic-version(0.9.9)]."));
+ "Unable to find module compatible with requested import " + "[openconfig-extensions(0.9.9)]."));
}
}
@Test
public void importInvalidNotsufficientTest1() throws Exception {
try {
- StmtTestUtils.parseYangSources("/semantic-version/import/import-invalid-notsufficient-1",
+ StmtTestUtils.parseYangSources("/openconfig-version/import/import-invalid-notsufficient-1",
StatementParserMode.SEMVER_MODE);
- fail("Test should fail due to invalid import of semantic-version module");
+ fail("Test should fail due to invalid import of openconfig-version module");
} catch (ReactorException e) {
assertTrue(e.getCause().getMessage().startsWith(
- "Unable to find module compatible with requested import " + "[semantic-version(2.0.0)]."));
+ "Unable to find module compatible with requested import " + "[openconfig-extensions(2.0.0)]."));
}
}
@Test
public void importInvalidNotsufficientTest2() throws Exception {
try {
- StmtTestUtils.parseYangSources("/semantic-version/import/import-invalid-notsufficient-2",
+ StmtTestUtils.parseYangSources("/openconfig-version/import/import-invalid-notsufficient-2",
StatementParserMode.SEMVER_MODE);
- fail("Test should fail due to invalid import of semantic-version module");
+ fail("Test should fail due to invalid import of openconfig-version module");
} catch (ReactorException e) {
assertTrue(e.getCause().getMessage().startsWith(
- "Unable to find module compatible with requested import " + "[semantic-version(2.0.5)]."));
+ "Unable to find module compatible with requested import " + "[openconfig-extensions(2.0.5)]."));
}
}
}
* terms of the Eclipse Public License v1.0 which accompanies this distribution,
* and is available at http://www.eclipse.org/legal/epl-v10.html
*/
-package org.opendaylight.yangtools.yang.stmt.semver;
+package org.opendaylight.yangtools.yang.stmt.openconfigver;
import static org.junit.Assert.assertEquals;
import static org.junit.Assert.assertNotNull;
import org.opendaylight.yangtools.yang.parser.spi.meta.ReactorException;
import org.opendaylight.yangtools.yang.stmt.StmtTestUtils;
-public class SemanticVersionMultipleImportTest {
+public class OpenconfigVersionMultipleImportTest {
@Test
public void multipleInvalidDeprecatedTest() throws Exception {
try {
- StmtTestUtils.parseYangSources("/semantic-version/multiple/multiple-invalid-deprecated",
+ StmtTestUtils.parseYangSources("/openconfig-version/multiple/multiple-invalid-deprecated",
StatementParserMode.SEMVER_MODE);
- fail("Test should fail due to invalid semantic version");
+ fail("Test should fail due to invalid openconfig version");
} catch (ReactorException e) {
assertTrue(e.getCause().getMessage()
.startsWith("Unable to find module compatible with requested import [bar(1.0.0)]."));
@Test
public void multipleInvalidNosufficientTest() throws Exception {
try {
- StmtTestUtils.parseYangSources("/semantic-version/multiple/multiple-invalid-nosufficient",
+ StmtTestUtils.parseYangSources("/openconfig-version/multiple/multiple-invalid-nosufficient",
StatementParserMode.SEMVER_MODE);
- fail("Test should fail due to invalid semantic version");
+ fail("Test should fail due to invalid openconfig version");
} catch (ReactorException e) {
assertTrue(e.getCause().getMessage()
.startsWith("Unable to find module compatible with requested import [bar(2.5.5)]."));
@Test
public void multipleValidDefaultsTest() throws Exception {
- SchemaContext context = StmtTestUtils.parseYangSources("/semantic-version/multiple/multiple-valid-defaults",
+ SchemaContext context = StmtTestUtils.parseYangSources("/openconfig-version/multiple/multiple-valid-defaults",
StatementParserMode.SEMVER_MODE);
assertNotNull(context);
Module foo = context.findModuleByNamespace(new URI("foo")).iterator().next();
- Module semVer = context.findModuleByNamespace(new URI("urn:opendaylight:yang:extension:semantic-version"))
+ Module semVer = context.findModuleByNamespace(new URI("http://openconfig.net/yang/openconfig-ext"))
.iterator().next();
assertEquals(SemVer.valueOf("0.0.1"), semVer.getSemanticVersion());
@Test
public void multipleValidSpecifiedTest() throws Exception {
- SchemaContext context = StmtTestUtils.parseYangSources("/semantic-version/multiple/multiple-valid-specified",
+ SchemaContext context = StmtTestUtils.parseYangSources("/openconfig-version/multiple/multiple-valid-specified",
StatementParserMode.SEMVER_MODE);
assertNotNull(context);
Module foo = context.findModuleByNamespace(new URI("foo")).iterator().next();
- Module semVer = context.findModuleByNamespace(new URI("urn:opendaylight:yang:extension:semantic-version"))
+ Module semVer = context.findModuleByNamespace(new URI("http://openconfig.net/yang/openconfig-ext"))
.iterator().next();
assertEquals(SemVer.valueOf("0.0.1"), semVer.getSemanticVersion());
* terms of the Eclipse Public License v1.0 which accompanies this distribution,
* and is available at http://www.eclipse.org/legal/epl-v10.html
*/
-package org.opendaylight.yangtools.yang.stmt.semver;
+package org.opendaylight.yangtools.yang.stmt.openconfigver;
import static org.junit.Assert.assertEquals;
import static org.junit.Assert.assertNotNull;
import org.opendaylight.yangtools.yang.model.repo.api.StatementParserMode;
import org.opendaylight.yangtools.yang.stmt.StmtTestUtils;
-public class SemanticVersionPositionTest {
+public class OpenconfigVersionPositionTest {
@Test
public void positionHeadTest() throws Exception {
- SchemaContext context = StmtTestUtils.parseYangSources("/semantic-version/position/position-head",
+ SchemaContext context = StmtTestUtils.parseYangSources("/openconfig-version/position/position-head",
StatementParserMode.SEMVER_MODE);
assertNotNull(context);
Module foo = context.findModuleByNamespace(new URI("foo")).iterator().next();
Module bar = context.findModuleByNamespace(new URI("bar")).iterator().next();
- Module semVer = context.findModuleByNamespace(new URI("urn:opendaylight:yang:extension:semantic-version"))
+ Module semVer = context.findModuleByNamespace(new URI("http://openconfig.net/yang/openconfig-ext"))
.iterator().next();
assertEquals(SemVer.valueOf("0.0.1"), semVer.getSemanticVersion());
@Test
public void positionMiddleTest() throws Exception {
- SchemaContext context = StmtTestUtils.parseYangSources("/semantic-version/position/position-middle",
+ SchemaContext context = StmtTestUtils.parseYangSources("/openconfig-version/position/position-middle",
StatementParserMode.SEMVER_MODE);
assertNotNull(context);
Module foo = context.findModuleByNamespace(new URI("foo")).iterator().next();
Module bar = context.findModuleByNamespace(new URI("bar")).iterator().next();
- Module semVer = context.findModuleByNamespace(new URI("urn:opendaylight:yang:extension:semantic-version"))
+ Module semVer = context.findModuleByNamespace(new URI("http://openconfig.net/yang/openconfig-ext"))
.iterator().next();
assertEquals(SemVer.valueOf("0.0.1"), semVer.getSemanticVersion());
@Test
public void positiontailTest() throws Exception {
- SchemaContext context = StmtTestUtils.parseYangSources("/semantic-version/position/position-tail",
+ SchemaContext context = StmtTestUtils.parseYangSources("/openconfig-version/position/position-tail",
StatementParserMode.SEMVER_MODE);
assertNotNull(context);
Module foo = context.findModuleByNamespace(new URI("foo")).iterator().next();
Module bar = context.findModuleByNamespace(new URI("bar")).iterator().next();
- Module semVer = context.findModuleByNamespace(new URI("urn:opendaylight:yang:extension:semantic-version"))
+ Module semVer = context.findModuleByNamespace(new URI("http://openconfig.net/yang/openconfig-ext"))
.iterator().next();
assertEquals(SemVer.valueOf("0.0.1"), semVer.getSemanticVersion());
* terms of the Eclipse Public License v1.0 which accompanies this distribution,
* and is available at http://www.eclipse.org/legal/epl-v10.html
*/
-package org.opendaylight.yangtools.yang.stmt.semver;
+package org.opendaylight.yangtools.yang.stmt.openconfigver;
import static org.junit.Assert.assertEquals;
import static org.junit.Assert.assertNotNull;
import org.opendaylight.yangtools.yang.parser.spi.meta.ReactorException;
import org.opendaylight.yangtools.yang.stmt.StmtTestUtils;
-public class SemanticVersionTest {
+public class OpenconfigVersionTest {
@Test
public void basicTest() throws Exception {
- SchemaContext context = StmtTestUtils.parseYangSources("/semantic-version/basic",
+ SchemaContext context = StmtTestUtils.parseYangSources("/openconfig-version/basic",
StatementParserMode.SEMVER_MODE);
assertNotNull(context);
Module foo = context.findModuleByNamespace(new URI("foo")).iterator().next();
Module bar = context.findModuleByNamespace(new URI("bar")).iterator().next();
- Module semVer = context.findModuleByNamespace(new URI("urn:opendaylight:yang:extension:semantic-version"))
+ Module semVer = context.findModuleByNamespace(new URI("http://openconfig.net/yang/openconfig-ext"))
.iterator().next();
assertEquals(SemVer.valueOf("0.0.1"), semVer.getSemanticVersion());
@Test
public void basicTest2() throws Exception {
- SchemaContext context = StmtTestUtils.parseYangSources("/semantic-version/basic-2",
+ SchemaContext context = StmtTestUtils.parseYangSources("/openconfig-version/basic-2",
StatementParserMode.SEMVER_MODE);
assertNotNull(context);
Module foo = context.findModuleByNamespace(new URI("foo")).iterator().next();
Module bar = context.findModuleByNamespace(new URI("bar")).iterator().next();
- Module semVer = context.findModuleByNamespace(new URI("urn:opendaylight:yang:extension:semantic-version"))
+ Module semVer = context.findModuleByNamespace(new URI("http://openconfig.net/yang/openconfig-ext"))
.iterator().next();
assertEquals(SemVer.valueOf("0.0.1"), semVer.getSemanticVersion());
@Test
public void basicTest3() throws Exception {
- SchemaContext context = StmtTestUtils.parseYangSources("/semantic-version/basic-3",
+ SchemaContext context = StmtTestUtils.parseYangSources("/openconfig-version/basic-3",
StatementParserMode.SEMVER_MODE);
assertNotNull(context);
Module foo = context.findModuleByNamespace(new URI("foo")).iterator().next();
- Module semVer = context.findModuleByNamespace(new URI("urn:opendaylight:yang:extension:semantic-version"))
+ Module semVer = context.findModuleByNamespace(new URI("http://openconfig.net/yang/openconfig-ext"))
.iterator().next();
assertEquals(SemVer.valueOf("0.0.1"), semVer.getSemanticVersion());
@Test
public void basicImportTest1() throws Exception {
- SchemaContext context = StmtTestUtils.parseYangSources("/semantic-version/basic-import-1",
+ SchemaContext context = StmtTestUtils.parseYangSources("/openconfig-version/basic-import-1",
StatementParserMode.SEMVER_MODE);
assertNotNull(context);
Module foo = context.findModuleByNamespace(new URI("foo")).iterator().next();
- Module semVer = context.findModuleByNamespace(new URI("urn:opendaylight:yang:extension:semantic-version"))
+ Module semVer = context.findModuleByNamespace(new URI("http://openconfig.net/yang/openconfig-ext"))
.iterator().next();
assertEquals(SemVer.valueOf("0.0.1"), semVer.getSemanticVersion());
@Test
public void multipleModulesTest() throws Exception {
- SchemaContext context = StmtTestUtils.parseYangSources("/semantic-version/multiple-modules",
+ SchemaContext context = StmtTestUtils.parseYangSources("/openconfig-version/multiple-modules",
StatementParserMode.SEMVER_MODE);
assertNotNull(context);
Module foo = context.findModuleByNamespace(new URI("foo")).iterator().next();
- Module semVer = context.findModuleByNamespace(new URI("urn:opendaylight:yang:extension:semantic-version"))
+ Module semVer = context.findModuleByNamespace(new URI("http://openconfig.net/yang/openconfig-ext"))
.iterator().next();
assertEquals(SemVer.valueOf("0.0.1"), semVer.getSemanticVersion());
@Test
public void basicImportErrTest1() throws Exception {
try {
- StmtTestUtils.parseYangSources("/semantic-version/basic-import-invalid-1", StatementParserMode.SEMVER_MODE);
- fail("Test should fail due to invalid semantic version");
+ StmtTestUtils.parseYangSources("/openconfig-version/basic-import-invalid-1", StatementParserMode.SEMVER_MODE);
+ fail("Test should fail due to invalid openconfig version");
} catch (ReactorException e) {
assertTrue(e.getCause().getMessage()
.startsWith("Unable to find module compatible with requested import [bar(0.1.2)]."));
@Test
public void basicImportErrTest2() throws Exception {
try {
- StmtTestUtils.parseYangSources("/semantic-version/basic-import-invalid-2", StatementParserMode.SEMVER_MODE);
- fail("Test should fail due to invalid semantic version");
+ StmtTestUtils.parseYangSources("/openconfig-version/basic-import-invalid-2", StatementParserMode.SEMVER_MODE);
+ fail("Test should fail due to invalid openconfig version");
} catch (ReactorException e) {
assertTrue(e.getCause().getMessage()
.startsWith("Unable to find module compatible with requested import [bar(0.1.2)]."));
@Test
public void nodeTest() throws Exception {
- SchemaContext context = StmtTestUtils.parseYangSources("/semantic-version/node-test",
+ SchemaContext context = StmtTestUtils.parseYangSources("/openconfig-version/node-test",
StatementParserMode.SEMVER_MODE);
assertNotNull(context);
Module foo = context.findModuleByNamespace(new URI("foo")).iterator().next();
- Module semVer = context.findModuleByNamespace(new URI("urn:opendaylight:yang:extension:semantic-version"))
+ Module semVer = context.findModuleByNamespace(new URI("http://openconfig.net/yang/openconfig-ext"))
.iterator().next();
assertEquals(SemVer.valueOf("0.0.1"), semVer.getSemanticVersion());
* and is available at http://www.eclipse.org/legal/epl-v10.html
*/
-package org.opendaylight.yangtools.yang.stmt.semver.yin;
+package org.opendaylight.yangtools.yang.stmt.openconfigver.yin;
import static org.junit.Assert.assertEquals;
import static org.junit.Assert.assertNotNull;
import org.opendaylight.yangtools.yang.parser.spi.source.SourceException;
import org.opendaylight.yangtools.yang.stmt.StmtTestUtils;
-public class YinSemanticVersionTest {
+public class YinOpenconfigVersionTest {
@Test
public void basicTest() throws SourceException, FileNotFoundException, ReactorException, URISyntaxException {
- SchemaContext context = StmtTestUtils.parseYinSources("/semantic-version/yin-input/basic",
+ SchemaContext context = StmtTestUtils.parseYinSources("/openconfig-version/yin-input/basic",
StatementParserMode.SEMVER_MODE);
assertNotNull(context);
Module foo = context.findModuleByNamespace(new URI("foo")).iterator().next();
Module bar = context.findModuleByNamespace(new URI("bar")).iterator().next();
- Module semVer = context.findModuleByNamespace(new URI("urn:opendaylight:yang:extension:semantic-version"))
+ Module semVer = context.findModuleByNamespace(new URI("http://openconfig.net/yang/openconfig-ext"))
.iterator().next();
assertEquals(SemVer.valueOf("0.0.1"), semVer.getSemanticVersion());
@Test
public void basicImportTest1() throws SourceException, FileNotFoundException, ReactorException, URISyntaxException {
- SchemaContext context = StmtTestUtils.parseYinSources("/semantic-version/yin-input/basic-import",
+ SchemaContext context = StmtTestUtils.parseYinSources("/openconfig-version/yin-input/basic-import",
StatementParserMode.SEMVER_MODE);
assertNotNull(context);
Module foo = context.findModuleByNamespace(new URI("foo")).iterator().next();
- Module semVer = context.findModuleByNamespace(new URI("urn:opendaylight:yang:extension:semantic-version"))
+ Module semVer = context.findModuleByNamespace(new URI("http://openconfig.net/yang/openconfig-ext"))
.iterator().next();
assertEquals(SemVer.valueOf("0.0.1"), semVer.getSemanticVersion());
public void basicImportErrTest1() throws SourceException, FileNotFoundException, ReactorException,
URISyntaxException {
try {
- StmtTestUtils.parseYinSources("/semantic-version/yin-input/basic-import-invalid", StatementParserMode.SEMVER_MODE);
- fail("Test should fail due to invalid semantic version");
+ StmtTestUtils.parseYinSources("/openconfig-version/yin-input/basic-import-invalid", StatementParserMode.SEMVER_MODE);
+ fail("Test should fail due to invalid openconfig version");
} catch (ReactorException e) {
assertTrue(e.getCause().getMessage()
.startsWith("Unable to find module compatible with requested import [bar(0.1.2)]."));
prefix bar;
yang-version 1;
- import semantic-version { prefix sv; revision-date 2016-02-02;}
+ import openconfig-extensions { prefix oc-ext; revision-date 2017-01-29;}
revision "2016-01-31" {
description "Initial version";
}
- sv:semantic-version "0.1.2";
+ oc-ext:openconfig-version "0.1.2";
container root {
}
prefix foo;
yang-version 1;
- import semantic-version { prefix sv; revision-date 2016-02-02;}
+ import openconfig-extensions { prefix oc-ext; revision-date 2017-01-29;}
import bar { prefix bar; revision-date 2016-01-31;}
revision "2016-02-01" {
description "Initial version";
}
- sv:semantic-version "0.1.1";
+ oc-ext:openconfig-version "0.1.1";
container root {
}
-module semantic-version {
- namespace "urn:opendaylight:yang:extension:semantic-version";
- prefix sv;
- yang-version 1;
+module openconfig-extensions {
+ yang-version "1";
+ namespace "http://openconfig.net/yang/openconfig-ext";
+ prefix "oc-ext";
- revision 2016-02-02 {
- description "Initial verison";
+ organization "OpenConfig working group";
+
+ contact
+ "OpenConfig working group
+ www.openconfig.net";
+
+ description
+ "This module provides extensions to the YANG language to allow
+ OpenConfig specific functionality and meta-data to be defined.";
+
+ revision "2017-01-29" {
+ description
+ "Added extension for annotating encrypted values.";
+ reference "TBD";
+ }
+
+ revision "2015-10-09" {
+ description
+ "Initial OpenConfig public release";
+ reference "TBD";
}
- extension semantic-version {
- argument "semantic-version" {
+ revision "2015-10-05" {
+ description
+ "Initial revision";
+ reference "TBD";
+ }
+
+ oc-ext:openconfig-version "0.0.1";
+
+ extension openconfig-version {
+ argument "semver" {
yin-element false;
}
description
The version number is stored in the module meta-data.";
}
- sv:semantic-version "0.0.1";
-}
+ extension openconfig-encrypted-value {
+ description
+ "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.";
+ }
+}
\ No newline at end of file
prefix foo;
yang-version 1;
- import semantic-version { prefix sv; revision-date 2016-02-02; sv:semantic-version "0.0.1"; }
+ import openconfig-extensions { prefix oc-ext; revision-date 2017-01-29; oc-ext:openconfig-version "0.0.1"; }
revision "2016-02-01" {
description "Initial version";
}
- sv:semantic-version "0.1.1";
+ oc-ext:openconfig-version "0.1.1";
container root {
}
-module semantic-version {
- namespace "urn:opendaylight:yang:extension:semantic-version";
- prefix sv;
- yang-version 1.1;
+module openconfig-extensions {
+ yang-version "1";
+ namespace "http://openconfig.net/yang/openconfig-ext";
+ prefix "oc-ext";
- revision 2016-02-02 {
- description "Initial verison";
+ organization "OpenConfig working group";
+
+ contact
+ "OpenConfig working group
+ www.openconfig.net";
+
+ description
+ "This module provides extensions to the YANG language to allow
+ OpenConfig specific functionality and meta-data to be defined.";
+
+ revision "2017-01-29" {
+ description
+ "Added extension for annotating encrypted values.";
+ reference "TBD";
+ }
+
+ revision "2015-10-09" {
+ description
+ "Initial OpenConfig public release";
+ reference "TBD";
}
- sv:semantic-version "1.3.95";
- extension semantic-version {
- argument "semantic-version" {
+ revision "2015-10-05" {
+ description
+ "Initial revision";
+ reference "TBD";
+ }
+
+ oc-ext:openconfig-version "0.0.1";
+
+ extension openconfig-version {
+ argument "semver" {
yin-element false;
}
description
The version number is stored in the module meta-data.";
}
-}
+
+ extension openconfig-encrypted-value {
+ description
+ "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.";
+ }
+}
\ No newline at end of file
prefix bar;
yang-version 1;
- import semantic-version { prefix sv; revision-date 2016-02-02; sv:semantic-version "0.0.1"; }
+ import openconfig-extensions { prefix oc-ext; revision-date 2017-01-29; oc-ext:openconfig-version "0.0.1"; }
revision "2016-01-01" {
description "Initial version";
}
- sv:semantic-version "0.1.2";
+ oc-ext:openconfig-version "0.1.2";
container root {
}
prefix bar;
yang-version 1;
- import semantic-version { prefix sv; revision-date 2016-02-02; sv:semantic-version "0.0.1"; }
+ import openconfig-extensions { prefix oc-ext; revision-date 2017-01-29; oc-ext:openconfig-version "0.0.1"; }
revision "2016-01-31" {
description "Initial version";
}
- sv:semantic-version "1.1.3";
+ oc-ext:openconfig-version "1.1.2";
container root {
}
--- /dev/null
+module foo {
+ namespace "foo";
+ prefix foo;
+ yang-version 1;
+
+ import openconfig-extensions { prefix oc-ext; revision-date 2017-01-29; oc-ext:openconfig-version "0.0.1"; }
+ import bar { prefix bar; oc-ext:openconfig-version "0.1.2";}
+
+ revision "2016-02-01" {
+ description "Initial version";
+ }
+ oc-ext:openconfig-version "0.1.1";
+
+ container root {
+ }
+}
-module semantic-version {
- namespace "urn:opendaylight:yang:extension:semantic-version";
- prefix sv;
- yang-version 1;
+module openconfig-extensions {
+ yang-version "1";
+ namespace "http://openconfig.net/yang/openconfig-ext";
+ prefix "oc-ext";
- revision 2016-02-02 {
- description "Initial verison";
+ organization "OpenConfig working group";
+
+ contact
+ "OpenConfig working group
+ www.openconfig.net";
+
+ description
+ "This module provides extensions to the YANG language to allow
+ OpenConfig specific functionality and meta-data to be defined.";
+
+ revision "2017-01-29" {
+ description
+ "Added extension for annotating encrypted values.";
+ reference "TBD";
+ }
+
+ revision "2015-10-09" {
+ description
+ "Initial OpenConfig public release";
+ reference "TBD";
}
- sv:semantic-version "0.0.1";
- extension semantic-version {
- argument "semantic-version" {
+ revision "2015-10-05" {
+ description
+ "Initial revision";
+ reference "TBD";
+ }
+
+ oc-ext:openconfig-version "0.0.1";
+
+ extension openconfig-version {
+ argument "semver" {
yin-element false;
}
description
The version number is stored in the module meta-data.";
}
-}
+
+ extension openconfig-encrypted-value {
+ description
+ "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.";
+ }
+}
\ No newline at end of file
prefix bar;
yang-version 1;
- import semantic-version { prefix sv; revision-date 2016-02-02; sv:semantic-version "0.0.1"; }
+ import openconfig-extensions { prefix oc-ext; revision-date 2017-01-29; oc-ext:openconfig-version "0.0.1"; }
revision "2016-01-01" {
description "Initial version";
}
- sv:semantic-version "1.1.2";
+ oc-ext:openconfig-version "1.1.2";
container root {
}
prefix bar;
yang-version 1;
- import semantic-version { prefix sv; revision-date 2016-02-02; sv:semantic-version "0.0.1"; }
+ import openconfig-extensions { prefix oc-ext; revision-date 2017-01-29; oc-ext:openconfig-version "0.0.1"; }
revision "2016-01-31" {
description "Initial version";
}
- sv:semantic-version "1.1.2";
+ oc-ext:openconfig-version "1.1.3";
container root {
}
--- /dev/null
+module foo {
+ namespace "foo";
+ prefix foo;
+ yang-version 1;
+
+ import openconfig-extensions { prefix oc-ext; revision-date 2017-01-29; oc-ext:openconfig-version "0.0.1"; }
+ import bar { prefix bar; oc-ext:openconfig-version "0.1.2";}
+
+ revision "2016-02-01" {
+ description "Initial version";
+ }
+ oc-ext:openconfig-version "0.1.1";
+
+ container root {
+ }
+}
--- /dev/null
+module openconfig-extensions {
+ yang-version "1";
+ namespace "http://openconfig.net/yang/openconfig-ext";
+ prefix "oc-ext";
+
+ organization "OpenConfig working group";
+
+ contact
+ "OpenConfig working group
+ www.openconfig.net";
+
+ description
+ "This module provides extensions to the YANG language to allow
+ OpenConfig specific functionality and meta-data to be defined.";
+
+ revision "2017-01-29" {
+ description
+ "Added extension for annotating encrypted values.";
+ reference "TBD";
+ }
+
+ revision "2015-10-09" {
+ description
+ "Initial OpenConfig public release";
+ reference "TBD";
+ }
+
+ revision "2015-10-05" {
+ description
+ "Initial revision";
+ reference "TBD";
+ }
+
+ oc-ext:openconfig-version "0.0.1";
+
+ extension openconfig-version {
+ argument "semver" {
+ yin-element false;
+ }
+ description
+ "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.";
+ }
+
+ extension openconfig-encrypted-value {
+ description
+ "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.";
+ }
+}
\ No newline at end of file
prefix bar;
yang-version 1;
- import semantic-version { prefix sv; revision-date 2016-02-02; sv:semantic-version "0.0.1"; }
+ import openconfig-extensions { prefix oc-ext; revision-date 2017-01-29; oc-ext:openconfig-version "0.0.1"; }
revision "2016-01-31" {
description "Initial version";
}
- sv:semantic-version "0.1.2";
+ oc-ext:openconfig-version "1.1.2";
container root {
}
--- /dev/null
+module foo {
+ namespace "foo";
+ prefix foo;
+ yang-version 1;
+
+ import openconfig-extensions { prefix oc-ext; revision-date 2017-01-29; oc-ext:openconfig-version "0.0.1"; }
+ import bar { prefix bar; revision-date 2016-01-31; oc-ext:openconfig-version "0.1.2";}
+
+ revision "2016-02-01" {
+ description "Initial version";
+ }
+ oc-ext:openconfig-version "0.1.1";
+
+ container root {
+ }
+}
--- /dev/null
+module openconfig-extensions {
+ yang-version "1";
+ namespace "http://openconfig.net/yang/openconfig-ext";
+ prefix "oc-ext";
+
+ organization "OpenConfig working group";
+
+ contact
+ "OpenConfig working group
+ www.openconfig.net";
+
+ description
+ "This module provides extensions to the YANG language to allow
+ OpenConfig specific functionality and meta-data to be defined.";
+
+ revision "2017-01-29" {
+ description
+ "Added extension for annotating encrypted values.";
+ reference "TBD";
+ }
+
+ revision "2015-10-09" {
+ description
+ "Initial OpenConfig public release";
+ reference "TBD";
+ }
+
+ revision "2015-10-05" {
+ description
+ "Initial revision";
+ reference "TBD";
+ }
+
+ oc-ext:openconfig-version "0.0.1";
+
+ extension openconfig-version {
+ argument "semver" {
+ yin-element false;
+ }
+ description
+ "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.";
+ }
+
+ extension openconfig-encrypted-value {
+ description
+ "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.";
+ }
+}
\ No newline at end of file
prefix bar;
yang-version 1;
- import semantic-version { prefix sv; revision-date 2016-02-02; sv:semantic-version "0.0.1"; }
+ import openconfig-extensions { prefix oc-ext; revision-date 2017-01-29; oc-ext:openconfig-version "0.0.1"; }
revision "2016-01-31" {
description "Initial version";
}
- sv:semantic-version "1.0.0";
+ oc-ext:openconfig-version "0.1.2";
container root {
}
--- /dev/null
+module foo {
+ namespace "foo";
+ prefix foo;
+ yang-version 1;
+
+ import openconfig-extensions { prefix oc-ext; revision-date 2017-01-29; oc-ext:openconfig-version "0.0.1"; }
+ import bar { prefix bar; revision-date 2016-01-31; oc-ext:openconfig-version "0.1.2";}
+
+ revision "2016-02-01" {
+ description "Initial version";
+ }
+ oc-ext:openconfig-version "0.1.1";
+
+ container root {
+ }
+}
--- /dev/null
+module openconfig-extensions {
+ yang-version "1";
+ namespace "http://openconfig.net/yang/openconfig-ext";
+ prefix "oc-ext";
+
+ organization "OpenConfig working group";
+
+ contact
+ "OpenConfig working group
+ www.openconfig.net";
+
+ description
+ "This module provides extensions to the YANG language to allow
+ OpenConfig specific functionality and meta-data to be defined.";
+
+ revision "2017-01-29" {
+ description
+ "Added extension for annotating encrypted values.";
+ reference "TBD";
+ }
+
+ revision "2015-10-09" {
+ description
+ "Initial OpenConfig public release";
+ reference "TBD";
+ }
+
+ revision "2015-10-05" {
+ description
+ "Initial revision";
+ reference "TBD";
+ }
+
+ oc-ext:openconfig-version "0.0.1";
+
+ extension openconfig-version {
+ argument "semver" {
+ yin-element false;
+ }
+ description
+ "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.";
+ }
+
+ extension openconfig-encrypted-value {
+ description
+ "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.";
+ }
+}
\ No newline at end of file
prefix bar;
yang-version 1;
- import semantic-version { prefix sv; revision-date 2016-02-02; sv:semantic-version "0.0.1"; }
+ import openconfig-extensions { prefix oc-ext; revision-date 2017-01-29; oc-ext:openconfig-version "0.0.1"; }
revision "2016-01-01" {
description "Initial version";
}
- sv:semantic-version "2.5.5";
+ oc-ext:openconfig-version "2.5.5";
container root {
}
prefix bar;
yang-version 1;
- import semantic-version { prefix sv; revision-date 2016-02-02; sv:semantic-version "0.0.1"; }
+ import openconfig-extensions { prefix oc-ext; revision-date 2017-01-29; oc-ext:openconfig-version "0.0.1"; }
revision "2016-01-02" {
description "Initial version";
}
- sv:semantic-version "3.5.5";
+ oc-ext:openconfig-version "3.5.5";
container root {
}
prefix bar;
yang-version 1;
- import semantic-version { prefix sv; revision-date 2016-02-02; sv:semantic-version "0.0.1"; }
+ import openconfig-extensions { prefix oc-ext; revision-date 2017-01-29; oc-ext:openconfig-version "0.0.1"; }
revision "2016-01-03" {
description "Initial version";
}
- sv:semantic-version "4.5.5";
+ oc-ext:openconfig-version "4.5.5";
container root {
}
--- /dev/null
+module foo {
+ namespace "foo";
+ prefix foo;
+ yang-version 1;
+
+ import openconfig-extensions { prefix oc-ext; revision-date 2017-01-29; oc-ext:openconfig-version "0.0.1"; }
+ import bar { prefix bar; oc-ext:openconfig-version "5.5.5"; }
+
+ revision "2016-02-01" {
+ description "Initial version";
+ }
+ oc-ext:openconfig-version "0.1.1";
+
+ container root {
+ }
+}
--- /dev/null
+module openconfig-extensions {
+ yang-version "1";
+ namespace "http://openconfig.net/yang/openconfig-ext";
+ prefix "oc-ext";
+
+ organization "OpenConfig working group";
+
+ contact
+ "OpenConfig working group
+ www.openconfig.net";
+
+ description
+ "This module provides extensions to the YANG language to allow
+ OpenConfig specific functionality and meta-data to be defined.";
+
+ revision "2017-01-29" {
+ description
+ "Added extension for annotating encrypted values.";
+ reference "TBD";
+ }
+
+ revision "2015-10-09" {
+ description
+ "Initial OpenConfig public release";
+ reference "TBD";
+ }
+
+ revision "2015-10-05" {
+ description
+ "Initial revision";
+ reference "TBD";
+ }
+
+ oc-ext:openconfig-version "0.0.1";
+
+ extension openconfig-version {
+ argument "semver" {
+ yin-element false;
+ }
+ description
+ "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.";
+ }
+
+ extension openconfig-encrypted-value {
+ description
+ "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.";
+ }
+}
\ No newline at end of file
prefix bar;
yang-version 1;
- import semantic-version { prefix sv; revision-date 2016-02-02; sv:semantic-version "0.0.1"; }
+ import openconfig-extensions { prefix oc-ext; revision-date 2017-01-29; oc-ext:openconfig-version "0.0.1"; }
revision "2016-01-01" {
description "Initial version";
}
- sv:semantic-version "5.2.5";
+ oc-ext:openconfig-version "5.2.5";
container root {
}
prefix bar;
yang-version 1;
- import semantic-version { prefix sv; revision-date 2016-02-02; sv:semantic-version "0.0.1"; }
+ import openconfig-extensions { prefix oc-ext; revision-date 2017-01-29; oc-ext:openconfig-version "0.0.1"; }
revision "2016-01-02" {
description "Initial version";
}
- sv:semantic-version "5.3.5";
+ oc-ext:openconfig-version "5.3.5";
container root {
}
prefix bar;
yang-version 1;
- import semantic-version { prefix sv; revision-date 2016-02-02; sv:semantic-version "0.0.1"; }
+ import openconfig-extensions { prefix oc-ext; revision-date 2017-01-29; oc-ext:openconfig-version "0.0.1"; }
revision "2016-01-03" {
description "Initial version";
}
- sv:semantic-version "5.4.5";
+ oc-ext:openconfig-version "5.4.5";
container root {
}
--- /dev/null
+module foo {
+ namespace "foo";
+ prefix foo;
+ yang-version 1;
+
+ import openconfig-extensions { prefix oc-ext; revision-date 2017-01-29; oc-ext:openconfig-version "0.0.1"; }
+ import bar { prefix bar; oc-ext:openconfig-version "5.5.5"; }
+
+ revision "2016-02-01" {
+ description "Initial version";
+ }
+ oc-ext:openconfig-version "0.1.1";
+
+ container root {
+ }
+}
--- /dev/null
+module openconfig-extensions {
+ yang-version "1";
+ namespace "http://openconfig.net/yang/openconfig-ext";
+ prefix "oc-ext";
+
+ organization "OpenConfig working group";
+
+ contact
+ "OpenConfig working group
+ www.openconfig.net";
+
+ description
+ "This module provides extensions to the YANG language to allow
+ OpenConfig specific functionality and meta-data to be defined.";
+
+ revision "2017-01-29" {
+ description
+ "Added extension for annotating encrypted values.";
+ reference "TBD";
+ }
+
+ revision "2015-10-09" {
+ description
+ "Initial OpenConfig public release";
+ reference "TBD";
+ }
+
+ revision "2015-10-05" {
+ description
+ "Initial revision";
+ reference "TBD";
+ }
+
+ oc-ext:openconfig-version "0.0.1";
+
+ extension openconfig-version {
+ argument "semver" {
+ yin-element false;
+ }
+ description
+ "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.";
+ }
+
+ extension openconfig-encrypted-value {
+ description
+ "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.";
+ }
+}
\ No newline at end of file
--- /dev/null
+module bar {
+ namespace "bar";
+ prefix bar;
+ yang-version 1;
+
+ import openconfig-extensions { prefix oc-ext; revision-date 2017-01-29; oc-ext:openconfig-version "0.0.1"; }
+
+ revision "2016-01-01" {
+ description "Initial version";
+ }
+ oc-ext:openconfig-version "5.5.2";
+
+ container root {
+ }
+}
prefix bar;
yang-version 1;
- import semantic-version { prefix sv; revision-date 2016-02-02; sv:semantic-version "0.0.1"; }
+ import openconfig-extensions { prefix oc-ext; revision-date 2017-01-29; oc-ext:openconfig-version "0.0.1"; }
revision "2016-01-02" {
description "Initial version";
}
- sv:semantic-version "5.5.3";
+ oc-ext:openconfig-version "5.5.3";
container root {
}
prefix bar;
yang-version 1;
- import semantic-version { prefix sv; revision-date 2016-02-02; sv:semantic-version "0.0.1"; }
+ import openconfig-extensions { prefix oc-ext; revision-date 2017-01-29; oc-ext:openconfig-version "0.0.1"; }
revision "2016-01-03" {
description "Initial version";
}
- sv:semantic-version "5.5.4";
+ oc-ext:openconfig-version "5.5.4";
container root {
}
--- /dev/null
+module foo {
+ namespace "foo";
+ prefix foo;
+ yang-version 1;
+
+ import openconfig-extensions { prefix oc-ext; revision-date 2017-01-29; oc-ext:openconfig-version "0.0.1"; }
+ import bar { prefix bar; oc-ext:openconfig-version "5.5.5"; }
+
+ revision "2016-02-01" {
+ description "Initial version";
+ }
+ oc-ext:openconfig-version "0.1.1";
+
+ container root {
+ }
+}
--- /dev/null
+module openconfig-extensions {
+ yang-version "1";
+ namespace "http://openconfig.net/yang/openconfig-ext";
+ prefix "oc-ext";
+
+ organization "OpenConfig working group";
+
+ contact
+ "OpenConfig working group
+ www.openconfig.net";
+
+ description
+ "This module provides extensions to the YANG language to allow
+ OpenConfig specific functionality and meta-data to be defined.";
+
+ revision "2017-01-29" {
+ description
+ "Added extension for annotating encrypted values.";
+ reference "TBD";
+ }
+
+ revision "2015-10-09" {
+ description
+ "Initial OpenConfig public release";
+ reference "TBD";
+ }
+
+ revision "2015-10-05" {
+ description
+ "Initial revision";
+ reference "TBD";
+ }
+
+ oc-ext:openconfig-version "0.0.1";
+
+ extension openconfig-version {
+ argument "semver" {
+ yin-element false;
+ }
+ description
+ "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.";
+ }
+
+ extension openconfig-encrypted-value {
+ description
+ "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.";
+ }
+}
\ No newline at end of file
--- /dev/null
+module bar {
+ namespace "bar";
+ prefix bar;
+ yang-version 1;
+
+ import openconfig-extensions { prefix oc-ext; revision-date 2017-01-29; oc-ext:openconfig-version "0.0.1"; }
+
+ revision "2016-01-01" {
+ description "Initial version";
+ }
+ oc-ext:openconfig-version "4.5.5";
+
+ container root {
+ }
+}
prefix bar;
yang-version 1;
- import semantic-version { prefix sv; revision-date 2016-02-02; sv:semantic-version "0.0.1"; }
+ import openconfig-extensions { prefix oc-ext; revision-date 2017-01-29; oc-ext:openconfig-version "0.0.1"; }
revision "2016-01-02" {
description "Initial version";
}
- sv:semantic-version "5.5.5";
+ oc-ext:openconfig-version "5.5.5";
container root {
}
prefix bar;
yang-version 1;
- import semantic-version { prefix sv; revision-date 2016-02-02; sv:semantic-version "0.0.1"; }
+ import openconfig-extensions { prefix oc-ext; revision-date 2017-01-29; oc-ext:openconfig-version "0.0.1"; }
revision "2016-01-03" {
description "Initial version";
}
- sv:semantic-version "6.5.5";
+ oc-ext:openconfig-version "6.5.5";
container root {
}
--- /dev/null
+module foo {
+ namespace "foo";
+ prefix foo;
+ yang-version 1;
+
+ import openconfig-extensions { prefix oc-ext; revision-date 2017-01-29; oc-ext:openconfig-version "0.0.1"; }
+ import bar { prefix bar; oc-ext:openconfig-version "5.5.5"; }
+
+ revision "2016-02-01" {
+ description "Initial version";
+ }
+ oc-ext:openconfig-version "0.1.1";
+
+ container root {
+ }
+}
--- /dev/null
+module openconfig-extensions {
+ yang-version "1";
+ namespace "http://openconfig.net/yang/openconfig-ext";
+ prefix "oc-ext";
+
+ organization "OpenConfig working group";
+
+ contact
+ "OpenConfig working group
+ www.openconfig.net";
+
+ description
+ "This module provides extensions to the YANG language to allow
+ OpenConfig specific functionality and meta-data to be defined.";
+
+ revision "2017-01-29" {
+ description
+ "Added extension for annotating encrypted values.";
+ reference "TBD";
+ }
+
+ revision "2015-10-09" {
+ description
+ "Initial OpenConfig public release";
+ reference "TBD";
+ }
+
+ revision "2015-10-05" {
+ description
+ "Initial revision";
+ reference "TBD";
+ }
+
+ oc-ext:openconfig-version "0.0.1";
+
+ extension openconfig-version {
+ argument "semver" {
+ yin-element false;
+ }
+ description
+ "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.";
+ }
+
+ extension openconfig-encrypted-value {
+ description
+ "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.";
+ }
+}
\ No newline at end of file
--- /dev/null
+module bar {
+ namespace "bar";
+ prefix bar;
+ yang-version 1;
+
+ import openconfig-extensions { prefix oc-ext; revision-date 2017-01-29; oc-ext:openconfig-version "0.0.1"; }
+
+ revision "2016-01-01" {
+ description "Initial version";
+ }
+ oc-ext:openconfig-version "5.4.5";
+
+ container root {
+ }
+}
--- /dev/null
+module bar {
+ namespace "bar";
+ prefix bar;
+ yang-version 1;
+
+ import openconfig-extensions { prefix oc-ext; revision-date 2017-01-29; oc-ext:openconfig-version "0.0.1"; }
+
+ revision "2016-01-02" {
+ description "Initial version";
+ }
+ oc-ext:openconfig-version "5.5.5";
+
+ container root {
+ }
+}
--- /dev/null
+module bar {
+ namespace "bar";
+ prefix bar;
+ yang-version 1;
+
+ import openconfig-extensions { prefix oc-ext; revision-date 2017-01-29; oc-ext:openconfig-version "0.0.1"; }
+
+ revision "2016-01-03" {
+ description "Initial version";
+ }
+ oc-ext:openconfig-version "5.6.5";
+
+ container root {
+ }
+}
--- /dev/null
+module foo {
+ namespace "foo";
+ prefix foo;
+ yang-version 1;
+
+ import openconfig-extensions { prefix oc-ext; revision-date 2017-01-29; oc-ext:openconfig-version "0.0.1"; }
+ import bar { prefix bar; oc-ext:openconfig-version "5.5.5"; }
+
+ revision "2016-02-01" {
+ description "Initial version";
+ }
+ oc-ext:openconfig-version "0.1.1";
+
+ container root {
+ }
+}
--- /dev/null
+module openconfig-extensions {
+ yang-version "1";
+ namespace "http://openconfig.net/yang/openconfig-ext";
+ prefix "oc-ext";
+
+ organization "OpenConfig working group";
+
+ contact
+ "OpenConfig working group
+ www.openconfig.net";
+
+ description
+ "This module provides extensions to the YANG language to allow
+ OpenConfig specific functionality and meta-data to be defined.";
+
+ revision "2017-01-29" {
+ description
+ "Added extension for annotating encrypted values.";
+ reference "TBD";
+ }
+
+ revision "2015-10-09" {
+ description
+ "Initial OpenConfig public release";
+ reference "TBD";
+ }
+
+ revision "2015-10-05" {
+ description
+ "Initial revision";
+ reference "TBD";
+ }
+
+ oc-ext:openconfig-version "0.0.1";
+
+ extension openconfig-version {
+ argument "semver" {
+ yin-element false;
+ }
+ description
+ "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.";
+ }
+
+ extension openconfig-encrypted-value {
+ description
+ "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.";
+ }
+}
\ No newline at end of file
--- /dev/null
+module bar {
+ namespace "bar";
+ prefix bar;
+ yang-version 1;
+
+ import openconfig-extensions { prefix oc-ext; revision-date 2017-01-29; oc-ext:openconfig-version "0.0.1"; }
+
+ revision "2016-01-01" {
+ description "Initial version";
+ }
+ oc-ext:openconfig-version "5.5.4";
+
+ container root {
+ }
+}
--- /dev/null
+module bar {
+ namespace "bar";
+ prefix bar;
+ yang-version 1;
+
+ import openconfig-extensions { prefix oc-ext; revision-date 2017-01-29; oc-ext:openconfig-version "0.0.1"; }
+
+ revision "2016-01-02" {
+ description "Initial version";
+ }
+ oc-ext:openconfig-version "5.5.5";
+
+ container root {
+ }
+}
--- /dev/null
+module bar {
+ namespace "bar";
+ prefix bar;
+ yang-version 1;
+
+ import openconfig-extensions { prefix oc-ext; revision-date 2017-01-29; oc-ext:openconfig-version "0.0.1"; }
+
+ revision "2016-01-03" {
+ description "Initial version";
+ }
+ oc-ext:openconfig-version "5.5.6";
+
+ container root {
+ }
+}
--- /dev/null
+module foo {
+ namespace "foo";
+ prefix foo;
+ yang-version 1;
+
+ import openconfig-extensions { prefix oc-ext; revision-date 2017-01-29; oc-ext:openconfig-version "0.0.1"; }
+ import bar { prefix bar; oc-ext:openconfig-version "5.5.5"; }
+
+ revision "2016-02-01" {
+ description "Initial version";
+ }
+ oc-ext:openconfig-version "0.1.1";
+
+ container root {
+ }
+}
--- /dev/null
+module openconfig-extensions {
+ yang-version "1";
+ namespace "http://openconfig.net/yang/openconfig-ext";
+ prefix "oc-ext";
+
+ organization "OpenConfig working group";
+
+ contact
+ "OpenConfig working group
+ www.openconfig.net";
+
+ description
+ "This module provides extensions to the YANG language to allow
+ OpenConfig specific functionality and meta-data to be defined.";
+
+ revision "2017-01-29" {
+ description
+ "Added extension for annotating encrypted values.";
+ reference "TBD";
+ }
+
+ revision "2015-10-09" {
+ description
+ "Initial OpenConfig public release";
+ reference "TBD";
+ }
+
+ revision "2015-10-05" {
+ description
+ "Initial revision";
+ reference "TBD";
+ }
+
+ oc-ext:openconfig-version "0.0.1";
+
+ extension openconfig-version {
+ argument "semver" {
+ yin-element false;
+ }
+ description
+ "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.";
+ }
+
+ extension openconfig-encrypted-value {
+ description
+ "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.";
+ }
+}
\ No newline at end of file
prefix bar;
yang-version 1;
- import semantic-version { prefix sv; sv:semantic-version "1.2.012"; }
- import foobar { prefix foobar; sv:semantic-version "2.25.3"; }
+ import openconfig-extensions { prefix oc-ext; oc-ext:openconfig-version "1.2.012"; }
+ import foobar { prefix foobar; oc-ext:openconfig-version "2.25.3"; }
revision "2016-01-03" {
description "Imported version";
}
- sv:semantic-version "1.2.6";
+ oc-ext:openconfig-version "1.2.6";
container root {
container test-container {
prefix bar;
yang-version 1;
- import semantic-version { prefix sv; sv:semantic-version "1.2.210"; }
- import foobar { prefix foobar; sv:semantic-version "2.25.3"; }
+ import openconfig-extensions { prefix oc-ext; oc-ext:openconfig-version "1.2.210"; }
+ import foobar { prefix foobar; oc-ext:openconfig-version "2.25.3"; }
revision "2016-01-04" {
description "Not-imported version";
}
- sv:semantic-version "2.200.200";
+ oc-ext:openconfig-version "2.200.200";
container root {
container test-container {
--- /dev/null
+module foo {
+ namespace "foo";
+ prefix foo;
+ yang-version 1;
+
+ import openconfig-extensions { prefix oc-ext; oc-ext:openconfig-version "1.0.0"; }
+ import bar { prefix bar; oc-ext:openconfig-version "1.2.5"; }
+
+ revision "2016-02-01" {
+ description "Initial version";
+ }
+ oc-ext:openconfig-version "1.50.02";
+}
prefix foobar;
yang-version 1;
- import semantic-version { prefix sv; sv:semantic-version "1.2.95"; }
+ import openconfig-extensions { prefix oc-ext; oc-ext:openconfig-version "1.2.95"; }
revision "2016-01-31" {
description "Not-imported version";
}
- sv:semantic-version "2.25.2";
+ oc-ext:openconfig-version "2.25.2";
grouping test-grouping {
leaf name {
prefix foobar;
yang-version 1;
- import semantic-version { prefix sv; sv:semantic-version "1.3.95"; }
+ import openconfig-extensions { prefix oc-ext; oc-ext:openconfig-version "1.3.95"; }
revision "2016-02-28" {
description "Imported version";
}
- sv:semantic-version "2.26.465";
+ oc-ext:openconfig-version "2.26.465";
grouping test-grouping {
leaf name {
--- /dev/null
+module openconfig-extensions {
+ yang-version "1";
+ namespace "http://openconfig.net/yang/openconfig-ext";
+ prefix "oc-ext";
+
+ organization "OpenConfig working group";
+
+ contact
+ "OpenConfig working group
+ www.openconfig.net";
+
+ description
+ "This module provides extensions to the YANG language to allow
+ OpenConfig specific functionality and meta-data to be defined.";
+
+ revision "2017-01-29" {
+ description
+ "Added extension for annotating encrypted values.";
+ reference "TBD";
+ }
+
+ revision "2015-10-09" {
+ description
+ "Initial OpenConfig public release";
+ reference "TBD";
+ }
+
+ revision "2015-10-05" {
+ description
+ "Initial revision";
+ reference "TBD";
+ }
+
+ oc-ext:openconfig-version "1.3.95";
+
+ extension openconfig-version {
+ argument "semver" {
+ yin-element false;
+ }
+ description
+ "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.";
+ }
+
+ extension openconfig-encrypted-value {
+ description
+ "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.";
+ }
+}
\ No newline at end of file
prefix bar;
yang-version 1;
- import semantic-version { prefix sv; sv:semantic-version "2.0.40"; }
- import foobar { prefix foobar; sv:semantic-version "7.12.54"; }
+ import openconfig-extensions { prefix oc-ext; oc-ext:openconfig-version "2.0.40"; }
+ import foobar { prefix foobar; oc-ext:openconfig-version "7.12.54"; }
revision "2016-01-03" {
description "Imported version";
}
- sv:semantic-version "4.9.8";
+ oc-ext:openconfig-version "4.9.8";
augment "/foobar:root/foobar:test-container" {
leaf should-present-leaf-1 {
prefix bar;
yang-version 1;
- import semantic-version { prefix sv; sv:semantic-version "2.0.50"; }
- import foobar { prefix foobar; sv:semantic-version "7.12.54"; }
+ import openconfig-extensions { prefix oc-ext; oc-ext:openconfig-version "2.0.50"; }
+ import foobar { prefix foobar; oc-ext:openconfig-version "7.12.54"; }
revision "2016-01-04" {
description "Not-imported version";
}
- sv:semantic-version "3.0.5";
+ oc-ext:openconfig-version "3.0.5";
augment "/foobar:root/foobar:test-container" {
leaf should-not-be-present-leaf-1 {
--- /dev/null
+module foo {
+ namespace "foo";
+ prefix foo;
+ yang-version 1;
+
+ import openconfig-extensions { prefix oc-ext; oc-ext:openconfig-version "2.5.40"; }
+ import bar { prefix bar; oc-ext:openconfig-version "4.1.1"; }
+
+ revision "2016-02-01" {
+ description "Initial version";
+ }
+ oc-ext:openconfig-version "2.32.2";
+}
prefix foobar;
yang-version 1;
- import semantic-version { prefix sv; sv:semantic-version "2.1.950"; }
+ import openconfig-extensions { prefix oc-ext; oc-ext:openconfig-version "2.1.950"; }
revision "2016-01-31" {
description "Not-imported version";
}
- sv:semantic-version "8.0.0";
+ oc-ext:openconfig-version "8.0.0";
container root {
leaf included-not-correct-mark {
prefix foobar;
yang-version 1;
- import semantic-version { prefix sv; sv:semantic-version "2.5.50"; }
+ import openconfig-extensions { prefix oc-ext; oc-ext:openconfig-version "2.5.50"; }
revision "2016-02-27" {
description "Not-imported version";
}
- sv:semantic-version "7.13.0";
+ oc-ext:openconfig-version "7.13.0";
container root {
leaf included-not-correct-mark {
prefix foobar;
yang-version 1;
- import semantic-version { prefix sv; sv:semantic-version "2.5.50"; }
+ import openconfig-extensions { prefix oc-ext; oc-ext:openconfig-version "2.5.50"; }
revision "2016-02-28" {
description "Imported version";
}
- sv:semantic-version "7.13.99";
+ oc-ext:openconfig-version "7.13.99";
container root {
leaf included-correct-mark {
--- /dev/null
+module openconfig-extensions {
+ yang-version "1";
+ namespace "http://openconfig.net/yang/openconfig-ext";
+ prefix "oc-ext";
+
+ organization "OpenConfig working group";
+
+ contact
+ "OpenConfig working group
+ www.openconfig.net";
+
+ description
+ "This module provides extensions to the YANG language to allow
+ OpenConfig specific functionality and meta-data to be defined.";
+
+ revision "2017-01-29" {
+ description
+ "Added extension for annotating encrypted values.";
+ reference "TBD";
+ }
+
+ revision "2015-10-09" {
+ description
+ "Initial OpenConfig public release";
+ reference "TBD";
+ }
+
+ revision "2015-10-05" {
+ description
+ "Initial revision";
+ reference "TBD";
+ }
+
+ oc-ext:openconfig-version "2.5.50";
+
+ extension openconfig-version {
+ argument "semver" {
+ yin-element false;
+ }
+ description
+ "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.";
+ }
+
+ extension openconfig-encrypted-value {
+ description
+ "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.";
+ }
+}
\ No newline at end of file
prefix bar;
yang-version 1;
- import semantic-version { prefix sv; revision-date 2016-02-02; sv:semantic-version "0.0.1"; }
+ import openconfig-extensions { prefix oc-ext; revision-date 2017-01-29; oc-ext:openconfig-version "0.0.1"; }
revision "2016-01-31" {
description "Initial version";
}
- sv:semantic-version "1.1.2";
+ oc-ext:openconfig-version "1.0.0";
container root {
}
prefix foo;
yang-version 1;
- import semantic-version { prefix sv; revision-date 2016-02-02; sv:semantic-version "0.0.1"; }
+ import openconfig-extensions { prefix oc-ext; revision-date 2017-01-29; oc-ext:openconfig-version "0.0.1"; }
import bar { prefix bar; revision-date 2016-01-31; }
revision "2016-02-01" {
--- /dev/null
+module openconfig-extensions {
+ yang-version "1";
+ namespace "http://openconfig.net/yang/openconfig-ext";
+ prefix "oc-ext";
+
+ organization "OpenConfig working group";
+
+ contact
+ "OpenConfig working group
+ www.openconfig.net";
+
+ description
+ "This module provides extensions to the YANG language to allow
+ OpenConfig specific functionality and meta-data to be defined.";
+
+ revision "2017-01-29" {
+ description
+ "Added extension for annotating encrypted values.";
+ reference "TBD";
+ }
+
+ revision "2015-10-09" {
+ description
+ "Initial OpenConfig public release";
+ reference "TBD";
+ }
+
+ revision "2015-10-05" {
+ description
+ "Initial revision";
+ reference "TBD";
+ }
+
+ oc-ext:openconfig-version "0.0.1";
+
+ extension openconfig-version {
+ argument "semver" {
+ yin-element false;
+ }
+ description
+ "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.";
+ }
+
+ extension openconfig-encrypted-value {
+ description
+ "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.";
+ }
+}
\ No newline at end of file
--- /dev/null
+module bar {
+ namespace "bar";
+ prefix bar;
+ yang-version 1;
+
+ import openconfig-extensions { prefix oc-ext; revision-date 2017-01-29; oc-ext:openconfig-version "0.0.1"; }
+
+ revision "2016-01-31" {
+ description "Initial version";
+ }
+ oc-ext:openconfig-version "0.99.99";
+
+ container root {
+ }
+}
prefix foo;
yang-version 1;
- import semantic-version { prefix sv; revision-date 2016-02-02; sv:semantic-version "0.0.1"; }
+ import openconfig-extensions { prefix oc-ext; revision-date 2017-01-29; oc-ext:openconfig-version "0.0.1"; }
import bar { prefix bar; revision-date 2016-01-31; }
revision "2016-02-01" {
--- /dev/null
+module openconfig-extensions {
+ yang-version "1";
+ namespace "http://openconfig.net/yang/openconfig-ext";
+ prefix "oc-ext";
+
+ organization "OpenConfig working group";
+
+ contact
+ "OpenConfig working group
+ www.openconfig.net";
+
+ description
+ "This module provides extensions to the YANG language to allow
+ OpenConfig specific functionality and meta-data to be defined.";
+
+ revision "2017-01-29" {
+ description
+ "Added extension for annotating encrypted values.";
+ reference "TBD";
+ }
+
+ revision "2015-10-09" {
+ description
+ "Initial OpenConfig public release";
+ reference "TBD";
+ }
+
+ revision "2015-10-05" {
+ description
+ "Initial revision";
+ reference "TBD";
+ }
+
+ oc-ext:openconfig-version "0.0.1";
+
+ extension openconfig-version {
+ argument "semver" {
+ yin-element false;
+ }
+ description
+ "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.";
+ }
+
+ extension openconfig-encrypted-value {
+ description
+ "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.";
+ }
+}
\ No newline at end of file
--- /dev/null
+module bar {
+ namespace "bar";
+ prefix bar;
+ yang-version 1;
+
+ import openconfig-extensions { prefix oc-ext; revision-date 2017-01-29; oc-ext:openconfig-version "0.0.1"; }
+
+ revision "2016-01-01" {
+ description "Initial version";
+ }
+ oc-ext:openconfig-version "0.1.2";
+
+ container root {
+ }
+}
prefix bar;
yang-version 1;
- import semantic-version { prefix sv; revision-date 2016-02-02; sv:semantic-version "0.0.1"; }
+ import openconfig-extensions { prefix oc-ext; revision-date 2017-01-29; oc-ext:openconfig-version "0.0.1"; }
revision "2016-01-31" {
description "Initial version";
}
- sv:semantic-version "1.1.2";
+ oc-ext:openconfig-version "1.1.2";
container root {
}
--- /dev/null
+module foo {
+ namespace "foo";
+ prefix foo;
+ yang-version 1;
+
+ import openconfig-extensions { prefix oc-ext; revision-date 2017-01-29; oc-ext:openconfig-version "0.0.1"; }
+ import bar { prefix bar; revision-date 2016-01-31; oc-ext:openconfig-version "0.1.2";}
+
+ revision "2016-02-01" {
+ description "Initial version";
+ }
+ oc-ext:openconfig-version "0.1.1";
+
+ container root {
+ }
+}
--- /dev/null
+module openconfig-extensions {
+ yang-version "1";
+ namespace "http://openconfig.net/yang/openconfig-ext";
+ prefix "oc-ext";
+
+ organization "OpenConfig working group";
+
+ contact
+ "OpenConfig working group
+ www.openconfig.net";
+
+ description
+ "This module provides extensions to the YANG language to allow
+ OpenConfig specific functionality and meta-data to be defined.";
+
+ revision "2017-01-29" {
+ description
+ "Added extension for annotating encrypted values.";
+ reference "TBD";
+ }
+
+ revision "2015-10-09" {
+ description
+ "Initial OpenConfig public release";
+ reference "TBD";
+ }
+
+ revision "2015-10-05" {
+ description
+ "Initial revision";
+ reference "TBD";
+ }
+
+ oc-ext:openconfig-version "0.0.1";
+
+ extension openconfig-version {
+ argument "semver" {
+ yin-element false;
+ }
+ description
+ "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.";
+ }
+
+ extension openconfig-encrypted-value {
+ description
+ "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.";
+ }
+}
\ No newline at end of file
--- /dev/null
+module bar {
+ namespace "bar";
+ prefix bar;
+ yang-version 1;
+
+ import openconfig-extensions { prefix oc-ext; revision-date 2017-01-29; oc-ext:openconfig-version "0.0.1"; }
+
+ revision "2016-01-01" {
+ description "Initial version";
+ }
+ oc-ext:openconfig-version "0.1.2";
+
+ container root {
+ }
+}
--- /dev/null
+module foo {
+ namespace "foo";
+ prefix foo;
+ yang-version 1;
+
+ import openconfig-extensions { prefix oc-ext; revision-date 2017-01-29; oc-ext:openconfig-version "0.0.1"; }
+ import bar { prefix bar; revision-date 2016-01-31; oc-ext:openconfig-version "0.1.2";}
+
+ revision "2016-02-01" {
+ description "Initial version";
+ }
+ oc-ext:openconfig-version "0.1.1";
+
+ container root {
+ }
+}
--- /dev/null
+module openconfig-extensions {
+ yang-version "1";
+ namespace "http://openconfig.net/yang/openconfig-ext";
+ prefix "oc-ext";
+
+ organization "OpenConfig working group";
+
+ contact
+ "OpenConfig working group
+ www.openconfig.net";
+
+ description
+ "This module provides extensions to the YANG language to allow
+ OpenConfig specific functionality and meta-data to be defined.";
+
+ revision "2017-01-29" {
+ description
+ "Added extension for annotating encrypted values.";
+ reference "TBD";
+ }
+
+ revision "2015-10-09" {
+ description
+ "Initial OpenConfig public release";
+ reference "TBD";
+ }
+
+ revision "2015-10-05" {
+ description
+ "Initial revision";
+ reference "TBD";
+ }
+
+ oc-ext:openconfig-version "0.0.1";
+
+ extension openconfig-version {
+ argument "semver" {
+ yin-element false;
+ }
+ description
+ "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.";
+ }
+
+ extension openconfig-encrypted-value {
+ description
+ "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.";
+ }
+}
\ No newline at end of file
prefix foo;
yang-version 1;
- import semantic-version { prefix sv; revision-date 2016-02-02; sv:semantic-version "1.0.0"; }
+ import openconfig-extensions { prefix oc-ext; revision-date 2017-01-29; oc-ext:openconfig-version "1.0.0"; }
revision "2016-02-01" {
description "Initial version";
--- /dev/null
+module openconfig-extensions {
+ yang-version "1";
+ namespace "http://openconfig.net/yang/openconfig-ext";
+ prefix "oc-ext";
+
+ organization "OpenConfig working group";
+
+ contact
+ "OpenConfig working group
+ www.openconfig.net";
+
+ description
+ "This module provides extensions to the YANG language to allow
+ OpenConfig specific functionality and meta-data to be defined.";
+
+ revision "2017-01-29" {
+ description
+ "Added extension for annotating encrypted values.";
+ reference "TBD";
+ }
+
+ revision "2015-10-09" {
+ description
+ "Initial OpenConfig public release";
+ reference "TBD";
+ }
+
+ revision "2015-10-05" {
+ description
+ "Initial revision";
+ reference "TBD";
+ }
+
+ oc-ext:openconfig-version "2.0.0";
+
+ extension openconfig-version {
+ argument "semver" {
+ yin-element false;
+ }
+ description
+ "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.";
+ }
+
+ extension openconfig-encrypted-value {
+ description
+ "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.";
+ }
+}
\ No newline at end of file
prefix foo;
yang-version 1;
- import semantic-version { prefix sv; revision-date 2016-02-02; sv:semantic-version "2.0.5"; }
+ import openconfig-extensions { prefix oc-ext; revision-date 2017-01-29; oc-ext:openconfig-version "0.9.9"; }
revision "2016-02-01" {
description "Initial version";
--- /dev/null
+module openconfig-extensions {
+ yang-version "1";
+ namespace "http://openconfig.net/yang/openconfig-ext";
+ prefix "oc-ext";
+
+ organization "OpenConfig working group";
+
+ contact
+ "OpenConfig working group
+ www.openconfig.net";
+
+ description
+ "This module provides extensions to the YANG language to allow
+ OpenConfig specific functionality and meta-data to be defined.";
+
+ revision "2017-01-29" {
+ description
+ "Added extension for annotating encrypted values.";
+ reference "TBD";
+ }
+
+ revision "2015-10-09" {
+ description
+ "Initial OpenConfig public release";
+ reference "TBD";
+ }
+
+ revision "2015-10-05" {
+ description
+ "Initial revision";
+ reference "TBD";
+ }
+
+ oc-ext:openconfig-version "1.0.0";
+
+ extension openconfig-version {
+ argument "semver" {
+ yin-element false;
+ }
+ description
+ "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.";
+ }
+
+ extension openconfig-encrypted-value {
+ description
+ "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.";
+ }
+}
\ No newline at end of file
prefix foo;
yang-version 1;
- import semantic-version { prefix sv; revision-date 2016-02-02; sv:semantic-version "0.9.9"; }
+ import openconfig-extensions { prefix oc-ext; revision-date 2017-01-29; oc-ext:openconfig-version "2.0.0"; }
revision "2016-02-01" {
description "Initial version";
--- /dev/null
+module openconfig-extensions {
+ yang-version "1";
+ namespace "http://openconfig.net/yang/openconfig-ext";
+ prefix "oc-ext";
+
+ organization "OpenConfig working group";
+
+ contact
+ "OpenConfig working group
+ www.openconfig.net";
+
+ description
+ "This module provides extensions to the YANG language to allow
+ OpenConfig specific functionality and meta-data to be defined.";
+
+ revision "2017-01-29" {
+ description
+ "Added extension for annotating encrypted values.";
+ reference "TBD";
+ }
+
+ revision "2015-10-09" {
+ description
+ "Initial OpenConfig public release";
+ reference "TBD";
+ }
+
+ revision "2015-10-05" {
+ description
+ "Initial revision";
+ reference "TBD";
+ }
+
+ oc-ext:openconfig-version "1.0.0";
+
+ extension openconfig-version {
+ argument "semver" {
+ yin-element false;
+ }
+ description
+ "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.";
+ }
+
+ extension openconfig-encrypted-value {
+ description
+ "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.";
+ }
+}
\ No newline at end of file
prefix foo;
yang-version 1;
- import semantic-version { prefix sv; revision-date 2016-02-02; sv:semantic-version "2.0.0"; }
+ import openconfig-extensions { prefix oc-ext; revision-date 2017-01-29; oc-ext:openconfig-version "2.0.5"; }
revision "2016-02-01" {
description "Initial version";
--- /dev/null
+module openconfig-extensions {
+ yang-version "1";
+ namespace "http://openconfig.net/yang/openconfig-ext";
+ prefix "oc-ext";
+
+ organization "OpenConfig working group";
+
+ contact
+ "OpenConfig working group
+ www.openconfig.net";
+
+ description
+ "This module provides extensions to the YANG language to allow
+ OpenConfig specific functionality and meta-data to be defined.";
+
+ revision "2017-01-29" {
+ description
+ "Added extension for annotating encrypted values.";
+ reference "TBD";
+ }
+
+ revision "2015-10-09" {
+ description
+ "Initial OpenConfig public release";
+ reference "TBD";
+ }
+
+ revision "2015-10-05" {
+ description
+ "Initial revision";
+ reference "TBD";
+ }
+
+ oc-ext:openconfig-version "2.0.0";
+
+ extension openconfig-version {
+ argument "semver" {
+ yin-element false;
+ }
+ description
+ "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.";
+ }
+
+ extension openconfig-encrypted-value {
+ description
+ "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.";
+ }
+}
\ No newline at end of file
--- /dev/null
+module foo {
+ namespace "foo";
+ prefix foo;
+ yang-version 1;
+
+ import openconfig-extensions { prefix oc-ext; revision-date 2017-01-29; oc-ext:openconfig-version "1.0.0"; }
+
+ revision "2016-02-01" {
+ description "Initial version";
+ }
+
+ container root {
+ }
+}
--- /dev/null
+module openconfig-extensions {
+ yang-version "1";
+ namespace "http://openconfig.net/yang/openconfig-ext";
+ prefix "oc-ext";
+
+ organization "OpenConfig working group";
+
+ contact
+ "OpenConfig working group
+ www.openconfig.net";
+
+ description
+ "This module provides extensions to the YANG language to allow
+ OpenConfig specific functionality and meta-data to be defined.";
+
+ revision "2017-01-29" {
+ description
+ "Added extension for annotating encrypted values.";
+ reference "TBD";
+ }
+
+ revision "2015-10-09" {
+ description
+ "Initial OpenConfig public release";
+ reference "TBD";
+ }
+
+ revision "2015-10-05" {
+ description
+ "Initial revision";
+ reference "TBD";
+ }
+
+ oc-ext:openconfig-version "1.0.0";
+
+ extension openconfig-version {
+ argument "semver" {
+ yin-element false;
+ }
+ description
+ "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.";
+ }
+
+ extension openconfig-encrypted-value {
+ description
+ "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.";
+ }
+}
\ No newline at end of file
--- /dev/null
+module bar {
+ namespace "bar";
+ prefix bar;
+ yang-version 1;
+
+ import openconfig-extensions { prefix oc-ext; revision-date 2017-01-29; oc-ext:openconfig-version "0.0.1"; }
+
+ revision "2016-01-01" {
+ description "Initial version";
+ }
+ oc-ext:openconfig-version "0.1.1";
+
+ container root {
+ }
+}
--- /dev/null
+module bar {
+ namespace "bar";
+ prefix bar;
+ yang-version 1;
+
+ import openconfig-extensions { prefix oc-ext; revision-date 2017-01-29; oc-ext:openconfig-version "0.0.1"; }
+
+ revision "2016-01-02" {
+ description "Initial version";
+ }
+ oc-ext:openconfig-version "0.1.2";
+
+ container root {
+ }
+}
--- /dev/null
+module bar {
+ namespace "bar";
+ prefix bar;
+ yang-version 1;
+
+ import openconfig-extensions { prefix oc-ext; revision-date 2017-01-29; oc-ext:openconfig-version "0.0.1"; }
+
+ revision "2016-01-03" {
+ description "Initial version";
+ }
+ oc-ext:openconfig-version "0.1.3";
+
+ container root {
+ }
+}
prefix bar;
yang-version 1;
- import semantic-version { prefix sv; revision-date 2016-02-02; sv:semantic-version "0.0.1"; }
+ import openconfig-extensions { prefix oc-ext; revision-date 2017-01-29; oc-ext:openconfig-version "0.0.1"; }
revision "2016-01-04" {
description "Initial version";
}
- sv:semantic-version "0.10.4";
+ oc-ext:openconfig-version "0.10.4";
container root {
}
prefix bar;
yang-version 1;
- import semantic-version { prefix sv; revision-date 2016-02-02; sv:semantic-version "0.0.1"; }
+ import openconfig-extensions { prefix oc-ext; revision-date 2017-01-29; oc-ext:openconfig-version "0.0.1"; }
revision "2016-01-31" {
description "Initial version";
}
- sv:semantic-version "1.1.2";
+ oc-ext:openconfig-version "1.1.2";
container root {
}
prefix bar;
yang-version 1;
- import semantic-version { prefix sv; revision-date 2016-02-02; sv:semantic-version "0.0.1"; }
+ import openconfig-extensions { prefix oc-ext; revision-date 2017-01-29; oc-ext:openconfig-version "0.0.1"; }
revision "2016-02-28" {
description "Initial version";
}
- sv:semantic-version "1.2.28";
+ oc-ext:openconfig-version "1.2.28";
container root {
}
--- /dev/null
+module foo {
+ namespace "foo";
+ prefix foo;
+ yang-version 1;
+
+ import openconfig-extensions { prefix oc-ext; revision-date 2017-01-29; oc-ext:openconfig-version "0.0.1"; }
+ import bar { prefix bar; oc-ext:openconfig-version "0.1.2";}
+
+ revision "2016-02-01" {
+ description "Initial version";
+ }
+ oc-ext:openconfig-version "0.1.1";
+
+ container root {
+ }
+}
--- /dev/null
+module openconfig-extensions {
+ yang-version "1";
+ namespace "http://openconfig.net/yang/openconfig-ext";
+ prefix "oc-ext";
+
+ organization "OpenConfig working group";
+
+ contact
+ "OpenConfig working group
+ www.openconfig.net";
+
+ description
+ "This module provides extensions to the YANG language to allow
+ OpenConfig specific functionality and meta-data to be defined.";
+
+ revision "2017-01-29" {
+ description
+ "Added extension for annotating encrypted values.";
+ reference "TBD";
+ }
+
+ revision "2015-10-09" {
+ description
+ "Initial OpenConfig public release";
+ reference "TBD";
+ }
+
+ revision "2015-10-05" {
+ description
+ "Initial revision";
+ reference "TBD";
+ }
+
+ oc-ext:openconfig-version "0.0.1";
+
+ extension openconfig-version {
+ argument "semver" {
+ yin-element false;
+ }
+ description
+ "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.";
+ }
+
+ extension openconfig-encrypted-value {
+ description
+ "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.";
+ }
+}
\ No newline at end of file
--- /dev/null
+module bar {
+ namespace "bar";
+ prefix bar;
+ yang-version 1;
+
+ import openconfig-extensions { prefix oc-ext; revision-date 2017-01-29; oc-ext:openconfig-version "0.0.1"; }
+
+ revision "2016-01-01" {
+ description "Initial version";
+ }
+ oc-ext:openconfig-version "2.1.1";
+
+ container root {
+ }
+}
--- /dev/null
+module bar {
+ namespace "bar";
+ prefix bar;
+ yang-version 1;
+
+ import openconfig-extensions { prefix oc-ext; revision-date 2017-01-29; oc-ext:openconfig-version "0.0.1"; }
+
+ revision "2016-01-02" {
+ description "Initial version";
+ }
+ oc-ext:openconfig-version "2.1.2";
+
+ container root {
+ }
+}
prefix bar;
yang-version 1;
- import semantic-version { prefix sv; revision-date 2016-02-02; sv:semantic-version "0.0.1"; }
+ import openconfig-extensions { prefix oc-ext; revision-date 2017-01-29; oc-ext:openconfig-version "0.0.1"; }
revision "2016-02-01" {
description "Initial version";
}
- sv:semantic-version "4.1.1";
+ oc-ext:openconfig-version "4.1.1";
container root {
}
prefix bar;
yang-version 1;
- import semantic-version { prefix sv; revision-date 2016-02-02; sv:semantic-version "0.0.1"; }
+ import openconfig-extensions { prefix oc-ext; revision-date 2017-01-29; oc-ext:openconfig-version "0.0.1"; }
revision "2016-02-02" {
description "Initial version";
}
- sv:semantic-version "5.0.0";
+ oc-ext:openconfig-version "5.0.0";
container root {
}
--- /dev/null
+module foo {
+ namespace "foo";
+ prefix foo;
+ yang-version 1;
+
+ import openconfig-extensions { prefix oc-ext; revision-date 2017-01-29; oc-ext:openconfig-version "0.0.1"; }
+ import bar { prefix bar; revision-date 2016-01-31; oc-ext:openconfig-version "1.0.0"; }
+
+ revision "2016-02-01" {
+ description "Initial version";
+ }
+ oc-ext:openconfig-version "0.1.1";
+
+ container root {
+ }
+}
--- /dev/null
+module openconfig-extensions {
+ yang-version "1";
+ namespace "http://openconfig.net/yang/openconfig-ext";
+ prefix "oc-ext";
+
+ organization "OpenConfig working group";
+
+ contact
+ "OpenConfig working group
+ www.openconfig.net";
+
+ description
+ "This module provides extensions to the YANG language to allow
+ OpenConfig specific functionality and meta-data to be defined.";
+
+ revision "2017-01-29" {
+ description
+ "Added extension for annotating encrypted values.";
+ reference "TBD";
+ }
+
+ revision "2015-10-09" {
+ description
+ "Initial OpenConfig public release";
+ reference "TBD";
+ }
+
+ revision "2015-10-05" {
+ description
+ "Initial revision";
+ reference "TBD";
+ }
+
+ oc-ext:openconfig-version "0.0.1";
+
+ extension openconfig-version {
+ argument "semver" {
+ yin-element false;
+ }
+ description
+ "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.";
+ }
+
+ extension openconfig-encrypted-value {
+ description
+ "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.";
+ }
+}
\ No newline at end of file
--- /dev/null
+module bar {
+ namespace "bar";
+ prefix bar;
+ yang-version 1;
+
+ import openconfig-extensions { prefix oc-ext; revision-date 2017-01-29; oc-ext:openconfig-version "0.0.1"; }
+
+ revision "2016-01-01" {
+ description "Initial version";
+ }
+ oc-ext:openconfig-version "2.0.0";
+
+ container root {
+ }
+}
--- /dev/null
+module bar {
+ namespace "bar";
+ prefix bar;
+ yang-version 1;
+
+ import openconfig-extensions { prefix oc-ext; revision-date 2017-01-29; oc-ext:openconfig-version "0.0.1"; }
+
+ revision "2016-01-02" {
+ description "Initial version";
+ }
+ oc-ext:openconfig-version "2.1.0";
+
+ container root {
+ }
+}
prefix bar;
yang-version 1;
- import semantic-version { prefix sv; revision-date 2016-02-02; sv:semantic-version "0.0.1"; }
+ import openconfig-extensions { prefix oc-ext; revision-date 2017-01-29; oc-ext:openconfig-version "0.0.1"; }
revision "2016-02-01" {
description "Initial version";
}
- sv:semantic-version "2.5.0";
+ oc-ext:openconfig-version "2.5.0";
container root {
}
prefix bar;
yang-version 1;
- import semantic-version { prefix sv; revision-date 2016-02-02; sv:semantic-version "0.0.1"; }
+ import openconfig-extensions { prefix oc-ext; revision-date 2017-01-29; oc-ext:openconfig-version "0.0.1"; }
revision "2016-02-02" {
description "Initial version";
}
- sv:semantic-version "2.5.4";
+ oc-ext:openconfig-version "2.5.4";
container root {
}
--- /dev/null
+module foo {
+ namespace "foo";
+ prefix foo;
+ yang-version 1;
+
+ import openconfig-extensions { prefix oc-ext; revision-date 2017-01-29; oc-ext:openconfig-version "0.0.1"; }
+ import bar { prefix bar; oc-ext:openconfig-version "2.5.5"; }
+
+ revision "2016-02-01" {
+ description "Initial version";
+ }
+ oc-ext:openconfig-version "0.1.1";
+
+ container root {
+ }
+}
--- /dev/null
+module openconfig-extensions {
+ yang-version "1";
+ namespace "http://openconfig.net/yang/openconfig-ext";
+ prefix "oc-ext";
+
+ organization "OpenConfig working group";
+
+ contact
+ "OpenConfig working group
+ www.openconfig.net";
+
+ description
+ "This module provides extensions to the YANG language to allow
+ OpenConfig specific functionality and meta-data to be defined.";
+
+ revision "2017-01-29" {
+ description
+ "Added extension for annotating encrypted values.";
+ reference "TBD";
+ }
+
+ revision "2015-10-09" {
+ description
+ "Initial OpenConfig public release";
+ reference "TBD";
+ }
+
+ revision "2015-10-05" {
+ description
+ "Initial revision";
+ reference "TBD";
+ }
+
+ oc-ext:openconfig-version "0.0.1";
+
+ extension openconfig-version {
+ argument "semver" {
+ yin-element false;
+ }
+ description
+ "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.";
+ }
+
+ extension openconfig-encrypted-value {
+ description
+ "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.";
+ }
+}
\ No newline at end of file
--- /dev/null
+module bar {
+ namespace "bar";
+ prefix bar;
+ yang-version 1;
+
+ import openconfig-extensions { prefix oc-ext; revision-date 2017-01-29; oc-ext:openconfig-version "0.0.1"; }
+
+ revision "2016-01-01" {
+ description "Initial version";
+ }
+ oc-ext:openconfig-version "0.0.1";
+
+ container root {
+ }
+}
--- /dev/null
+module bar {
+ namespace "bar";
+ prefix bar;
+ yang-version 1;
+
+ import openconfig-extensions { prefix oc-ext; revision-date 2017-01-29; oc-ext:openconfig-version "0.0.1"; }
+
+ revision "2016-01-02" {
+ description "Initial version";
+ }
+ oc-ext:openconfig-version "0.1.0";
+
+ container root {
+ }
+}
prefix bar;
yang-version 1;
- import semantic-version { prefix sv; revision-date 2016-02-02; sv:semantic-version "0.0.1"; }
+ import openconfig-extensions { prefix oc-ext; revision-date 2017-01-29; oc-ext:openconfig-version "0.0.1"; }
revision "2016-02-01" {
description "Initial version";
}
- sv:semantic-version "0.9.5";
+ oc-ext:openconfig-version "0.9.5";
container root {
}
prefix bar;
yang-version 1;
- import semantic-version { prefix sv; revision-date 2016-02-02; sv:semantic-version "0.0.1"; }
+ import openconfig-extensions { prefix oc-ext; revision-date 2017-01-29; oc-ext:openconfig-version "0.0.1"; }
revision "2016-02-02" {
description "Initial version";
}
- sv:semantic-version "1.0.0";
+ oc-ext:openconfig-version "1.0.0";
container root {
}
prefix foo;
yang-version 1;
- import semantic-version { prefix sv; revision-date 2016-02-02; sv:semantic-version "0.0.1"; }
+ import openconfig-extensions { prefix oc-ext; revision-date 2017-01-29; oc-ext:openconfig-version "0.0.1"; }
import bar { prefix bar; }
revision "2016-02-01" {
description "Initial version";
}
- sv:semantic-version "0.1.1";
+ oc-ext:openconfig-version "0.1.1";
container root {
}
--- /dev/null
+module openconfig-extensions {
+ yang-version "1";
+ namespace "http://openconfig.net/yang/openconfig-ext";
+ prefix "oc-ext";
+
+ organization "OpenConfig working group";
+
+ contact
+ "OpenConfig working group
+ www.openconfig.net";
+
+ description
+ "This module provides extensions to the YANG language to allow
+ OpenConfig specific functionality and meta-data to be defined.";
+
+ revision "2017-01-29" {
+ description
+ "Added extension for annotating encrypted values.";
+ reference "TBD";
+ }
+
+ revision "2015-10-09" {
+ description
+ "Initial OpenConfig public release";
+ reference "TBD";
+ }
+
+ revision "2015-10-05" {
+ description
+ "Initial revision";
+ reference "TBD";
+ }
+
+ oc-ext:openconfig-version "0.0.1";
+
+ extension openconfig-version {
+ argument "semver" {
+ yin-element false;
+ }
+ description
+ "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.";
+ }
+
+ extension openconfig-encrypted-value {
+ description
+ "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.";
+ }
+}
\ No newline at end of file
--- /dev/null
+module bar {
+ namespace "bar";
+ prefix bar;
+ yang-version 1;
+
+ import openconfig-extensions { prefix oc-ext; revision-date 2017-01-29; oc-ext:openconfig-version "0.0.1"; }
+
+ revision "2016-01-01" {
+ description "Initial version";
+ }
+ oc-ext:openconfig-version "4.4.0";
+
+ container root {
+ }
+}
--- /dev/null
+module bar {
+ namespace "bar";
+ prefix bar;
+ yang-version 1;
+
+ import openconfig-extensions { prefix oc-ext; revision-date 2017-01-29; oc-ext:openconfig-version "0.0.1"; }
+
+ revision "2016-01-02" {
+ description "Initial version";
+ }
+ oc-ext:openconfig-version "5.5.0";
+
+ container root {
+ }
+}
prefix bar;
yang-version 1;
- import semantic-version { prefix sv; revision-date 2016-02-02; sv:semantic-version "0.0.1"; }
+ import openconfig-extensions { prefix oc-ext; revision-date 2017-01-29; oc-ext:openconfig-version "0.0.1"; }
revision "2016-02-01" {
description "Initial version";
}
- sv:semantic-version "5.5.5";
+ oc-ext:openconfig-version "5.5.5";
container root {
}
prefix bar;
yang-version 1;
- import semantic-version { prefix sv; revision-date 2016-02-02; sv:semantic-version "0.0.1"; }
+ import openconfig-extensions { prefix oc-ext; revision-date 2017-01-29; oc-ext:openconfig-version "0.0.1"; }
revision "2016-02-02" {
description "Initial version";
}
- sv:semantic-version "5.5.6";
+ oc-ext:openconfig-version "5.5.6";
container root {
}
--- /dev/null
+module foo {
+ namespace "foo";
+ prefix foo;
+ yang-version 1;
+
+ import openconfig-extensions { prefix oc-ext; revision-date 2017-01-29; oc-ext:openconfig-version "0.0.1"; }
+ import bar { prefix bar; oc-ext:openconfig-version "5.5.5"; }
+
+ revision "2016-02-01" {
+ description "Initial version";
+ }
+ oc-ext:openconfig-version "0.1.1";
+
+ container root {
+ }
+}
--- /dev/null
+module openconfig-extensions {
+ yang-version "1";
+ namespace "http://openconfig.net/yang/openconfig-ext";
+ prefix "oc-ext";
+
+ organization "OpenConfig working group";
+
+ contact
+ "OpenConfig working group
+ www.openconfig.net";
+
+ description
+ "This module provides extensions to the YANG language to allow
+ OpenConfig specific functionality and meta-data to be defined.";
+
+ revision "2017-01-29" {
+ description
+ "Added extension for annotating encrypted values.";
+ reference "TBD";
+ }
+
+ revision "2015-10-09" {
+ description
+ "Initial OpenConfig public release";
+ reference "TBD";
+ }
+
+ revision "2015-10-05" {
+ description
+ "Initial revision";
+ reference "TBD";
+ }
+
+ oc-ext:openconfig-version "0.0.1";
+
+ extension openconfig-version {
+ argument "semver" {
+ yin-element false;
+ }
+ description
+ "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.";
+ }
+
+ extension openconfig-encrypted-value {
+ description
+ "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.";
+ }
+}
\ No newline at end of file
prefix bar;
yang-version 1;
- import semantic-version { prefix sv; revision-date 2016-02-02; sv:semantic-version "0.0.1"; }
+ import openconfig-extensions { prefix oc-ext; revision-date 2017-01-29; oc-ext:openconfig-version "0.0.1"; }
revision 2016-04-04 {
description "test";
}
- sv:semantic-version "2016.4.4";
+ oc-ext:openconfig-version "2016.4.4";
grouping grp {
container con20160404 {
prefix bar;
yang-version 1;
- import semantic-version { prefix sv; revision-date 2016-02-02; sv:semantic-version "0.0.1"; }
+ import openconfig-extensions { prefix oc-ext; revision-date 2017-01-29; oc-ext:openconfig-version "0.0.1"; }
revision 2016-04-05 {
description "test";
}
- sv:semantic-version "2016.4.5";
+ oc-ext:openconfig-version "2016.4.5";
grouping grp {
container con20160404 {
prefix bar;
yang-version 1;
- import semantic-version { prefix sv; revision-date 2016-02-02; sv:semantic-version "0.0.1"; }
+ import openconfig-extensions { prefix oc-ext; revision-date 2017-01-29; oc-ext:openconfig-version "0.0.1"; }
revision 2016-04-06 {
description "test";
}
- sv:semantic-version "2016.4.6";
+ oc-ext:openconfig-version "2016.4.6";
grouping grp {
container con20160404 {
prefix bar;
yang-version 1;
- import semantic-version { prefix sv; revision-date 2016-02-02; sv:semantic-version "0.0.1"; }
+ import openconfig-extensions { prefix oc-ext; revision-date 2017-01-29; oc-ext:openconfig-version "0.0.1"; }
revision 2017-04-06 {
description "test";
}
- sv:semantic-version "2017.4.6";
+ oc-ext:openconfig-version "2017.4.6";
grouping grp {
container con20160404 {
--- /dev/null
+module foo {
+ namespace "foo";
+ prefix foo;
+ yang-version 1;
+
+ import openconfig-extensions { prefix oc-ext; revision-date 2017-01-29; oc-ext:openconfig-version "0.0.1"; }
+ import bar { prefix bar; revision-date 2017-04-06; oc-ext:openconfig-version "2016.4.5"; }
+
+ revision 2016-01-01 {
+ description "test";
+ }
+
+ oc-ext:openconfig-version "2016.1.1";
+
+ container foo-root {
+ uses bar:grp;
+ }
+}
--- /dev/null
+module openconfig-extensions {
+ yang-version "1";
+ namespace "http://openconfig.net/yang/openconfig-ext";
+ prefix "oc-ext";
+
+ organization "OpenConfig working group";
+
+ contact
+ "OpenConfig working group
+ www.openconfig.net";
+
+ description
+ "This module provides extensions to the YANG language to allow
+ OpenConfig specific functionality and meta-data to be defined.";
+
+ revision "2017-01-29" {
+ description
+ "Added extension for annotating encrypted values.";
+ reference "TBD";
+ }
+
+ revision "2015-10-09" {
+ description
+ "Initial OpenConfig public release";
+ reference "TBD";
+ }
+
+ revision "2015-10-05" {
+ description
+ "Initial revision";
+ reference "TBD";
+ }
+
+ oc-ext:openconfig-version "0.0.1";
+
+ extension openconfig-version {
+ argument "semver" {
+ yin-element false;
+ }
+ description
+ "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.";
+ }
+
+ extension openconfig-encrypted-value {
+ description
+ "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.";
+ }
+}
\ No newline at end of file
--- /dev/null
+module bar {
+ namespace "bar";
+ prefix bar;
+ yang-version 1;
+
+ import openconfig-extensions { prefix oc-ext; revision-date 2017-01-29; oc-ext:openconfig-version "0.0.1"; }
+
+ revision "2016-01-01" {
+ description "Initial version";
+ }
+ oc-ext:openconfig-version "0.1.2";
+
+ container root {
+ }
+}
--- /dev/null
+module foo {
+ namespace "foo";
+ prefix foo;
+ yang-version 1;
+
+ import openconfig-extensions { prefix oc-ext; revision-date 2017-01-29; oc-ext:openconfig-version "0.0.1"; }
+ import bar { prefix bar; revision-date 2016-01-31; oc-ext:openconfig-version "0.1.2";}
+
+ revision "2016-02-01" {
+ description "Initial version";
+ }
+ oc-ext:openconfig-version "0.1.1";
+
+ container root {
+ }
+}
--- /dev/null
+module openconfig-extensions {
+ yang-version "1";
+ namespace "http://openconfig.net/yang/openconfig-ext";
+ prefix "oc-ext";
+
+ organization "OpenConfig working group";
+
+ contact
+ "OpenConfig working group
+ www.openconfig.net";
+
+ description
+ "This module provides extensions to the YANG language to allow
+ OpenConfig specific functionality and meta-data to be defined.";
+
+ revision "2017-01-29" {
+ description
+ "Added extension for annotating encrypted values.";
+ reference "TBD";
+ }
+
+ revision "2015-10-09" {
+ description
+ "Initial OpenConfig public release";
+ reference "TBD";
+ }
+
+ revision "2015-10-05" {
+ description
+ "Initial revision";
+ reference "TBD";
+ }
+
+ oc-ext:openconfig-version "0.0.1";
+
+ extension openconfig-version {
+ argument "semver" {
+ yin-element false;
+ }
+ description
+ "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.";
+ }
+
+ extension openconfig-encrypted-value {
+ description
+ "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.";
+ }
+}
\ No newline at end of file
module bar {
- sv:semantic-version "0.1.2";
+ oc-ext:openconfig-version "0.1.2";
namespace "bar";
prefix bar;
yang-version 1;
- import semantic-version { prefix sv; revision-date 2016-02-02; sv:semantic-version "0.0.1"; }
+ import openconfig-extensions { prefix oc-ext; revision-date 2017-01-29; oc-ext:openconfig-version "0.0.1"; }
revision "2016-01-31" {
description "Initial version";
--- /dev/null
+module foo {
+ oc-ext:openconfig-version "0.1.1";
+ import bar { prefix bar; revision-date 2016-01-31; oc-ext:openconfig-version "0.1.2";}
+
+ namespace "foo";
+ prefix foo;
+ yang-version 1;
+
+ import openconfig-extensions { prefix oc-ext; revision-date 2017-01-29; oc-ext:openconfig-version "0.0.1"; }
+
+ revision "2016-02-01" {
+ description "Initial version";
+ }
+
+ container root {
+ }
+}
-module semantic-version {
- sv:semantic-version "0.0.1";
+module openconfig-extensions {
+ oc-ext:openconfig-version "0.0.1";
+ yang-version "1";
+ namespace "http://openconfig.net/yang/openconfig-ext";
+ prefix "oc-ext";
- namespace "urn:opendaylight:yang:extension:semantic-version";
- prefix sv;
- yang-version 1;
+ organization "OpenConfig working group";
- revision 2016-02-02 {
- description "Initial verison";
+ contact
+ "OpenConfig working group
+ www.openconfig.net";
+
+ description
+ "This module provides extensions to the YANG language to allow
+ OpenConfig specific functionality and meta-data to be defined.";
+
+ revision "2017-01-29" {
+ description
+ "Added extension for annotating encrypted values.";
+ reference "TBD";
+ }
+
+ revision "2015-10-09" {
+ description
+ "Initial OpenConfig public release";
+ reference "TBD";
}
- extension semantic-version {
- argument "semantic-version" {
+ revision "2015-10-05" {
+ description
+ "Initial revision";
+ reference "TBD";
+ }
+
+ extension openconfig-version {
+ argument "semver" {
yin-element false;
}
description
The version number is stored in the module meta-data.";
}
-}
+
+ extension openconfig-encrypted-value {
+ description
+ "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.";
+ }
+}
\ No newline at end of file
--- /dev/null
+module bar {
+ namespace "bar";
+ prefix bar;
+ yang-version 1;
+
+ import openconfig-extensions { prefix oc-ext; revision-date 2017-01-29; oc-ext:openconfig-version "0.0.1"; }
+
+ revision "2016-01-31" {
+ description "Initial version";
+ }
+ oc-ext:openconfig-version "0.1.2";
+
+ container root {
+ }
+}
--- /dev/null
+module foo {
+ namespace "foo";
+ prefix foo;
+ yang-version 1;
+
+ import openconfig-extensions { prefix oc-ext; revision-date 2017-01-29; oc-ext:openconfig-version "0.0.1"; }
+ import bar { prefix bar; revision-date 2016-01-31; oc-ext:openconfig-version "0.1.2";}
+
+ revision "2016-02-01" {
+ description "Initial version";
+ }
+ oc-ext:openconfig-version "0.1.1";
+
+ container root {
+ }
+}
--- /dev/null
+module openconfig-extensions {
+ yang-version "1";
+ namespace "http://openconfig.net/yang/openconfig-ext";
+ prefix "oc-ext";
+
+ organization "OpenConfig working group";
+
+ contact
+ "OpenConfig working group
+ www.openconfig.net";
+
+ description
+ "This module provides extensions to the YANG language to allow
+ OpenConfig specific functionality and meta-data to be defined.";
+
+ revision "2017-01-29" {
+ description
+ "Added extension for annotating encrypted values.";
+ reference "TBD";
+ }
+
+ revision "2015-10-09" {
+ description
+ "Initial OpenConfig public release";
+ reference "TBD";
+ }
+
+ revision "2015-10-05" {
+ description
+ "Initial revision";
+ reference "TBD";
+ }
+
+ oc-ext:openconfig-version "0.0.1";
+
+ extension openconfig-version {
+ argument "semver" {
+ yin-element false;
+ }
+ description
+ "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.";
+ }
+
+ extension openconfig-encrypted-value {
+ description
+ "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.";
+ }
+}
\ No newline at end of file
prefix bar;
yang-version 1;
- import semantic-version { prefix sv; revision-date 2016-02-02; sv:semantic-version "0.0.1"; }
+ import openconfig-extensions { prefix oc-ext; revision-date 2017-01-29; oc-ext:openconfig-version "0.0.1"; }
revision "2016-01-31" {
description "Initial version";
container root {
}
- sv:semantic-version "0.1.2";
+ oc-ext:openconfig-version "0.1.2";
}
--- /dev/null
+module foo {
+ namespace "foo";
+ prefix foo;
+ yang-version 1;
+
+ import openconfig-extensions { prefix oc-ext; revision-date 2017-01-29; oc-ext:openconfig-version "0.0.1"; }
+
+ revision "2016-02-01" {
+ description "Initial version";
+ }
+
+ container root {
+ }
+
+ oc-ext:openconfig-version "0.1.1";
+ import bar { prefix bar; revision-date 2016-01-31; oc-ext:openconfig-version "0.1.2";}
+}
--- /dev/null
+module openconfig-extensions {
+ yang-version "1";
+ namespace "http://openconfig.net/yang/openconfig-ext";
+ prefix "oc-ext";
+
+ organization "OpenConfig working group";
+
+ contact
+ "OpenConfig working group
+ www.openconfig.net";
+
+ description
+ "This module provides extensions to the YANG language to allow
+ OpenConfig specific functionality and meta-data to be defined.";
+
+ revision "2017-01-29" {
+ description
+ "Added extension for annotating encrypted values.";
+ reference "TBD";
+ }
+
+ revision "2015-10-09" {
+ description
+ "Initial OpenConfig public release";
+ reference "TBD";
+ }
+
+ revision "2015-10-05" {
+ description
+ "Initial revision";
+ reference "TBD";
+ }
+
+ extension openconfig-version {
+ argument "semver" {
+ yin-element false;
+ }
+ description
+ "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.";
+ }
+
+ extension openconfig-encrypted-value {
+ description
+ "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.";
+ }
+
+ oc-ext:openconfig-version "0.0.1";
+}
\ No newline at end of file
--- /dev/null
+module bar {
+ namespace "bar";
+ prefix bar;
+ yang-version 1;
+
+ import openconfig-extensions { prefix oc-ext; revision-date 2017-01-29; oc-ext:openconfig-version "0.0.1"; }
+
+ revision "2016-01-01" {
+ description "Initial version";
+ }
+ oc-ext:openconfig-version "0.1.2";
+
+ container root {
+ }
+}
--- /dev/null
+module foo {
+ namespace "foo";
+ prefix foo;
+ yang-version 1;
+
+ import openconfig-extensions { prefix oc-ext; revision-date 2017-01-29; oc-ext:openconfig-version "0.0.1"; }
+ import bar { prefix bar; revision-date 2016-01-01; oc-ext:openconfig-version "0.1.2";}
+
+ revision "2016-02-01" {
+ description "Initial version";
+ }
+ oc-ext:openconfig-version "0.1.1";
+
+ container root {
+ }
+}
--- /dev/null
+module openconfig-extensions {
+ yang-version "1";
+ namespace "http://openconfig.net/yang/openconfig-ext";
+ prefix "oc-ext";
+
+ organization "OpenConfig working group";
+
+ contact
+ "OpenConfig working group
+ www.openconfig.net";
+
+ description
+ "This module provides extensions to the YANG language to allow
+ OpenConfig specific functionality and meta-data to be defined.";
+
+ revision "2017-01-29" {
+ description
+ "Added extension for annotating encrypted values.";
+ reference "TBD";
+ }
+
+ revision "2015-10-09" {
+ description
+ "Initial OpenConfig public release";
+ reference "TBD";
+ }
+
+ revision "2015-10-05" {
+ description
+ "Initial revision";
+ reference "TBD";
+ }
+
+ oc-ext:openconfig-version "0.0.1";
+
+ extension openconfig-version {
+ argument "semver" {
+ yin-element false;
+ }
+ description
+ "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.";
+ }
+
+ extension openconfig-encrypted-value {
+ description
+ "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.";
+ }
+}
\ No newline at end of file
<?xml version="1.0" encoding="UTF-8"?>
<module xmlns="urn:ietf:params:xml:ns:yang:yin:1" xmlns:bar="bar"
- xmlns:sv="urn:opendaylight:yang:extension:semantic-version" name="bar">
+ xmlns:oc-ext="http://openconfig.net/yang/openconfig-ext" name="bar">
<yang-version value="1"></yang-version>
<namespace uri="bar"></namespace>
<prefix value="bar"></prefix>
- <import module="semantic-version">
- <prefix value="sv"></prefix>
+ <import module="openconfig-extensions">
+ <prefix value="oc-ext"></prefix>
<revision-date date="2016-02-02"></revision-date>
- <sv:semantic-version semantic-version="0.0.1"></sv:semantic-version>
+ <oc-ext:openconfig-version semver="0.0.1"></oc-ext:openconfig-version>
</import>
<organization>
<text></text>
<text></text>
</contact>
<revision date="2016-01-01"></revision>
- <sv:semantic-version semantic-version="1.1.2"></sv:semantic-version>
+ <oc-ext:openconfig-version semver="1.1.2"></oc-ext:openconfig-version>
<container name="root">
<presence value="false"></presence>
<config value="true"></config>
<?xml version="1.0" encoding="UTF-8"?>
<module xmlns="urn:ietf:params:xml:ns:yang:yin:1" xmlns:bar="bar"
- xmlns:sv="urn:opendaylight:yang:extension:semantic-version" name="bar">
+ xmlns:oc-ext="http://openconfig.net/yang/openconfig-ext" name="bar">
<yang-version value="1"></yang-version>
<namespace uri="bar"></namespace>
<prefix value="bar"></prefix>
- <import module="semantic-version">
- <prefix value="sv"></prefix>
+ <import module="openconfig-extensions">
+ <prefix value="oc-ext"></prefix>
<revision-date date="2016-02-02"></revision-date>
- <sv:semantic-version semantic-version="0.0.1"></sv:semantic-version>
+ <oc-ext:openconfig-version semver="0.0.1"></oc-ext:openconfig-version>
</import>
<organization>
<text></text>
<text></text>
</contact>
<revision date="2016-01-31"></revision>
- <sv:semantic-version semantic-version="0.1.2"></sv:semantic-version>
+ <oc-ext:openconfig-version semver="1.1.3"></oc-ext:openconfig-version>
<container name="root">
<presence value="false"></presence>
<config value="true"></config>
<?xml version="1.0" encoding="UTF-8"?>
<module xmlns="urn:ietf:params:xml:ns:yang:yin:1" xmlns:foo="foo" xmlns:bar="bar"
- xmlns:sv="urn:opendaylight:yang:extension:semantic-version" name="foo">
+ xmlns:oc-ext="http://openconfig.net/yang/openconfig-ext" name="foo">
<yang-version value="1"></yang-version>
<namespace uri="foo"></namespace>
<prefix value="foo"></prefix>
<import module="bar">
<prefix value="bar"></prefix>
<revision-date date="2016-01-31"></revision-date>
- <sv:semantic-version semantic-version="0.1.2"></sv:semantic-version>
+ <oc-ext:openconfig-version semver="0.1.2"></oc-ext:openconfig-version>
</import>
- <import module="semantic-version">
- <prefix value="sv"></prefix>
+ <import module="openconfig-extensions">
+ <prefix value="oc-ext"></prefix>
<revision-date date="2016-02-02"></revision-date>
- <sv:semantic-version semantic-version="0.0.1"></sv:semantic-version>
+ <oc-ext:openconfig-version semver="0.0.1"></oc-ext:openconfig-version>
</import>
<organization>
<text></text>
<text></text>
</contact>
<revision date="2016-02-01"></revision>
- <sv:semantic-version semantic-version="0.1.1"></sv:semantic-version>
+ <oc-ext:openconfig-version semver="0.1.1"></oc-ext:openconfig-version>
<container name="root">
<presence value="false"></presence>
<config value="true"></config>
--- /dev/null
+<?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
<?xml version="1.0" encoding="UTF-8"?>
<module xmlns="urn:ietf:params:xml:ns:yang:yin:1" xmlns:bar="bar"
- xmlns:sv="urn:opendaylight:yang:extension:semantic-version" name="bar">
+ xmlns:oc-ext="http://openconfig.net/yang/openconfig-ext" name="bar">
<yang-version value="1"></yang-version>
<namespace uri="bar"></namespace>
<prefix value="bar"></prefix>
- <import module="semantic-version">
- <prefix value="sv"></prefix>
+ <import module="openconfig-extensions">
+ <prefix value="oc-ext"></prefix>
<revision-date date="2016-02-02"></revision-date>
- <sv:semantic-version semantic-version="0.0.1"></sv:semantic-version>
+ <oc-ext:openconfig-version semver="0.0.1"></oc-ext:openconfig-version>
</import>
<organization>
<text></text>
<text></text>
</contact>
<revision date="2016-01-01"></revision>
- <sv:semantic-version semantic-version="0.1.2"></sv:semantic-version>
+ <oc-ext:openconfig-version semver="0.1.2"></oc-ext:openconfig-version>
<container name="root">
<presence value="false"></presence>
<config value="true"></config>
<?xml version="1.0" encoding="UTF-8"?>
<module xmlns="urn:ietf:params:xml:ns:yang:yin:1" xmlns:bar="bar"
- xmlns:sv="urn:opendaylight:yang:extension:semantic-version" name="bar">
+ xmlns:oc-ext="http://openconfig.net/yang/openconfig-ext" name="bar">
<yang-version value="1"></yang-version>
<namespace uri="bar"></namespace>
<prefix value="bar"></prefix>
- <import module="semantic-version">
- <prefix value="sv"></prefix>
+ <import module="openconfig-extensions">
+ <prefix value="oc-ext"></prefix>
<revision-date date="2016-02-02"></revision-date>
- <sv:semantic-version semantic-version="0.0.1"></sv:semantic-version>
+ <oc-ext:openconfig-version semver="0.0.1"></oc-ext:openconfig-version>
</import>
<organization>
<text></text>
<text></text>
</contact>
<revision date="2016-01-31"></revision>
- <sv:semantic-version semantic-version="1.1.3"></sv:semantic-version>
+ <oc-ext:openconfig-version semver="1.1.2"></oc-ext:openconfig-version>
<container name="root">
<presence value="false"></presence>
<config value="true"></config>
<?xml version="1.0" encoding="UTF-8"?>
<module xmlns="urn:ietf:params:xml:ns:yang:yin:1" xmlns:foo="foo" xmlns:bar="bar"
- xmlns:sv="urn:opendaylight:yang:extension:semantic-version" name="foo">
+ xmlns:oc-ext="http://openconfig.net/yang/openconfig-ext" name="foo">
<yang-version value="1"></yang-version>
<namespace uri="foo"></namespace>
<prefix value="foo"></prefix>
<import module="bar">
<prefix value="bar"></prefix>
<revision-date date="2016-01-31"></revision-date>
- <sv:semantic-version semantic-version="0.1.2"></sv:semantic-version>
+ <oc-ext:openconfig-version semver="0.1.2"></oc-ext:openconfig-version>
</import>
- <import module="semantic-version">
- <prefix value="sv"></prefix>
+ <import module="openconfig-extensions">
+ <prefix value="oc-ext"></prefix>
<revision-date date="2016-02-02"></revision-date>
- <sv:semantic-version semantic-version="0.0.1"></sv:semantic-version>
+ <oc-ext:openconfig-version semver="0.0.1"></oc-ext:openconfig-version>
</import>
<organization>
<text></text>
<text></text>
</contact>
<revision date="2016-02-01"></revision>
- <sv:semantic-version semantic-version="0.1.1"></sv:semantic-version>
+ <oc-ext:openconfig-version semver="0.1.1"></oc-ext:openconfig-version>
<container name="root">
<presence value="false"></presence>
<config value="true"></config>
--- /dev/null
+<?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
<?xml version="1.0" encoding="UTF-8"?>
<module xmlns="urn:ietf:params:xml:ns:yang:yin:1" xmlns:bar="bar"
- xmlns:sv="urn:opendaylight:yang:extension:semantic-version" name="bar">
+ xmlns:oc-ext="http://openconfig.net/yang/openconfig-ext" name="bar">
<yang-version value="1"></yang-version>
<namespace uri="bar"></namespace>
<prefix value="bar"></prefix>
- <import module="semantic-version">
- <prefix value="sv"></prefix>
- <revision-date date="2016-02-02"></revision-date>
- <sv:semantic-version semantic-version="0.0.1"></sv:semantic-version>
+ <import module="openconfig-extensions">
+ <prefix value="oc-ext"></prefix>
+ <revision-date date="2017-01-29"></revision-date>
+ <oc-ext:openconfig-version semver="0.0.1"></oc-ext:openconfig-version>
</import>
<organization>
<text></text>
<text></text>
</contact>
<revision date="2016-01-31"></revision>
- <sv:semantic-version semantic-version="1.1.2"></sv:semantic-version>
+ <oc-ext:openconfig-version semver="0.1.2"></oc-ext:openconfig-version>
<container name="root">
<presence value="false"></presence>
<config value="true"></config>
<?xml version="1.0" encoding="UTF-8"?>
<module xmlns="urn:ietf:params:xml:ns:yang:yin:1" xmlns:foo="foo" xmlns:bar="bar"
- xmlns:sv="urn:opendaylight:yang:extension:semantic-version" name="foo">
+ xmlns:oc-ext="http://openconfig.net/yang/openconfig-ext" name="foo">
<yang-version value="1"></yang-version>
<namespace uri="foo"></namespace>
<prefix value="foo"></prefix>
<import module="bar">
<prefix value="bar"></prefix>
<revision-date date="2016-01-31"></revision-date>
- <sv:semantic-version semantic-version="0.1.2"></sv:semantic-version>
+ <oc-ext:openconfig-version semver="0.1.2"></oc-ext:openconfig-version>
</import>
- <import module="semantic-version">
- <prefix value="sv"></prefix>
- <revision-date date="2016-02-02"></revision-date>
- <sv:semantic-version semantic-version="0.0.1"></sv:semantic-version>
+ <import module="openconfig-extensions">
+ <prefix value="oc-ext"></prefix>
+ <revision-date date="2017-01-29"></revision-date>
+ <oc-ext:openconfig-version semver="0.0.1"></oc-ext:openconfig-version>
</import>
<organization>
<text></text>
<text></text>
</contact>
<revision date="2016-02-01"></revision>
- <sv:semantic-version semantic-version="0.1.1"></sv:semantic-version>
+ <oc-ext:openconfig-version semver="0.1.1"></oc-ext:openconfig-version>
<container name="root">
<presence value="false"></presence>
<config value="true"></config>
--- /dev/null
+<?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
prefix bar;
yang-version 1.1;
- import semantic-version { prefix sv; sv:semantic-version "1.2.012"; }
- import foobar { prefix foobar; sv:semantic-version "2.25.3"; }
+ import openconfig-extensions { prefix oc-ext; oc-ext:openconfig-version "1.2.012"; }
+ import foobar { prefix foobar; oc-ext:openconfig-version "2.25.3"; }
revision "2016-01-03" {
description "Imported version";
}
- sv:semantic-version "1.2.6";
+ oc-ext:openconfig-version "1.2.6";
container root {
container test-container {
prefix bar;
yang-version 1.1;
- import semantic-version { prefix sv; sv:semantic-version "1.2.210"; }
- import foobar { prefix foobar; sv:semantic-version "2.25.3"; }
+ import openconfig-extensions { prefix oc-ext; oc-ext:openconfig-version "1.2.210"; }
+ import foobar { prefix foobar; oc-ext:openconfig-version "2.25.3"; }
revision "2016-01-04" {
description "Not-imported version";
}
- sv:semantic-version "2.200.200";
+ oc-ext:openconfig-version "2.200.200";
container root {
container test-container {
--- /dev/null
+module foo {
+ namespace "foo";
+ prefix foo;
+ yang-version 1.1;
+
+ import openconfig-extensions { prefix oc-ext; oc-ext:openconfig-version "1.0.0"; }
+ import bar { prefix bar; oc-ext:openconfig-version "1.2.5"; }
+
+ revision "2016-02-01" {
+ description "Initial version";
+ }
+ oc-ext:openconfig-version "1.50.02";
+}
prefix foobar;
yang-version 1.1;
- import semantic-version { prefix sv; sv:semantic-version "1.2.95"; }
+ import openconfig-extensions { prefix oc-ext; oc-ext:openconfig-version "1.2.95"; }
revision "2016-01-31" {
description "Not-imported version";
}
- sv:semantic-version "2.25.2";
+ oc-ext:openconfig-version "2.25.2";
grouping test-grouping {
leaf name {
prefix foobar;
yang-version 1.1;
- import semantic-version { prefix sv; sv:semantic-version "1.3.95"; }
+ import openconfig-extensions { prefix oc-ext; oc-ext:openconfig-version "1.3.95"; }
revision "2016-02-28" {
description "Imported version";
}
- sv:semantic-version "2.26.465";
+ oc-ext:openconfig-version "2.26.465";
grouping test-grouping {
leaf name {
--- /dev/null
+module openconfig-extensions {
+ yang-version "1.1";
+ namespace "http://openconfig.net/yang/openconfig-ext";
+ prefix "oc-ext";
+
+ organization "OpenConfig working group";
+
+ contact
+ "OpenConfig working group
+ www.openconfig.net";
+
+ description
+ "This module provides extensions to the YANG language to allow
+ OpenConfig specific functionality and meta-data to be defined.";
+
+ revision "2017-01-29" {
+ description
+ "Added extension for annotating encrypted values.";
+ reference "TBD";
+ }
+
+ revision "2015-10-09" {
+ description
+ "Initial OpenConfig public release";
+ reference "TBD";
+ }
+
+ revision "2015-10-05" {
+ description
+ "Initial revision";
+ reference "TBD";
+ }
+
+ oc-ext:openconfig-version "1.3.95";
+
+ extension openconfig-version {
+ argument "semver" {
+ yin-element false;
+ }
+ description
+ "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.";
+ }
+
+ extension openconfig-encrypted-value {
+ description
+ "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.";
+ }
+}
\ No newline at end of file
prefix bar;
yang-version 1;
- import semantic-version { prefix sv; sv:semantic-version "2.0.40"; }
- import foobar { prefix foobar; sv:semantic-version "7.12.54"; }
+ import openconfig-extensions { prefix oc-ext; oc-ext:openconfig-version "2.0.40"; }
+ import foobar { prefix foobar; oc-ext:openconfig-version "7.12.54"; }
revision "2016-01-03" {
description "Imported version";
}
- sv:semantic-version "4.9.8";
+ oc-ext:openconfig-version "4.9.8";
augment "/foobar:root/foobar:test-container" {
leaf should-present-leaf-1 {
prefix bar;
yang-version 1.1;
- import semantic-version { prefix sv; sv:semantic-version "2.0.50"; }
- import foobar { prefix foobar; sv:semantic-version "7.12.54"; }
+ import openconfig-extensions { prefix oc-ext; oc-ext:openconfig-version "2.0.50"; }
+ import foobar { prefix foobar; oc-ext:openconfig-version "7.12.54"; }
revision "2016-01-04" {
description "Not-imported version";
}
- sv:semantic-version "3.0.5";
+ oc-ext:openconfig-version "3.0.5";
augment "/foobar:root/foobar:test-container" {
leaf should-not-be-present-leaf-1 {
--- /dev/null
+module foo {
+ namespace "foo";
+ prefix foo;
+ yang-version 1.1;
+
+ import openconfig-extensions { prefix oc-ext; oc-ext:openconfig-version "2.5.40"; }
+ import bar { prefix bar; oc-ext:openconfig-version "4.1.1"; }
+
+ revision "2016-02-01" {
+ description "Initial version";
+ }
+ oc-ext:openconfig-version "2.32.2";
+}
prefix foobar;
yang-version 1;
- import semantic-version { prefix sv; sv:semantic-version "2.1.950"; }
+ import openconfig-extensions { prefix oc-ext; oc-ext:openconfig-version "2.1.950"; }
revision "2016-01-31" {
description "Not-imported version";
}
- sv:semantic-version "8.0.0";
+ oc-ext:openconfig-version "8.0.0";
container root {
leaf included-not-correct-mark {
prefix foobar;
yang-version 1;
- import semantic-version { prefix sv; sv:semantic-version "2.5.50"; }
+ import openconfig-extensions { prefix oc-ext; oc-ext:openconfig-version "2.5.50"; }
revision "2016-02-27" {
description "Not-imported version";
}
- sv:semantic-version "7.13.0";
+ oc-ext:openconfig-version "7.13.0";
container root {
leaf included-not-correct-mark {
prefix foobar;
yang-version 1;
- import semantic-version { prefix sv; sv:semantic-version "2.5.50"; }
+ import openconfig-extensions { prefix oc-ext; oc-ext:openconfig-version "2.5.50"; }
revision "2016-02-28" {
description "Imported version";
}
- sv:semantic-version "7.13.99";
+ oc-ext:openconfig-version "7.13.99";
container root {
leaf included-correct-mark {
--- /dev/null
+module openconfig-extensions {
+ yang-version "1";
+ namespace "http://openconfig.net/yang/openconfig-ext";
+ prefix "oc-ext";
+
+ organization "OpenConfig working group";
+
+ contact
+ "OpenConfig working group
+ www.openconfig.net";
+
+ description
+ "This module provides extensions to the YANG language to allow
+ OpenConfig specific functionality and meta-data to be defined.";
+
+ revision "2017-01-29" {
+ description
+ "Added extension for annotating encrypted values.";
+ reference "TBD";
+ }
+
+ revision "2015-10-09" {
+ description
+ "Initial OpenConfig public release";
+ reference "TBD";
+ }
+
+ revision "2015-10-05" {
+ description
+ "Initial revision";
+ reference "TBD";
+ }
+
+ oc-ext:openconfig-version "2.5.50";
+
+ extension openconfig-version {
+ argument "semver" {
+ yin-element false;
+ }
+ description
+ "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.";
+ }
+
+ extension openconfig-encrypted-value {
+ description
+ "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.";
+ }
+}
\ No newline at end of file
+++ /dev/null
-module foo {
- namespace "foo";
- prefix foo;
- yang-version 1.1;
-
- import semantic-version { prefix sv; sv:semantic-version "1.0.0"; }
- import bar { prefix bar; sv:semantic-version "1.2.5"; }
-
- revision "2016-02-01" {
- description "Initial version";
- }
- sv:semantic-version "1.50.02";
-}
+++ /dev/null
-module foo {
- namespace "foo";
- prefix foo;
- yang-version 1.1;
-
- import semantic-version { prefix sv; sv:semantic-version "2.5.40"; }
- import bar { prefix bar; sv:semantic-version "4.1.1"; }
-
- revision "2016-02-01" {
- description "Initial version";
- }
- sv:semantic-version "2.32.2";
-}
+++ /dev/null
-module semantic-version {
- namespace "urn:opendaylight:yang:extension:semantic-version";
- prefix sv;
- yang-version 1;
-
- revision 2016-02-02 {
- description "Initial verison";
- }
- sv:semantic-version "2.5.50";
-
- extension semantic-version {
- argument "semantic-version" {
- yin-element false;
- }
- description
- "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.";
- }
-}
+++ /dev/null
-module semantic-version {
- namespace "urn:opendaylight:yang:extension:semantic-version";
- prefix sv;
- yang-version 1;
-
- revision 2016-02-02 {
- description "Initial verison";
- }
- sv:semantic-version "0.0.1";
-
- extension semantic-version {
- argument "semantic-version" {
- yin-element false;
- }
- description
- "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.";
- }
-}
+++ /dev/null
-module foo {
- namespace "foo";
- prefix foo;
- yang-version 1;
-
- import semantic-version { prefix sv; revision-date 2016-02-02; sv:semantic-version "0.0.1"; }
- import bar { prefix bar; sv:semantic-version "0.1.2";}
-
- revision "2016-02-01" {
- description "Initial version";
- }
- sv:semantic-version "0.1.1";
-
- container root {
- }
-}
+++ /dev/null
-module semantic-version {
- namespace "urn:opendaylight:yang:extension:semantic-version";
- prefix sv;
- yang-version 1;
-
- revision 2016-02-02 {
- description "Initial verison";
- }
- sv:semantic-version "0.0.1";
-
- extension semantic-version {
- argument "semantic-version" {
- yin-element false;
- }
- description
- "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.";
- }
-}
+++ /dev/null
-module foo {
- namespace "foo";
- prefix foo;
- yang-version 1;
-
- import semantic-version { prefix sv; revision-date 2016-02-02; sv:semantic-version "0.0.1"; }
- import bar { prefix bar; sv:semantic-version "0.1.2";}
-
- revision "2016-02-01" {
- description "Initial version";
- }
- sv:semantic-version "0.1.1";
-
- container root {
- }
-}
+++ /dev/null
-module semantic-version {
- namespace "urn:opendaylight:yang:extension:semantic-version";
- prefix sv;
- yang-version 1;
-
- revision 2016-02-02 {
- description "Initial verison";
- }
- sv:semantic-version "0.0.1";
-
- extension semantic-version {
- argument "semantic-version" {
- yin-element false;
- }
- description
- "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.";
- }
-}
+++ /dev/null
-module foo {
- namespace "foo";
- prefix foo;
- yang-version 1;
-
- import semantic-version { prefix sv; revision-date 2016-02-02; sv:semantic-version "0.0.1"; }
- import bar { prefix bar; revision-date 2016-01-31; sv:semantic-version "0.1.2";}
-
- revision "2016-02-01" {
- description "Initial version";
- }
- sv:semantic-version "0.1.1";
-
- container root {
- }
-}
+++ /dev/null
-module semantic-version {
- namespace "urn:opendaylight:yang:extension:semantic-version";
- prefix sv;
- yang-version 1;
-
- revision 2016-02-02 {
- description "Initial verison";
- }
- sv:semantic-version "0.0.1";
-
- extension semantic-version {
- argument "semantic-version" {
- yin-element false;
- }
- description
- "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.";
- }
-}
+++ /dev/null
-module foo {
- namespace "foo";
- prefix foo;
- yang-version 1;
-
- import semantic-version { prefix sv; revision-date 2016-02-02; sv:semantic-version "0.0.1"; }
- import bar { prefix bar; revision-date 2016-01-31; sv:semantic-version "0.1.2";}
-
- revision "2016-02-01" {
- description "Initial version";
- }
- sv:semantic-version "0.1.1";
-
- container root {
- }
-}
+++ /dev/null
-module semantic-version {
- namespace "urn:opendaylight:yang:extension:semantic-version";
- prefix sv;
- yang-version 1;
-
- revision 2016-02-02 {
- description "Initial verison";
- }
- sv:semantic-version "0.0.1";
-
- extension semantic-version {
- argument "semantic-version" {
- yin-element false;
- }
- description
- "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.";
- }
-}
+++ /dev/null
-module foo {
- namespace "foo";
- prefix foo;
- yang-version 1;
-
- import semantic-version { prefix sv; revision-date 2016-02-02; sv:semantic-version "0.0.1"; }
- import bar { prefix bar; sv:semantic-version "5.5.5"; }
-
- revision "2016-02-01" {
- description "Initial version";
- }
- sv:semantic-version "0.1.1";
-
- container root {
- }
-}
+++ /dev/null
-module semantic-version {
- namespace "urn:opendaylight:yang:extension:semantic-version";
- prefix sv;
- yang-version 1;
-
- revision 2016-02-02 {
- description "Initial verison";
- }
- sv:semantic-version "0.0.1";
-
- extension semantic-version {
- argument "semantic-version" {
- yin-element false;
- }
- description
- "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.";
- }
-}
+++ /dev/null
-module foo {
- namespace "foo";
- prefix foo;
- yang-version 1;
-
- import semantic-version { prefix sv; revision-date 2016-02-02; sv:semantic-version "0.0.1"; }
- import bar { prefix bar; sv:semantic-version "5.5.5"; }
-
- revision "2016-02-01" {
- description "Initial version";
- }
- sv:semantic-version "0.1.1";
-
- container root {
- }
-}
+++ /dev/null
-module semantic-version {
- namespace "urn:opendaylight:yang:extension:semantic-version";
- prefix sv;
- yang-version 1;
-
- revision 2016-02-02 {
- description "Initial verison";
- }
- sv:semantic-version "0.0.1";
-
- extension semantic-version {
- argument "semantic-version" {
- yin-element false;
- }
- description
- "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.";
- }
-}
+++ /dev/null
-module bar {
- namespace "bar";
- prefix bar;
- yang-version 1;
-
- import semantic-version { prefix sv; revision-date 2016-02-02; sv:semantic-version "0.0.1"; }
-
- revision "2016-01-01" {
- description "Initial version";
- }
- sv:semantic-version "5.5.2";
-
- container root {
- }
-}
+++ /dev/null
-module foo {
- namespace "foo";
- prefix foo;
- yang-version 1;
-
- import semantic-version { prefix sv; revision-date 2016-02-02; sv:semantic-version "0.0.1"; }
- import bar { prefix bar; sv:semantic-version "5.5.5"; }
-
- revision "2016-02-01" {
- description "Initial version";
- }
- sv:semantic-version "0.1.1";
-
- container root {
- }
-}
+++ /dev/null
-module semantic-version {
- namespace "urn:opendaylight:yang:extension:semantic-version";
- prefix sv;
- yang-version 1;
-
- revision 2016-02-02 {
- description "Initial verison";
- }
- sv:semantic-version "0.0.1";
-
- extension semantic-version {
- argument "semantic-version" {
- yin-element false;
- }
- description
- "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.";
- }
-}
+++ /dev/null
-module bar {
- namespace "bar";
- prefix bar;
- yang-version 1;
-
- import semantic-version { prefix sv; revision-date 2016-02-02; sv:semantic-version "0.0.1"; }
-
- revision "2016-01-01" {
- description "Initial version";
- }
- sv:semantic-version "4.5.5";
-
- container root {
- }
-}
+++ /dev/null
-module foo {
- namespace "foo";
- prefix foo;
- yang-version 1;
-
- import semantic-version { prefix sv; revision-date 2016-02-02; sv:semantic-version "0.0.1"; }
- import bar { prefix bar; sv:semantic-version "5.5.5"; }
-
- revision "2016-02-01" {
- description "Initial version";
- }
- sv:semantic-version "0.1.1";
-
- container root {
- }
-}
+++ /dev/null
-module semantic-version {
- namespace "urn:opendaylight:yang:extension:semantic-version";
- prefix sv;
- yang-version 1;
-
- revision 2016-02-02 {
- description "Initial verison";
- }
- sv:semantic-version "0.0.1";
-
- extension semantic-version {
- argument "semantic-version" {
- yin-element false;
- }
- description
- "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.";
- }
-}
+++ /dev/null
-module bar {
- namespace "bar";
- prefix bar;
- yang-version 1;
-
- import semantic-version { prefix sv; revision-date 2016-02-02; sv:semantic-version "0.0.1"; }
-
- revision "2016-01-01" {
- description "Initial version";
- }
- sv:semantic-version "5.4.5";
-
- container root {
- }
-}
+++ /dev/null
-module bar {
- namespace "bar";
- prefix bar;
- yang-version 1;
-
- import semantic-version { prefix sv; revision-date 2016-02-02; sv:semantic-version "0.0.1"; }
-
- revision "2016-01-02" {
- description "Initial version";
- }
- sv:semantic-version "5.5.5";
-
- container root {
- }
-}
+++ /dev/null
-module bar {
- namespace "bar";
- prefix bar;
- yang-version 1;
-
- import semantic-version { prefix sv; revision-date 2016-02-02; sv:semantic-version "0.0.1"; }
-
- revision "2016-01-03" {
- description "Initial version";
- }
- sv:semantic-version "5.6.5";
-
- container root {
- }
-}
+++ /dev/null
-module foo {
- namespace "foo";
- prefix foo;
- yang-version 1;
-
- import semantic-version { prefix sv; revision-date 2016-02-02; sv:semantic-version "0.0.1"; }
- import bar { prefix bar; sv:semantic-version "5.5.5"; }
-
- revision "2016-02-01" {
- description "Initial version";
- }
- sv:semantic-version "0.1.1";
-
- container root {
- }
-}
+++ /dev/null
-module semantic-version {
- namespace "urn:opendaylight:yang:extension:semantic-version";
- prefix sv;
- yang-version 1;
-
- revision 2016-02-02 {
- description "Initial verison";
- }
- sv:semantic-version "0.0.1";
-
- extension semantic-version {
- argument "semantic-version" {
- yin-element false;
- }
- description
- "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.";
- }
-}
+++ /dev/null
-module bar {
- namespace "bar";
- prefix bar;
- yang-version 1;
-
- import semantic-version { prefix sv; revision-date 2016-02-02; sv:semantic-version "0.0.1"; }
-
- revision "2016-01-01" {
- description "Initial version";
- }
- sv:semantic-version "5.5.4";
-
- container root {
- }
-}
+++ /dev/null
-module bar {
- namespace "bar";
- prefix bar;
- yang-version 1;
-
- import semantic-version { prefix sv; revision-date 2016-02-02; sv:semantic-version "0.0.1"; }
-
- revision "2016-01-02" {
- description "Initial version";
- }
- sv:semantic-version "5.5.5";
-
- container root {
- }
-}
+++ /dev/null
-module bar {
- namespace "bar";
- prefix bar;
- yang-version 1;
-
- import semantic-version { prefix sv; revision-date 2016-02-02; sv:semantic-version "0.0.1"; }
-
- revision "2016-01-03" {
- description "Initial version";
- }
- sv:semantic-version "5.5.6";
-
- container root {
- }
-}
+++ /dev/null
-module foo {
- namespace "foo";
- prefix foo;
- yang-version 1;
-
- import semantic-version { prefix sv; revision-date 2016-02-02; sv:semantic-version "0.0.1"; }
- import bar { prefix bar; sv:semantic-version "5.5.5"; }
-
- revision "2016-02-01" {
- description "Initial version";
- }
- sv:semantic-version "0.1.1";
-
- container root {
- }
-}
+++ /dev/null
-module semantic-version {
- namespace "urn:opendaylight:yang:extension:semantic-version";
- prefix sv;
- yang-version 1;
-
- revision 2016-02-02 {
- description "Initial verison";
- }
- sv:semantic-version "0.0.1";
-
- extension semantic-version {
- argument "semantic-version" {
- yin-element false;
- }
- description
- "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.";
- }
-}
+++ /dev/null
-module foo {
- namespace "foo";
- prefix foo;
- yang-version 1;
-
- import semantic-version { prefix sv; sv:semantic-version "1.0.0"; }
- import bar { prefix bar; sv:semantic-version "1.2.5"; }
-
- revision "2016-02-01" {
- description "Initial version";
- }
- sv:semantic-version "1.50.02";
-}
+++ /dev/null
-module semantic-version {
- namespace "urn:opendaylight:yang:extension:semantic-version";
- prefix sv;
- yang-version 1;
-
- revision 2016-02-02 {
- description "Initial verison";
- }
- sv:semantic-version "1.3.95";
-
- extension semantic-version {
- argument "semantic-version" {
- yin-element false;
- }
- description
- "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.";
- }
-}
+++ /dev/null
-module foo {
- namespace "foo";
- prefix foo;
- yang-version 1;
-
- import semantic-version { prefix sv; sv:semantic-version "2.5.40"; }
- import bar { prefix bar; sv:semantic-version "4.1.1"; }
-
- revision "2016-02-01" {
- description "Initial version";
- }
- sv:semantic-version "2.32.2";
-}
+++ /dev/null
-module semantic-version {
- namespace "urn:opendaylight:yang:extension:semantic-version";
- prefix sv;
- yang-version 1;
-
- revision 2016-02-02 {
- description "Initial verison";
- }
- sv:semantic-version "2.5.50";
-
- extension semantic-version {
- argument "semantic-version" {
- yin-element false;
- }
- description
- "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.";
- }
-}
+++ /dev/null
-module semantic-version {
- namespace "urn:opendaylight:yang:extension:semantic-version";
- prefix sv;
- yang-version 1;
-
- revision 2016-02-02 {
- description "Initial verison";
- }
- sv:semantic-version "0.0.1";
-
- extension semantic-version {
- argument "semantic-version" {
- yin-element false;
- }
- description
- "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.";
- }
-}
+++ /dev/null
-module bar {
- namespace "bar";
- prefix bar;
- yang-version 1;
-
- import semantic-version { prefix sv; revision-date 2016-02-02; sv:semantic-version "0.0.1"; }
-
- revision "2016-01-31" {
- description "Initial version";
- }
- sv:semantic-version "0.99.99";
-
- container root {
- }
-}
+++ /dev/null
-module semantic-version {
- namespace "urn:opendaylight:yang:extension:semantic-version";
- prefix sv;
- yang-version 1;
-
- revision 2016-02-02 {
- description "Initial verison";
- }
- sv:semantic-version "0.0.1";
-
- extension semantic-version {
- argument "semantic-version" {
- yin-element false;
- }
- description
- "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.";
- }
-}
+++ /dev/null
-module bar {
- namespace "bar";
- prefix bar;
- yang-version 1;
-
- import semantic-version { prefix sv; revision-date 2016-02-02; sv:semantic-version "0.0.1"; }
-
- revision "2016-01-01" {
- description "Initial version";
- }
- sv:semantic-version "0.1.2";
-
- container root {
- }
-}
+++ /dev/null
-module foo {
- namespace "foo";
- prefix foo;
- yang-version 1;
-
- import semantic-version { prefix sv; revision-date 2016-02-02; sv:semantic-version "0.0.1"; }
- import bar { prefix bar; revision-date 2016-01-31; sv:semantic-version "0.1.2";}
-
- revision "2016-02-01" {
- description "Initial version";
- }
- sv:semantic-version "0.1.1";
-
- container root {
- }
-}
+++ /dev/null
-module semantic-version {
- namespace "urn:opendaylight:yang:extension:semantic-version";
- prefix sv;
- yang-version 1;
-
- revision 2016-02-02 {
- description "Initial verison";
- }
- sv:semantic-version "0.0.1";
-
- extension semantic-version {
- argument "semantic-version" {
- yin-element false;
- }
- description
- "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.";
- }
-}
+++ /dev/null
-module bar {
- namespace "bar";
- prefix bar;
- yang-version 1;
-
- import semantic-version { prefix sv; revision-date 2016-02-02; sv:semantic-version "0.0.1"; }
-
- revision "2016-01-01" {
- description "Initial version";
- }
- sv:semantic-version "0.1.2";
-
- container root {
- }
-}
+++ /dev/null
-module foo {
- namespace "foo";
- prefix foo;
- yang-version 1;
-
- import semantic-version { prefix sv; revision-date 2016-02-02; sv:semantic-version "0.0.1"; }
- import bar { prefix bar; revision-date 2016-01-31; sv:semantic-version "0.1.2";}
-
- revision "2016-02-01" {
- description "Initial version";
- }
- sv:semantic-version "0.1.1";
-
- container root {
- }
-}
+++ /dev/null
-module semantic-version {
- namespace "urn:opendaylight:yang:extension:semantic-version";
- prefix sv;
- yang-version 1;
-
- revision 2016-02-02 {
- description "Initial verison";
- }
- sv:semantic-version "0.0.1";
-
- extension semantic-version {
- argument "semantic-version" {
- yin-element false;
- }
- description
- "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.";
- }
-}
+++ /dev/null
-module semantic-version {
- namespace "urn:opendaylight:yang:extension:semantic-version";
- prefix sv;
- yang-version 1;
-
- revision 2016-02-02 {
- description "Initial verison";
- }
- sv:semantic-version "2.0.0";
-
- extension semantic-version {
- argument "semantic-version" {
- yin-element false;
- }
- description
- "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.";
- }
-}
+++ /dev/null
-module semantic-version {
- namespace "urn:opendaylight:yang:extension:semantic-version";
- prefix sv;
- yang-version 1;
-
- revision 2016-02-02 {
- description "Initial verison";
- }
- sv:semantic-version "1.0.0";
-
- extension semantic-version {
- argument "semantic-version" {
- yin-element false;
- }
- description
- "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.";
- }
-}
+++ /dev/null
-module semantic-version {
- namespace "urn:opendaylight:yang:extension:semantic-version";
- prefix sv;
- yang-version 1;
-
- revision 2016-02-02 {
- description "Initial verison";
- }
- sv:semantic-version "1.0.0";
-
- extension semantic-version {
- argument "semantic-version" {
- yin-element false;
- }
- description
- "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.";
- }
-}
+++ /dev/null
-module semantic-version {
- namespace "urn:opendaylight:yang:extension:semantic-version";
- prefix sv;
- yang-version 1;
-
- revision 2016-02-02 {
- description "Initial verison";
- }
- sv:semantic-version "2.0.0";
-
- extension semantic-version {
- argument "semantic-version" {
- yin-element false;
- }
- description
- "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.";
- }
-}
+++ /dev/null
-module foo {
- namespace "foo";
- prefix foo;
- yang-version 1;
-
- import semantic-version { prefix sv; revision-date 2016-02-02; sv:semantic-version "1.0.0"; }
-
- revision "2016-02-01" {
- description "Initial version";
- }
-
- container root {
- }
-}
+++ /dev/null
-module semantic-version {
- namespace "urn:opendaylight:yang:extension:semantic-version";
- prefix sv;
- yang-version 1;
-
- revision 2016-02-02 {
- description "Initial verison";
- }
- sv:semantic-version "1.0.0";
-
- extension semantic-version {
- argument "semantic-version" {
- yin-element false;
- }
- description
- "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.";
- }
-}
+++ /dev/null
-module bar {
- namespace "bar";
- prefix bar;
- yang-version 1;
-
- import semantic-version { prefix sv; revision-date 2016-02-02; sv:semantic-version "0.0.1"; }
-
- revision "2016-01-01" {
- description "Initial version";
- }
- sv:semantic-version "0.1.1";
-
- container root {
- }
-}
+++ /dev/null
-module bar {
- namespace "bar";
- prefix bar;
- yang-version 1;
-
- import semantic-version { prefix sv; revision-date 2016-02-02; sv:semantic-version "0.0.1"; }
-
- revision "2016-01-02" {
- description "Initial version";
- }
- sv:semantic-version "0.1.2";
-
- container root {
- }
-}
+++ /dev/null
-module bar {
- namespace "bar";
- prefix bar;
- yang-version 1;
-
- import semantic-version { prefix sv; revision-date 2016-02-02; sv:semantic-version "0.0.1"; }
-
- revision "2016-01-03" {
- description "Initial version";
- }
- sv:semantic-version "0.1.3";
-
- container root {
- }
-}
+++ /dev/null
-module foo {
- namespace "foo";
- prefix foo;
- yang-version 1;
-
- import semantic-version { prefix sv; revision-date 2016-02-02; sv:semantic-version "0.0.1"; }
- import bar { prefix bar; sv:semantic-version "0.1.2";}
-
- revision "2016-02-01" {
- description "Initial version";
- }
- sv:semantic-version "0.1.1";
-
- container root {
- }
-}
+++ /dev/null
-module semantic-version {
- namespace "urn:opendaylight:yang:extension:semantic-version";
- prefix sv;
- yang-version 1;
-
- revision 2016-02-02 {
- description "Initial verison";
- }
- sv:semantic-version "0.0.1";
-
- extension semantic-version {
- argument "semantic-version" {
- yin-element false;
- }
- description
- "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.";
- }
-}
+++ /dev/null
-module bar {
- namespace "bar";
- prefix bar;
- yang-version 1;
-
- import semantic-version { prefix sv; revision-date 2016-02-02; sv:semantic-version "0.0.1"; }
-
- revision "2016-01-01" {
- description "Initial version";
- }
- sv:semantic-version "2.1.1";
-
- container root {
- }
-}
+++ /dev/null
-module bar {
- namespace "bar";
- prefix bar;
- yang-version 1;
-
- import semantic-version { prefix sv; revision-date 2016-02-02; sv:semantic-version "0.0.1"; }
-
- revision "2016-01-02" {
- description "Initial version";
- }
- sv:semantic-version "2.1.2";
-
- container root {
- }
-}
+++ /dev/null
-module foo {
- namespace "foo";
- prefix foo;
- yang-version 1;
-
- import semantic-version { prefix sv; revision-date 2016-02-02; sv:semantic-version "0.0.1"; }
- import bar { prefix bar; revision-date 2016-01-31; sv:semantic-version "1.0.0"; }
-
- revision "2016-02-01" {
- description "Initial version";
- }
- sv:semantic-version "0.1.1";
-
- container root {
- }
-}
+++ /dev/null
-module semantic-version {
- namespace "urn:opendaylight:yang:extension:semantic-version";
- prefix sv;
- yang-version 1;
-
- revision 2016-02-02 {
- description "Initial verison";
- }
- sv:semantic-version "0.0.1";
-
- extension semantic-version {
- argument "semantic-version" {
- yin-element false;
- }
- description
- "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.";
- }
-}
+++ /dev/null
-module bar {
- namespace "bar";
- prefix bar;
- yang-version 1;
-
- import semantic-version { prefix sv; revision-date 2016-02-02; sv:semantic-version "0.0.1"; }
-
- revision "2016-01-01" {
- description "Initial version";
- }
- sv:semantic-version "2.0.0";
-
- container root {
- }
-}
+++ /dev/null
-module bar {
- namespace "bar";
- prefix bar;
- yang-version 1;
-
- import semantic-version { prefix sv; revision-date 2016-02-02; sv:semantic-version "0.0.1"; }
-
- revision "2016-01-02" {
- description "Initial version";
- }
- sv:semantic-version "2.1.0";
-
- container root {
- }
-}
+++ /dev/null
-module foo {
- namespace "foo";
- prefix foo;
- yang-version 1;
-
- import semantic-version { prefix sv; revision-date 2016-02-02; sv:semantic-version "0.0.1"; }
- import bar { prefix bar; sv:semantic-version "2.5.5"; }
-
- revision "2016-02-01" {
- description "Initial version";
- }
- sv:semantic-version "0.1.1";
-
- container root {
- }
-}
+++ /dev/null
-module semantic-version {
- namespace "urn:opendaylight:yang:extension:semantic-version";
- prefix sv;
- yang-version 1;
-
- revision 2016-02-02 {
- description "Initial verison";
- }
- sv:semantic-version "0.0.1";
-
- extension semantic-version {
- argument "semantic-version" {
- yin-element false;
- }
- description
- "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.";
- }
-}
+++ /dev/null
-module bar {
- namespace "bar";
- prefix bar;
- yang-version 1;
-
- import semantic-version { prefix sv; revision-date 2016-02-02; sv:semantic-version "0.0.1"; }
-
- revision "2016-01-01" {
- description "Initial version";
- }
- sv:semantic-version "0.0.1";
-
- container root {
- }
-}
+++ /dev/null
-module bar {
- namespace "bar";
- prefix bar;
- yang-version 1;
-
- import semantic-version { prefix sv; revision-date 2016-02-02; sv:semantic-version "0.0.1"; }
-
- revision "2016-01-02" {
- description "Initial version";
- }
- sv:semantic-version "0.1.0";
-
- container root {
- }
-}
+++ /dev/null
-module semantic-version {
- namespace "urn:opendaylight:yang:extension:semantic-version";
- prefix sv;
- yang-version 1;
-
- revision 2016-02-02 {
- description "Initial verison";
- }
- sv:semantic-version "0.0.1";
-
- extension semantic-version {
- argument "semantic-version" {
- yin-element false;
- }
- description
- "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.";
- }
-}
+++ /dev/null
-module bar {
- namespace "bar";
- prefix bar;
- yang-version 1;
-
- import semantic-version { prefix sv; revision-date 2016-02-02; sv:semantic-version "0.0.1"; }
-
- revision "2016-01-01" {
- description "Initial version";
- }
- sv:semantic-version "4.4.0";
-
- container root {
- }
-}
+++ /dev/null
-module bar {
- namespace "bar";
- prefix bar;
- yang-version 1;
-
- import semantic-version { prefix sv; revision-date 2016-02-02; sv:semantic-version "0.0.1"; }
-
- revision "2016-01-02" {
- description "Initial version";
- }
- sv:semantic-version "5.5.0";
-
- container root {
- }
-}
+++ /dev/null
-module foo {
- namespace "foo";
- prefix foo;
- yang-version 1;
-
- import semantic-version { prefix sv; revision-date 2016-02-02; sv:semantic-version "0.0.1"; }
- import bar { prefix bar; sv:semantic-version "5.5.5"; }
-
- revision "2016-02-01" {
- description "Initial version";
- }
- sv:semantic-version "0.1.1";
-
- container root {
- }
-}
+++ /dev/null
-module semantic-version {
- namespace "urn:opendaylight:yang:extension:semantic-version";
- prefix sv;
- yang-version 1;
-
- revision 2016-02-02 {
- description "Initial verison";
- }
- sv:semantic-version "0.0.1";
-
- extension semantic-version {
- argument "semantic-version" {
- yin-element false;
- }
- description
- "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.";
- }
-}
+++ /dev/null
-module foo {
- namespace "foo";
- prefix foo;
- yang-version 1;
-
- import semantic-version { prefix sv; revision-date 2016-02-02; sv:semantic-version "0.0.1"; }
- import bar { prefix bar; revision-date 2017-04-06; sv:semantic-version "2016.4.5"; }
-
- revision 2016-01-01 {
- description "test";
- }
-
- sv:semantic-version "2016.1.1";
-
- container foo-root {
- uses bar:grp;
- }
-}
+++ /dev/null
-module semantic-version {
- namespace "urn:opendaylight:yang:extension:semantic-version";
- prefix sv;
- yang-version 1;
-
- revision 2016-02-02 {
- description "Initial verison";
- }
- sv:semantic-version "0.0.1";
-
- extension semantic-version {
- argument "semantic-version" {
- yin-element false;
- }
- description
- "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.";
- }
-}
+++ /dev/null
-module foo {
- sv:semantic-version "0.1.1";
- import bar { prefix bar; revision-date 2016-01-31; sv:semantic-version "0.1.2";}
-
- namespace "foo";
- prefix foo;
- yang-version 1;
-
- import semantic-version { prefix sv; revision-date 2016-02-02; sv:semantic-version "0.0.1"; }
-
- revision "2016-02-01" {
- description "Initial version";
- }
-
- container root {
- }
-}
+++ /dev/null
-module bar {
- namespace "bar";
- prefix bar;
- yang-version 1;
-
- import semantic-version { prefix sv; revision-date 2016-02-02; sv:semantic-version "0.0.1"; }
-
- revision "2016-01-31" {
- description "Initial version";
- }
- sv:semantic-version "0.1.2";
-
- container root {
- }
-}
+++ /dev/null
-module foo {
- namespace "foo";
- prefix foo;
- yang-version 1;
-
- import semantic-version { prefix sv; revision-date 2016-02-02; sv:semantic-version "0.0.1"; }
- import bar { prefix bar; revision-date 2016-01-31; sv:semantic-version "0.1.2";}
-
- revision "2016-02-01" {
- description "Initial version";
- }
- sv:semantic-version "0.1.1";
-
- container root {
- }
-}
+++ /dev/null
-module semantic-version {
- namespace "urn:opendaylight:yang:extension:semantic-version";
- prefix sv;
- yang-version 1;
-
- revision 2016-02-02 {
- description "Initial verison";
- }
- sv:semantic-version "0.0.1";
-
- extension semantic-version {
- argument "semantic-version" {
- yin-element false;
- }
- description
- "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.";
- }
-}
+++ /dev/null
-module foo {
- namespace "foo";
- prefix foo;
- yang-version 1;
-
- import semantic-version { prefix sv; revision-date 2016-02-02; sv:semantic-version "0.0.1"; }
-
- revision "2016-02-01" {
- description "Initial version";
- }
-
- container root {
- }
-
- sv:semantic-version "0.1.1";
- import bar { prefix bar; revision-date 2016-01-31; sv:semantic-version "0.1.2";}
-}
+++ /dev/null
-module bar {
- namespace "bar";
- prefix bar;
- yang-version 1;
-
- import semantic-version { prefix sv; revision-date 2016-02-02; sv:semantic-version "0.0.1"; }
-
- revision "2016-01-01" {
- description "Initial version";
- }
- sv:semantic-version "0.1.2";
-
- container root {
- }
-}
+++ /dev/null
-module foo {
- namespace "foo";
- prefix foo;
- yang-version 1;
-
- import semantic-version { prefix sv; revision-date 2016-02-02; sv:semantic-version "0.0.1"; }
- import bar { prefix bar; revision-date 2016-01-31; sv:semantic-version "0.1.2";}
-
- revision "2016-02-01" {
- description "Initial version";
- }
- sv:semantic-version "0.1.1";
-
- container root {
- }
-}
+++ /dev/null
-module semantic-version {
- namespace "urn:opendaylight:yang:extension:semantic-version";
- prefix sv;
- yang-version 1;
-
- revision 2016-02-02 {
- description "Initial verison";
- }
- sv:semantic-version "0.0.1";
-
- extension semantic-version {
- argument "semantic-version" {
- yin-element false;
- }
- description
- "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.";
- }
-}
+++ /dev/null
-module bar {
- namespace "bar";
- prefix bar;
- yang-version 1;
-
- import semantic-version { prefix sv; revision-date 2016-02-02; sv:semantic-version "0.0.1"; }
-
- revision "2016-01-01" {
- description "Initial version";
- }
- sv:semantic-version "0.1.2";
-
- container root {
- }
-}
+++ /dev/null
-module foo {
- namespace "foo";
- prefix foo;
- yang-version 1;
-
- import semantic-version { prefix sv; revision-date 2016-02-02; sv:semantic-version "0.0.1"; }
- import bar { prefix bar; revision-date 2016-01-01; sv:semantic-version "0.1.2";}
-
- revision "2016-02-01" {
- description "Initial version";
- }
- sv:semantic-version "0.1.1";
-
- container root {
- }
-}
+++ /dev/null
-module semantic-version {
- namespace "urn:opendaylight:yang:extension:semantic-version";
- prefix sv;
- yang-version 1;
-
- revision 2016-02-02 {
- description "Initial verison";
- }
- sv:semantic-version "0.0.1";
-
- extension semantic-version {
- argument "semantic-version" {
- yin-element false;
- }
- description
- "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.";
- }
-}
+++ /dev/null
-<?xml version="1.0" encoding="UTF-8"?>
-<module xmlns="urn:ietf:params:xml:ns:yang:yin:1" xmlns:sv="urn:opendaylight:yang:extension:semantic-version"
- name="semantic-version">
- <yang-version value="1"></yang-version>
- <namespace uri="urn:opendaylight:yang:extension:semantic-version"></namespace>
- <prefix value="sv"></prefix>
- <organization>
- <text></text>
- </organization>
- <contact>
- <text></text>
- </contact>
- <revision date="2016-02-02"></revision>
- <sv:semantic-version semantic-version="0.0.1"></sv:semantic-version>
- <extension name="semantic-version">
- <argument name="semantic-version">
- <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>
-</module>
\ No newline at end of file
+++ /dev/null
-<?xml version="1.0" encoding="UTF-8"?>
-<module xmlns="urn:ietf:params:xml:ns:yang:yin:1" xmlns:sv="urn:opendaylight:yang:extension:semantic-version"
- name="semantic-version">
- <yang-version value="1"></yang-version>
- <namespace uri="urn:opendaylight:yang:extension:semantic-version"></namespace>
- <prefix value="sv"></prefix>
- <organization>
- <text></text>
- </organization>
- <contact>
- <text></text>
- </contact>
- <revision date="2016-02-02"></revision>
- <sv:semantic-version semantic-version="0.0.1"></sv:semantic-version>
- <extension name="semantic-version">
- <argument name="semantic-version">
- <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>
-</module>
\ No newline at end of file
+++ /dev/null
-<?xml version="1.0" encoding="UTF-8"?>
-<module xmlns="urn:ietf:params:xml:ns:yang:yin:1" xmlns:sv="urn:opendaylight:yang:extension:semantic-version"
- name="semantic-version">
- <yang-version value="1"></yang-version>
- <namespace uri="urn:opendaylight:yang:extension:semantic-version"></namespace>
- <prefix value="sv"></prefix>
- <organization>
- <text></text>
- </organization>
- <contact>
- <text></text>
- </contact>
- <revision date="2016-02-02"></revision>
- <sv:semantic-version semantic-version="0.0.1"></sv:semantic-version>
- <extension name="semantic-version">
- <argument name="semantic-version">
- <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>
-</module>
\ No newline at end of file
Code Review / yangtools.git / commitdiff