3 namespace "urn:opendaylight:yang:extension:yang-ext";
6 contact "Anton Tkacik <ttkacik@cisco.com>";
9 "Copyright (c) 2013 Cisco Systems, Inc. and others. All rights reserved.
11 This program and the accompanying materials are made available under the
12 terms of the Eclipse Public License v1.0 which accompanies this distribution,
13 and is available at http://www.eclipse.org/legal/epl-v10.html";
15 revision "2013-07-09" {
21 extension "augment-identifier" {
23 "YANG language extension which assigns an identifier to
24 augmentation. Augment identifier is used to identify
25 specific augment statement by name.
27 The identifier syntax is defined formally defined by the rule
28 'identifier' in Section 12 of RFC 6020.
30 All augment identifiers defined in a namespace MUST be unique.
31 The namespace of augment identifiers is shared by module and
36 This extension allows for ease of development / debug
37 of YANG modules and it is suitable for code generation,
38 where each augment statement is nicely identified by
39 unique name instead of combination of augment target
42 argument "identifier";
49 "YANG language extension which marks a place where a semantic mount
50 point can be present. This extension can only be used in a container or
51 a list statement, for example:
63 In this example, container foo can contain a local leaf bar and some
64 mounted data. From addressing perspective, the extension use acts as
65 a container with yang-ext's namespace, i.e. it looks as though as this
66 (yang-ext) module contained the following construct:
68 import foo { prefix foo; }
74 From data lifecycle perspective, this container should never be
75 automatically included in the datastore content for 'container foo', unless
76 specifically explicitly requested.";
81 grouping rpc-context-ref {
83 "A reference to RPC context.";
84 leaf context-instance {
85 type instance-identifier;
86 description "Pointer to the context. ";
91 extension "rpc-context-instance" {
93 "YANG language extension which defines enclosing (parent)
94 schema node as referencable context for RPCs.
96 The argument is identity which is used to identify RPC context
99 argument "context-type";
102 extension "context-reference" {
103 argument "context-type";
106 extension "context-instance" {
107 argument "context-type";
110 extension "instance-target" {