Hi,
thx for the feedback.
Keep it your way - I am going to change PISI ...
Michael
Sebastian Krzyszkowiak wrote:
>
> All of that field names are compatible with opimd client apps I
> already wrote, except two little things: I have "E-mail", and "Home
> phone", "Work phone" etc. (with space and
On 8/9/09, Michael Pilgermann wrote:
> Well, for now I simly used the ones that were documented already and
> added fields I use for PISI - the outcome:
>
> Name
> Middlename
> Surname
> Email
> Phone / CellPhone
> HomePhone
> WorkPhone
> HomeStreet
> HomePostalCode
> HomeCity
> HomeCountry
> Home
Well, for now I simly used the ones that were documented already and
added fields I use for PISI - the outcome:
Name
Middlename
Surname
Email
Phone / CellPhone
HomePhone
WorkPhone
HomeStreet
HomePostalCode
HomeCity
HomeCountry
HomeState
Organisation
BusinessPostalCode
BusinessStreet
BusinessCity
B
On Thursday 06 August 2009, Sebastian Krzyszkowiak wrote:
> On 8/6/09, Al Johnson wrote:
> > On Thursday 06 August 2009, Michal Brzozowski wrote:
> >> 2009/8/5 Sebastian Krzyszkowiak
> >>
> >> > This way you
> >> > could have for instance voip:d...@shr.com ,
> >> > skype:dos or something else.
>
> I would vote for syncML structure, even opimd can hold a more flexible
> structure. But syncML is used in a lot of phones and this way i can be
> easier
> to integradte opimd in exisiting sync programms, perhaps on windows too.
>
> So syncML: +1
>
> Thomas
>
which would mean, that we are lo
Am Donnerstag 06 August 2009 09:09:58 schrieb Michael Pilgermann:
> Many thanks for all your input ...
> I had noticed already by going through the opimd code / db scheme that the
> selection of fields is dynamic.
>
> However, I think there is really a need to agree upon a common set of
> attribute
On 8/6/09, Al Johnson wrote:
> On Thursday 06 August 2009, Michal Brzozowski wrote:
>> 2009/8/5 Sebastian Krzyszkowiak
>>
>> > This way you
>> > could have for instance voip:d...@shr.com , skype:dos
>> > or something else.
>> > But of course it would be nice to discuss it with FSO guys.
>>
>> You
On Thursday 06 August 2009, Michal Brzozowski wrote:
> 2009/8/5 Sebastian Krzyszkowiak
>
> > This way you
> > could have for instance voip:d...@shr.com , skype:dos
> > or something else.
> > But of course it would be nice to discuss it with FSO guys.
>
> You suggest 'Peer' : 'tel:+xxx' or 'Peer' :
2009/8/5 Sebastian Krzyszkowiak
> This way you
> could have for instance voip:d...@shr.com , skype:dos
> or something else.
> But of course it would be nice to discuss it with FSO guys.
>
You suggest 'Peer' : 'tel:+xxx' or 'Peer' : 'voip:a...@bbb'.
How about putting the prefix in the attribute
look in which fields
they are using and how they structure the content. (http://www.imc.org/pdi/)
Mike
Original-Nachricht
> Datum: Wed, 5 Aug 2009 23:57:13 +0200
> Von: Sebastian Krzyszkowiak
> An: List for Openmoko community discussion
> Betreff: Re: OPIMD: List
On 8/5/09, Michal Brzozowski wrote:
> 2009/8/5 Sebastian Krzyszkowiak
>
>>
>> opimd supports every field - you can add to contact whatever you want.
>>
>
> Isn't the data supposed to be shared across different clients? If yes, then
> this should be part of the standard. Of course if I want to add
2009/8/5 Sebastian Krzyszkowiak
>
> opimd supports every field - you can add to contact whatever you want.
>
Isn't the data supposed to be shared across different clients? If yes, then
this should be part of the standard. Of course if I want to add dog-name and
cat-name then why not, but fields
On 8/5/09, Michael Pilgermann wrote:
> Hi,
> I am currently on the way of implementing OPIMD Contacts Domain
> integration in our PIM synchronization tool PISI.
> After having all the connectivity bits and pieces in place, it would be
> helpful to have an
>
> ** up-to-date list of attributes / fie
>Also when adding phone number that's good to prefix it with 'tel:',
>and 'mail:' with e-mails.
>
>Could someone add what I wrote here to wiki somewhere? :)
i added it into http://wiki.openmoko.org/wiki/Opimd
why would one want to prefix numbers and emails in fields and then
parse it away again?
Hi,
I am currently on the way of implementing OPIMD Contacts Domain
integration in our PIM synchronization tool PISI.
After having all the connectivity bits and pieces in place, it would be
helpful to have an
** up-to-date list of attributes / fields **
, which are supported in OPIMD (especially
15 matches
Mail list logo
