Fwd: Re: [NEW KEP] KEP #17: Kolab XML Format 3.0

Christian Mollekopf mollekopf at kolabsys.com
Fri Dec 16 09:55:31 CET 2011


Forgot to cc the list

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

Subject: Re: [NEW KEP] KEP #17: Kolab XML Format 3.0
Date: Friday 16 December 2011, 09.33:24
From: Christian Mollekopf <mollekopf at kolabsys.com>
To: thomas at koch.ro

On Thursday 15 December 2011 17.04:54 Thomas Koch wrote:
> Christian Mollekopf:
> > A first draft of a KEP which rebases the whole Kolab XML Format on the
> > xCal
> > & xCard RFCs resulting in the Kolab XML Format 3.0 specification, has been
> > released.
> > 
> >         KEP 17: Kolab XML Format 3.0
> >         http://wiki.kolab.org/User:Mollekopf/Drafts/KEP:17
> 
> Hi Christian,
> 
> I really like the approach to keep compatibility to the RFCs and only add
> additional constraints.
> I'm trying to read through the KEP, but it's a lot of material and also not
> so easy to understand what is described where.
> It seems, that the KEP repeats a lot of information already present in the
> RFCs, only expressing them in RelaxNG. I'm not sure whether this is a good
> idea. Couldn't the KEP be made much shorter by referring as much as possible
> to the RFCs? I got the impression that the RFCs are easier to read and
> grasp then the KEP.
> 

Hi Thomas,

I realize it's fairly complicated and it was already difficult to give it some 
sort of reasonable structure. Especially for values which share semantics 
among different object types, but use a different representation internally.

The best way to go IMO is starting at the object of interest and then going 
to the properties through the provided links.

All the RelaxNG parts are definitely needed, as we're using a subset and this 
should be clearer than defining "according to rfc section.... but you may not 
use property X and Y".

Otherwise there is *some* repetition, so the document can be used normally as 
standalone specification, referring to the rfcs where necessary and for further 
background information. I don't think that this can be improved with more 
referencing.

> It would also help to see some example XML files. :-)
> 

Yeah, I know, I should make some examples. Times to short! ;-)

Thanks for your input,
Christian

> Regards,
> 
> Thomas Koch, http://www.koch.ro
> 
> _______________________________________________
> Kolab-format mailing list
> Kolab-format at kolab.org
> https://kolab.org/mailman/listinfo/kolab-format
-----------------------------------------
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.kolab.org/pipermail/format/attachments/20111216/59fba489/attachment.sig>


More information about the format mailing list