56
•
javax.microedition.pim.FieldEmptyException;
•
javax.microedition.pim.FieldFullException;
•
javax.microedition.pim.UnsupportedFieldException;
•
javax.microedition.pim.PIMItem;
•
javax.microedition.pim.Contact;
•
javax.microedition.pim.Event;
•
javax.microedition.pim.PIMList;
•
javax.microedition.pim.ContactList;
•
javax.microedition.pim.EventList.
The implementation should include support of the following packages, classes, and
interfaces with appropriate methods and fields of FileConnection API described in JSR-
75, related to
javax.microedition.io.file
:
•
javax.microedition.io.file.ConnectionClosedException;
•
javax.microedition.io.file.IllegalModeException;
•
javax.microedition.io.file.FileConnection;
Security Requirements Personal information read/write permissions should be supported
by the device’s native system:
•
javax.microedition.pim.ContactList.read
- should enable reading the contact
information available on the device (hereinafter just “contact read permission”)
•
javax.microedition.pim.ContactList.write
- should enable updating the contact
information available on the device (hereinafter just “contact write permission”)
•
javax.microedition.pim.ContactList.write
- should enable updating the contact
information available on the device (hereinafter just “contact write permission”)
•
javax.microedition.pim.ContactList.write
- shall enable updating the contact
information available on the device (hereinafter just “contact write permission”)
The PIM permissions should be mapped to the function groups “User Data Read
Capability” and “User Data Write Capability” depending on the read/write conditions.
These two groups and the permissions are in the following Table 17:
Function Group
Trusted Third
Party
Untrusted
Manufacturer
Operator
User Data Read
Capability
Always Ask, Ask
Once Per App,
Never Ask, No
Access
No Access
Full Access
Full Access
User Data Write
Capability
Always Ask, Ask
Once Per App,
Never Ask, No
No Access
Full Access
Full Access
