1 module odl-test-toplevel {
3 namespace "urn:opendaylight:params:xml:ns:yang:mdsal:binding2:test:toplevel";
7 "Testing for various data structures at top level of module.
8 see http://tools.ietf.org/html/rfc6020#section-7.1.1";
10 revision "2016-03-31" {
12 "Initial revision, for ODL Boron.";
15 // TODO: Create model with other non-data structures, such as rpc and notification.
16 // TODO: Test definitions at top level of submodule.
18 grouping config-leaf {
32 uses state-leaf; // Top level non-config string leaf named "state-leaf".
34 container non-presence-container {
38 container presence-container {
39 presence "Container is present.";
43 leaf-list ordered-leaflist {
48 leaf-list unordered-leaflist {
53 list ordered-keyed-list {
59 list unordered-keyed-list {
65 list ordered-unkeyed-list {
66 config false; // 'The "key" statement, which MUST be present if the list represents configuration'
69 "http://tools.ietf.org/html/rfc6020#section-7.7.5
70 says \"This statement is ignored if the list represents state data\",
71 but we are still hoping for some kind of ordering (perhaps from MD-SAL application?)
76 list unordered-unkeyed-list {
77 config false; // 'The "key" statement, which MUST be present if the list represents configuration'
80 "http://tools.ietf.org/html/rfc6020#section-7.7.5
81 says \"This statement is ignored if the list represents state data\",
82 but we are still hoping the system responds with a reasonable ordering.
84 http://tools.ietf.org/html/rfc6020#section-7.7.5.1
85 \"An implementation SHOULD use the same order for
86 the same data, regardless of how the data were created.\"";