From 486e1cddf7553ed1b445e84cb7c68916846a4bca Mon Sep 17 00:00:00 2001 From: Robert Varga Date: Mon, 19 Apr 2021 20:33:24 +0200 Subject: [PATCH 1/1] Push out NormalizedNode fixmes We do not have the runway to deal with the modeling changes required here. Push them out to the next major release. Change-Id: I9ed9ef3aaf2280089b90f1092836ae93e32e7a7c Signed-off-by: Robert Varga --- .../yangtools/yang/data/api/schema/NormalizedNode.java | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/yang/yang-data-api/src/main/java/org/opendaylight/yangtools/yang/data/api/schema/NormalizedNode.java b/yang/yang-data-api/src/main/java/org/opendaylight/yangtools/yang/data/api/schema/NormalizedNode.java index df94761c70..e9c03d49d4 100644 --- a/yang/yang-data-api/src/main/java/org/opendaylight/yangtools/yang/data/api/schema/NormalizedNode.java +++ b/yang/yang-data-api/src/main/java/org/opendaylight/yangtools/yang/data/api/schema/NormalizedNode.java @@ -20,7 +20,7 @@ import org.opendaylight.yangtools.yang.data.api.YangInstanceIdentifier.PathArgum * See subinterfaces of this interface for concretization of node. */ /* - * FIXME: 7.0.0: NormalizedNode represents the perfectly-compliant view of the data, as evaluated by an implementation, + * FIXME: 8.0.0: NormalizedNode represents the perfectly-compliant view of the data, as evaluated by an implementation, * which is currently singular, with respect of its interpretation of a SchemaContext. This includes * leaf values, which are required to hold normalized representation for a particular implementation, * which may be affected by its understanding of any YANG extensions present -- such as optional type @@ -35,12 +35,12 @@ import org.opendaylight.yangtools.yang.data.api.YangInstanceIdentifier.PathArgum * to check/fixup if it wishes to use it as a NormalizedNode. Such a concept should be called * "UnverifiedData". * - * FIXME: 7.0.0: Once we have UnverifiedData, we should really rename this to "NormalizedData" or similar to unload + * FIXME: 8.0.0: Once we have UnverifiedData, we should really rename this to "NormalizedData" or similar to unload * some "Node" ambiguity. "Node" should be a generic term reserved for a particular domain -- hence 'node' * can be used to refer to either a 'schema node' in context of yang.model.api, or to * a 'normalized data node' in context of yang.data.api. * - * FIXME: 7.0.0: Well, not quite. The structure of unverified data is really codec specific -- and JSON and XML + * FIXME: 8.0.0: Well, not quite. The structure of unverified data is really codec specific -- and JSON and XML * do not agree on details. Furthermore things get way more complicated when we have a cross-schema * boundary -- like RFC8528. Hence we cannot really have a reasonably-structured concept of unverified * data. Nevertheless, this interface should be named 'NormalizedData'. -- 2.36.6