|WikiProject Telecommunications||(Rated Start-class)|
- 1 This entire talk page is off topic and should be removed - anon...
- 2 .vcf, Virtual Card Format
- 3 Device pairing?
- 4 vCards and wikiengine
- 5 programs
- 6 vCard Extensions
- 7 Full vCard 2.1 and/or 3.0 examples
- 8 Definition
- 9 vCard 1.0 and 2.0
- 10 xCard Removed or Explained Please
- 11 xCard text tag
- 12 Check marks
This entire talk page is off topic and should be removed - anon...
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 ;-)
- 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
tel;type=work,voice,msg,cell:+1 234 456-8901
.vcf, Virtual Card Format
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)
What's that? No explanation or link in the text. 22.214.171.124 00:26, 20 January 2007 (UTC)
Name: Number: +60138080970 Content: BEGIN:VCARD VERSION:2.1 N;CHARSET=UTF-8;ENCODING=QUOTED-PRINTABLE:=E8=80=81=E5=A9=86=E5=A4=A7=E4=BA=BA TEL:0138080970 END:VCARD I removed the vCard examples. They are my parents. Who put this there? Why? Please don't revert. I think it is supremely improper to put private information of unknown people on wikipedia. —Preceding unsigned comment added by 126.96.36.199 (talk) 00:33, 27 November 2007 (UTC)
- 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)
What vCard specification do the examples conform? The vCard 3.0 object MUST contain the FN, N and VERSION types [RFC 2426]. Some of these properties are also mandatory in vCard 2.1 ... but there may be another variant I'm not aware. (Rjgodoy 02:24, 22 February 2007 (UTC))
- 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).
If you think the example should refer to a fictional person, I do not oppose the change. The following example could be used instead:
BEGIN:VCARD FN:Mr. John Q. Public\, Esq. N:Public;John;Quinlan;Mr.;Esq. VERSION:3.0 END:VCARD
(It is from the RFC itself)
Rjgodoy 04:10, 16 June 2007 (UTC)
vCards and wikiengine
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).
- 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)
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)
- 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)
Full vCard 2.1 and/or 3.0 examples
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. --188.8.131.52 (talk) 18:00, 30 August 2008 (UTC)
- 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)
vCard 1.0 and 2.0
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)
- 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)
xCard Removed or Explained Please
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.
xCard text tag
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)
- 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)