Re: CfC: publish FPWD of Contacts API; deadline Feb 8

Hello,

On Fri, Feb 1, 2013 at 8:20 AM, Tomoyuki SHIMIZU
<tomoyuki.labs@gmail.com> wrote:
> I would like to suggest an optional attribute of contactProperties for
> private extensions, which could be applied to arbitrary purposes.
>
> The vCard specification allows us to define private extensions[1], which are
> widely applied to various purposes[2].

This is a good suggestion.

In addition, Editors, could you please consider the following:
- change the ContactRequest so that instead of an array of objects it
returns an iterator (like it's done in Mozilla/Telefonica Messaging
API), or add the iterator functionality to the ContactRequest object
(similarly how PendingRequest is done in the Intel Messaging
proposal).

- did you consider handling transient fields too (for instance
presence information)? Transient fields are not saved to a database,
but are runtime information gathered and available to applications
about contacts. Since ContactProperties already has an 'impp'
property, would it make sense to add a 'presence' property to support
presence functionality? It could be an object like this:

interface ContactPresence {
     attribute DOMString status; // "available", "busy", ...
     attribute DOMString message; // status message e.g. "having lunch"
     readonly attribute DOMString icon;
}

Of course all of these can be handled later and are not objections
against the CfC status.

Best regards,
Zoltan

Received on Friday, 1 February 2013 09:29:44 UTC