Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://www.rfc-editor.org/rfc/rfc9555.xml below:

• TIME ()
• DATE-TIME ()
• DATE-AND-OR-TIME ()
• DATE type values that only define a month or day (but not both)

• One Patch per Property: For each vCard property with a LANGUAGE parameter, set the complete path in the PatchObject to the JSContact property that the vCard property converts to. The value of the patch is the converted property value. This is simple to process and adequate if the vCard only contains a few properties with the LANGUAGE parameter.
• Bundle Patches by Parent: If a PatchObject contains multiple paths that have the same parent paths, then it might be possible to combine these patches into one patch that patches the parent property. This is possible if the property in the Card is patched in its entirety.

• "beginner" converts to "low";
• "average" converts to "medium"; and
• "expert" converts to "high".

• ANNIVERSARY ()
• BDAY ()
• BIRTHPLACE ()
• DEATHDATE ()
• DEATHPLACE ()

• room
• floor
• apartment
• building

• number
• name
• block
• direction
• landmark
• subdistrict
• district

• The LABEL parameter converts to the Address object's full property.
• The GEO parameter converts to the Address object's coordinates property.
• The TZ parameter converts to the Address object's timeZone property.
• The CC parameter converts to the Address object's countryCode property.

• If the hour offset is zero, use the time zone name "Etc/UTC".
• Otherwise, construct the time zone name with "Etc/GMT" suffixed with the string representation of the reversed sign hour offset, including the sign but excluding leading zeros and minutes. For example, the UTC offset value "-0500" converts to "Etc/GMT+5".

• The GROUP parameter values of the properties match.
• The GROUP parameters are not set, but they are set on any other ADR, GEO, and TZ properties.

vCardProps: JCardProp[] (optional).

Contains vCard properties that are set in the vCard represented by this JSContact object. The JCardProp type denotes a jCard-encoded vCard property as defined in .

Example:

This illustrates how to convert a vCard extension property: JSContact vCardProps Example item1.X-FOO;X-BAR=Hello:World! "vCardProps": [ ["x-foo", { "x-bar": "Hello", "group": "item1" }, "unknown", "World!"] ]

vCardParams: String[String|String[]] (optional).

Contains vCard parameters that are set on the vCard property represented by this JSContact object. The value MUST be a JSON object containing vCard property parameters as defined in . Each entry represents a parameter of the vCard property that converts to the JSContact object.

Example:

This illustrates how to convert a vCard extension parameter: JSContact vCardParams Example EMAIL;X-FOO=Bar:jane_doe@example.com "emails": { "email1": { "address": "jane_doe@example.com", "vCardParams": { "x-foo": "Bar" } } }

vCardName: String (optional).

Contains the name of the vCard element that is represented by this JSContact object. For example, this allows to preserve the name of a vCard property when multiple vCard properties convert the same JSContact type. The case-insensitive value MUST be valid according to the "name" ABNF defined in .

Example:

Both vCard IMPP and SOCIALPROFILE convert to an OnlineService object ( ) in JSContact. The vCardName property value indicates that the vCard source element was IMPP as follows: JSContact vCardName Example IMPP:xmpp:alice@example.com "onlineServices": { "os1": { "uri": "xmpp:alice@example.com", "vCardName": "impp" }, }

• Multivalued JSContact properties convert to separate instances of their equivalent vCard property, and each of the PROP-ID parameters MUST be set to the Id-typed key of the converted value (see ).
• The full property of the name property in JSContact is optional, but the FN property is mandatory in vCard. The following rules apply:
  • If the Name object's full property is set, then implementations MUST use its value for the vCard FN property.
  • If the Name object's full property is not set, then implementations SHOULD derive the full name from the Name object's components property values. If the isOrdered property is "true", then this can be done by concatenating the name component values. Otherwise, or alternatively, an implementation can choose any other heuristic to generate the full name from its components such as . Implementations MUST set the DERIVED parameter on the FN property.
  • Otherwise, the FN property MUST be set to the empty value.
• Vendor-specific and unknown properties convert to vCard as outlined in .

Property name:

JSPROP

Purpose:

Represents a JSContact property in vCard.

Value type:

TEXT; also see "Format definition" below for value restrictions.

Conformance:

Can be specified multiple times in a vCard.

Property parameters:

The JSPTR parameter MUST be set for this property. Other IANA-registered and experimental property parameters can be specified on this property.

Description:

This property converts an arbitrary JSContact property from and to vCard. The vCard property value is the JSON-encoded value of the JSContact property, represented as a TEXT value. The format of the JSON value MUST be compact, e.g., without insignificant whitespace as defined in . The value of the JSPTR parameter points to the JSContact property within the Card. The root of the JSON pointer is always the Card object that this vCard converts to, irrespective if the JSON pointer starts with the SOLIDUS (U+002F) character. The pointer MUST NOT reference into an array. All JSPROP properties in a vCard together form a PatchObject as defined in . The value of its JSPTR parameter corresponds to a key in the PatchObject; the value of the JSPROP property corresponds to the value for that key. When converting from vCard to JSContact, the PatchObject MUST only be applied after all other vCard properties have already been converted. The PatchObject MUST be valid, including the restriction that an invalid PatchObject MUST NOT be applied.

Format definition:

This property is defined by the following notation: jsprop = "JSPROP" jsprop-param ":" TEXT jsprop-param = *( ; The following are REQUIRED and MUST NOT ; occur more than once ( ";" jsptr-param ) / ; see next section ( ";" "VALUE" "=" "TEXT") ; ; The following is OPTIONAL ; and MAY occur more than once. ; (";" other-param) ; )

Example(s):

This illustrates how to convert a property at the top level in a Card object that is unknown to the implementation. Unknown Property Example "someUnknownProperty": true JSPROP;JSPTR="someUnknownProperty":true This illustrates how to convert a vendor-specific property at the top level of a Card object. Note the required use of quoted string for the JSPTR value, which allows the path to include the COLON (U+003A) character. Vendor-Specific Property Conversion Example "example.com:foo": { "bar": 1234 } JSPROP;JSPTR="example.com:foo":{"bar":1234} This illustrates how to convert a vendor-specific property at a nested level in a Card object using a path relative to the Card object. Although not recommended, the property name includes the SOLIDUS (U+002F) character, which requires escaping in the JSON pointer. Nested Vendor-Specific Property Example with a Path Relative to Card "phones": { "phone1": { "number": "tel:+33-01-23-45-67", "example.com:foo/bar": "tux hux" } } TEL:tel:+33-01-23-45-67 JSPROP;JSPTR="phones/phone1/example.com:foo~1bar": "tux hux"

Parameter name:

JSCOMPS

Purpose:

Defines the order and separators for the elements of a structured property value.

Description:

The JSCOMPS parameter value facilitates converting name and address components between JSContact and vCard. It preserves the order of the components of the JSContact property and contains the verbatim values of separator components. If this parameter is set and its value is valid (see later), then implementations MUST set the isOrdered property of the Name or Address object to "true". Otherwise, they MUST set the isOrdered property value to "false". The JSCOMPS parameter value is a structured type value. Its value MUST be quoted. The parameter value consists of a sequence of entries, separated by the SEMICOLON character (U+003B). The first entry defines the value of the defaultSeparator property. If it is the empty string, then no default separator is defined. Otherwise, the first entry MUST be a separator entry. All following entries processed in order result in an ordered list of JSContact components and MUST be one of the following two kinds:

1. A positional. This refers to a component value in the vCard structured value. A position consists of the numeric index of a component in the structured value, optionally followed by a COMMA (U+002C) character and the non-zero index of a value within that component. The zero index selects the first component or value, respectively. The second index is zero by default, in which case it MUST be omitted (as well as the leading COMMA). The resulting JSContact component is formed by determining its kind by the position in the vCard structured value. The component value is the verbatim value of the vCard component. Figures and illustrate this by example.
2. A separator. This contains the verbatim value of a separator component. It starts with the LATIN SMALL LETTER S (U+0073) character, followed by the COMMA (U+002C) character, followed by zero or more "param-value" characters (see ), where the COMMA (U+002C) and SEMICOLON (U+003B) characters MUST be escaped according to the rules defined in . illustrates this by example. The resulting JSContact component is formed by setting its kind to "separator" and its value to the verbatim value of the entry.

A JSCOMPS parameter value is valid if and only if:

• All indexes in the positional entries refer to an existing component value in the vCard property value.
• The count of positional entries equals the count of deduplicated component values. Deduplication is required because some values may occur in both their designated and backwards-compatible components in the vCard property value:
  • A value that occurs in both the N property secondary surname component and the family name component only counts once.
  • A value that occurs in both the N property generation component and the honorific suffix component only counts once.
  • A value in the ADR property street address component does not count if the ADR property value contains a value in one of the new components defined in .
  • All other values count once each.

Format definition:

jscomps-param = "JSCOMPS" "=" DQUOTE [jscomps-entry-sep ] ";" jscomps-entrylist DQUOTE jscomps-entrylist = jscomps-entry *(";" jscomps-entry) jscomps-entry = jscomps-entry-pos / jscomps-entry-sep jscomps-entry-pos = 1*DIGIT [ "," 1*DIGIT ] jscomps-entry-sep = "s" "," jscomps-entry-verb jscomps-entry-verb = *QSAFE-CHAR ; encode according to RFC 6868

Example(s):

The following example demonstrates the use of positional entries for the name "Jane Doe". The given name is ordered before the surname. No secondary index is required for either positional because both are zero. Example of a Secondary Positional Index "name": { "components": [ { "kind": "given", "value": "Jane" }, { "kind": "surname", "value": "Doe" } ], "isOrdered": true } N;JSCOMPS=";1;0":Doe;Jane;;;;;; FN;DERIVED=TRUE:Jane Doe The following example demonstrates a secondary positional index. The "Jr." generation marker only counts once because it occurs in both the designated generation component and the backwards-compatible honorific suffixes component. Example of Positional Entries "name": { "components": [ { "kind": "given", "value": "John" }, { "kind": "given2", "value": "Philip" }, { "kind": "given2", "value": "Paul" }, { "kind": "surname", "value": "Stevenson" }, { "kind": "generation", "value": "Jr." }, { "kind": "credential", "value": "M.D." } ], "isOrdered": true } N;JSCOMPS=";1;2;2,1;0;6;4,1": Stevenson;John;Philip,Paul;;Jr.,M.D.;;Jr. The following example demonstrates the use of separator entries for the (shortened for brevity) address "54321 Oak St, Reston". The first entry defines the default separator to be ", ". The second and fourth positional entries are separated with the separator value " ". For backwards compatibility, the street address component of the ADR property contains both the street number and name, but it is not referred to in the JSCOMPS parameter and does not contribute to the count of values. Example of Separator Entries "addresses": { "a1": { "components": [ { "kind": "number", "value": "54321" }, { "kind": "separator", "value": " " }, { "kind": "name", "value": "Oak St" }, { "kind": "locality", "value": "Reston" } ], "defaultSeparator": ", ", "isOrdered": true } } ADR;JSCOMPS="s,\, ;11;s, ;10;3": ;;54321 Oak St;Reston;;;;;;;Oak St;54321;;;;;;

Parameter name:

JSPTR

Purpose:

This parameter is set on a JSPROP property. Its value is a JSON pointer that points to the JSContact property that has the value of the JSPROP property.

Description:

This parameter has a single value that MUST be a valid JSON pointer as defined in . Note that the value MUST be quoted according to the "param-value" ABNF in .

Format definition:

jsptr-param = "JSPTR" "=" param-value ; also see param-value in RFC 6350, Section 3.3

Example(s):

This illustrates a simple example. For further examples, see . JSPROP;JSPTR="example.com:foo":"bar"

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4