WebAPI/ContactsAPI: Difference between revisions

Jump to navigation Jump to search
incorporate geo components / flatten into ContactAddress and use same types as Geolocation API, incorporate gender components/flatted into Contact interface
(→‎Proposed API: add 'rev' per discussion with Gregor (need it for updated / merging semantics), also private "id" field for persisting)
(incorporate geo components / flatten into ContactAddress and use same types as Geolocation API, incorporate gender components/flatted into Contact interface)
Line 37: Line 37:
             attribute DOMString[]            tel;
             attribute DOMString[]            tel;
             attribute DOMString[]            org;
             attribute DOMString[]            org;
             attribute Date?                  bday;
             attribute Date                   bday;
             attribute DOMString[]            note;
             attribute DOMString[]            note;
             attribute DOMString[]            impp; /* per RFC 4770, included in vCard4 */
             attribute DOMString[]            impp; /* per RFC 4770, included in vCard4 */
             attribute Date?                  anniversary; /* new in vCard4 */
             attribute Date                   anniversary; /* new in vCard4 */
            attribute DOMString              sex; /* new in vCard4, gender sub-component 1 */
            attribute DOMstring              gender-identity'; /* new in vCard4, gender sub-comp 2 */
     readonly attribute Date                  rev;
     readonly attribute Date                  rev;
  /* readonly attribute DOMString              id; // private device-implementation-only field */
  /* readonly attribute DOMString              id; // private device-implementation-only field */
Line 51: Line 53:
             attribute DOMString              postalCode;
             attribute DOMString              postalCode;
             attribute DOMString              countryName;
             attribute DOMString              countryName;
            attribute double                latitude;
            attribute double                longitude;
            attribute double                altitude;
   };
   };


Line 63: Line 68:
* 'post-office-box' - NU, AB
* 'post-office-box' - NU, AB
* 'extended-address' - ER. in practice such data typically ends up in a long 'street-address'.
* 'extended-address' - ER. in practice such data typically ends up in a long 'street-address'.
* 'geo', 'latitude', 'longitude' - AB
* 'organization-name' and 'organization-unit' are rarely separately specified, users/publishers preferring to use the simple flat 'org' property instead.
* 'organization-name' and 'organization-unit' are rarely separately specified, users/publishers preferring to use the simple flat 'org' property instead.
* 'gender', 'sex', 'gender-identity' (from vCard4/hCard2 in particular) - AB
 
Added for B2G db (but not in any known existing device address books):
* ContactAddress 'geo' property components 'latitude', 'longitude' and additional 'altitude' from GeoLocation API
* Contact 'gender' property components 'sex', 'gender-identity' (from vCard4/hCard2 in particular)


== Considered changes ==
== Considered changes ==
canmove, Confirmed users
2,887

edits

Navigation menu