[netconf] YANG Library 1.1: a deviation module may exist without a module entry?

[Jernej Tuljak <[e-mail]>]

Hi,

is there a particular reason for the deviation leaf-list in 
ietf-yang-library@2019-01-04 not having require-instance true for its 
leafref path, therefore allowing servers to report "incomplete" module 
sets/schemas to the client?

      grouping module-implementation-parameters {
        description
          "Parameters for describing the implementation of a module.";
        leaf-list feature {
          type yang:yang-identifier;
          description
            "List of all YANG feature names from this module that are
             supported by the server, regardless whether they are defined
             in the module or any included submodule.";
        }
        leaf-list deviation {
          type leafref {
            path "../../module/name";
          }

          description
            "List of all YANG deviation modules used by this server to
             modify the conformance of the module associated with this
             entry.  Note that the same module can be used for deviations
             for multiple modules, so the same entry MAY appear within
             multiple 'module' entries.

             This reference MUST NOT (directly or indirectly)
             refer to the module being deviated.

             Robust clients may want to make sure that they handle a
             situation where a module deviates itself (directly or
             indirectly) gracefully.";
        }
      }

Why are deviation modules allowed to exist without a module entry within 
YANG Library instances? Why would a server choose to withhold namespace 
information for a deviation module?

Jernej