[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-pim
Subject:    [Kde-pim] Fwd: [discuss] Re: [dev-groupware] Re: [discuss] Re:
From:       CPH <cphennessy () openoffice ! org>
Date:       2003-08-06 21:42:42
[Download RAW message or body]

Something which may be of interest here. :)

----------  Forwarded Message  ----------

Subject: [discuss] Re: [dev-groupware] Re: [discuss] Re: [dev-groupware] Re: 
[discuss] Please redirect to groupware/glow mailing list
Date: Wednesday 06 August 2003 19:21
From: colm.smyth@sun.com
To: dev@groupware.openoffice.org
Cc: discuss@openoffice.org

Hi Edward,

I'm all in favour of open-source projects trying
to lead the way with standards.
It is certainly in line with the OOoGW charter
to try to progress standards where none exist
(we have started doing this in the
calendaring space, it would make
sense to do this also with
addressbook/contacts).
	
As regards getting a standard adopted, Netscape
(and more recently Mozilla) have been the leaders
in defining a succession of LDAP-related schema
proposals. Even though they have used the
'mozilla' prefix for attributes and the
schema itself, their schema is actually
pretty good, at least as a starting point.
We derived our current schema (using a code generator
hack I created) from a Mozilla source file just
a couple of months ago (not yet in CVS; the
Contacts feature will be added as a biggish
patch in time for 0.2 in about 3 weeks).

I favour getting the other open-source client
(kde-pim, Evolution and Chandler)
and server (OpenGroupware.org, Kolab, OpenLDAP)
as well as Mozilla involved in drafting
this. With that level of common agreement, it should
be straightforward to draft an RFC that would
have a good chance of also being adopted by
closed-source directories and groupware.

Here are my suggested criteria for a common
addressbook schema:
- names are not related to any given project
- suitable for international use
- attributes for new kinds of protocol, e.g. instant messaging,
   web-site, ...
- common scheme for handling multiple instances of
   a logical attribute (e.g. second or third email addresses)
- we need one logical addressbook schema with multiple incarnations
   for different underlying directory services or import/export formats
   (especially vCard)

Is this something you (and anyone else in the OOo/OOoGW
community) would like to get involved with? If it
is, I can help you setup a project under the groupware umbrella
and we can start some work on this.

Colm.

Edward Buck wrote:
> Hi Colm,
>
> colm.smyth@sun.com wrote:
>> Right now, we currently have one developer working
>> on a Contacts feature based around the OOo/Mozilla
>> addressbook framework, which uses the Mozilla AB schema
>> (which is largely based on the
>> standard LDAP inetOrgPerson schema).
>> The backend is complete, we just need a UI
>> to integrate it into Glow. Glow will
>> use an AttributeSet to contain the
>> attributes of a Contact, backed
>> by a ContactAttributeSetDefinition
>> to define the schema.
>
> Are you using the planned mozillaOrgPerson schema from bugzilla 116692
> or a different one?
>
> http://bugzilla.mozilla.org/show_bug.cgi?id=116692
>
> Interestingly, the new schema has yet to be implemented in Mozilla's
> address book code (AFAIK).  There's already a patch available but the
> integration of the code seems very slow going.
>
> Since the state of mozillaOrgPerson is still somewhat pending, I wonder
> if it makes sense for OOo to take more of a leadership role here and
> define an object class that incorporates the schema extensions needed by
> Glow AND Mozilla?  We could call it something neutral (not mozilla*),
> release a RFC and make it the defacto standard for LDAP schema extension
> for address books.
>
> The last thing LDAP needs is a plethora of schema extensions from
> various address book vendors.  It's great to see that we're leveraging
> work from the Mozilla project on this but the time is now to push an
> extended address book schema that multiple parties can utilize.
>
> Just some food for thought.
>
> Edward
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@groupware.openoffice.org
> For additional commands, e-mail: dev-help@groupware.openoffice.org

---------------------------------------------------------------------
To unsubscribe, e-mail: discuss-unsubscribe@openoffice.org
For additional commands, e-mail: discuss-help@openoffice.org

-------------------------------------------------------

-- 
CPH : openoffice.org volunteer

Please reply *only* to users@openoffice.org, as your responses will be
answered more quickly, more correctly, and shared to help more people.
_______________________________________________
kde-pim mailing list
kde-pim@mail.kde.org
http://mail.kde.org/mailman/listinfo/kde-pim
kde-pim home page at http://pim.kde.org/
[prev in list] [next in list] [prev in thread] [next in thread]