Multiple values in different content lines
"Germán M. Rivera" <[email protected]> Fri, 12 Nov 2004 16:22:54 +0100
| Newsgroups | gmane.ietf.vcard |
|---|---|
| Message-ID | <000301c4c8cb$7f799fd0$9f04048a@woody> |
This is a multi-part message in MIME format.
------=_NextPart_000_0004_01C4C8D3.E13F8E70
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Dear all,
=20
Could anyone please tell me if all (or which of) the
properties can be repeated in multiple lines of a vCard 3.0 object? E.g.
Is it possible to have multiple N properties?
=20
RFC 2425 states that:
=20
Each attribute defined in the text/directory body MAY have multiple
values, if allowed in the definition of the profile in which the
attribute is used. The general rule for encoding multi-valued items
is to simply create a new content line for each value (including the
type name). However, it should be noted that some value types
support encoding multiple values in a single content line by
separating the values with a comma ",".
=20
However, RFC 2426, which defines the vCard profile, does not
say anything in favour or against multiple values in different content
lines. It does allow multiple values separated with a comma for some
types (NICKNAME, for example). Properties like TEL and ADR can be
repeated with different TYPE parameters, as can be seen in the examples,
but could they be repeated with the same TYPE parameter? (In order to
describe to different work phones, for example) And what about the rest
of the properties?
=20
Thank you very much in advance.
Best regards,
Germ=E1n
------=_NextPart_000_0004_01C4C8D3.E13F8E70
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns=3D"http://www.w3.org/TR/REC-html40">
<head>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<meta name=3DProgId content=3DWord.Document>
<meta name=3DGenerator content=3D"Microsoft Word 10">
<meta name=3DOriginator content=3D"Microsoft Word 10">
<link rel=3DFile-List href=3D"cid:[email protected]">
<!--[if gte mso 9]><xml>
<o:OfficeDocumentSettings>
<o:DoNotRelyOnCSS/>
</o:OfficeDocumentSettings>
</xml><![endif]--><!--[if gte mso 9]><xml>
<w:WordDocument>
<w:SpellingState>Clean</w:SpellingState>
<w:GrammarState>Clean</w:GrammarState>
<w:DocumentKind>DocumentEmail</w:DocumentKind>
<w:HyphenationZone>21</w:HyphenationZone>
<w:EnvelopeVis/>
<w:Compatibility>
<w:BreakWrappedTables/>
<w:SnapToGridInCell/>
<w:WrapTextWithPunct/>
<w:UseAsianBreakRules/>
<w:UseFELayout/>
</w:Compatibility>
<w:BrowserLevel>MicrosoftInternetExplorer4</w:BrowserLevel>
</w:WordDocument>
</xml><![endif]-->
<style>
<!--
/* Font Definitions */
@font-face
{font-family:SimSun;
panose-1:2 1 6 0 3 1 1 1 1 1;
mso-font-alt:\5B8B\4F53;
mso-font-charset:134;
mso-generic-font-family:auto;
mso-font-pitch:variable;
mso-font-signature:3 135135232 16 0 262145 0;}
@font-face
{font-family:"\@SimSun";
panose-1:2 1 6 0 3 1 1 1 1 1;
mso-font-charset:134;
mso-generic-font-family:auto;
mso-font-pitch:variable;
mso-font-signature:3 135135232 16 0 262145 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{mso-style-parent:"";
margin:0cm;
margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:12.0pt;
font-family:"Times New Roman";
mso-fareast-font-family:SimSun;}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;
text-underline:single;}
a:visited, span.MsoHyperlinkFollowed
{color:purple;
text-decoration:underline;
text-underline:single;}
pre
{margin:0cm;
margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:10.0pt;
font-family:"Courier New";
mso-fareast-font-family:SimSun;
color:black;}
span.EstiloCorreo17
{mso-style-type:personal-compose;
mso-style-noshow:yes;
mso-ansi-font-size:10.0pt;
mso-bidi-font-size:10.0pt;
font-family:Arial;
mso-ascii-font-family:Arial;
mso-hansi-font-family:Arial;
mso-bidi-font-family:Arial;
color:windowtext;}
span.SpellE
{mso-style-name:"";
mso-spl-e:yes;}
span.GramE
{mso-style-name:"";
mso-gram-e:yes;}
@page Section1
{size:595.3pt 841.9pt;
margin:70.85pt 3.0cm 70.85pt 3.0cm;
mso-header-margin:35.4pt;
mso-footer-margin:35.4pt;
mso-paper-source:0;}
div.Section1
{page:Section1;}
-->
</style>
<!--[if gte mso 10]>
<style>
/* Style Definitions */=20
table.MsoNormalTable
{mso-style-name:"Tabla normal";
mso-tstyle-rowband-size:0;
mso-tstyle-colband-size:0;
mso-style-noshow:yes;
mso-style-parent:"";
mso-padding-alt:0cm 5.4pt 0cm 5.4pt;
mso-para-margin:0cm;
mso-para-margin-bottom:.0001pt;
mso-pagination:widow-orphan;
font-size:10.0pt;
font-family:"Times New Roman";}
</style>
<![endif]-->
</head>
<body lang=3DES link=3Dblue vlink=3Dpurple =
style=3D'tab-interval:35.4pt'>
<div class=3DSection1>
<p class=3DMsoNormal><span class=3DSpellE><font size=3D2 =
face=3DArial><span
style=3D'font-size:10.0pt;font-family:Arial'>Dear</span></font></span><fo=
nt
size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;font-family:Arial'> <span
class=3DSpellE>all</span>,<o:p></o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><o:p> </o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3DArial><span =
style=3D'font-size:10.0pt;
font-family:Arial'><span =
style=3D'mso-tab-count:1'>=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 =
</span></span></font><font
size=3D2 face=3DArial><span lang=3DEN-GB =
style=3D'font-size:10.0pt;font-family:Arial;
mso-ansi-language:EN-GB'>Could anyone please tell me if all (or which =
of) the properties
can be repeated in multiple lines of a vCard 3.0 object? E.g. <span
class=3DGramE>Is</span> it possible to have multiple N =
properties?<o:p></o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-GB =
style=3D'font-size:
10.0pt;font-family:Arial;mso-ansi-language:EN-GB'><o:p> </o:p></span=
></font></p>
<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-GB =
style=3D'font-size:
10.0pt;font-family:Arial;mso-ansi-language:EN-GB'>RFC 2425 states =
that:<o:p></o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-GB =
style=3D'font-size:
10.0pt;font-family:Arial;mso-ansi-language:EN-GB'><o:p> </o:p></span=
></font></p>
<pre><font size=3D2 color=3Dblack face=3D"Courier New"><span =
lang=3DEN-GB
style=3D'font-size:10.0pt;mso-ansi-language:EN-GB'><span =
style=3D'mso-spacerun:yes'>=A0=A0 </span>Each attribute defined in the =
text/directory body MAY have =
multiple<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3D"Courier New"><span lang=3DEN-GB =
style=3D'font-size:10.0pt;
mso-ansi-language:EN-GB'><span style=3D'mso-spacerun:yes'>=A0=A0 =
</span><span
class=3DGramE>values</span>, if allowed in the definition of the profile =
in which the<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3D"Courier New"><span lang=3DEN-GB =
style=3D'font-size:10.0pt;
mso-ansi-language:EN-GB'><span style=3D'mso-spacerun:yes'>=A0=A0 =
</span><span
class=3DGramE>attribute</span> is used. The general rule for encoding =
multi-valued items<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3D"Courier New"><span lang=3DEN-GB =
style=3D'font-size:10.0pt;
mso-ansi-language:EN-GB'><span style=3D'mso-spacerun:yes'>=A0=A0 =
</span><span
class=3DGramE>is</span> to simply create a new content line for each =
value (including the<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3D"Courier New"><span lang=3DEN-GB =
style=3D'font-size:10.0pt;
mso-ansi-language:EN-GB'><span style=3D'mso-spacerun:yes'>=A0=A0 =
</span><span
class=3DGramE>type</span> name).<span style=3D'mso-spacerun:yes'>=A0 =
</span>However, it should be noted that some value =
types<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3D"Courier New"><span lang=3DEN-GB =
style=3D'font-size:10.0pt;
mso-ansi-language:EN-GB'><span style=3D'mso-spacerun:yes'>=A0=A0 =
</span><span
class=3DGramE>support</span> encoding multiple values in a single =
content line by<o:p></o:p></span></font></pre><pre><font
size=3D2 color=3Dblack face=3D"Courier New"><span lang=3DEN-GB =
style=3D'font-size:10.0pt;
mso-ansi-language:EN-GB'><span style=3D'mso-spacerun:yes'>=A0=A0 =
</span><span
class=3DGramE>separating</span> the values with a comma =
",".<o:p></o:p></span></font></pre>
<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-GB =
style=3D'font-size:
10.0pt;font-family:Arial;mso-ansi-language:EN-GB'><o:p> </o:p></span=
></font></p>
<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-GB =
style=3D'font-size:
10.0pt;font-family:Arial;mso-ansi-language:EN-GB'><span =
style=3D'mso-tab-count:
1'>=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0=A0 </span>However, RFC 2426, which =
defines the vCard profile, does
not say anything in favour or against multiple values in different =
content
lines. It does allow multiple values separated with a comma for some =
types (NICKNAME,
for example). Properties like TEL and ADR can be repeated with different =
TYPE
parameters, as can be seen in the examples, but could they be repeated =
with the
same TYPE parameter? (In order to describe to different work phones, for
example) <span class=3DGramE>And what about the rest of the =
properties?</span><o:p></o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-GB =
style=3D'font-size:
10.0pt;font-family:Arial;mso-ansi-language:EN-GB'><o:p> </o:p></span=
></font></p>
<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-GB =
style=3D'font-size:
10.0pt;font-family:Arial;mso-ansi-language:EN-GB'>Thank you very much in
advance.<o:p></o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-GB =
style=3D'font-size:
10.0pt;font-family:Arial;mso-ansi-language:EN-GB'>Best =
regards,<o:p></o:p></span></font></p>
<p class=3DMsoNormal><font size=3D2 face=3DArial><span lang=3DEN-GB =
style=3D'font-size:
10.0pt;font-family:Arial;mso-ansi-language:EN-GB'>Germ=E1n<o:p></o:p></sp=
an></font></p>
</div>
</body>
</html>
------=_NextPart_000_0004_01C4C8D3.E13F8E70--