rfc9880v5.txt		rfc9880.txt
	skipping to change at line 58 ¶		skipping to change at line 58 ¶
	to this document. Code Components extracted from this document must		to this document. Code Components extracted from this document must
	include Revised BSD License text as described in Section 4.e of the		include Revised BSD License text as described in Section 4.e of the
	Trust Legal Provisions and are provided without warranty as described		Trust Legal Provisions and are provided without warranty as described
	in the Revised BSD License.		in the Revised BSD License.
	Table of Contents		Table of Contents
	1. Introduction		1. Introduction
	1.1. Structure of This Document		1.1. Structure of This Document
	1.2. Terminology and Conventions		1.2. Terminology and Conventions
	Programming Platform Terms		1.2.1. Programming Platform Terms
	Conceptual Terms		1.2.2. Conceptual Terms
	Specification Language Terms		1.2.3. Specification Language Terms
	Conventions		1.2.4. Conventions
	2. Overview		2. Overview
	2.1. Example Definition		2.1. Example Definition
	2.2. Elements of an SDF Model		2.2. Elements of an SDF Model
	2.2.1. sdfObject		2.2.1. sdfObject
	2.2.2. sdfProperty		2.2.2. sdfProperty
	2.2.3. sdfAction		2.2.3. sdfAction
	2.2.4. sdfEvent		2.2.4. sdfEvent
	2.2.5. sdfData		2.2.5. sdfData
	2.2.6. sdfThing		2.2.6. sdfThing
	2.3. Member Names: Given Names and Quality Names		2.3. Member Names: Given Names and Quality Names
	skipping to change at line 192 ¶		skipping to change at line 192 ¶
	composition in SDF. Finally, Appendix E provides some historical		composition in SDF. Finally, Appendix E provides some historical
	information that can be useful in upgrading earlier, pre-standard SDF		information that can be useful in upgrading earlier, pre-standard SDF
	models and implementations to base SDF.		models and implementations to base SDF.
	1.2. Terminology and Conventions		1.2. Terminology and Conventions
	Terms introduced in this section are capitalized when used in this		Terms introduced in this section are capitalized when used in this
	section. To maintain readability, capitalization is only used when		section. To maintain readability, capitalization is only used when
	needed where they are used in the body of this document.		needed where they are used in the body of this document.
	Programming Platform Terms		1.2.1. Programming Platform Terms
	The following definitions mention terms that are used with specific		The following definitions mention terms that are used with specific
	meanings in various programming platforms, but often have an		meanings in various programming platforms, but often have an
	independent definition for this document, which can be found further		independent definition for this document, which can be found further
	below in this section.		below in this section.
	Element: A generic term used here in its English sense.		Element: A generic term used here in its English sense.
	Exceptionally, in Appendix C, the term is used explicitly in		Exceptionally, in Appendix C, the term is used explicitly in
	accordance with its meaning in the JSON ecosystem, i.e., the		accordance with its meaning in the JSON ecosystem, i.e., the
	elements of JSON arrays.		elements of JSON arrays.
	skipping to change at line 229 ¶		skipping to change at line 229 ¶
	Property: Certain environments use the term "property" for a JSON		Property: Certain environments use the term "property" for a JSON
	concept that JSON calls "member" and is called "entry" here, or		concept that JSON calls "member" and is called "entry" here, or
	sometimes just for the map key of these. In this document, the		sometimes just for the map key of these. In this document, the
	term Property is specifically reserved for a certain kind of		term Property is specifically reserved for a certain kind of
	Affordance, even if the map key "properties" is imported with		Affordance, even if the map key "properties" is imported with
	JSON-related semantics from a data definition language.		JSON-related semantics from a data definition language.
	Byte: This document uses the term "byte" in its now-customary sense		Byte: This document uses the term "byte" in its now-customary sense
	as a synonym for "octet".		as a synonym for "octet".
	Conceptual Terms		1.2.2. Conceptual Terms
	Thing: A physical item that is also available for interaction over a		Thing: A physical item that is also available for interaction over a
	network.		network.
	Element: A part or an aspect of something abstract; i.e., the term		Element: A part or an aspect of something abstract; i.e., the term
	is used here in its usual English definition.		is used here in its usual English definition.
	Affordance: An element of an interface offered for interaction.		Affordance: An element of an interface offered for interaction.
	Such an element becomes an Affordance when information is		Such an element becomes an Affordance when information is
	available (directly or indirectly) that indicates how it can or		available (directly or indirectly) that indicates how it can or
	skipping to change at line 256 ¶		skipping to change at line 256 ¶
	Property: An Affordance that can potentially be used to read, write,		Property: An Affordance that can potentially be used to read, write,
	and/or observe state (current/stored information) on a Grouping.		and/or observe state (current/stored information) on a Grouping.
	Action: An Affordance that can potentially be used to perform a		Action: An Affordance that can potentially be used to perform a
	named operation on a Grouping.		named operation on a Grouping.
	Event: An Affordance that can potentially be used to obtain		Event: An Affordance that can potentially be used to obtain
	information about what happened to a Grouping.		information about what happened to a Grouping.
	Specification Language Terms		1.2.3. Specification Language Terms
	SDF Document: Container for SDF Definitions, together with data		SDF Document: Container for SDF Definitions, together with data
	about the SDF Document itself (information block). Represented as		about the SDF Document itself (information block). Represented as
	a JSON text representing a single JSON map, which is built from		a JSON text representing a single JSON map, which is built from
	nested maps.		nested maps.
	SDF Model: Definitions and declarations that model the digital		SDF Model: Definitions and declarations that model the digital
	interaction opportunities offered by one or more kinds of Things,		interaction opportunities offered by one or more kinds of Things,
	represented by Groupings (sdfObjects and sdfThings). An SDF Model		represented by Groupings (sdfObjects and sdfThings). An SDF Model
	can be fully contained in a single SDF Document, or it can be		can be fully contained in a single SDF Document, or it can be
	skipping to change at line 340 ¶		skipping to change at line 340 ¶
	specific Augmentation Mechanisms are defined in base SDF. A		specific Augmentation Mechanisms are defined in base SDF. A
	simple mechanism for such augmentations has been discussed as a		simple mechanism for such augmentations has been discussed as a
	"mapping file" [SDF-MAPPING].		"mapping file" [SDF-MAPPING].
	Protocol Binding: A companion document to an SDF Model that defines		Protocol Binding: A companion document to an SDF Model that defines
	how to map the abstract concepts in the model into the protocols		how to map the abstract concepts in the model into the protocols
	that are in use in a specific ecosystem. The Protocol Binding		that are in use in a specific ecosystem. The Protocol Binding
	might supply URL components, numeric IDs, and similar details.		might supply URL components, numeric IDs, and similar details.
	Protocol Bindings are one case of an Augmentation Mechanism.		Protocol Bindings are one case of an Augmentation Mechanism.
	Conventions		1.2.4. Conventions
	Regular expressions that are used in the text as a "pattern" for some		Regular expressions that are used in the text as a "pattern" for some
	string are interpreted as per [RFC9485]. (Note that a form of		string are interpreted as per [RFC9485]. (Note that a form of
	regular expressions is also used as values of the quality pattern;		regular expressions is also used as values of the quality pattern;
	see Appendix C.2.)		see Appendix C.2.)
	The term "URI" in this document always refers to "full" URIs ("URI"		The term "URI" in this document always refers to "full" URIs ("URI"
	in Section 3 of RFC 3986 [STD66]), never to relative URI references		in Section 3 of RFC 3986 [STD66]), never to relative URI references
	("relative-ref" in Section 4.1 of RFC 3986 [STD66]), so the term		("relative-ref" in Section 4.1 of RFC 3986 [STD66]), so the term
	"URI" does _NOT_ serve as the colloquial abbreviation of "URI-		"URI" does _NOT_ serve as the colloquial abbreviation of "URI-
End of changes. 5 change blocks.
	8 lines changed or deleted		8 lines changed or added
This html diff was produced by rfcdiff 1.48.