📄 overview-summary.html
字号:
type value in N</td>
<td>4th name component in the semi-colon separated string
type value in N</td>
</tr>
<tr>
<td>NAME_SUFFIX</td>
<td>5th name component in the semi-colon separated string
type value in N</td>
<td>5th name component in the semi-colon separated string
type value in N</td>
</tr>
<tr>
<td>NICKNAME</td>
<td>NICKNAME</td>
<td>NICKNAME</td>
</tr>
<tr>
<td>NOTE</td>
<td>NOTE</td>
<td>NOTE</td>
</tr>
<tr>
<td>ORG</td>
<td>ORG</td>
<td>ORG</td>
</tr>
<tr>
<td>PHOTO</td>
<td>PHOTO (inline specification of photo)</td>
<td>PHOTO (inline specification of photo)</td>
</tr>
<tr>
<td>PHOTO_URL</td>
<td>PHOTO/VALUE=URL</td>
<td>PHOTO/VALUE=URL</td>
</tr>
<tr>
<td>PUBLIC_KEY</td>
<td>KEY (inline binary specification)</td>
<td>KEY</td>
</tr>
<tr>
<td>PUBLIC_KEY_STRING</td>
<td>KEY (default text string)</td>
<td>KEY</td>
</tr>
<tr>
<td>REVISION</td>
<td>REV</td>
<td>REV</td>
</tr>
<tr>
<td>TEL</td>
<td>TEL/VOICE</td>
<td>TEL/VOICE</td>
</tr>
<tr>
<td>TITLE</td>
<td>TITLE</td>
<td>TITLE</td>
</tr>
<tr>
<td>UID</td>
<td>UID</td>
<td>UID</td>
</tr>
<tr>
<td>URL</td>
<td>URL</td>
<td>URL</td>
</tr>
<tr>
<td>ATTR_ASST</td>
<td><em>Implementation specific mapping</em></td>
<td><em>Implementation specific mapping</em></td>
</tr>
<tr>
<td>ATTR_AUTO</td>
<td>CAR property parameter</td>
<td>CAR property parameter</td>
</tr>
<tr>
<td>ATTR_FAX</td>
<td>FAX property parameter</td>
<td>FAX property parameter</td>
</tr>
<tr>
<td>ATTR_HOME</td>
<td>HOME property parameter</td>
<td>HOME property parameter</td>
</tr>
<tr>
<td>ATTR_MOBILE</td>
<td>CELL property parameter</td>
<td>CELL property parameter</td>
</tr>
<tr>
<td>ATTR_OTHER</td>
<td><em>Implementation specific mapping</em></td>
<td><em>Implementation specific mapping</em></td>
</tr>
<tr>
<td>ATTR_PAGER</td>
<td>PAGER property parameter</td>
<td>PAGER property parameter</td>
</tr>
<tr>
<td>ATTR_PREFERRED</td>
<td>PREF property parameter</td>
<td>PREF property parameter</td>
</tr>
<tr>
<td>ATTR_SMS</td>
<td>MSG property parameter</td>
<td>MSG property parameter</td>
</tr>
<tr>
<td>ATTR_WORK</td>
<td>WORK property parameter</td>
<td>WORK property parameter</td>
</tr>
<tr>
<td>ATTR_NONE</td>
<td><em>no mapping</em></td>
<td><em>no mapping</em></td>
</tr>
</table>
<blockquote>
<p><em>Table: Event Field Mappings</em></p>
</blockquote>
<table border="1" cellpadding="2">
<tr>
<th align="left">Event Field</th>
<th align="left">vCalendar 1.0 Property Name/Property
Parameters</th>
</tr>
<tr>
<td>ALARM</td>
<td>DALARM/DATE-TIME <i>(implementations may also
additionally set AALARM in concert with this property)</i></td>
</tr>
<tr>
<td>CLASS</td>
<td>CLASS</td>
</tr>
<tr>
<td>END</td>
<td>DTEND</td>
</tr>
<tr>
<td>LOCATION</td>
<td>LOCATION</td>
</tr>
<tr>
<td>NOTE</td>
<td>DESCRIPTION</td>
</tr>
<tr>
<td>REVISION</td>
<td>LAST-MODIFIED</td>
</tr>
<tr>
<td>START</td>
<td>DTSTART</td>
</tr>
<tr>
<td>SUMMARY</td>
<td>SUMMARY</td>
</tr>
<tr>
<td>UID</td>
<td>UID</td>
</tr>
</table>
<blockquote>
<p><em>Table: ToDo Field Mappings</em></p>
</blockquote>
<table border="1" cellpadding="2">
<tr>
<th align="left">ToDo Field</th>
<th align="left">vCalendar 1.0 Property Name/Property
Parameters</th>
</tr>
<tr>
<td>CLASS</td>
<td>CLASS</td>
</tr>
<tr>
<td>COMPLETION_DATE</td>
<td>COMPLETED</td>
</tr>
<tr>
<td>COMPLETED</td>
<td>COMPLETED (presence of field indicates completed is
true)</td>
</tr>
<tr>
<td>DUE</td>
<td>DUE</td>
</tr>
<tr>
<td>NOTE</td>
<td>DESCRIPTION</td>
</tr>
<tr>
<td>PRIORITY</td>
<td>PRIORITY</td>
</tr>
<tr>
<td>REVISION</td>
<td>LAST-MODIFIED</td>
</tr>
<tr>
<td>SUMMARY</td>
<td>SUMMARY</td>
</tr>
<tr>
<td>UID</td>
<td>UID</td>
</tr>
</table>
<p> </p>
<ul>
<li><strong>Serial Data Format Specification:</strong> The
strings used for the support serial data formats returned
from <code>PIM.contactSerialFormats()</code>, <code>PIM.eventSerialFormats()</code>,
and <code>PIM.toDoSerialFormats()</code> must follow a
consistent naming convention. The naming convention is
the common name of the data format in all capital
letters, followed by a slash ("/") followed by
the version number of the data format. For example,
"VCARD/2.1", "VCARD/3.0" and
"VCALENDAR/1.0". The formats required by this
spec and/or any formats required by an including profile
must be returned first in the string arrays returned from
the aforementioned methods (i.e. "VCARD/2.1"
must be the first item in the array returned from <code>PIM.contactSerialFormats()</code>
and "VCALENDAR/1.0" must be the first item in
the arrays returned from <code>PIM.eventSerialFormats()</code>
and <code>PIM.toDoSerialFormats()</code>. The following
table outlines the naming convention for some current
well known PIM protocols.</li>
</ul>
<table border="1">
<tr>
<th align="left">PIM Data Format</th>
<th align="left">PIM API String</th>
</tr>
<tr>
<td>vCard 2.1(<a
href="http://www.imc.org/pdi/vcard-21.txt">http://www.imc.org/pdi/vcard-21.txt</a>)</td>
<td>VCARD/2.1</td>
</tr>
<tr>
<td>vCard 3.0 (<a
href="http://www.ietf.org/rfc/rfc2426.txt">http://www.ietf.org/rfc/rfc2426.txt</a>)</td>
<td>VCARD/3.0</td>
</tr>
<tr>
<td>vCalendar 1.0 (<a
href="http://www.imc.org/pdi/vcal-10.txt">http://www.imc.org/pdi/vcal-10.txt</a>)</td>
<td>VCALENDAR/1.0</td>
</tr>
<tr>
<td>iCalendar (a.k.a. VCALENDAR 2.0) (<a
href="http://www.ietf.org/rfc/rfc2445.txt">http://www.ietf.org/rfc/rfc2445.txt</a>)</td>
<td>VCALENDAR/2.0</td>
</tr>
</table>
<ul>
<li><strong>Ordering of Fields Lists</strong>: It is
recommended (but not required) that implementations
return the fields from the method <code>PIMList.getSupportedFields()</code>
in an order similar, if not identical, to the display
ordering of those same fields in any corresponding native
PIM application. This allows Java applications using the
PIM APIs to maintain a semblance of platform continuity
in their application (i.e. trying to maintain look and
feel of the platform's applications).</li>
</ul>
<P>
<P>
<HR>
<!-- ========== START OF NAVBAR ========== -->
<A NAME="navbar_bottom"><!-- --></A><TABLE BORDER="0" WIDTH="100%" CELLPADDING="1" CELLSPACING="0">
<TR>
<TD COLSPAN=3 BGCOLOR="#EEEEFF" CLASS="NavBarCell1">
<A NAME="navbar_bottom_firstrow"><!-- --></A><TABLE BORDER="0" CELLPADDING="0" CELLSPACING="3">
<TR ALIGN="center" VALIGN="top">
<TD BGCOLOR="#FFFFFF" CLASS="NavBarCell1Rev"> <FONT CLASS="NavBarFont1Rev"><B>Overview</B></FONT> </TD>
<TD BGCOLOR="#EEEEFF" CLASS="NavBarCell1"> <FONT CLASS="NavBarFont1">Package</FONT> </TD>
<TD BGCOLOR="#EEEEFF" CLASS="NavBarCell1"> <FONT CLASS="NavBarFont1">Class</FONT> </TD>
<TD BGCOLOR="#EEEEFF" CLASS="NavBarCell1"> <A HREF="javax/microedition/pim/package-tree.html"><FONT CLASS="NavBarFont1"><B>Tree</B></FONT></A> </TD>
<TD BGCOLOR="#EEEEFF" CLASS="NavBarCell1"> <A HREF="deprecated-list.html"><FONT CLASS="NavBarFont1"><B>Deprecated</B></FONT></A> </TD>
<TD BGCOLOR="#EEEEFF" CLASS="NavBarCell1"> <A HREF="index-all.html"><FONT CLASS="NavBarFont1"><B>Index</B></FONT></A> </TD>
<TD BGCOLOR="#EEEEFF" CLASS="NavBarCell1"> <A HREF="help-doc.html"><FONT CLASS="NavBarFont1"><B>Help</B></FONT></A> </TD>
</TR>
</TABLE>
</TD>
<TD ALIGN="right" VALIGN="top" ROWSPAN=3><EM>
Proposed Final Draft<br>Rev. 0.24</EM>
</TD>
</TR>
<TR>
<TD BGCOLOR="white" CLASS="NavBarCell2"><FONT SIZE="-2">
PREV
NEXT</FONT></TD>
<TD BGCOLOR="white" CLASS="NavBarCell2"><FONT SIZE="-2">
<A HREF="index.html" TARGET="_top"><B>FRAMES</B></A>
<A HREF="overview-summary.html" TARGET="_top"><B>NO FRAMES</B></A>
<SCRIPT> <!-- if(window==top) { document.writeln('<A HREF="allclasses-noframe.html" TARGET=""><B>All Classes</B></A>'); } //--></SCRIPT><NOSCRIPT><A HREF="allclasses-noframe.html" TARGET=""><B>All Classes</B></A></NOSCRIPT></FONT></TD>
</TR>
</TABLE>
<!-- =========== END OF NAVBAR =========== -->
<HR>
<font size=-1>Copyright © 2002-2003 PalmSource, Inc. All Rights Reserved.<br>Java is a trademark of Sun Microsystems, Inc.</font>
</BODY>
</HTML>
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -