58
•
The implementation should provide access to all available actual PIM lists for the
EventList list type.
•
At least the following Event fields should be supported : SUMMARY, UID, END,
START, ALARM.
•
At least the following repeat rules fields should be supported: FREQUENCY,
DAY_IN_WEEK, WEEK_IN_MONTH, DAY_IN_MONTH.
•
At least one attribute should be supported: ATTR_NONE
To Do List
The To Do database contains entries to tasks that must be executed on determined data
and times.
File Connection API
The primary goal of the FileConnection API is to provide access to file systems on devices
and/or mounted removable memory cards supported by Motorola devices.
Requirements
File Connection API requirements will be replaced with the requirements below.
•
The implementation should provide a security model for accessing the
FileConnection APIs as defined in JSR-75.
•
File Connection API should be accessible to manufacturer and operator domain
MIDlets subject to security restrictions.
•
Connection API should prohibit the modification or removing the files and
directories marked with the system attribute.
•
Call to System.getProperty with key microedition.io.file.FileConnection.version
should return the implementation version number starting with 1.0.
Files read/write permissions should be supported by the device’s native system:
•
javax.microedition.io.Connector.file.read
- should enable reading from the file
system (hereinafter just “read permission”).
•
javax.microedition.io.Connector.file.write
- should enable writing to the file
system (hereinafter just “write permission”).
The “read permission” and “write permission” should be mapped to the function groups
“User Data Read Capability” and “User Data Write Capability” respectively. These two
groups and permissions are in the Table 18: