Talk:VCard

message: Hello! The information box specifies .vcf and ".v card" with a space as a file extension. Please link the source where this is actually done because it seems a bit odd. 188.230.129.18 (talk) 00:53, 27 October 2020 (UTC)
thread_title: .v card extension? source?

message: I have a request for enhancement to the editors of the vCard and similar standards:
I know many people who have two cellular phone numbers: one business and one private.
Many nations have more active cellular phones than inhabitants.
It is not possible to express this in vCard:
there is HOME and WORK for phone numbers but just CELL for both cases of cellular phone numbers.
So please introduce two types of cellular phone numbers.
(I don't require any intellectual properties for this idea, just do it, please ;-)
Gerd Castan
:It's already part of the standard.  There can be multiple 'type' parameters on a single 'type:value' statement, eg
tel;type=work,voice,msg:+1 313 747-4454
:or
tel;type=work,voice,msg,cell:+1 234 456-8901
:See RFC 2425, Section 8 Examples
:--Bob 22:51, 10 September 2006 (UTC)
thread_title:  Request for enhancement: Multiple cellphone types 

message: Shouldn't we mention either in the " Redirected from .vcf " or in the vCard article that .vcf stands for Virtual Card Format ?  —Preceding unsigned comment added by SvenAERTS (talk • contribs) 10:05, 21 November 2009 (UTC)
thread_title:  .vcf, Virtual Card Format 

message: What's that? No explanation or link in the text. 86.136.250.200 00:26, 20 January 2007 (UTC)
replies: text: Bluetooth#Pairing I just added the link. Good catch. Awg1010 (talk) 03:07, 31 May 2009 (UTC)

text: I have emailed the Oversight administrators on your behalf and FloNight deleted all the personal information from the history log. So it is no longer available even if someone looks at the edit history. (As a side note, we should include an example VCard with fake information.) Ariel. (talk) 00:34, 16 January 2008 (UTC)

text: In addition, version 3.0 specifies CELL as a value for TYPE (as a TEL parameter). I will make all the changes at once if no one thinks different (anyway, the current examples give a clue about what a vCard is...) —The preceding unsigned comment was added by Rjgodoy (talk • contribs) 05:21, 22 February 2007 (UTC)
thread_title:  Device pairing? 

message: What if wikiengine would be able to show vCards as html and make vCard reference link to entries that being showed. By pressing reference link contact information would then go into personal address book of  "what ever is your organizer software". —The preceding unsigned comment was added by Sami Kerola (talk • contribs) 16:20, 17 March 2007 (UTC)
thread_title:  vCards and wikiengine 

message: which programs besides outlook open vcard files?  —Preceding unsigned comment added by 72.208.96.44 (talk) 19:54, 20 November 2007 (UTC)
replies: text: While by no means an exhaustive list, some programs that can open them are listed here at fileinfo.net. —lensovet–talk – 08:34, 17 February 2008 (UTC)
thread_title:  Programs 

message: There have been a number of discussions in developer mailing lists about having a place to record vCard extensions that are in use - X- properties, so that reuse is possible.  It might be better as a separate page.
Dgc03052 (talk) 00:21, 15 May 2008 (UTC)
replies: text: Such record is part of the proposal for vCard 4.0 . However, this mechanism is intended for properties in the VND- (vendor) namespace. On the other hand, names that begin with X- are reserved for experimental use and not intended for released products. Rjgodoy (talk) 03:11, 15 May 2008 (UTC)
thread_title:  vCard Extensions 

message: Hi, I think it would make sense to bring a full example of a 2.1 or 3.0 vCard. Meaning valid and with all standard and maybe one or two X-* properties. --85.127.103.67 (talk) 18:00, 30 August 2008 (UTC)
thread_title:  Full vCard 2.1 and/or 3.0 examples 

message: Hmmmm. I thought a "V-card" was something entirely different.
Oh well. Jack Meihoffer (talk) 01:06, 25 January 2011 (UTC)
replies: text: Ha yeah... I was thinking the same thing... ONEder Boy (talk) 20:39, 21 September 2011 (UTC)

text: Haha, wow, that's awkward.  Someone had previously added a note saying that "V-card" has a different meaning, but I reverted their changes because I thought they were trolling. xD Mangst (talk) 01:45, 12 December 2012 (UTC)
thread_title:  Definition 

message: Can we point to vCard 1.0 and 2.0 specifications?  And, more important, where are they?  I didn't manage to find one of these two on the Net.  — Preceding unsigned comment added by Yevstifeyev (talk • contribs) 04:34, 17 September 2011 (UTC)
replies: text: There is no version 1.0 or 2.0.  The only versions are 2.1, 3.0, and 4.0.  Mangst (talk) 01:43, 12 December 2012 (UTC)
thread_title:  vCard 1.0 and 2.0 

message: I wanted to learn about the vCard standard and xCard is in here as though it's the latest in the progression of versions. Wanting to be cutting edge I started looking into it, but I found out that xCard is only a few months old, it's only a proposed standard (albeit maybe in the same way that HTML5 is still a draft), and I haven't really seen any evidence of people adopting it and using it. I'm usually decent at sniffing out documentation, but there isn't much beyond the IETF's proposal for the standard.
So, maybe it should be noted that xCard is new, or maybe it should get its own page?
Brendinooo (talk) 18:48, 22 December 2011 (UTC)
thread_title:  xCard removed or explained Please 

message: In the example given of a vCard, it has for example <fn><text>Forrest Gump</text></fn>. I don't see any reference to this <text> tag in the standard. Why is it there ? --Martvefun (talk) 21:05, 4 April 2012 (UTC)
replies: text: Never mind, I found this example --Martvefun (talk) 14:52, 7 April 2012 (UTC)

text: In xCard, a property's value is usually enclosed within an XML element which defines the data type of the value (there are a few exceptions to this rule, like the N and ADR properties).  Since the FN property accepts a free-form text value, its value is enclosed in a "<text>" element.  Another example is the URL property, which encloses its value in a "<uri>" element.  The idea is that parsers can look at these elements to better determine how to handle the data. Mangst (talk) 01:44, 12 December 2012 (UTC)
thread_title:  xCard text tag 

message: Can we come up with a method other than green and blue check marks for the table?  It's not easy to parse for the color blind.  Thanks! Plastikspork ―Œ(talk) 01:42, 13 March 2014 (UTC)
replies: text: I've replaced them with letters, is this better to read? -- Evilninja (talk) 02:01, 8 May 2015 (UTC)
thread_title:  Check marks 

message: I made the following changes to this edit:
* Made all vCard examples consistent so they store the same exact information. For example, the 3.0 example had a "Mr." prefix, but the 2.1 and 4.0 examples did not.
* Used consistent line folding.
* Quoted-printable folded lines should end with "=".
* Property values that are encoded in quoted-printable should have a CHARSET parameter to define the character set that the encoded string is in.
* Removed the parameters from the EMAIL property--they didn't really add anything important and just made things confusing IMO.  Note that the PREF parameter is used to specify the preferred method of contact amongst the same contact type (e.g. if you have 2 email addresses), not amongst all contact types.
* Added a PREF parameter to the work ADR property to demonstrate the different ways the versions handle this (i.e. "TYPE=PREF" (2.1 and 3.0) vs "PREF=1" (4.0)).
* Used the 3.0 values of the TEL property in the hCard example because hCard adheres to version 3.0.
--Mangst (talk) 14:50, 22 June 2016 (UTC)
thread_title:  Detailed list of changes in an edit 

message: Why are there examples of xCard, jCard, and hCard on this page? These are separate file formats or adaptations of vCard for special purposes. They are not "the new version of" vCard, which is alive and well as is. hCard even has its own WP page.
You wouldn't have examples of GIF and JPEG formats on the PNG page; this is no different.
I propose moving these examples of alternative formats off the vCard page and onto their own pages (creating them if necessary) and making sure there are links between them. Doug Ewell (talk) 21:40, 22 October 2016 (UTC)
replies: text: Make sense but is not the case: all are "vCard variants" (and must to preserve vCard VERSION attribute). The article need some explanation about "usefull intermediary formats", because TXT data is not usefull... --Krauss (talk) 23:36, 7 January 2017 (UTC)
thread_title:  Examples of formats other than vCard 

message: jCard is not a standard, and have strong rejection because not enconde all information into "first-class JSON objects".  Example:
* jCard format: [["version", {}, "text", "4.0"],["fn", {}, "text", "Forrest Gump"]]
* First-class JSON format: {"version":"4.0","fn":"Forrest Gump"}
To be encyclopedic, is interesting to show other "standards" for JSON vCard. --Krauss (talk) 23:32, 7 January 2017 (UTC)
thread_title:  jCard is not first-class JSON, article need to show alternatives 

message: The article confuses the terms "RFC", which stands for "Request For Comment", with "standard".  Some RFCs eventually evolve to become published standards by organizations such as IEEE, ISO, ANSI, etc., while others never progress beyond the RFC stage, so the two terms should be distinguished.  As far as I can tell, vCard is not a standard in any of its versions to-date, just a series of RFCs. — Quicksilver (Hydrargyrum)T @ 17:12, 25 April 2019 (UTC)
thread_title:  RFCs are not "standards" 

message: https://www.urbandictionary.com/define.php?term=V-Card says:
 V-Card Term used to define one's virginity. All virgins have a "V-Card" until they "cash it in" for sex.
AndrewA (talk) 14:13, 13 September 2020 (UTC)
thread_title:  Why does the page have a distinguish template for "Virginity"? 

message: On 29 April 2021‎, user "Smuckola" single-handedly deleted almost all the substantive content for this article with only the comment, "delete a mountain of wholesale unencyclopedic tome WP:RS WP:NOTMANUAL WP:NOTHOWTO WP:NOTDIR WP:ELNO WP:LINKFARM; as it stands, this article probably needs to be merged elsewhere."  
I profoundly disagree with this change.  It removed almost all technically interesting content and no longer serves to educate the reader about the various formats.  This one user wiped away almost all of the years of work spent on this article.  Perhaps it was a "principled" change, but it bordered on vandalism and was at odds with the actions of all previous maintainers of this article.
This stands in contrast to articles on JSON, XML, and RSS all of which have concrete examples.
: I agree that the examples were too lengthy, but I restored the properties table as it provides a good comparison between versions. A well crafted (small) example of the most recent vCard version (4) might be a useful addition, but I as I am unsure, I did not restore it. Nuretok (talk) 19:43, 30 September 2021 (UTC)
thread_title:  Restore massive deletion of long-standing useful content 

message: Many articles on vcards, including this one, are incomprehensible because of terminology. The various versions of vcard rfc's certainly don't help with this. Early versions of rfc's speak of "contentlines", "properties", "parametes" and "values". Latter versions, rfc 6350, seem to redefine these terms. For example 6350 seems to say "BEGIN:VCARD" is not a "contentline" consisting of the "property" BEGIN and "value" VCARD, As previously described in ABNF but is a unique token. Perhaps the terminolgy can be clarified here. 2601:18A:180:A5D0:3DB8:FF05:3A5D:4FD2 (talk) 02:50, 11 March 2022 (UTC)
thread_title:  Terminology 

message: I have to profoundly disagree with the assertion in "This article has multiple issues" that "The topic of this article may not meet Wikipedia's general notability guideline".
It is just the sort of reference that Wikipedia should include.
Can someone with the knowledge to do so please remove that?  BMJ-pdx (talk) 19:03, 21 June 2022 (UTC)
replies: text: I agree that this article meets the notability guideline, also considering that the page has been updated to include more general non-technical information since that issue was raised in April 2021, and your call has remained uncontested for two months. I have removed the template from the page. If anyone disagrees, please reply here so we can discuss this further to see what needs to be done concretely to fix issues on this page (and please also leave a message on my personal talk page, otherwise I might not get a notification. Thank you!) FWDekker (talk) 12:58, 18 August 2022 (UTC)
thread_title:  This article '''is''' "generally notable" 

message: Following reference https://datatracker.ietf.org/doc/html/rfc2426#section-3.1.5 the correct syntax for BDAY is of the form BDAY:1996-04-15 Ismael F. F. dos Santos (talk) 00:40, 2 May 2023 (UTC)
thread_title:  BDAY syntax 

message: Bat hindi ma log in acc ko ok naman ang password ko
Nirejohn123 po ang pangalan 2001:4454:406:3E00:2D57:7697:869A:6A7E (talk) 16:48, 22 June 2023 (UTC)
replies: text: Na hack bayan 2001:4454:406:3E00:2D57:7697:869A:6A7E (talk) 16:49, 22 June 2023 (UTC)
thread_title:  Boss