Found 2 records.
Status: Verified (1)
RFC 9554, "vCard Format Extensions for JSContact", May 2024
Source of RFC: calext (art)
Errata ID: 8652
Status: Verified
Type: Technical
Publication Format(s) : TEXT, PDF, HTML
Reported By: Robert Stepanek
Date Reported: 2025-11-21
Verifier Name: Orie Steele
Date Verified: 2025-12-03
Section 4.9 says:
Example(s):
SOCIALPROFILE;SERVICE-TYPE=Mastodon:https://example.com/@foo
It should say:
Example(s):
SOCIALPROFILE;SERVICE-TYPE="Mastodon":https://example.com/@foo
Notes:
The description of the SERVICE-TYPE parameter states that its value is case-sensitive. RFC 6350 allows case-sensitive, unquoted parameter values but its exemplifies the only case-sensitive parameter SORT-AS with a quoted parameter value. Doing so for the SERVICE-TYPE parameter too indicates to implementers to use quoted strings and is likely to improve interoperability.
Status: Reported (1)
RFC 9554, "vCard Format Extensions for JSContact", May 2024
Source of RFC: calext (art)
Errata ID: 8626
Status: Reported
Type: Technical
Publication Format(s) : HTML
Reported By: Robert Stepanek
Date Reported: 2025-11-03
Section 3.5 says:
Property parameters:
[...] In either case, it MUST NOT be assigned more than once.
Format definition:
socialpr-param = "VALUE=uri" / "VALUE=text" /
service-type-param / any-param
It should say:
Property parameters:
[...] In either case, it MUST NOT be assigned more than once.
The USERNAME parameter MAY be assigned if the value type is URI.
Format definition:
socialpr-param = "VALUE=uri" / "VALUE=text" /
service-type-param / username-param /
any-param
Notes:
This clarifies that the USERNAME parameter is likely to be set on the SOCIALPROFILE property. The USERNAME parameter definition in section 4.10 does explicitly describe this relation. The SOCIALPROFILE property definition should do, too.