p 22, sec 4.3. YANG Module

[flycoolman]

(10) p 22, sec 4.3. YANG Module
leaf constrained {
type empty;
description
"Indicates that 'where' filters and 'sort-by' parameters
on the targeted 'config false' list node are constrained.
If a list is not 'constrained', then full XPath 1.0
expressions may be used in 'where' filters and all node
identifiers are usable by 'sort-by'.";
}
leaf indexed {
type empty;
description
"Indicates that the targeted descendent node of a
'constrained' list (see the 'constrained' leaf) may be
used in 'where' filters and/or 'sort-by' parameters.
If a descendent node of a 'constrained' list is not
'indexed', then it MUST NOT be used in 'where' filters
or 'sort-by' parameters.";
}
leaf cursor-supported {
type empty;
description
"Indicates that the targeted list node supports the
'cursor' parameter.";
}
}
Rather than the capabilities (like constrained) being type empty, it would
be better if this was a boolean values, which would allow more flexibility
in the definition of hierarchical capabilities, since they would allow a
server to express that a given capability is enabled by default, but
excluded for particular child subtrees, or conversely, that a given
capability is disabled by default, but can be enabled for particular
subtrees, or any combination of the two.
I would suggest that it may be helpful to also allow the 'constrained'
capability on configuration datastores as well.
I think that cursor should always be supported (as per my high level
comment), and instead it should be the offset field that is optional to
support.