* @param <T> Identifier class, must conform to API contract outlined by {@link Identifier}, even if it does not
* implement it.
*/
-// FIXME: 4.0.0: consider requiring "T extends Serializable"
+// FIXME: 5.0.0: consider requiring "T extends Serializable"
public interface Identifiable<T> {
/**
* Return this objects Identifier.
* @author Robert Varga
*/
@Beta
-// FIXME: 4.0.0: evaluate if we still need to extend SchemaContext here
+// FIXME: 5.0.0: evaluate if we still need to extend SchemaContext here
public interface EffectiveModelContext extends SchemaContext {
Map<QNameModule, ModuleEffectiveStatement> getModuleStatements();
* <p>
* The import statement makes definitions from one module available inside another module or submodule.
*/
-// FIXME: 3.0.0 this class is a leak of the declared world into the effective one. In effective world, all nodes form
+// FIXME: 5.0.0 this class is a leak of the declared world into the effective one. In effective world, all nodes form
// a tree, which consists of multiple (mostly) QName-navigated namespaces. As such module imports contribute
// only a prefix/QNameModule mapping to the effective world and hence should be mapped that way:
// - Module exposes String->QNameModule mapping
* Instances MUST be immutable and thus usage in multi threaded
* environment is safe.
*/
-// FIXME: 3.0.0: ContainerSchemaNode is far too broad. A combination of DataNodeContainer, NotificationNodeContainer
+// FIXME: 5.0.0: ContainerSchemaNode is far too broad. A combination of DataNodeContainer, NotificationNodeContainer
// and possibly DataSchemaNode would reflect SchemaContext traits better.
-// FIXME: 4.0.0: consider deprecating this class in favor of EffectiveModelContext
+// FIXME: 5.0.0: consider deprecating this class in favor of EffectiveModelContext
public interface SchemaContext extends ContainerSchemaNode, Immutable {
/**
* QName of NETCONF top-level data node.