WebAPI/AppDefinedTeleophony: Difference between revisions

WebAPI/AppDefinedTeleophony (view source)

590 bytes removed , 28 June 2013

Confirmed users

398

edits

@@ Line 28: / Line 28: @@
                  attribute DOMString         sex;
                  attribute DOMString         genderIdentity;
-                attribute ContactAppField[]  otherAddresses;
   };
+  interface ContactField : nsISupports
-  interface ContactAppField : ContactField
   {
-    attribute DOMString handler;  // the application/or activity name that can handle voice/video call and messaging.
+    attribute DOMString[] type;   // "home", "work", etc.
-    attribute DOMURI status;      // an status icon as an indication of the presence (online/offline) of the user and alike.
+    attribute DOMString   value;
+   attribute boolean     pref; // false = no pref, true = preferred (vCard3 TYPE:PREF; vCard4 PREF:1)
   };
-Add an interface '''ContactAppField''' and add '''otherAddresses''' to '''ContactProperties'''
+* https://wiki.mozilla.org/ContactsAPI
-* '''handler''' and
+* http://tools.ietf.org/html/rfc4770
-* '''status''' fields
-With them, the contact app can invoke the correct APP to initiate a voice/video call or concall.
-For most IM now, '''status''' field can be used to show presence and status of a user.  The communication Apps update this variable with URIs of icons to indicate if a user is online or offline or other cases.  For handling changing of '''status''', the App should listen on ContactsManager::oncontactchange event.
 == Add a Friend ==