Motorola E680 Technical Manual - Page 60

Phonebook Access API

Get Motorola E680 - Smartphone - GSM PDF manuals and user guides View all Motorola E680 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 60 highlights

15 Phonebook Access API Phonebook Access API Using the Phonebook Access API, an application will be able to locate and update contact information on the handset. This contact information includes phone numbers, email addresses, and any other directory information related to individuals, groups, or organizations. The database used to store phonebook information will be unique and integrated for native phonebook, SIM card, and other applications using Phonebook API. The primary goal of the Phonebook Access API is to be simple and thin to fit in resourcelimited devices like the Motorola E680 handset. This API will specify a base storage class for all types of contacts items presented in the vCard specification (RFC2426 -vCard MIME Directory Profile - vCard 3.0 Specification). In addition, schema strings used in querying and storing contact information are those specified in the RFC2426 specification. The Phonebook Access API will perform the following functions: • Allow multiple phone numbers and email addresses for each contact • Store new entries • Retrieve entries • Edit existing entries • Delete entries • Check memory status • Order and sort contact parameters • Support standard schema strings Phonebook Access API Permissions Prior to a MIDlet accessing the Phonebook API for all Phonebook operations, the implementation will check the Phonebook permissions granted to the application. 60

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
60
15
Phonebook Access API
Phonebook Access API
Using the Phonebook Access API, an application will be able to locate and update contact
information on the handset. This contact information includes phone numbers, email
addresses, and any other directory information related to individuals, groups, or
organizations. The database used to store phonebook information will be unique and
integrated for native phonebook, SIM card, and other applications using Phonebook API.
The primary goal of the Phonebook Access API is to be simple and thin to fit in resource-
limited devices like the Motorola E680 handset. This API will specify a base storage class
for all types of contacts items presented in the vCard specification (RFC2426 –vCard
MIME Directory Profile – vCard 3.0 Specification). In addition, schema strings used in
querying and storing contact information are those specified in the RFC2426 specification.
The Phonebook Access API will perform the following functions:
•
Allow multiple phone numbers and email addresses for each contact
•
Store new entries
•
Retrieve entries
•
Edit existing entries
•
Delete entries
•
Check memory status
•
Order and sort contact parameters
•
Support standard schema strings
Phonebook Access API Permissions
Prior to a MIDlet accessing the Phonebook API for all Phonebook operations, the
implementation will check the Phonebook permissions granted to the application.