rfc9569v2.txt		rfc9569.txt
	skipping to change at line 526 ¶		skipping to change at line 526 ¶
	items, the ID of each added node in the updates graph must increment		items, the ID of each added node in the updates graph must increment
	contiguously by 1. More specifically, the updates graph MUST satisfy		contiguously by 1. More specifically, the updates graph MUST satisfy
	the following invariants:		the following invariants:
	Continuity: At any time, let ns denote the smallest non-zero version		Continuity: At any time, let ns denote the smallest non-zero version
	(i.e., <start-seq>) in the updates graph and let ne denote the		(i.e., <start-seq>) in the updates graph and let ne denote the
	latest version (i.e., <end-seq>). Then, any version in between ns		latest version (i.e., <end-seq>). Then, any version in between ns
	and ne MUST also exist. This implies that the incremental update		and ne MUST also exist. This implies that the incremental update
	from ni to ni + 1 exists for any ns <= ni <= ne, and all the		from ni to ni + 1 exists for any ns <= ni <= ne, and all the
	version numbers in the updates graph (except 0) constitute exactly		version numbers in the updates graph (except 0) constitute exactly
	the integer interval [ns, ne]..		the integer interval [ns, ne].
	Feasibility: Let ns denote <start-seq> in the updates graph. The		Feasibility: Let ns denote <start-seq> in the updates graph. The
	server MUST provide a snapshot of ns; in other words, there is		server MUST provide a snapshot of ns; in other words, there is
	always a direct link to ns in the updates graph.		always a direct link to ns in the updates graph.
	"Right shift" only: Assume a server provides versions in [n1, n2] at		"Right shift" only: Assume a server provides versions in [n1, n2] at
	time t and versions in [n1', n2'] at time t'. If t' > t, then n1'		time t and versions in [n1', n2'] at time t'. If t' > t, then n1'
	>= n1 and n2' >= n2.		>= n1 and n2' >= n2.
	For example, consider the case that a server compacts a resource's		For example, consider the case that a server compacts a resource's
	skipping to change at line 694 ¶		skipping to change at line 694 ¶
	object {		object {
	IncrementalUpdateMediaTypes incremental-change-media-types;		IncrementalUpdateMediaTypes incremental-change-media-types;
	} TIPSCapabilities;		} TIPSCapabilities;
	object-map {		object-map {
	ResourceID -> String;		ResourceID -> String;
	} IncrementalUpdateMediaTypes;		} IncrementalUpdateMediaTypes;
	Figure 5: TIPSCapabilities		Figure 5: TIPSCapabilities
	With the field:		with the field:
	incremental-change-media-types: If a TIPS information resource can		incremental-change-media-types: If a TIPS information resource can
	provide updates with incremental changes for a resource, the		provide updates with incremental changes for a resource, the
	"incremental-change-media-types" field has an entry whose key is		"incremental-change-media-types" field has an entry whose key is
	the ID of the resource and the value is the supported media types		the ID of the resource and the value is the supported media types
	of incremental changes, separated by commas. For the		of incremental changes, separated by commas. For the
	implementation of this specification, this MUST be "application/		implementation of this specification, this MUST be "application/
	merge-patch+json", "application/json-patch+json", or "application/		merge-patch+json", "application/json-patch+json", or "application/
	merge-patch+json,application/json-patch+json", unless defined by a		merge-patch+json,application/json-patch+json", unless defined by a
	future extension.		future extension.
	skipping to change at line 864 ¶		skipping to change at line 864 ¶
	of the TIPSReq type, where:		of the TIPSReq type, where:
	object {		object {
	ResourceID resource-id;		ResourceID resource-id;
	[JSONString tag;]		[JSONString tag;]
	[Object input;]		[Object input;]
	} TIPSReq;		} TIPSReq;
	Figure 7: TIPSReq		Figure 7: TIPSReq
	With the following fields:		with the following fields:
	resource-id: This field contains the resource ID of an ALTO resource		resource-id: This field contains the resource ID of an ALTO resource
	to be monitored, which MUST be in the TIPS information resource's		to be monitored, which MUST be in the TIPS information resource's
	"uses" list (Section 5). If a client does not support all		"uses" list (Section 5). If a client does not support all
	incremental methods from the set announced in the server's		incremental methods from the set announced in the server's
	capabilities, the client MUST NOT use the TIPS information		capabilities, the client MUST NOT use the TIPS information
	resource.		resource.
	tag: If the "resource-id" is associated with a GET-mode resource		tag: If the "resource-id" is associated with a GET-mode resource
	with a version tag (or "vtag"), as defined in Section 10.3 of		with a version tag (or "vtag"), as defined in Section 10.3 of
	skipping to change at line 915 ¶		skipping to change at line 915 ¶
	StartEdgeRec start-edge-rec;		StartEdgeRec start-edge-rec;
	} UpdatesGraphSummary;		} UpdatesGraphSummary;
	object {		object {
	JSONNumber seq-i;		JSONNumber seq-i;
	JSONNumber seq-j;		JSONNumber seq-j;
	} StartEdgeRec;		} StartEdgeRec;
	Figure 8: AddTIPSResponse		Figure 8: AddTIPSResponse
	With the following fields:		with the following fields:
	tips-view-uri: This is the URI to the requested TIPS view. The		tips-view-uri: This is the URI to the requested TIPS view. The
	value of this field MUST have the following format:		value of this field MUST have the following format:
	scheme "://" tips-view-host "/" tips-view-path		scheme "://" tips-view-host "/" tips-view-path
	tips-view-host = host [ ":" port]		tips-view-host = host [ ":" port]
	tips-view-path = path		tips-view-path = path
	Where scheme MUST be "http" or "https" unless specified by a		Where scheme MUST be "http" or "https" unless specified by a
End of changes. 4 change blocks.
	4 lines changed or deleted		4 lines changed or added
This html diff was produced by rfcdiff 1.48.