rfc9553v5.txt		rfc9553.txt
	skipping to change at line 227 ¶		skipping to change at line 227 ¶
	The xCard [RFC6351] and jCard [RFC7095] specifications define		The xCard [RFC6351] and jCard [RFC7095] specifications define
	alternative representations for vCard data in XML and JSON formats,		alternative representations for vCard data in XML and JSON formats,
	respectively. Both explicitly aim to not change the underlying data		respectively. Both explicitly aim to not change the underlying data
	model. Accordingly, they are regarded as equal to vCard in the		model. Accordingly, they are regarded as equal to vCard in the
	context of this document.		context of this document.
	1.2. Notational Conventions		1.2. Notational Conventions
	The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",		The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
	"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and		"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
	"OPTIONAL" in this document are to be interpreted as described in BCP		"OPTIONAL" in this document are to be interpreted as described in
	14 [RFC2119] [RFC8174] when, and only when, they appear in all		BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all
	capitals, as shown here.		capitals, as shown here.
	The ABNF definitions in this document use the notations of [RFC5234].		The ABNF definitions in this document use the notations of [RFC5234].
	ABNF rules not defined in this document are defined in either		ABNF rules not defined in this document are defined in either
	[RFC5234] (such as the ABNF for CRLF, WSP, DQUOTE, VCHAR, ALPHA, and		[RFC5234] (such as the ABNF for CRLF, WSP, DQUOTE, VCHAR, ALPHA, and
	DIGIT) or [RFC6350].		DIGIT) or [RFC6350].
	1.3. Data Type Notations		1.3. Data Type Notations
	This section introduces the notations and terminology used to define		This section introduces the notations and terminology used to define
	skipping to change at line 1010 ¶		skipping to change at line 1010 ¶
	2.1.8. relatedTo		2.1.8. relatedTo
	relatedTo: String[Relation] (optional). The set of Card objects that		relatedTo: String[Relation] (optional). The set of Card objects that
	relate to the Card. The value is a map, where each key is the uid		relate to the Card. The value is a map, where each key is the uid
	property value of the related Card, and the value defines the		property value of the related Card, and the value defines the
	relation.		relation.
	The Relation object has the following properties:		The Relation object has the following properties:
	@type: String. The JSContact type of the object. The value MUST be		@type: String.
	"Relation", if set.		The JSContact type of the object. The value MUST be "Relation",
			if set.
	relation: String[Boolean] (optional; default: empty Object). The rel		relation: String[Boolean] (optional; default: empty Object).
	ationship of the related Card to the Card, defined as a set of		The relationship of the related Card to the Card, defined as a set
	relation types. The keys in the set define the relation type; the		of relation types. The keys in the set define the relation type;
	values for each key in the set MUST be "true". The relationship		the values for each key in the set MUST be "true". The
	between the two objects is undefined if the set is empty.		relationship between the two objects is undefined if the set is
			empty.
	The initial list of enumerated (Section 1.7.5) relation types		The initial list of enumerated (Section 1.7.5) relation types
	matches the IANA-registered TYPE [IANA-vCard] parameter values of		matches the IANA-registered TYPE [IANA-vCard] parameter values of
	the vCard RELATED property (Section 6.6.6 of [RFC6350]):		the vCard RELATED property (Section 6.6.6 of [RFC6350]):
	* acquaintance		* acquaintance
	* agent		* agent
	* child		* child
End of changes. 3 change blocks.
	9 lines changed or deleted		11 lines changed or added
This html diff was produced by rfcdiff 1.48.