[YANGTOOLS-685] [Yang 1.1] Allow notifications to be tied to data nodes Created: 07/Oct/16  Updated: 10/Apr/22  Resolved: 19/Dec/16

Status: Resolved
Project: yangtools
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug
Reporter: Peter Kajsa Assignee: Peter Kajsa
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All


Issue Links:
Blocks
blocks YANGTOOLS-355 Milestone: Introduce support for YANG... Resolved
is blocked by YANGTOOLS-664 Extend yang statement parser to suppo... Resolved
is blocked by YANGTOOLS-699 Milestone: [Yang 1.1] Yang model API ... Resolved
External issue ID: 6897

 Comments   
Comment by Martin Ciglan [ 19/Oct/16 ]

RFC7950:

7.16. The "notification" Statement
The "notification" statement is used to define a notification. It
takes one argument, which is an identifier, followed by a block of
substatements that holds detailed notification information. The
"notification" statement defines a notification node in the schema
tree.
A notification can be defined at the top level of a module, or
connected to a specific container or list data node in the schema
tree.
A notification MUST NOT be defined within an rpc, action, or another
notification, i.e., a notification node MUST NOT have an rpc, action,
or a notification node as one of its ancestors in the schema tree.
For example, this means that it is an error if a grouping that
contains a notification somewhere in its node hierarchy is used in an
rpc definition.
A notification MUST NOT have any ancestor node that is a list node
without a "key" statement.

Comment by Igor Foltin [ 14/Nov/16 ]

API change - https://git.opendaylight.org/gerrit/#/c/48245/

Comment by Peter Kajsa [ 07/Dec/16 ]

https://git.opendaylight.org/gerrit/#/c/48926/8

Generated at Wed Feb 07 20:54:00 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.