ietf-yang-instance-data@2022-01-20.yang		ietf-yang-instance-data-formatted@2022-01-20.yang
	skipping to change at line 87 ¶		skipping to change at line 86 ¶
	type string {		type string {
	pattern '[a-zA-Z_][a-zA-Z0-9\-_.]*'		pattern '[a-zA-Z_][a-zA-Z0-9\-_.]*'
	+ '(@\d{4}-(1[0-2]|0[1-9])-(0[1-9]|[1|2][0-9]|3[0-1]))?';		+ '(@\d{4}-(1[0-2]|0[1-9])-(0[1-9]|[1|2][0-9]|3[0-1]))?';
	pattern '.|..|[^xX].*|.[^mM].*|..[^lL].*';		pattern '.|..|[^xX].*|.[^mM].*|..[^lL].*';
	}		}
	description		description
	"A type defining a module name and an optional revision		"A type defining a module name and an optional revision
	date, e.g., ietf-yang-library@2019-01-04.";		date, e.g., ietf-yang-library@2019-01-04.";
	}		}
	sx:structure "instance-data-set" {		sx:structure instance-data-set {
	description		description
	"A data structure to define a format for YANG instance		"A data structure to define a format for YANG instance
	data. The majority of the YANG nodes provides metadata		data. The majority of the YANG nodes provides metadata
	about the instance data; the instance data itself is		about the instance data; the instance data itself is
	contained only in the 'content-data' node.";		contained only in the 'content-data' node.";
	leaf name {		leaf name {
	type string;		type string;
	description		description
	"An arbitrary name for the YANG instance data set. This		"An arbitrary name for the YANG instance data set. This
	value is primarily used for descriptive purposes. However,		value is primarily used for descriptive purposes. However,
	skipping to change at line 101 ¶		skipping to change at line 100 ¶
	about the instance data; the instance data itself is		about the instance data; the instance data itself is
	contained only in the 'content-data' node.";		contained only in the 'content-data' node.";
	leaf name {		leaf name {
	type string;		type string;
	description		description
	"An arbitrary name for the YANG instance data set. This		"An arbitrary name for the YANG instance data set. This
	value is primarily used for descriptive purposes. However,		value is primarily used for descriptive purposes. However,
	when the instance data set is saved to a file, then the		when the instance data set is saved to a file, then the
	filename MUST encode the name's value per Section 2		filename MUST encode the name's value per Section 2
	of RFC 9195.";		of RFC 9195.";
	}		}
	leaf format-version {		leaf format-version {
	type string {		type string {
	pattern '\d{4}-(1[0-2]|0[1-9])-(0[1-9]|[1|2][0-9]|3[0-1])';		pattern '\d{4}-(1[0-2]|0[1-9])-(0[1-9]|[1|2][0-9]|3[0-1])';
	}		}
	default "2021-09-16";		default "2021-09-16";
	description		description
	"The 'revision' of the 'ietf-yang-instance-data' module		"The 'revision' of the 'ietf-yang-instance-data' module
	used to encode this 'instance-data-set'.";		used to encode this 'instance-data-set'.";
	}		}
	leaf includes-defaults {		leaf includes-defaults {
	type ncwd:with-defaults-mode;		type ncwd:with-defaults-mode;
	default report-all;		default "report-all";
	description		description
	"Indicates how data nodes with default values are		"Indicates how data nodes with default values are
	represented for all data nodes contained in the		represented for all data nodes contained in the
	instance-data-set.		instance-data-set.
	It uses the same definitions as per Section 3 of RFC 6243		It uses the same definitions as per Section 3 of RFC 6243
	but applied in the context of an instance data file rather		but applied in the context of an instance data file rather
	than a NETCONF request using the <with-defaults>		than a NETCONF request using the <with-defaults>
	parameter.		parameter.
	For JSON files, the encoding of the 'report-all-tagged'		For JSON files, the encoding of the 'report-all-tagged'
	option is as defined in Section 4.8.9 of RFC 8040.";		option is as defined in Section 4.8.9 of RFC 8040.";
	reference "RFC 6243: With-defaults Capability for NETCONF";		reference
			"RFC 6243: With-defaults Capability for NETCONF";
	}		}
	container content-schema {		container content-schema {
	description		description
	"The content schema (i.e., YANG modules) used to create		"The content schema (i.e., YANG modules) used to create
	the instance data set.		the instance data set.
	If not present, the user needs to obtain the information		If not present, the user needs to obtain the information
	through external documents.";		through external documents.";
	choice content-schema-spec {		choice content-schema-spec {
	description		description
	"Specification of the content-schema.";		"Specification of the content-schema.";
End of changes. 6 change blocks.
	12 lines changed or deleted		12 lines changed or added
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/